Cii1

I am rebuilding the data and there is a read error warning with one of the healthy disk. Now the log is 100% and server is unresponsive and I can't stop the data rebuild process. Should I just force power off or there is a work around in this situation takserver-diagnostics-20240109-2302.zip

I tried swapping to on-board SATA controller, changing different SATA cables and rearranging the SATA power connections, the problem is still here

The diagnostics is uploaded above

I had one drive fail, so I got an Ironwolf Pro 8TB to replace. I've noticed there are issue with this drive with LSI controller in Unraid, so I follow the steps from the link bellow I also changed the SATA connection to on-board one as well. However, there are errors keeps popping up with the drive, like COMRESET FAILED (ERRNO=-16), and I/O error logical block async paage read. This is a replacement, I had the same problem with the first one I got. I don't know if it's the drive issue, the power delivery issue. Since I am using 550W for 4x 12TB HDD, 1x 8TB HDD, 4x 4TB HDD and 1x 1TB SSD Here is the diagnose file takserver-diagnostics-20240104-1821.zip

Thanks. I totally forgot about thepower supply issue. I've rearranged the power cables for the drives and it works fine again for now. I think my 550W PSU doesn't provide enough power for 1x SSD + 5x 7200RPM +5x 5400RPM harddrives when it's under full load.

Unfortunately, the issue has came back. I noticed there is problem with the connection. Is it also cause by bad connection between the drive and motherboard? Jun 30 22:15:58 TakServer emhttpd: error: hotplug_devices, 1706: No such file or directory (2): tagged device ST12000NE0008-2PK103_ZS805F5F was (sdg) is now (sdn) Jun 30 22:15:58 TakServer emhttpd: error: hotplug_devices, 1706: No such file or directory (2): tagged device WDC_WD120EFAX-68UNTN0_8DGG1WTY was (sdf) is now (sdo) takserver-diagnostics-20230630-2246.zip

After switching to onboard SATA controller, the disk errors are gone. I suspect that either the HBA is loosen by the vibration, or the mini SAS to SATA cables are broken. I have a spare cable at home and I will try to replace it later when I have time to do maintenance. Thank you for all the help!

Thank you for the quick response. I am currently working on a project involving the server. I hope no drives fail before I can rebuild the parity in a few days. Thank you for the help! I will post an update in a few days.

Thanks for the reply. I've swapped to onboard SATA connection for the parity drive. Howevery, the parity is still disable. Is there any method which I can enable the parity drive without rebuilding the whole parity again?

All drives works after I secured all the cables. I ran extended self-test on the parity drive and disk9, which both having warnings before, and no error has been found. I thought it all went well. But after I rebuilt the parity drive and the array started normal, I ran the parity check and now there are errors again on the parity disk. takserver-diagnostics-20230626-1236.zip

Thanks. I noticed the free space was ~5GB for disk9. After a rebooy and the free space went back to ~60GB. There is a warning from Fix Common Problem. I think the disk9 is too full to copy the files. So the parity sync failed. And now docker doesn't work as the path of the docker folder doesn't exist anymore

takserver-diagnostics-20230622-2148.zip

I am rebuilding the parity. And it seems one of my drive is going to fail soon, as it has read error during the parity rebuild. I think will let the rebuild finish and replace my failed drive. I got 2 Ironwolf drives and both got read errors with 3 years. I have 7 WD Red drives in my server and I only replace 2 in 5 years. I am really disappointed by Seagate..

The parity drive is disabled right after I copied 100GB of video footage to the array. I tried running SMART short test and it finished with no errors. I am not able to resolve the issue no matter what I tried. I updated my server from Unraid 6.11.5 to 6.12.0. But I have restored back to 6.11.5 after I encountered this situation. I also tried to replace with several different SATA cables but no luck I attached the diagnotics of my unraid serve below takserver-diagnostics-20230620-1954.zip

I don't really know what to do with that. So ending up, I restore the flash drive with backup. Now all the issues are gone. Everything works fine now.