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

According to the diagnostics the disk was disabled (has a red ‘x’ icon?) because a write to it failed. To clear the disabled state the normal process is to rebuild the disk. However before doing that run a check filesystem on disk3 and post the diagnostics after doing that and restarting the array in Normal mode. We need to decide if a rebuild is the best action to take at this point.

It also looks like you may have one or more docker containers continually crashing and restarting. Look at the uptime for your containers on the Docket tab to identify the culprit(s).

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

CheckFilesystemStatus.txt

Sorry it was the updated diagnostics you asked for, attaching here.

morialta-safemode-diagnostics-20260827-2332.zip

What we really needed was the Diagnostics with the array started in Normal (not Maintenance) mode. SAFE mode isn't relevant in this case, but Maintenance mode means no filesystems are mounted, so we can't see whether any disks need filesystem repair.

But apparently, at least that one filesystem does need repair, so go ahead and click FIX.

Then start the array in Normal (not Maintenance) mode and posts new diagnostics.

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

The emulated disk is mounting which is a good sign the fix worked, browse the contents and ensure the data looks correct.

You would then need to rebuild onto either the same disk OR a new disk.

The SMART report for the disabled disk looks ok to me.

Edited Thursday at 02:43 PM5 days by MowMdown

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!

Edited Thursday at 11:13 PM4 days by lukeg

Doesn't look like repair created any lost+found, so that's good.

But your config/shares folder is a mess with a lot (162) of cfg files for shares that no longer exist. Probably you accidentally created a lot of shares at some time in the past. Go to User Shares page and click CLEAN UP at the bottom.

Also, after you rebuild disk3, your system share has files on disk1. Nothing can move or delete open files, so you will have to go to Settings - Docker and disable it before you can move those to cache. And mover won't overwrite files so if they are duplicates you will have to delete them.

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 drive disconnected as sdc and is now Unassigned Device sdh. Looks like it disconnected after rebuilding for about 9 hours. Emulated disk3 is mounted.

SMART for the drive looks OK. Check connections, both ends, data and power, including splitters, maybe try another cable.

Each plug must sit squarely and firmly on the connection, with no tension in the cables. Don't bundle data cables.

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

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

Edited Saturday at 01:41 AM3 days by lukeg

Have you done memtest recently?

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

Ran memtest86+ for just over 5 hours and no issues were encountered, memory passes.

morialta-diagnostics-20260829-1657.zip

Edited Saturday at 07:29 AM3 days by lukeg
Adding latest diagnostics

No ATA errors so far, check filesystem on both emulated disks.

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:

Click the zero log button.

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

That is expected, if contents for the emulated disk look correct and the cables have been replaced, you can try rebuilding on top:

https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

It looks like the second rebuild has worked successfully, thanks so much all for your help!

On 8/28/2026 at 12:34 PM, trurl said:

Also, after you rebuild disk3, your system share has files on disk1. Nothing can move or delete open files, so you will have to go to Settings - Docker and disable it before you can move those to cache. And mover won't overwrite files so if they are duplicates you will have to delete them.

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

Edited yesterday at 11:08 AM1 day by lukeg

If they are duplicates it should already be using the system files on cache. Do they have the most recent timestamp?

domains share has files on disk1 also. VMs will perform better if those are on pool such as cache, if your vDisks aren't too large to put there.