Making my first TrueNAS Build... 20TB x24

PK1048 · July 15, 2025, 9:02pm

What about it?

I have used it multiple times with no issues* as long as you match the type of aggregation on TrueNAS and the switch ports. My current home server has dual 10Gbe SFP+ cables ( 10 Gbps Direct Attach Copper Cable - Ubiquiti Store United States ) to an Ubiquiti ES-48-500w switch ( EdgeSwitch 48 PoE (500W) - Ubiquiti Store United States ). I have not had any issues.

*no issues: assumes no non-TrueNAS issues. At a previous employer we had dual fiber 10Gbe (SFP+) and every once in a while we would have a 30 second I/O outage on NFS going to VMs. Turns out it was a combination of a flaky fiber and the LAG timeout on the switch (set to default of 30 seconds), we replaced the flaky fiber and all was good.

scarbrtj · July 15, 2025, 9:50pm

Sorry… SAS link aggregation

1up · July 16, 2025, 12:07am

Welcome to the community. I’ve been using TrueNAS for nearly a decade now. As a fellow hobbyist myself, I wanted to help you save money so that you can collect more hard drives instead.

Cases
I think you may be better off in a proper NAS case rather than the Sliger CX4170A + Areca 12-bay towers. Sliger makes great cases. I have the Sliger S610 for gaming. But other manufactures make better NAS cases. These cases have ample cooling, significant HD mounting capacity, and some even offer bays for swappable HDs:

Rosewill Thor NAS ATX Tower (ATX) - link

Dark Rock Classico Storage Master ATX NAS Case - link

Fractal Design Node 804 (mATX) - link

I have the Node 804 for my TrueNas setup and I love it. The airflow is awesome and the built-in fan filters keep dust out. I have 8 HDs and 4 SSDs in that case.

PSU
I didn’t see any mention of power supply but I wanted to say, heat kills and heat + dust kill indefinitely. If you’re going to have Areca 12-bay SAS towers for your HDs, then I guess this is less of a concern since they have their own power and cooling. But if you’re going to keep HDs in the same box as the CPU/MB, make sure cooling is good and even better, get an energy efficient PSU.

Energy efficient PSUs will consume less energy (less wastage) and also generate less heat inside your chassis. This is awesome for longevity of HDs and other components. With Platinum and Titanium PSUs, you may not even feel any heat coming out of the back of the case.

Make sure you have enough power for your HD harem. You can calculate how much you need using PSU calculators online or just ask an AI.

SSDs
2x 2TB NVMEs for the TrueNAS OS is overkill. The OS doesn’t take more than 32-64GB of disk space…a 128GB SSD is fine. So is a 256 GB SSD. or 512 GB SSD.

What matters more is having two in a pool where one is mirrored (as others have said) and also the quality of SSD itself. For TrueNas purposes, SSDs with NAND are considered better and last longer.

I am not sure how many PCIE lanes your motherboar dhas (it appears to have a lot) but generally for TrueNAS OS, you dont need M2 nvme ssd speeds for the OS. SATA6 is plenty for the OS.

Having those 2TB SSDs for the VMs, in a pool, would be better. I’m not sure what your VM use case is, but I am running somewhere between 6-8 applications in VMs on my TrueNAS off of 256GB SSDs in a mirror pool and I am not really concerned about disk usage right now. Its barely dented.

L2Arc Cache
You mentioned you have a lot of media files. I do too and in my 10 years using TrueNAS an issue I encountered was how long it was taking some of my datasets to load their thumbnail images (it would make GoPro workflows a bit longer cause I wouldn’t be able to preview the files quickly). If you suspect you may run into this issue, look into L2Arc caching. Its basically a single m2 NVME SSD that gets designated as short term storage for files that get accessed a lot (like video files during a workflow). Having PCIE lanes to support the various caching mechanisms found in TrueNAS is important hence why you need to put the OS on one of those lanes.

GPU
Technically, you don’t GPU unless you desire transcoding for Plex or have some sort of graphical need. But to answer your question, yes, you will need GPU in order to install the OS. After installing the OS, you can remove the graphics card (and save on energy costs this way) since TrueNAS OS offers a web application for connecting to and administering it.

If you don’t have a graphics card, or would like to have one regardless, Nvidia’s workstation graphics like the T400 or P400 are recommended since they are lower power.

Cooling
Stick with traditional cooling. Its cheaper, just as good now, and safer for a 24/7 NAS unit.

