Liquidtouch

Thanks so much! Hopefully it stays this way...

Thanks for looking at that. I have added the old 2TB back into the array and will just use it for non-important stuff for now. I swapped around my SATA cables and connected my Parity drive to its own cable going to the power supply, before it was one of four on the cable. I don't think I see anymore ATA errors if I was looking at the same thing you noticed in the syslog. Here are my new logs after the changes above. homeserver-diagnostics-20250207-1550.zip

Here they are. Thanks! homeserver-diagnostics-20250206-2358.zip

I should also note that in the midst of all this I updated my server to 7.0

I opened up my server to install a new drive into it. When I booted it back up a different pre-existing drive showed as unenabled. I reconnected the cable thinking perhaps something came unseated during the install of my new disk and then did an extended smart test which it passed. I rebuilt the drive and thought the problem was solved. A couple days later I noticed the drive had once again been disabled. I decided to replace the drive completely just in case its in a pre-failure state but also decided to replace my power supply, sata cables, and LBA cables, at the same time suspecting anyone of them could also be the culprit and unable to handle the new drive I installed. I had already exhausted the SATA power connectors on my PSU and was using molex to sata adaptors. Now I have everything installed and my array seems to be working. I want to determine if the older drive I pulled out is pre-failure or if one of my other fixes was the issue. I put the suspect drive into unassigned disks and ran a pre-clear which it passed. The only thing that looks odd is the "Reads" the value seems much higher than my other disks. Is this normal? I also attached the Smart Report, any thoughts on this drive? Thanks, Disk Smart Report.zip