Hello to all. I have a Wandboard Quad that basically serves as a headless server. It has a 5-Tb USB drive connected to the USB port and a 6-Tb HDD (Seagate ST6000DM003) connected to the SATA port.
All was well until I upgraded to Arch Linux ARM Kernel version 5.6.11-1-ARCH. Since then, the 6-Tb HDD has been periodically disappearing. The shares on it become unavailable and the HDD can no longer be found in /dev/sda, where it usually is, or anywhere else in /dev/. The console shows:
$this->bbcode_second_pass_code('', 'ata1: SATA link down (SStatus 0 SControl 300)')
multiple times and then:
$this->bbcode_second_pass_code('', 'exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000000
ata1.00: failed command: READ DMA
ata1.00: cmd 25/00:08:00:f4:a0/00:00:ba:02:00/e0 tag 24 dma 4096 in
res 53/04:08:00:f4:a0/00:00:ba:02:00/e0 Emask 0x1 (device error)
ata1.00: status: { DRDY SENSE ERR }
ata1.00: error: { ABRT }
ata1.00: configured for UDMA/133 (device error ignored)
ata1: EH complete')
and that also repeats several times.
At other times, just after
$this->bbcode_second_pass_code('', 'ata1: SATA link down (SStatus 0 SControl 300)')
I get:
$this->bbcode_second_pass_code('', 'ata1: limiting SATA link speed to 1.5 Gbps
ata1: softreset failed (1st FIS failed)
ata1: softreset failed (1st FIS failed)
ata1: softreset failed (1st FIS failed)
ata1: softreset failed (device not ready)
ata1: reset failed, giving up')
However if I run hdparm it can communicate with the drive and the drive responds to commands, but it remains cold as if it had spun down to save power and can't spin up again, or can't receive the signal to spin up again. If I reboot, the shared partition on the disk can't be found for mounting and a "Timed out waiting for device" error is thrown. However, if I unplug and replug power to the drive before I reboot, the disk is found and mounts and is available... that is, until it drops out again.
I've run Seagate's Long Generic SeaTools tests under Windows and also a full Smartmon test under Linux and no failures are found by either of them. Also if I connect the HDD to my Windows desktop computer, it seems to operate with no problems. (Perhaps I should mention that the main partition on the drive is formatted as NTFS for compatibility with the Windows boxes on my network.)
SeaGate don't seem to know what to tell me. I've been back and forth with two of their people and they ended up telling me they'll replace the drive. But I have a feeling the problem is related to Arch Linux.
If anyone has any ideas I'd love to hear them. I can provide any further info anyone might need, including the errors I get during the boot process.
Cheers,
Les