AIO water coolers are great but in theory could leak…why risk expensive server grade components over water? BeQuiet (DarkRock), Noctua, and Zalman all make great coolers. If you want something more niche, consider Alpenfoehn as they are ze Germans.

That being said, welcome to TrueNAS and happy tinkering!

PK1048 · July 16, 2025, 1:14pm

I have not tried SAS link aggregation. Hurmmm, now I want to try, but that is my production box.

If you do, let us know how it works.

scarbrtj · July 26, 2025, 12:55am

Mobo’s came in. CPUs came in. Bought this case (CX4170i | Sliger) with the Asetek AIO cooler. Waiting on the Areca ARC 12 bay case. Waiting on a Broadcom 9400-16e. I’ll use (hotswap, in the Icy Dock 4-bay) SSDs mirrored with spares for OS. Will use NVMEs for apps.

scarbrtj · July 27, 2025, 8:22am

To install TrueNAS on the WRX80 motherboard from ASUS, you must:

Have a wired keyboard. A wireless keyboard will not work.
For TrueNAS to see SSDs attached to the motherboard’s SATA ports, make the following BIOS changes:
a) change resize bar to auto.
b) changed SR-IOV to enabled.
c) set IOMMU to enabled.

If you don’t change the BIOS, TrueNAS doesn’t have the right driver support for these SATA ports. ChatGPT solved this problem for me.

=================

