dyedfire

I admit that I do have a few power splitters used for my setup. I'll try re-arranging them to see if I can spot the bad splitter or if there's an overdraw in the power usage. (Leaning more on the former than the latter)

I've encountered an issue on my hard drive where it produces errors like this on the disk log: Mar 21 16:42:04 TemposRAID kernel: ata1.00: exception Emask 0x10 SAct 0x30000 SErr 0x4090000 action 0xe frozen Mar 21 16:42:04 TemposRAID kernel: ata1.00: irq_stat 0x00400040, connection status changed Mar 21 16:42:04 TemposRAID kernel: ata1: SError: { PHYRdyChg 10B8B DevExch } Mar 21 16:42:04 TemposRAID kernel: ata1.00: failed command: READ FPDMA QUEUED Mar 21 16:42:04 TemposRAID kernel: ata1.00: cmd 60/00:80:c8:2a:e6/01:00:9d:00:00/40 tag 16 ncq dma 131072 in Mar 21 16:42:04 TemposRAID kernel: ata1.00: status: { DRDY } Mar 21 16:42:04 TemposRAID kernel: ata1.00: failed command: READ FPDMA QUEUED Mar 21 16:42:04 TemposRAID kernel: ata1.00: cmd 60/00:88:c8:29:e6/01:00:9d:00:00/40 tag 17 ncq dma 131072 in Mar 21 16:42:04 TemposRAID kernel: ata1.00: status: { DRDY } Mar 21 16:42:04 TemposRAID kernel: ata1: hard resetting link This accompanies with a sound coming from the hard drive itself, as if it's skipping inside. At first, I thought it was because of my Sata expansion card but I've eliminated that from the equation. I also thought it was the sata cable / port from the motherboard to the drive, but simply switching it didn't change anything. I was in the middle of moving all my files off there a new thing appear on the Array Devices list: errors... About 36. So, I thought turning off "Turbo Write" to test if it was that. No. After an extended test on the drive itself, S.M.A.R.T. came back with nothing. Before that, Check Filesystem showed nothing. Before I go through the exhausting method of testing this new Seagate IronWolf with their software (perhaps sending in a warranty claim), are there any other steps that I need to take? If not, then should I not touch my files (or move them off) and instead replace, then allow the parity to build them back? Thank you for your time temposraid-diagnostics-20240322-0739.zip temposraid-smart-20240322-0740.zip

I just wanted to say that #5 on this list was the culprit for me. There were a lot of old share configurations that the mover was getting hung up on, therefore never running. After a clean up, the move now worked with the proper filters in place. Thank you for this checklist.