I've  been using unraid since last summer and up to today was running 5.0-rc8a. Last night the filesystem became inaccessible. I tried to reboot the server but when I ran sync it just hung. I gave up trying to unmount everything and just ran reboot and even that didn't work. In the end I had to run reboot -fn to get it to restart.

 

When the server came back up everything seemed to be working again, a parity check started and I could access my files again. I did notice that my mysql database had become corrupt so I restored that from a backup (I do daily backups at 2am and the first problems seemed to start at 2:30 so that was quite lucky). Everything was running fine for about an hour and then the same happened again. I have transmission running and its web api became inaccessible. If I try to use transmission-remote it just times out. I also can't kill the process with kill -9. lsof shows that tranmission-deamon still has files open. I then tried to reboot again and the same happened where sync hangs. ctrl-c wouldn't work to cancel it.

 

I then saw that I was a few version behind and upgraded to 5.0-rc12a and the same thing keeps happening.

 

I do have some SMART errors on one drive

*ERROR* - Current_Pending_Sector it is now 14 (error threshold is 5)

WARNING - Power_On_Hours it is now 21584 (warning threshold is 20000)

WARNING - Offline_Uncorrectable it is now 2 (warning threshold is 1)

*ERROR* - UDMA_CRC_Error_Count it is now 154 (error threshold is 75)

 

I don't know if this has anything to do with it though.

Disable ALL add-ons, reboot

Then ... follow the instructions from the general support forum and attach a zipped syslog to your next post.

Then ... perform a file-system check on all /dev/mdX devices as per the wiki

Then ... fix the issue with noise pickup on the data cable to the drive with CRC errors

Then ... deal with the un-readable sectors on the disk with sectors pending re-allocation.

 

If you have so many issues you cannot stop add-on process, do NOT re-start them after rebooting.

 

Joe L.

 

You should fix the cable issue first. The file systems may not respond correctly to reiserfsck if there are lower layer issues.. The disk surface needs to be pristine before you start fixing the data it contains.

 

Start from the bottom and work your way up: cables, pending sectors, then file systems.

 

See my sig to disable add-ons and then post a zipped syslog collected at least 30 minutes after the system is started.