Ok…I finally got my TrueNAS hardware build completed with no issues and I successfully installed TrueNAS 25.04.1 with no issues. Interestingly, from a cold boot, TrueNAS throws errors which scroll across the monitor so fast that I can’t really tell what’s being reported - I took a picture with my phone and saw the following:
PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID) device [10b5:8724] error status/mask=000000c1/0000a000
[ 0] RxErr (First)
[ 6] BadTLP or it could say BadDLLP
[12] Timeout
Now, if I hit the reset button on the computer while this error scrolls by so fast on the monitor, and TrueNAS restarts, it seems that TrueNAS starts as you would expect it to. I can login to the dashboard with no issues at that point and I see no errors. I’m also presently copying data from a QNAP NAS that’s failing on me to my new TrueNAS with no issues.
By chance has anyone seen this error before and/or know what it’s referencing and how to fix it? Thank you.
If it’s doing that but still booting and acting normal, ignore it. Linux has all kinds of little checks for this and that and they aren’t all show stoppers. You might have a weird component or a specific value is expected of some hardware bit that gives a different value, keep on truckin. 3 of my wd drives don’t supply the expected normal SMART values but they keep spinning and don’t error out anyway.
Boot with pcie_aspm=off to see if it shuts up. Old debian forum post says this is a power state with pcie, if you turn it off it eats more power but settles down.
@afrosheen Thanks for the reply. I definitely see on boot that Linux does an effton of checks. Once all of my data is copied over, I’ll take a look in the BIOS to see if I can find and disable PCIe ASPM as a test. In the meantime, as you say, I’ll keep on truckin.
With a little more digging, at the TrueNAS shell I used dmesg to find the following:
pcieport 0000:00:06.0: AER: Correctable error message received from 0000:00:06.0
pcieport 0000:00:06.0: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
Some searching found that AER apparently stands for Advanced Error Reporting. The search result also found that it is recommended to check the hardware connections, update the firmware, and ensure that the system is running the latest version of TrueNAS. I have the latest BIOS update, the system is running the latest TrueNAS version. I guess I could check the connections again. I wonder if it’s my HBA for my 8 drives; maybe the connection or cabling to the drives? It’s a SAS9300-16i LSI 9300-16i; Amazon B0BYZBNXBS.
Ok. So I cracked the case, re-seated the HBA card and replaced the cabling to the drives from the HBA card. I have an ASUS Pro WS W680M-ACE SE Intel LGA 1700 mATX BMC AST2600 workstation motherboard.
I turn on the computer to let it boot. After booting, when it gets to the screen that asks you to enter an option for what you would like to do, the screen randomly displays an error for device [10b5:8724]. Several searches for this device describes error [10b5] is apparently associated with a PCI Express Gen 3 (8 GT/s) switch manufactured by PLX Technology, specifically the PEX 8724 model, which has 24 lanes and 6 ports. This device is listed in a database of hardware that works under Linux, indicating it is compatible with the Linux operating system. As well, the device is supposed to be recognized under the PCI identifier PCI\VEN_10B5&DEV_8724, and it is noted that the vendor is PLX Technology, Inc. The error might be related to the device’s functionality or driver issues, but specific details about the error are not provided. The search result also states that if you encounter this error, it may be necessary to check the device’s drivers or consult the Linux hardware compatibility database for further information.
I’m not trying to be a pest by continually posting, I’m just trying to troubleshoot to find what is causing the issue and fix it, if possible. Anyone have any ideas on what this may be pointing to?
If it’s the HBA card, can anyone suggest an HBA card that actually works that will support a minimum of 8 drives?
@SmallBarky Thanks for the reply. I don’t know if the issue was occurring prior to updating the BIOS but I updated the BIOS to the most current without issue.
Interestingly, when I go to the TrueNAS shell, it appears that sas3flash is not found, so I can’t tell what firmware this HBA has. As well, I’m trying to find a firmware update for this HBA from Broadcomm and info that I’ve found says it’s supposedly available on the TrueNAS forums but I can’t find it.
Welcome to TrueNAS
Last login: Fri Jun 27 22:06:24 CDT 2025 on pts/4
truenas_admin@truenas[~]$ sas3flash
zsh: command not found: sas3flash
truenas_admin@truenas[~]$ sudo sas3flash -list
[sudo] password for truenas_admin:
Avago Technologies SAS3 Flash Utility
Version 16.00.00.00 (2017.05.02)
Copyright 2008-2017 Avago Technologies. All rights reserved.
No Avago SAS adapters found! Limited Command Set Available!
ERROR: Command Not allowed without an adapter!
ERROR: Couldn't Create Command -list
Exiting Program.
truenas_admin@truenas[~]$
@SmallBarky Thanks for the sas3flash -list clarification to use sudo; doh! So, I get the same version as you 16.00.00.00.
So I read to get the latest firmware update for this HBA here from the community. Do you concur? It shows for an 8i, I have a 16i.
As well, I’m reading several different command line update parameters. Do you have the correct update syntax? I read something that I now can’t find that you have to update both controllers for the 16i.
Hmmmm. It looks like my device is a SAS3008(C0) controller.
Avago Technologies SAS3 Flash Utility
Version 16.00.00.00 (2017.05.02)
Copyright 2008-2017 Avago Technologies. All rights reserved.
Adapter Selected is a Avago SAS: SAS3008(C0)
Controller Number : 0
Controller : SAS3008(C0)
PCI Address : 00:03:00:00
SAS Address : 500062b-2-041a-b680
NVDATA Version (Default) : 0e.01.00.07
NVDATA Version (Persistent) : 0e.01.00.07
Firmware Product ID : 0x2221 (IT)
Firmware Version : 16.00.01.00
NVDATA Vendor : LSI
NVDATA Product ID : SAS9300-8i
BIOS Version : 08.37.00.00
UEFI BSD Version : 06.00.00.00
FCODE Version : N/A
Board Name : SAS9300-16i
Board Assembly : 03-25600-01B
Board Tracer Number : SP82813896
Finished Processing Commands Successfully.
Exiting SAS3Flash.
Let’s see if anyone experienced with the HBA posts.
It was just posting the version of the sas3flash utility for my example as I don’t have any HBA cards.
You might want to post a detailed hardware, os and pool setup. It helps catch things like OEM versions of HBAs using different firmware or hard drive models that use SMR and not CMR tech.
Ok. So I looked at the community download from the page I listed. There is a 16i firmware. I copied the firmware to a share on TrueNAS but I can’t seem to find a way for the truenas_admin account in the shell to find the share I copied it to. Seeing I’m still new to TrueNAS, I’m likely missing something.
The new results of the last command I used:
sas3flash -o -fwall SAS9300-16i_IT.bin
Avago Technologies SAS3 Flash Utility
Version 16.00.00.00 (2017.05.02)
Copyright 2008-2017 Avago Technologies. All rights reserved.
Adapter Selected is a Avago SAS: SAS3008(C0)
Controller Number : 0
Controller : SAS3008(C0)
PCI Address : 00:03:00:00
SAS Address : 500062b-2-041a-b680
NVDATA Version (Default) : 0e.01.00.03
NVDATA Version (Persistent) : 0e.01.00.07
Firmware Product ID : 0x2221 (IT)
Firmware Version : 16.00.12.00
NVDATA Vendor : LSI
NVDATA Product ID : SAS9300-16i
BIOS Version : 08.37.00.00
UEFI BSD Version : 06.00.00.00
FCODE Version : N/A
Board Name : SAS9300-16i
Board Assembly : 03-25600-01B
Board Tracer Number : SP82813896
Finished Processing Commands Successfully.
Exiting SAS3Flash.
So on boot, I did notice 1 line that stated FAILED. I tried to get a picture of it but it scrolled by so fast that the picture is blurry. Unless you know of a dmesg command to find this failure, I’m at a loss to describe it.
I found this error message using dmesg as well:
[ 19.766449] Error: Driver ‘pcspkr’ is already registered, aborting…
sudo dmesg | grep -i 10b5, which was the offending error I was seeing:
[ 0.285611] pci 0000:01:00.0: [10b5:8724] type 01 class 0x060400 PCIe Switch Upstream Port
[ 0.285897] pci 0000:02:00.0: [10b5:8724] type 01 class 0x060400 PCIe Switch Downstream Port
[ 0.286093] pci 0000:02:08.0: [10b5:8724] type 01 class 0x060400 PCIe Switch Downstream Port
[ 0.286285] pci 0000:02:09.0: [10b5:8724] type 01 class 0x060400 PCIe Switch Downstream Port
@SmallBarky Thanks for the reply. Well, I don’t know that I’m seeing any issues. I don’t know what I don’t know. When I find an error message, I try to do some research and find what may be occurring which would allow me to get to know the system much more and maybe find a fix. Curiosity with wondering what others may have seen and done.
