06-13-2021, 08:13 AM
After recieving and assembling my Pine NASCase (with 2x 3,5" HDDs, Western
Digital WD40EFAX-68JH4N1, certified for NAS) I immediately got a lot of these
errors when I created some IO (i.e. running badblocks on both disks, or creating
an md softraid):
ata1.00: exception Emask 0x10 SAct 0x200 SErr 0x400000 action 0x6 frozen
ata1.00: irq_stat 0x08000000, interface fatal error
ata1: SError: { Handshk }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/90:48:70:f6:af/09:00:05:00:00/40 tag 9 ncq dma 1253376 ou
res 40/00:48:70:f6:af/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY }
ata1: hard resetting link
see https://forum.pine64.org/showthread.php?tid=6511,
https://forum.pine64.org/showthread.php?tid=6932&page=3,
and https://wiki.archlinux.org/index.php/Sol...NCQ_errors
Booting with the "libata.force=noncq" kernel parameter resolved those issues.
echo 'extraargs=libata.force=noncq' >> /boot/armbianEnv.txt
When doing high IO on the disks (badblocks in parallel on both disks,
syncing an md softraid etc) I frequently get `WRITE DMA EXT` errors,
which fortunatly don't corrupt the write operations:
ata2.00: irq_stat 0x08000000, interface fatal error
ata2: SError: { Handshk }
ata2.00: failed command: WRITE DMA EXT
ata2.00: cmd 35/00:00:00:14:a8/00:0a:47:00:00/e0 tag 9 dma 1310720 out
res 50/00:00:00:14:a8/00:00:47:00:00/e0 Emask 0x10 (ATA bus error)
ata2.00: status: { DRDY }
ata2: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
ata1.00: configured for UDMA/133
ata1: EH complete
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata2.00: configured for UDMA/133
ata2: EH complete
ata1: limiting SATA link speed to 1.5 Gbps
ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400000 action 0x6 frozen
ata1.00: irq_stat 0x08000000, interface fatal error
ata1: SError: { Handshk }
ata1.00: failed command: WRITE DMA EXT
ata1.00: cmd 35/00:00:00:28:bd/00:0a:47:00:00/e0 tag 0 dma 1310720 out
res 50/00:00:00:28:bd/00:00:47:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/133
ata1: EH complete
Still, those errors are a mess in the syslog and downgrade the SATA link spped
from 6 Gbit/s to 1,5 Gbit/s (back and forth).
I even tried glueing some heatsink onto the SATA controller's main chip which
got hot under load (just enough that it hurt my fingertip), but this doesn't
resolve the issue.
I also replaced both SATA cables with ones that I had lying around,
without any difference.
I must say I'm unhappy by the lack of proper support by Pine64 here in this
thread, which started 2018, and I didn't see any investigations/solutions by Pine64.
Digital WD40EFAX-68JH4N1, certified for NAS) I immediately got a lot of these
errors when I created some IO (i.e. running badblocks on both disks, or creating
an md softraid):
ata1.00: exception Emask 0x10 SAct 0x200 SErr 0x400000 action 0x6 frozen
ata1.00: irq_stat 0x08000000, interface fatal error
ata1: SError: { Handshk }
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/90:48:70:f6:af/09:00:05:00:00/40 tag 9 ncq dma 1253376 ou
res 40/00:48:70:f6:af/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY }
ata1: hard resetting link
see https://forum.pine64.org/showthread.php?tid=6511,
https://forum.pine64.org/showthread.php?tid=6932&page=3,
and https://wiki.archlinux.org/index.php/Sol...NCQ_errors
Booting with the "libata.force=noncq" kernel parameter resolved those issues.
echo 'extraargs=libata.force=noncq' >> /boot/armbianEnv.txt
When doing high IO on the disks (badblocks in parallel on both disks,
syncing an md softraid etc) I frequently get `WRITE DMA EXT` errors,
which fortunatly don't corrupt the write operations:
ata2.00: irq_stat 0x08000000, interface fatal error
ata2: SError: { Handshk }
ata2.00: failed command: WRITE DMA EXT
ata2.00: cmd 35/00:00:00:14:a8/00:0a:47:00:00/e0 tag 9 dma 1310720 out
res 50/00:00:00:14:a8/00:00:47:00:00/e0 Emask 0x10 (ATA bus error)
ata2.00: status: { DRDY }
ata2: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
ata1.00: configured for UDMA/133
ata1: EH complete
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata2.00: configured for UDMA/133
ata2: EH complete
ata1: limiting SATA link speed to 1.5 Gbps
ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400000 action 0x6 frozen
ata1.00: irq_stat 0x08000000, interface fatal error
ata1: SError: { Handshk }
ata1.00: failed command: WRITE DMA EXT
ata1.00: cmd 35/00:00:00:28:bd/00:0a:47:00:00/e0 tag 0 dma 1310720 out
res 50/00:00:00:28:bd/00:00:47:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/133
ata1: EH complete
Still, those errors are a mess in the syslog and downgrade the SATA link spped
from 6 Gbit/s to 1,5 Gbit/s (back and forth).
I even tried glueing some heatsink onto the SATA controller's main chip which
got hot under load (just enough that it hurt my fingertip), but this doesn't
resolve the issue.
I also replaced both SATA cables with ones that I had lying around,
without any difference.
I must say I'm unhappy by the lack of proper support by Pine64 here in this
thread, which started 2018, and I didn't see any investigations/solutions by Pine64.