Recently I've had a disk that is no longer mountable. The drive is pretty new ~1 year old and has worked fine up till now. Anyone mind taking a look and seeing what the problem could be? tower-diagnostics-20210921-1807.ziptower-diagnostics-20210921-1807.zip Thank you!

Your diagnostics are not working. Try again.

Sorry aboot that. Here are the diagnostics.

tower-diagnostics-20210921-1807.zip

Looks like disk5 was already unmountable when you booted up, and syslog restarts when you reboot, so can't see anything from before that to see what might have happened. You will have to repair its filesystem.

 

Disk2 is disabled. Why didn't you mention that? How long has it been disabled? Since you have only single parity, you haven't had any parity protection since disk2 became disabled. You will have to rebuild it.

 

Why are you still using ReiserFS?

 

Also, your docker.img is unnecessarily large at 50G, and your system share has files on the array.

Yeah sounds like my whole server is a mess atm. I'm waiting on a replacement for disk 2 from WD. Thanks I'll look into those other problems.

Do you know how to do the repair of disk5 and the rebuild of disk2?

4 minutes ago, zer0vash said:

waiting on a replacement for disk 2 from WD

Doesn't really look like anything is wrong with the original disk2, You could just rebuild it to itself. It is somewhat safer though to rebuild to another disk and keep the original in case there are problems with rebuild.

I've had issues with disk 2 since I got it, unfortunately.   Pre clear gave errors and this is the third time its just failed on me like this. I shouldn't have used it from the start. I am not sure about how to do these other things but it sounds like I should get disk 2 going first.

1 hour ago, zer0vash said:

issues with disk 2 since I got it

SMART attributes for it looks OK, though it hasn't had an extended SMART test run on it in a while.

 

Connection or cable to SATA or power (or splitter) are much more common reasons for a disk to become disabled than an actual disk failure.

 

If Unraid can't write to a disk for any reason, it emulates the write by updating parity and disables the disk since it is now out-of-sync.

 

After a disk is disabled, it isn't used again until rebuilt. Reads from the disk are emulated from the parity calculation by reading all other disks, and writes to the disk are emulated by updating parity as it would have been based on the data written.

 

The only way to recover those writes and get the disk back in sync and enabled again is to rebuild it from the parity calculation by reading all other disks and writing the result back to the disk.

 

https://wiki.unraid.net/Manual/Storage_Management#Drive_shows_as_unmountable

 

https://wiki.unraid.net/Manual/Storage_Management#Replacing_failed.2Fdisabled_disk.28s.29

And emulated disk2 is mounted so you should be able to see its files and read and write the emulated disk. Even if you removed the physical disk2 the emulated disk2 would still work since the physical disk is disabled and isn't being accessed anyway.

From diagnostics it looks like you already have a lost+found share, which would have been created from a previous filesystem repair. Have you checked the contents of lost+found?

 

Often not worth the trouble to try to make any sense of its contents. Repair couldn't figure out what to do with that data so it put it in lost+found, often with no idea of what files belong in what folders, or even what the names of the files and folders are.