sudo dmesg | grep -i ‘ahci|sata|error|fail’
[sudo] password for truenas_admin:
[ 1.609139] swapper/0: page allocation failure: order:12, mode:0xcc1(GFP_KERNEL|GFP_DMA), nodemask=(null),cpuset=/,mems_allowed=0
[ 1.642412] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 512
[ 1.642418] {1}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 1.642422] {1}[Hardware Error]: event severity: corrected
[ 1.642425] {1}[Hardware Error]: Error 0, type: corrected
[ 1.642429] {1}[Hardware Error]: fru_text: PcieError
[ 1.642432] {1}[Hardware Error]: section_type: PCIe error
[ 1.642435] {1}[Hardware Error]: port_type: 4, root port
[ 1.642438] {1}[Hardware Error]: version: 0.2
[ 1.642441] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.642445] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.642448] {1}[Hardware Error]: slot: 0
[ 1.642451] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.642453] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.642457] {1}[Hardware Error]: class_code: 060400
[ 1.642460] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.642464] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.642468] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.642472] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.642475] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.642479] {1}[Hardware Error]: Error 1, type: corrected
[ 1.642482] {1}[Hardware Error]: section_type: PCIe error
[ 1.642485] {1}[Hardware Error]: port_type: 4, root port
[ 1.642488] {1}[Hardware Error]: version: 0.2
[ 1.642491] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.642494] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.642497] {1}[Hardware Error]: slot: 0
[ 1.642500] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.642503] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.642506] {1}[Hardware Error]: class_code: 060400
[ 1.642509] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.642513] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.642517] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.642521] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.642524] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.642528] {1}[Hardware Error]: Error 2, type: corrected
[ 1.642531] {1}[Hardware Error]: section_type: PCIe error
[ 1.642534] {1}[Hardware Error]: port_type: 4, root port
[ 1.642537] {1}[Hardware Error]: version: 0.2
[ 1.642540] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.642543] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.642546] {1}[Hardware Error]: slot: 0
[ 1.642548] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.642551] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.642555] {1}[Hardware Error]: class_code: 060400
[ 1.642558] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.642561] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.642565] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.642569] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.642572] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.642576] {1}[Hardware Error]: Error 3, type: corrected
[ 1.642579] {1}[Hardware Error]: section_type: PCIe error
[ 1.642582] {1}[Hardware Error]: port_type: 4, root port
[ 1.642585] {1}[Hardware Error]: version: 0.2
[ 1.642588] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.642591] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.642594] {1}[Hardware Error]: slot: 0
[ 1.642597] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.642600] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.642603] {1}[Hardware Error]: class_code: 060400
[ 1.642606] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.642610] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.642613] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.642617] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.642620] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.642624] {1}[Hardware Error]: Error 4, type: corrected
[ 1.642627] {1}[Hardware Error]: section_type: PCIe error
[ 1.642630] {1}[Hardware Error]: port_type: 4, root port
[ 1.642633] {1}[Hardware Error]: version: 0.2
[ 1.642636] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.642639] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.642642] {1}[Hardware Error]: slot: 0
[ 1.642645] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.642648] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.642651] {1}[Hardware Error]: class_code: 060400
[ 1.642654] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.642658] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.642662] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.642666] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.642669] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.642673] {1}[Hardware Error]: Error 5, type: corrected
[ 1.642676] {1}[Hardware Error]: section_type: PCIe error
[ 1.642678] {1}[Hardware Error]: port_type: 4, root port
[ 1.642681] {1}[Hardware Error]: version: 0.2
[ 1.642684] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.642687] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.642690] {1}[Hardware Error]: slot: 0
[ 1.642693] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.642696] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.642699] {1}[Hardware Error]: class_code: 060400
[ 1.642702] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.642706] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.642710] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.642714] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.642717] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.642721] {1}[Hardware Error]: Error 6, type: corrected
[ 1.642724] {1}[Hardware Error]: section_type: PCIe error
[ 1.642727] {1}[Hardware Error]: port_type: 4, root port
[ 1.642730] {1}[Hardware Error]: version: 0.2
[ 1.642732] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.642735] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.642739] {1}[Hardware Error]: slot: 0
[ 1.642741] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.642744] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.642747] {1}[Hardware Error]: class_code: 060400
[ 1.642750] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.642754] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.642758] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.642762] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.642765] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.642769] {1}[Hardware Error]: Error 7, type: corrected
[ 1.642772] {1}[Hardware Error]: section_type: PCIe error
[ 1.642775] {1}[Hardware Error]: port_type: 4, root port
[ 1.642778] {1}[Hardware Error]: version: 0.2
[ 1.642780] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.642784] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.642787] {1}[Hardware Error]: slot: 0
[ 1.642789] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.642792] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.642795] {1}[Hardware Error]: class_code: 060400
[ 1.642798] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.642802] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.642806] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.642810] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.642813] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.642817] {1}[Hardware Error]: Error 8, type: corrected
[ 1.642820] {1}[Hardware Error]: section_type: PCIe error
[ 1.642823] {1}[Hardware Error]: port_type: 4, root port
[ 1.642826] {1}[Hardware Error]: version: 0.2
[ 1.642829] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.642832] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.642835] {1}[Hardware Error]: slot: 0
[ 1.642837] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.642840] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.642844] {1}[Hardware Error]: class_code: 060400
[ 1.642846] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.642850] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.642854] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.642858] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.642861] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.642865] {1}[Hardware Error]: Error 9, type: corrected
[ 1.642868] {1}[Hardware Error]: section_type: PCIe error
[ 1.642871] {1}[Hardware Error]: port_type: 4, root port
[ 1.642874] {1}[Hardware Error]: version: 0.2
[ 1.642877] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.642880] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.642883] {1}[Hardware Error]: slot: 0
[ 1.642886] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.642888] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.642892] {1}[Hardware Error]: class_code: 060400
[ 1.642895] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.642898] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.642902] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.642906] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.642909] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.642913] {1}[Hardware Error]: Error 10, type: corrected
[ 1.642916] {1}[Hardware Error]: section_type: PCIe error
[ 1.642919] {1}[Hardware Error]: port_type: 4, root port
[ 1.642922] {1}[Hardware Error]: version: 0.2
[ 1.642925] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.642928] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.642931] {1}[Hardware Error]: slot: 0
[ 1.642934] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.642937] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.642940] {1}[Hardware Error]: class_code: 060400
[ 1.642943] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.642947] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.642951] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.642954] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.642958] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.642962] {1}[Hardware Error]: Error 11, type: corrected
[ 1.642965] {1}[Hardware Error]: section_type: PCIe error
[ 1.642967] {1}[Hardware Error]: port_type: 4, root port
[ 1.642970] {1}[Hardware Error]: version: 0.2
[ 1.642973] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.642976] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.642980] {1}[Hardware Error]: slot: 0
[ 1.642982] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.642985] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.642988] {1}[Hardware Error]: class_code: 060400
[ 1.642991] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.642995] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.642999] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.643003] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.643006] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.643010] {1}[Hardware Error]: Error 12, type: corrected
[ 1.643013] {1}[Hardware Error]: section_type: PCIe error
[ 1.643016] {1}[Hardware Error]: port_type: 4, root port
[ 1.643019] {1}[Hardware Error]: version: 0.2
[ 1.643021] {1}[Hardware Error]: command: 0x0007, status: 0x0010
[ 1.643025] {1}[Hardware Error]: device_id: 0000:20:01.1
[ 1.643028] {1}[Hardware Error]: slot: 0
[ 1.643030] {1}[Hardware Error]: secondary_bus: 0x21
[ 1.643033] {1}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 1.643036] {1}[Hardware Error]: class_code: 060400
[ 1.643039] {1}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 1.643043] {1}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 1.643047] {1}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 1.643051] {1}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 1.643054] {1}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 1.724380] pci 0000:24:00.0: VF BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.724383] pci 0000:24:00.0: VF BAR 3 [mem size 0x00100000 64bit]: failed to assign
[ 1.724387] pci 0000:24:00.1: VF BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.724391] pci 0000:24:00.1: VF BAR 3 [mem size 0x00100000 64bit]: failed to assign
[ 1.724598] pci 0000:22:02.0: bridge window [mem size 0x00500000]: failed to assign
[ 1.724617] pci 0000:24:00.0: ROM [mem size 0x00080000 pref]: failed to assign
[ 1.724620] pci 0000:24:00.1: ROM [mem size 0x00080000 pref]: failed to assign
[ 1.724623] pci 0000:24:00.0: VF BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.724626] pci 0000:24:00.0: VF BAR 3 [mem size 0x00100000 64bit]: failed to assign
[ 1.724629] pci 0000:24:00.1: VF BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.724632] pci 0000:24:00.1: VF BAR 3 [mem size 0x00100000 64bit]: failed to assign
[ 1.724890] pci 0000:21:00.0: bridge window [mem size 0x04c00000]: failed to assign
[ 1.724894] pci 0000:22:06.0: bridge window [mem size 0x04100000]: failed to assign
[ 1.724897] pci 0000:22:01.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.724900] pci 0000:22:02.0: bridge window [mem size 0x00500000]: failed to assign
[ 1.724903] pci 0000:22:04.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.724906] pci 0000:22:05.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.724909] pci 0000:22:08.0: bridge window [mem size 0x00200000]: failed to assign
[ 1.724912] pci 0000:22:0a.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.724915] pci 0000:23:00.0: BAR 0 [mem size 0x00008000 64bit]: failed to assign
[ 1.724932] pci 0000:24:00.0: VF BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.724935] pci 0000:24:00.0: VF BAR 3 [mem size 0x00100000 64bit]: failed to assign
[ 1.724938] pci 0000:24:00.1: VF BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.724941] pci 0000:24:00.1: VF BAR 3 [mem size 0x00100000 64bit]: failed to assign
[ 1.724959] pci 0000:25:00.0: BAR 5 [mem size 0x00000200]: failed to assign
[ 1.724978] pci 0000:26:00.0: BAR 5 [mem size 0x00000200]: failed to assign
[ 1.724998] pci 0000:27:00.0: bridge window [mem size 0x04100000]: failed to assign
[ 1.725001] pci 0000:28:00.0: BAR 0 [mem size 0x04000000]: failed to assign
[ 1.725004] pci 0000:28:00.0: BAR 1 [mem size 0x00020000]: failed to assign
[ 1.725043] pci 0000:29:00.1: BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.725047] pci 0000:29:00.3: BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.725063] pci 0000:2a:00.0: BAR 5 [mem size 0x00000800]: failed to assign
[ 1.725154] pci 0000:20:01.1: bridge window [mem size 0x07000000]: failed to assign
[ 1.725157] pci 0000:21:00.0: bridge window [mem size 0x07000000]: failed to assign
[ 1.725161] pci 0000:22:06.0: bridge window [mem size 0x06000000]: failed to assign
[ 1.725164] pci 0000:22:01.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.725167] pci 0000:22:02.0: bridge window [mem size 0x00500000]: failed to assign
[ 1.725170] pci 0000:22:04.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.725172] pci 0000:22:05.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.725175] pci 0000:22:08.0: bridge window [mem size 0x00200000]: failed to assign
[ 1.725178] pci 0000:22:0a.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.725182] pci 0000:23:00.0: BAR 0 [mem size 0x00008000 64bit]: failed to assign
[ 1.725199] pci 0000:24:00.0: VF BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.725202] pci 0000:24:00.0: VF BAR 3 [mem size 0x00100000 64bit]: failed to assign
[ 1.725205] pci 0000:24:00.1: VF BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.725208] pci 0000:24:00.1: VF BAR 3 [mem size 0x00100000 64bit]: failed to assign
[ 1.725226] pci 0000:25:00.0: BAR 5 [mem size 0x00000200]: failed to assign
[ 1.725245] pci 0000:26:00.0: BAR 5 [mem size 0x00000200]: failed to assign
[ 1.725264] pci 0000:27:00.0: bridge window [mem size 0x06000000]: failed to assign
[ 1.725267] pci 0000:28:00.0: BAR 0 [mem size 0x04000000]: failed to assign
[ 1.725270] pci 0000:28:00.0: BAR 1 [mem size 0x00020000]: failed to assign
[ 1.725310] pci 0000:29:00.1: BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.725313] pci 0000:29:00.3: BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.725329] pci 0000:2a:00.0: BAR 5 [mem size 0x00000800]: failed to assign
[ 1.725435] pci 0000:20:01.1: bridge window [mem size 0x07000000]: failed to assign
[ 1.725443] pci 0000:20:01.1: bridge window [mem size 0x07000000]: failed to assign
[ 1.725452] pci 0000:21:00.0: bridge window [mem size 0x07000000]: failed to assign
[ 1.725455] pci 0000:21:00.0: bridge window [mem size 0x07000000]: failed to assign
[ 1.725459] pci 0000:22:06.0: bridge window [mem size 0x06000000]: failed to assign
[ 1.725462] pci 0000:22:01.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.725465] pci 0000:22:02.0: bridge window [mem size 0x00500000]: failed to assign
[ 1.725468] pci 0000:22:04.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.725471] pci 0000:22:05.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.725474] pci 0000:22:08.0: bridge window [mem size 0x00200000]: failed to assign
[ 1.725477] pci 0000:22:0a.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.725480] pci 0000:22:06.0: bridge window [mem size 0x06000000]: failed to assign
[ 1.725483] pci 0000:22:01.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.725486] pci 0000:22:02.0: bridge window [mem size 0x00500000]: failed to assign
[ 1.725489] pci 0000:22:04.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.725492] pci 0000:22:05.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.725496] pci 0000:22:08.0: bridge window [mem size 0x00200000]: failed to assign
[ 1.725499] pci 0000:22:0a.0: bridge window [mem size 0x00100000]: failed to assign
[ 1.725502] pci 0000:23:00.0: BAR 0 [mem size 0x00008000 64bit]: failed to assign
[ 1.725505] pci 0000:23:00.0: BAR 0 [mem size 0x00008000 64bit]: failed to assign
[ 1.725522] pci 0000:24:00.0: VF BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.725525] pci 0000:24:00.0: VF BAR 3 [mem size 0x00100000 64bit]: failed to assign
[ 1.725528] pci 0000:24:00.1: VF BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.725531] pci 0000:24:00.1: VF BAR 3 [mem size 0x00100000 64bit]: failed to assign
[ 1.725535] pci 0000:24:00.1: VF BAR 3 [mem size 0x00100000 64bit]: failed to assign
[ 1.725538] pci 0000:24:00.1: VF BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.725541] pci 0000:24:00.0: VF BAR 3 [mem size 0x00100000 64bit]: failed to assign
[ 1.725544] pci 0000:24:00.0: VF BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.725562] pci 0000:25:00.0: BAR 5 [mem size 0x00000200]: failed to assign
[ 1.725581] pci 0000:26:00.0: BAR 5 [mem size 0x00000200]: failed to assign
[ 1.725600] pci 0000:27:00.0: bridge window [mem size 0x06000000]: failed to assign
[ 1.725603] pci 0000:28:00.0: BAR 0 [mem size 0x04000000]: failed to assign
[ 1.725606] pci 0000:28:00.0: BAR 1 [mem size 0x00020000]: failed to assign
[ 1.725646] pci 0000:29:00.1: BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.725649] pci 0000:29:00.3: BAR 0 [mem size 0x00100000 64bit]: failed to assign
[ 1.725665] pci 0000:2a:00.0: BAR 5 [mem size 0x00000800]: failed to assign
[ 2.060750] ERST: Error Record Serialization Table (ERST) support is initialized.
[ 2.706303] RAS: Correctable Errors collector initialized.
[ 2.878298] fjes: module verification failed: signature and/or required key missing - tainting kernel
[ 2.900983] xhci_hcd 0000:23:00.0: init 0000:23:00.0 fail, -16
[ 2.901002] xhci_hcd 0000:23:00.0: probe with driver xhci_hcd failed with error -16
[ 2.901145] xhci_hcd 0000:29:00.1: init 0000:29:00.1 fail, -16
[ 2.901162] xhci_hcd 0000:29:00.1: probe with driver xhci_hcd failed with error -16
[ 2.901231] xhci_hcd 0000:29:00.3: init 0000:29:00.3 fail, -16
[ 2.901248] xhci_hcd 0000:29:00.3: probe with driver xhci_hcd failed with error -16
[ 3.001766] ahci 0000:25:00.0: version 3.0
[ 3.001865] ahci 0000:25:00.0: probe with driver ahci failed with error -22
[ 3.001977] ahci 0000:26:00.0: probe with driver ahci failed with error -22
[ 3.002487] ahci 0000:2a:00.0: probe with driver ahci failed with error -22
[ 22.844890] ee1004 3-0056: Failed to select page 0 (-6)
[ 22.847370] ast 0000:28:00.0: probe with driver ast failed with error -22
[ 22.848771] Error: Driver ‘pcspkr’ is already registered, aborting…
[ 146.818770] {2}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 512
[ 146.818816] {2}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 146.818847] {2}[Hardware Error]: event severity: corrected
[ 146.818873] {2}[Hardware Error]: Error 0, type: corrected
[ 146.818900] {2}[Hardware Error]: section_type: PCIe error
[ 146.818922] {2}[Hardware Error]: port_type: 4, root port
[ 146.818946] {2}[Hardware Error]: version: 0.2
[ 146.818964] {2}[Hardware Error]: command: 0x0407, status: 0x0010
[ 146.818988] {2}[Hardware Error]: device_id: 0000:20:01.3
[ 146.819010] {2}[Hardware Error]: slot: 0
[ 146.819027] {2}[Hardware Error]: secondary_bus: 0x2c
[ 146.819047] {2}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 146.819071] {2}[Hardware Error]: class_code: 060400
[ 146.819091] {2}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x0012
[ 146.819118] {2}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 146.819147] {2}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 146.819176] {2}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 146.819200] {2}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 330.626102] {3}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 512
[ 330.626644] {3}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 330.627072] {3}[Hardware Error]: event severity: corrected
[ 330.627416] {3}[Hardware Error]: Error 0, type: corrected
[ 330.627754] {3}[Hardware Error]: section_type: PCIe error
[ 330.628088] {3}[Hardware Error]: port_type: 4, root port
[ 330.628418] {3}[Hardware Error]: version: 0.2
[ 330.628743] {3}[Hardware Error]: command: 0x0407, status: 0x0010
[ 330.629068] {3}[Hardware Error]: device_id: 0000:20:01.1
[ 330.629394] {3}[Hardware Error]: slot: 0
[ 330.629719] {3}[Hardware Error]: secondary_bus: 0x21
[ 330.630046] {3}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 330.630378] {3}[Hardware Error]: class_code: 060400
[ 330.630708] {3}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 330.631049] {3}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 330.631393] {3}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 330.631742] {3}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 330.632092] {3}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 369.025954] {4}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 512
[ 369.026514] {4}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 369.026958] {4}[Hardware Error]: event severity: corrected
[ 369.027341] {4}[Hardware Error]: Error 0, type: corrected
[ 369.027689] {4}[Hardware Error]: section_type: PCIe error
[ 369.028031] {4}[Hardware Error]: port_type: 4, root port
[ 369.028368] {4}[Hardware Error]: version: 0.2
[ 369.028699] {4}[Hardware Error]: command: 0x0407, status: 0x0010
[ 369.029032] {4}[Hardware Error]: device_id: 0000:20:01.1
[ 369.029364] {4}[Hardware Error]: slot: 0
[ 369.029695] {4}[Hardware Error]: secondary_bus: 0x21
[ 369.030029] {4}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 369.030369] {4}[Hardware Error]: class_code: 060400
[ 369.030705] {4}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 369.031050] {4}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 369.031401] {4}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 369.031757] {4}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 369.032115] {4}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
[ 630.400384] {5}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 512
[ 630.400832] {5}[Hardware Error]: It has been corrected by h/w and requires no further action
[ 630.401380] {5}[Hardware Error]: event severity: corrected
[ 630.401823] {5}[Hardware Error]: Error 0, type: corrected
[ 630.402178] {5}[Hardware Error]: section_type: PCIe error
[ 630.402515] {5}[Hardware Error]: port_type: 4, root port
[ 630.402849] {5}[Hardware Error]: version: 0.2
[ 630.403174] {5}[Hardware Error]: command: 0x0407, status: 0x0010
[ 630.403502] {5}[Hardware Error]: device_id: 0000:20:01.1
[ 630.403828] {5}[Hardware Error]: slot: 0
[ 630.404153] {5}[Hardware Error]: secondary_bus: 0x21
[ 630.404481] {5}[Hardware Error]: vendor_id: 0x1022, device_id: 0x1483
[ 630.404816] {5}[Hardware Error]: class_code: 060400
[ 630.405148] {5}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x001a
[ 630.405489] {5}[Hardware Error]: aer_cor_status: 0x00000040, aer_cor_mask: 0x00000000
[ 630.405836] {5}[Hardware Error]: aer_uncor_status: 0x00000000, aer_uncor_mask: 0x04000000
[ 630.406187] {5}[Hardware Error]: aer_uncor_severity: 0x034f6030
[ 630.406539] {5}[Hardware Error]: TLP Header: 00000000 00000000 00000000 00000000
truenas_admin@truenas[~]$ sudo dmesg | grep -i ‘ahci|sata|error|fail’

