Hey guys, i have run into a bit of a problem after my server crashed last night.

 

I was copying some files around the machine froze and on reboot i went to restart the array and perform a parity check but my disk 2 showed the error Unmountable: No File System. After searching the forums i found the thread below, This looked like the same problem as i was having with file system corruption, i ran the xfs repair and rebooted but to no avail.

 

After powering the box back up this morning it appears as if unraid is treating this drive as a faulty drive now with the old contents being emultated by the parity drive? I dont want to try anything more until i get an idea of what has happened.

 

Cheers for any assistance guys, all a bit stressful!

unraid-diagnostics-20180408-1116.zip

Edited April 12, 20188 yr by nine

There are many, many threads around about repairing filesystems, and though the general idea is the same, the specifics can be somewhat different. So your explanation that you followed that thread isn't really that much of a clue about what you did. Can you tell us exactly what you did to repair?

 

For many issues in unRAID, rebooting can't really change anything. And anything that happened before the reboot is gone from the diagnostics.

 

The usual advice would be to repair the filesystem of the emulated disk then rebuild the disk, or rebuild the disk then repair the filesystem. So it would help a lot if you could tell us in detail exactly what you already did to repair.

 

 

 

 

 

 

Thanks for the quick reply trurl.

 

After the machine froze on reboot when I tried to start the array for the parity check disk 2 had unmountable: no file system.

 

I stopped the array and jumped on the above thread and found I had the same error in the logs saying 

/mnt/disk2 mount error: Unsupported partition layout

I then restarted the array in maintenance mode and ran the xfs -L which appeared to go through correctly. Being late at night I shut down and rebooted to the above images.

 

Im out at the moment but can attach the old Diag from when I performed the xfs repair when I get home.

 

 

Thanks again!

Edited April 8, 20188 yr by nine
Edit

Attatching the two diags from last night. first being when trying to mount and getting error, second being after i ran the xfs -L

 

 

Cheers! 

01.unraid-diagnostics-20180407-2053.zip

02.unraid-diagnostics-20180407-2114.zip

On the final part of the log you unassigned disk2 and started the array, the emulated disk2 mounted correctly, you now just need to rebuilt it.

Thanks for the reply, that is good news. 

 

Do you think the corruption would be due to the system crashing or more so the drive failing, or a combination?, as now the disk is being flagged as failing smart status due to Reported Uncorrect. A bit of a worry as the drive is only from Jan this year.

 

I think i will purchase a new drive tomorrow and rebuild to that, i dont want to risk trouble like this again =(

31 minutes ago, nine said:

Do you think the corruption would be due to the system crashing or more so the drive failing, or a combination?, as now the disk is being flagged as failing smart status due to Reported Uncorrect. A bit of a worry as the drive is only from Jan this year.

Never a good sign, especially for a new drive.

 

31 minutes ago, nine said:

I think i will purchase a new drive tomorrow and rebuild to that, i dont want to risk trouble like this again =(

That's sensible, keep the old disk intact for now just in case it's needed.

Just to wrap my problem up, i am now back up and running.

 

I ended up purchasing 2x10tb iron wolfs that should be a bit more suited for my build. Due to my Parity drive being 8tb i followed the quick guide in performing a swap disable, which ends up using that parity drive as a replacement for my above failed drive.

 

Day or two later now and its all done with all my data restored,  thanks turl & johnnie for the assistance.