Warnings I don't quite understand.

resonator79 · January 10, 2023

Hi,

I'm getting warning I don't quite understand>

Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: cmd 60/40:30:78:e5:57/05:00:d2:06:00/40 tag 6 ncq dma 688128 in
Jan 10 03:42:58 AB-NAS1 kernel:         res 40/00:48:38:f5:57/00:00:d2:06:00/40 Emask 0x50 (ATA bus error)
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: cmd 60/40:38:b8:ea:57/05:00:d2:06:00/40 tag 7 ncq dma 688128 in
Jan 10 03:42:58 AB-NAS1 kernel:         res 40/00:48:38:f5:57/00:00:d2:06:00/40 Emask 0x50 (ATA bus error)
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: cmd 60/40:40:f8:ef:57/05:00:d2:06:00/40 tag 8 ncq dma 688128 in
Jan 10 03:42:58 AB-NAS1 kernel:         res 40/00:48:38:f5:57/00:00:d2:06:00/40 Emask 0x50 (ATA bus error)
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: cmd 60/d8:48:38:f5:57/02:00:d2:06:00/40 tag 9 ncq dma 372736 in
Jan 10 03:42:58 AB-NAS1 kernel:         res 40/00:48:38:f5:57/00:00:d2:06:00/40 Emask 0x50 (ATA bus error)
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: cmd 60/e8:50:10:f8:57/02:00:d2:06:00/40 tag 10 ncq dma 380928 in
Jan 10 03:42:58 AB-NAS1 kernel:         res 40/00:48:38:f5:57/00:00:d2:06:00/40 Emask 0x50 (ATA bus error)
Jan 10 03:42:58 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 10 03:42:58 AB-NAS1 kernel: ata4: hard resetting link
Jan 10 03:42:59 AB-NAS1 kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 10 03:42:59 AB-NAS1 kernel: ata4.00: configured for UDMA/133
Jan 10 03:42:59 AB-NAS1 kernel: ata4: EH complete
Jan 10 03:49:01 AB-NAS1  sSMTP[10090]: Creating SSL connection to host
Jan 10 03:49:01 AB-NAS1  sSMTP[10090]: SSL connection using TLS_AES_256_GCM_SHA384
Jan 10 03:49:01 AB-NAS1  sSMTP[10090]: Authorization failed (535 5.7.8  https://support.google.com/mail/?p=BadCredentials v27-20020a17090606db00b0081d2d9a0b45sm4388771ejb.186 - gsmtp)
Jan 10 05:24:01 AB-NAS1 kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
Jan 10 05:24:01 AB-NAS1 kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jan 10 05:24:01 AB-NAS1 kernel: pcieport 0000:00:1c.0:   device [8086:a338] error status/mask=00000001/00002000
Jan 10 05:24:01 AB-NAS1 kernel: pcieport 0000:00:1c.0:    [ 0] RxErr                 
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: exception Emask 0x50 SAct 0x7c000006 SErr 0x280900 action 0x6 frozen
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: irq_stat 0x08000000, interface fatal error
Jan 10 05:24:01 AB-NAS1 kernel: ata4: SError: { UnrecovData HostInt 10B8B BadCRC }
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: cmd 60/40:08:58:ff:3b/05:00:26:07:00/40 tag 1 ncq dma 688128 in
Jan 10 05:24:01 AB-NAS1 kernel:         res 40/00:08:58:ff:3b/00:00:26:07:00/40 Emask 0x50 (ATA bus error)
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: cmd 60/40:10:98:04:3c/05:00:26:07:00/40 tag 2 ncq dma 688128 in
Jan 10 05:24:01 AB-NAS1 kernel:         res 40/00:08:58:ff:3b/00:00:26:07:00/40 Emask 0x50 (ATA bus error)
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: cmd 60/40:d0:d8:e9:3b/05:00:26:07:00/40 tag 26 ncq dma 688128 in
Jan 10 05:24:01 AB-NAS1 kernel:         res 40/00:08:58:ff:3b/00:00:26:07:00/40 Emask 0x50 (ATA bus error)
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: cmd 60/40:d8:18:ef:3b/05:00:26:07:00/40 tag 27 ncq dma 688128 in
Jan 10 05:24:01 AB-NAS1 kernel:         res 40/00:08:58:ff:3b/00:00:26:07:00/40 Emask 0x50 (ATA bus error)
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: cmd 60/40:e0:58:f4:3b/05:00:26:07:00/40 tag 28 ncq dma 688128 in
Jan 10 05:24:01 AB-NAS1 kernel:         res 40/00:08:58:ff:3b/00:00:26:07:00/40 Emask 0x50 (ATA bus error)
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: cmd 60/40:e8:98:f9:3b/05:00:26:07:00/40 tag 29 ncq dma 688128 in
Jan 10 05:24:01 AB-NAS1 kernel:         res 40/00:08:58:ff:3b/00:00:26:07:00/40 Emask 0x50 (ATA bus error)
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: cmd 60/80:f0:d8:fe:3b/00:00:26:07:00/40 tag 30 ncq dma 65536 in
Jan 10 05:24:01 AB-NAS1 kernel:         res 40/00:08:58:ff:3b/00:00:26:07:00/40 Emask 0x50 (ATA bus error)
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 10 05:24:01 AB-NAS1 kernel: ata4: hard resetting link
Jan 10 05:24:01 AB-NAS1 kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 10 05:24:01 AB-NAS1 kernel: ata4.00: configured for UDMA/133
Jan 10 05:24:01 AB-NAS1 kernel: ata4: EH complete
Jan 10 05:51:01 AB-NAS1  sSMTP[30973]: Creating SSL connection to host
Jan 10 05:51:02 AB-NAS1  sSMTP[30973]: SSL connection using TLS_AES_256_GCM_SHA384
Jan 10 06:04:13 AB-NAS1 kernel: md: sync done. time=145046sec
Jan 10 06:04:13 AB-NAS1 kernel: md: recovery thread: exit status: 0
Jan 10 06:05:01 AB-NAS1  sSMTP[21849]: Creating SSL connection to host
Jan 10 06:05:02 AB-NAS1  sSMTP[21849]: SSL connection using TLS_AES_256_GCM_SHA384
Jan 10 06:14:03 AB-NAS1 kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
Jan 10 06:14:03 AB-NAS1 kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jan 10 06:14:03 AB-NAS1 kernel: pcieport 0000:00:1c.0:   device [8086:a338] error status/mask=00000001/00002000
Jan 10 06:14:03 AB-NAS1 kernel: pcieport 0000:00:1c.0:    [ 0] RxErr                 
Jan 10 06:27:24 AB-NAS1 kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
Jan 10 06:27:24 AB-NAS1 kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jan 10 06:27:24 AB-NAS1 kernel: pcieport 0000:00:1c.0:   device [8086:a338] error status/mask=00000001/00002000
Jan 10 06:27:24 AB-NAS1 kernel: pcieport 0000:00:1c.0:    [ 0] RxErr                 
Jan 10 06:49:47 AB-NAS1 kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
Jan 10 06:49:47 AB-NAS1 kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jan 10 06:49:47 AB-NAS1 kernel: pcieport 0000:00:1c.0:   device [8086:a338] error status/mask=00000001/00002000
Jan 10 06:49:47 AB-NAS1 kernel: pcieport 0000:00:1c.0:    [ 0] RxErr                 
Jan 10 07:19:27 AB-NAS1 kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
Jan 10 07:19:27 AB-NAS1 kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jan 10 07:19:27 AB-NAS1 kernel: pcieport 0000:00:1c.0:   device [8086:a338] error status/mask=00000001/00002000
Jan 10 07:19:27 AB-NAS1 kernel: pcieport 0000:00:1c.0:    [ 0] RxErr

[8086:a338] 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0)