ChatGPT said:
Thank you for this extremely detailed output — and we now have a clear answer.

What’s Going On:
The key messages are these:

vbnet
Copy
Edit
[ 3.001766] ahci 0000:25:00.0: version 3.0
[ 3.001865] ahci 0000:25:00.0: probe with driver ahci failed with error -22
[ 3.001977] ahci 0000:26:00.0: probe with driver ahci failed with error -22
[ 3.002487] ahci 0000:2a:00.0: probe with driver ahci failed with error -22
These correspond to:

25:00.0 and 26:00.0 = ASMedia ASM1062 SATA controllers

2a:00.0 = AMD FCH SATA controller — this is your mainboard’s native SATA ports

The error -22 means “Invalid Argument”, which in kernel driver-speak almost always points to a driver-to-firmware incompatibility or misbehavior in PCIe enumeration.

Interpretation
TrueNAS SCALE is detecting the AMD and ASMedia SATA controllers.

But ALL THREE are failing to initialize (even the AMD one you’re plugged into).

This is likely due to:

A PCIe resource conflict,

A BIOS bug, or

A Linux kernel driver edge-case with WRX80/EPYC platforms.

These errors are fatal to drive detection, which is why lsblk only shows NVMe drives.

What You Can Do
1. Simplest Fix: Use the 9300-8i HBA
You’ve already found the right card:

