solidus_ty

Good to know. I have a bit of a Frankenstein build (3d printed drive housing) currently but I have been working towards fixing and setting up the system a lot better. Just hoping this issue will be solved so I can move on to other things I have been working on. I'll keep you guys updated on the parity sync. It was looking better today but we will see when it is completed.

Apologies I should have been more clear. I didn't pull a new diagnostics. That was from the initial post. so it would show the errors from the other drive. I am currently running a new parity sync while only having all the drives connected via Sata on the MB. It's sitting at 9 hours of run time and zero errors so far. Once this is done ill let the server resume as normal and keep an eye on the drives. If I see not errors for 24 hours after that ill assume it would be my SAS to SATA cables. Is it fairly common to have those cables go bad? Are they fairly fragile?

Here is the whole zip file that I pulled the diagnostics from. Let me know if that helps. I just went ahead and stopped the server checked all cables and everything seems fine. I only plugged in the Sata cables directly to the motherboard to eliminate the SAS to Sata cables as a problem. I am still using the Sata power splitters but I set them up here only three drives are per cable from the PSU (which is per rail I believe). Let me know if anything else could help narrow this down. tpmediaserver-diagnostics-20240528-0719.zip

Currently running a Read-Check after swapping cables and also adding the drive to a single data power cable from the PSU. I was using the 4 slot extensions but read they could cause issues. After running for 11 hours it's only at 7.9% and showing just over 1 million errors on the array 16tb drive, not the parity one. Is this expected from the drive being down and its fixing the errors?

I'll do the onboard SATA connector and try that. Then try the power connector. Would there be a good way to stress test it after? Seems odd it made it through both Parity Syncs when I installed it with no errors and then randomly threw it.

I recently upgraded my parity and one of my other array drives (2 used 16 TB EXOS drives for serverpartdeals). Sadly after this upgrade, my parity drive is throwing a "disk disabled contents emulated" but has zero smart errors. I looked through the forums and found a few posts regarding this issue checked cables, deleted the disk, and retried the sync to see if it would fix it. Sadly the disk worked overnight fine but while transferring some data this morning the drive is back into this error state. The log shows Disk Read Errors but the unraid says the drive is healthy. Is the drive bad or is it another issue? I have attached Diagnotiscs and the most recent SMART report. Im not sure what to look for in these documents to determine what is wrong or if it is a disk issue. I greatly appreciate the help. syslog.txt ST16000NM001G-2KK103_WL20DQVN-20240528-0743.txt