I did a Parity Check, ahead of upgrading one of the array drives, and I got like ~20 UDMA CRC error on three drives, one of them just a few weeks old.

Does this mean the motherboard is failing?! The SATA controller for these three drives is the onboard controller.

Can anybody enlighten me?

Thx!

trurl · January 10, 2023

Attach Diagnostics to your NEXT post in this thread

resonator79 · January 10, 2023

Of course, sorry.

Thank you!

ab-nas1-diagnostics-20230110-1446.zip

JorgeB · January 10, 2023

7 hours ago, resonator79 said:
{ UnrecovData HostInt 10B8B BadCRC }

This is usually a bad SATA cable, replace it, ata4 is parity.

7 hours ago, resonator79 said:
AER: Corrected error received:

For those try this:

https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009

resonator79 · January 10, 2023

Yeah, I've already ordered some new cables, I figured it might be the cause.

Thank you for the tip about pcie_aspm=off. I will try that.

resonator79 · January 11, 2023

So today I replaced all SATA cables with brand new ones (Sabrant, brand type ones), and I triple checked all of them as to whether they the connectors are seated right. Did they array rebuild / HDD upgrade, and again - 3 drives with CRC new errors within minutes.

Jan 11 18:53:04 AB-NAS1 kernel: ata4.00: exception Emask 0x50 SAct 0x4 SErr 0x280900 action 0x6 frozen
Jan 11 18:53:04 AB-NAS1 kernel: ata4.00: irq_stat 0x08000000, interface fatal error
Jan 11 18:53:04 AB-NAS1 kernel: ata4: SError: { UnrecovData HostInt 10B8B BadCRC }
Jan 11 18:53:04 AB-NAS1 kernel: ata4.00: failed command: READ FPDMA QUEUED
Jan 11 18:53:04 AB-NAS1 kernel: ata4.00: cmd 60/40:10:48:82:fe/05:00:10:00:00/40 tag 2 ncq dma 688128 in
Jan 11 18:53:04 AB-NAS1 kernel:         res 40/00:00:48:82:fe/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
Jan 11 18:53:04 AB-NAS1 kernel: ata4.00: status: { DRDY }
Jan 11 18:53:04 AB-NAS1 kernel: ata4: hard resetting link
Jan 11 18:53:04 AB-NAS1 kernel: ata5.00: exception Emask 0x50 SAct 0x2 SErr 0x280900 action 0x6 frozen
Jan 11 18:53:04 AB-NAS1 kernel: ata5.00: irq_stat 0x08000000, interface fatal error
Jan 11 18:53:04 AB-NAS1 kernel: ata5: SError: { UnrecovData HostInt 10B8B BadCRC }
Jan 11 18:53:04 AB-NAS1 kernel: ata5.00: failed command: READ FPDMA QUEUED
Jan 11 18:53:04 AB-NAS1 kernel: ata5.00: cmd 60/40:08:48:82:fe/05:00:10:00:00/40 tag 1 ncq dma 688128 in
Jan 11 18:53:04 AB-NAS1 kernel:         res 40/00:00:48:82:fe/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
Jan 11 18:53:04 AB-NAS1 kernel: ata5.00: status: { DRDY }
Jan 11 18:53:04 AB-NAS1 kernel: ata5: hard resetting link
Jan 11 18:53:04 AB-NAS1 kernel: ata1.00: exception Emask 0x50 SAct 0x10000000 SErr 0x280900 action 0x6 frozen
Jan 11 18:53:04 AB-NAS1 kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Jan 11 18:53:04 AB-NAS1 kernel: ata1: SError: { UnrecovData HostInt 10B8B BadCRC }
Jan 11 18:53:04 AB-NAS1 kernel: ata1.00: failed command: READ FPDMA QUEUED
Jan 11 18:53:04 AB-NAS1 kernel: ata1.00: cmd 60/40:e0:48:82:fe/05:00:10:00:00/40 tag 28 ncq dma 688128 in
Jan 11 18:53:04 AB-NAS1 kernel:         res 40/00:00:48:82:fe/00:00:10:00:00/40 Emask 0x50 (ATA bus error)
Jan 11 18:53:04 AB-NAS1 kernel: ata1.00: status: { DRDY }
Jan 11 18:53:04 AB-NAS1 kernel: ata1: hard resetting link
Jan 11 18:53:04 AB-NAS1 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 11 18:53:04 AB-NAS1 kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 11 18:53:04 AB-NAS1 kernel: ata4.00: supports DRM functions and may not be fully accessible
Jan 11 18:53:04 AB-NAS1 kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 11 18:53:04 AB-NAS1 kernel: ata4.00: supports DRM functions and may not be fully accessible
Jan 11 18:53:04 AB-NAS1 kernel: ata5.00: configured for UDMA/133
Jan 11 18:53:04 AB-NAS1 kernel: ata5: EH complete
Jan 11 18:53:04 AB-NAS1 kernel: ata4.00: configured for UDMA/133
Jan 11 18:53:04 AB-NAS1 kernel: ata4: EH complete
Jan 11 18:53:04 AB-NAS1 kernel: ata1.00: configured for UDMA/133
Jan 11 18:53:04 AB-NAS1 kernel: ata1: EH complete

I don't know what to do. I guess the board is dying?!

JorgeB · January 11, 2023

Could be, you can try using an add-on controller if you have one available.

resonator79 · January 20, 2023

So, it turns out it was merely ONE defective drive in the array; it went to "disabled" on its own a few days after the rebuild, after which I replaced it with a new one, and all of a sudden ALL the UDMA errors on the other drives just stopped.

I rebuilt the array again, no errors during that "stress" on the system, and now the system's been up and running for a few days ... no more errors.

Edited January 20, 2023 by resonator79

Warnings I don't quite understand.

Recommended Posts

resonator79

Link to comment

trurl

Link to comment

resonator79

Link to comment

JorgeB

Link to comment

resonator79

Link to comment

resonator79

Link to comment

JorgeB

Link to comment

resonator79

Link to comment

Join the conversation