Plug it into any open PCIe x8 or x16 slot.

Connect your SSDs via breakout cables.

TrueNAS SCALE will see the drives immediately as /dev/sdX — no BIOS setup, no driver hacks.

This bypasses all broken onboard SATA entirely.

2. Optional: Try BIOS/UEFI Tweaks
If you’re curious or want to attempt further recovery before installing the HBA:

Update your BIOS to the latest firmware version from ASUS for the WRX80E-SAGE SE WIFI.

In BIOS:

Disable CSM.

Set SATA controller to AHCI.

Try turning PCIe 4.0 to Gen 3 for affected slots.

Look for any settings like “Above 4G decoding”, “PCIe spread spectrum”, or “IOMMU” and try toggling them.

Then reboot and check dmesg again. But realistically, this may not help, and installing the HBA will give you rock-solid results instantly.

scarbrtj · July 27, 2025, 7:44pm

My first experience with TrueNAS: not good.

So just as an initial test. I tried copying and pasting a file from one PC (an NVME in the mobo) to another PC (a shared folder on an NVME in the mobo) across my network; running at about 1GB/s:

And the same attempt to transfer to the new TrueNAS build (it is on the same switch as both PCs). This transfer runs at 0 to 700 MB/s, very “spotty”. I have a mirrored 2 drive NVME setup, the NVME’s in the mobo.

