Hello.  Im running 6.3 and woke up the other day to an unresponsive web GUI.  Network shares weren't working as well.  I sshd into the machine and noticed there was no /mnt/user directory which leads me to think the array isn't started.  I noticed in the logs it was complaining about /mnt/disk 13, but a faulty disk shouldn't stop the server from working.  right?  There were also some other xfs errors in there will a stack trace.  I restarted the machine and encountered the same result.  ssh works, but no GUI, nor array.  I'll attach my diagnostics.zip file. 

 

Any help would be appreciated!

jabba-diagnostics-20170208-1535.zip

6.3.0 has a bug that prevents SMART from getting saved to your diagnostics. Download 6.3.1 and replace the bz* files to upgrade.

 

If it still doesn't work try booting in GUI mode.

 

You have filesystem corruption on disk13 but we will should get a better diagnostic and a webUI if possible before trying to work on that.

ok. I upgraded to 6.3.1.  Same behavior.  I can boot to the GUI mode, but the firefox page never shows anything, just spins waiting, really rendering it no more useful than the normal boot.

 

I'll attach the diagnostics from 6.3.1

jabba-diagnostics-20170208-2104.zip

Disable array autostart by editing disk.cfg on your flash drive (in the config folder):

 

change startArray="yes" to "no"

 

Then check filesystem on disk13:

 

https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS

Sorry no real help but wanted to let you know you are not alone, I just went back down to unRAID 6.2.4 and gonna wait a little while 6.3 spun up but same issue no shares, and slow GUI. It must be my OLD hardware as the release notes put it. I built this server to run ESXi and it ran fine but decided to run unRAID as the base and liking it so far. I want to see how you go on the fix please keep us posted! Thanks

Sorry no real help but wanted to let you know you are not alone, I just went back down to unRAID 6.2.4 and gonna wait a little while 6.3 spun up but same issue no shares, and slow GUI. It must be my OLD hardware as the release notes put it. I built this server to run ESXi and it ran fine but decided to run unRAID as the base and liking it so far. I want to see how you go on the fix please keep us posted! Thanks

 

The OP's problem has nothing to do with v6.3 but with file system corruption on one of the disks.

I turned off auto array start and restarted the server.  That allowed the GUI to start. I started the server in maint mode.  ran [pre]xfs_repair -v /dev/md13[/pre]It quickly exited complaining "The filesystem has valuable metadata changes in a log which needs to be replayed.  Mount the filesystem to replay the log, and unmount it before re-running xfs_repair".  I found an earlier thread you replied to saying "You need to run xfs_repair with -L, usually there's no data loss."  I then ran [pre]xfs_repair -v -L /dev/md13[/pre]After about 5 minutes it completed successfully with no apparent errors or recommended action.  I started the array and it's currently doing a Parity-Sync / Data Rebuild.  Hopefully that was the next step   If that completes successfully in the next day or two, i'll mark the thread solved.

 

Thank you so much for your help!!!!!

I turned off auto array start and restarted the server.  That allowed the GUI to start. I started the server in maint mode.  ran [pre]xfs_repair -v /dev/md13[/pre]It quickly exited complaining "The filesystem has valuable metadata changes in a log which needs to be replayed.  Mount the filesystem to replay the log, and unmount it before re-running xfs_repair".  I found an earlier thread you replied to saying "You need to run xfs_repair with -L, usually there's no data loss."  I then ran [pre]xfs_repair -v -L /dev/md13[/pre]After about 5 minutes it completed successfully with no apparent errors or recommended action.  I started the array and it's currently doing a Parity-Sync / Data Rebuild.  Hopefully that was the next step   If that completes successfully in the next day or two, i'll mark the thread solved.

 

Thank you so much for your help!!!!!

If the disk was disabled, then you were repairing the emulated filesystem. It is rebuilding the fixed filesystem to the disk, which will enable the disk again.

I assume he's rebuild disk12, that was the disable, disk13 was ok.

I assume he's rebuild disk12, that was the disable, disk13 was ok.

That makes sense.

 

tjiddy, if you look at Main - Array Devices, you should see a lot of writes to the disk that is being rebuilt, and a lot of reads from all other disks.

Yep, it looks like it's rebuilding disk 12