lukeg

It looks like the second rebuild has worked successfully, thanks so much all for your help! Also just wanted to get clarification on the above suggestion, is this suggesting after stopping docker that I should delete all the system share files on disk1 if they are duplicates? then it will use the one in cache? Fresh logs attached if that is helpful.morialta-diagnostics-20260831-2024.zip

Okay upon checking and fixing the filesystem on both disks, the error has gone, Disk 2 has returned to normal operation, but Disk 3 is still in disabled state, new diagnostics attached: morialta-diagnostics-20260829-1957.zip

I've run the Filesystem check on Disk 3 and the Fix option, it did a lot more than last time, I did see it has created some lost+found from the repair logs, however before I proceeded any further I wanted to check what was the correct next steps as I've just run the check on Disk 2 now that Disk 3 is finished repairing, and I've now got this message:

Ran memtest86+ for just over 5 hours and no issues were encountered, memory passes. morialta-diagnostics-20260829-1657.zip

No I haven't but I am happy to give that a go and share the results

I've now shut down the system, identified the two drives listed above and replaced the SATA cables for those, I did find one loose power connector on an unrelated drive but fixed that one, booted the system back up and I am seeing the same screen as above with two drives noted as unmountable Fresh diagnostics attached after completing these steps morialta-diagnostics-20260829-1106.zip

Okay I have simply rebooted the system and I now have two drives with issues fresh diagnostics attached: I will double check the data cables as suggested but there has been no changes made to my build recently and its all been operating for a couple years now no issues morialta-diagnostics-20260829-1007.zip

Okay after data rebuild on that drive its gone back to a similar state, the parity check is flagging some errors so I could run the full parity check, the drive is also showing over 2000 device errors on the main array page: morialta-diagnostics-20260829-0752.zip

That's excellent news, okay I will attempt to rebuild on the same disk, if it has the issue again after that I will replace the disk. Emulated contents looks fine, theres less stuff on this disk that I'm concerned about which helps :) Thanks so much to you all for the excellent support and responsiveness, its really appreciated!

Apologies for missing that detail, have applied the fixes and restarted into normal mode, please find new diagnostic logs, Disk 3 is still showing with a red cross. morialta-diagnostics-20260827-2352.zip

Sorry it was the updated diagnostics you asked for, attaching here. morialta-safemode-diagnostics-20260827-2332.zip

Thanks for the super quick reply, I have done that now and its found corruption, should I click the button labeled "Fix" CheckFilesystemStatus.txt

Hi there, Just seeking some advice on the best way to proceed with an error that has just popped up on one of my disks in my array, I got an alert from Unraid at 4:39am yesterday (while I was sleeping) that Disk 3 was in error state, upon looking the error is File system status: Unmountable: wrong or no file system, when I noticed the error I went in and tried to run a SMART diag, but that failed to start, so I figured the next best thing was to give the server a reboot incase something clears the error, but that did not. I have since run a short SMART check since the reboot and that's passed with no issues, running an extended SMART check now. I also can't say what could have caused this to occur in the wee hours of the morning, would it be safer to replace the disk in this scenario (early signs of drive failure?) or could this be something that's corrupted on that drive? Diagnostics attached. morialta-diagnostics-20260827-2149.zip