This is not good.

scarbrtj · July 27, 2025, 11:05pm

Tinkering around, not really changing any parameters significantly, but just creating a new pool and dataset leads to:

thoresson · July 28, 2025, 2:20pm

I had the same problem when I installed TN for the first time. Turned out that the bottleneck was a bad Ethernet cable, identified using iperf3. So my suggestion is to start there, to find out if it’s the server’s network connection or something else.

ChrisRJ · July 28, 2025, 4:11pm

You probably mean Bluetooth. A non-Bluetooth wireless keyboard is not a problem, because its receiver presents a USB keyboard to the motherboard.

scarbrtj · July 28, 2025, 5:11pm

No, I definitely meant wireless USB, and confirmed it was a problem with multiple wireless USB dongles (Amazon.com, Amazon.com … and yes the kayboards are working on other PCs) before being forced to buy a wired keyboard to get install to work.

AFTER install, the wireless keyboards work fine. The “hang” is at the 4-option install screen after install boot.

==============

Tell me about wireless USB keyboards and TrueNAS install problems.

ChatGPT said:

Wireless USB keyboards can sometimes cause issues during the installation of TrueNAS (or other BSD-based operating systems) due to how early-stage USB initialization and driver support are handled in the boot process. Here’s a breakdown of the common problems and workarounds:

