August 21, 20214 yr Building a 3rd unRaid server and I have 5 SAS drives for the array. I am using 8TB HUH728080AL5200 Hitachi Ultrastar As I started the array and going through the parity sync I get these errors in my console: [ 2787.398201] pcieport 0000:00:03.0: AER: Corrected error received: 0000:04:00.0 [ 2787.398207] mpt3sas 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 2787.398211] mpt3sas 0000:04:00.0: device [1000:0072] error status/mask=00001000/00002000 [ 2787.398214] mpt3sas 0000:04:00.0: [12] Timeout [ 2787.508714] pcieport 0000:00:03.0: AER: Corrected error received: 0000:04:00.0 [ 2787.508724] mpt3sas 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 2787.508729] mpt3sas 0000:04:00.0: device [1000:0072] error status/mask=00001000/00002000 [ 2787.508732] mpt3sas 0000:04:00.0: [12] Timeout [ 2787.655567] pcieport 0000:00:03.0: AER: Corrected error received: 0000:04:00.0 [ 2787.655577] mpt3sas 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 2787.655581] mpt3sas 0000:04:00.0: device [1000:0072] error status/mask=00001000/00002000 [ 2787.655585] mpt3sas 0000:04:00.0: [12] Timeout root@Tower:/boot/config# tower-diagnostics-20210821-1704.zip
August 22, 20214 yr Community Expert Try moving the HBA to a different PCIe slot, or see below: https://forums.unraid.net/topic/111161-pcie-errors/?do=findComment&comment=1013378
August 22, 20214 yr Author Unfortunately I only have one PCIe slot on this mini-itx board I installed Debian 11 and get the same error I have the latest firmware and is in IT mode. Not sure what else I can do Looks like suppressing the error from messages is the way to go as long is not really a hardware issue I guess? [ 9.324468] igb 0000:00:14.0 enp0s20f0: igb: enp0s20f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 9.364463] igb 0000:00:14.1 enp0s20f1: igb: enp0s20f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ 9.540181] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20f0: link becomes ready [ 9.580187] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20f1: link becomes ready [ 9.940463] rfkill: input handler disabled [ 50.983598] rfkill: input handler enabled [ 54.895148] rfkill: input handler disabled [ 85.178157] pcieport 0000:00:03.0: AER: Corrected error received: 0000:04:00.0 [ 85.178166] mpt3sas 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 85.178170] mpt3sas 0000:04:00.0: device [1000:0072] error status/mask=00001000/00002000 [ 85.178173] mpt3sas 0000:04:00.0: [12] Timeout [ 85.245303] pcieport 0000:00:03.0: AER: Corrected error received: 0000:04:00.0 [ 85.245313] mpt3sas 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 85.245316] mpt3sas 0000:04:00.0: device [1000:0072] error status/mask=00001000/00002000 [ 85.245319] mpt3sas 0000:04:00.0: [12] Timeout [ 85.248430] pcieport 0000:00:03.0: AER: Corrected error received: 0000:04:00.0 [ 85.248436] mpt3sas 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 85.248439] mpt3sas 0000:04:00.0: device [1000:0072] error status/mask=00001000/00002000 [ 85.248442] mpt3sas 0000:04:00.0: [12] Timeout [ 85.322659] pcieport 0000:00:03.0: AER: Corrected error received: 0000:04:00.0 [ 85.322684] mpt3sas 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 85.322688] mpt3sas 0000:04:00.0: device [1000:0072] error status/mask=00001000/00002000 [ 85.322691] mpt3sas 0000:04:00.0: [12] Timeout [ 100.561345] pcieport 0000:00:03.0: AER: Corrected error received: 0000:04:00.0 [ 100.561397] mpt3sas 0000:04:00.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 100.561400] mpt3sas 0000:04:00.0: device [1000:0072] error status/mask=00001000/00002000 [ 100.561403] mpt3sas 0000:04:00.0: [12] Timeout [ 119.726496] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 145.548023] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) root@smicro:~# root@smicro:~# root@smicro:~# root@smicro:~# dd if=/dev/zero of=/media/exile/DISK-1/test1.img bs=10G count=1 oflag=dsync 0+1 records in 0+1 records out 2147479552 bytes (2.1 GB, 2.0 GiB) copied, 17.2788 s, 124 MB/s root@smicro:~# root@smicro:~# Edited August 22, 20214 yr by johnwhicker
August 23, 20214 yr Community Expert 8 hours ago, johnwhicker said: Looks like suppressing the error from messages is the way to go as long is not really a hardware issue I guess? It's not ideal but other than using a different board it's your best option.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.