Hi,
I upgraded my drives to 12TB Seagate IronWolf and WD Reds, but it appears two Seagate drives don't enjoy the experience so far. At least I believe it's the drives, not the cables.
I only found one similar thread, and it was probably power splitters back then:
I get similar messages at the moment for ata1 and ata8. Can't complete parity checks (kilobytes/s), so something's not good.
I believe I identified the culprits via lshw -class disk -short and ls -l /sys/class/ata_port/ to be
* ata1: /dev/sdb ST12000VN0008-2Y disk1
* ata8: /dev/sdg ST12000VN0008-2Y parity
Spoiler contains the raw output that led me to the conclusions.
It's quite tricky to identify ataX numbers and also the drives I wired 😬
Parity fails a bit differently than disk1, with "found unknown device (class 0)" errors in the end of a failure cycle.
I've removed disk1 from the Global Shares to not put more data onto it.
I've checked the SATA cables. One did 'click' a bit deeper, actually, but that didn't change anything.
SMART report produced no errors.
I've used xfs_repair and it found issues on disk1, but no other data drive.
Parity can't be checked that way because it has no file system. But I'd love to! Any ideas?
I've used the unbalance app to move all but 100GB of data off of the 12TB drive (was very new and not very full). During the process, the log spawned problems like this again and the device audibly clicks and seems to spin up a disk again and again.
Someone suggested this might also be a SATA card in the PCIe slot that fails. I wouldn't know how to test this, though, without 'blindly' buying more equipment to check replacements.
Anything else I might try to diagnose?
Log in the spoilers:
I'd appreciate any other hints: How would you interpret these issues, for example?