Common Problems

1. No Keyboard Response at Boot Menu or Installer

The keyboard may not work at the TrueNAS bootloader screen or in the installation menu.
Often seen with wireless keyboards that use a USB dongle, especially models from Logitech (Unifying Receiver), Microsoft, etc.

2. BIOS/UEFI Settings Blocking USB Input

Some motherboards disable USB legacy support or don’t initialize USB hubs fully until the OS loads.
Wireless receivers plugged into USB 3.x ports (blue) may not initialize in time for early boot.

3. Incompatibility with FreeBSD

TrueNAS is based on FreeBSD, which has limited early-stage USB driver support compared to Linux or Windows.
Some wireless receivers require HID drivers that aren’t available during bootloader/installer phases.

scarbrtj · July 28, 2025, 7:19pm

Checking the ethernet cable… well, it did handle “sawtoothing” to ~700MB/s, but it was a nice idea; didn’t work. Tried a brand new 10 foot Cat6a cable.

scarbrtj · July 28, 2025, 7:26pm

Just for fun, I installed Unraid on this system and set up a RAIDZ1 pool of the 4 SSDs. Got a write speed of 100 MB/s, but at least no sawtoothing.

I will re-install TrueNAS. The only thing I am waiting now is the 12 disk JBOD and the HBA, hooking those up, and seeing what happens.

Have to say I am not hopeful. This is my attitude about TrueNAS so far: https://www.youtube.com/watch?v=p0_QJVgYNMk

But am I the problem? I can’t identify the failure point. I have good hardware, a totally fresh install, just using default settings (I have tried compression off/on, sync off/on, big record sizes), there has to be something I’m missing. But I never wanted to get in to the minutiae and nuances of TrueNAS. I just wanted to buy good stuff. Hook up to my network. And have it perform as well as or better than my QNAP boxes. I have two 4-disk (SSD) RAID5 setups in two separate QNAP boxes. They have routinely done 700-1000MB/s since 2018 when I got them. I expected similar TrueNAS performance. Instead my TrueNAS install prefers R/W speeds that seem happy to be at 0MB/s, a lot.

I could say learning curve, but I don’t know what I need to learn.

Awaiting JBOD boxes for 20TB HDDs, as I said.

geri91 · July 29, 2025, 3:33pm

Hi,

There are so many variables, especially with a DIY build, so try to narrow it down.

1) Test with a single NVME disk

Just create a partition on one NVME disk. Single disk. Perform a write speed test on it, and note down the measured throughput.
Do this test on the machine itself. No network copy!

2) Test with an NVME mirror

Create a simple mirror from two NVME disks, then run the test again and note down the results.
Do this test on the machine itself. No network copy!

3) Create a samba share and test over the network

Create a samba share, and repeat the test. The file copy test from Windows is fine.

Utilities for benchmarking

SSH into the system and you may use “dd” to do a quick test like this. It will give you a rough speed measurement, it is good enough for quick troubleshooting.

# Go to a dataset on the NVME mirror
cd /mnt/nvme1/testnvme

# Write speed test
dd if=/dev/zero of=testfile bs=1G count=10 oflag=direct status=progress

# Read speed test
dd if=testfile of=/dev/null bs=1G iflag=direct status=progress

# Cleanup
rm testfile

Never give up!