Current status:

Web GUI is not responding at all,cant even connect a telnet session

Disk 4 is not mounting

 

I've just upgraded from 6.1.9 to 6.2.1.

I've also just updated all plugins,including Dynamix

At first all was well after upgrade, all performing well, in fact the web GUI seemed more responsive than normal.

One day later suddenly webgui not responding.

SSH still working

Responding to ping requests

Shares were working, but now seem to have stopped

 

Unfortunately I've rebooted since initial problem - didnt realise syslog doesnt auto archive (learnt my lesson now!)

syslog attached

syslog.zip

You've got some corruption on disk #4 which may be the cause.  Check Disk Filesystems

 

Also, just uploading the diagnostics file (type diagnostics at the prompt) would be preferred over you logging all of those files....

i've been running xfs_repair all night,nothing seems to be happening. Do I need to stop the array first? How do I do that from cli?

 

Attached full diagnostics

go-unraid-diagnostics-20161017-0857.zip

Sorry,other thing I should make clear is that the webgui stopped responding a day (and a reboot) before the shares stopped working.

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

 

change startArray="yes" to "no"

 

Then start in maintenance mode and run xfs_repair

 

 

Thanks, thats got it.

 

The was a problem on disk 4.

 

Curious that a corruption on a data drive would stop the web gui from working.

 

One followup question, where do I find the lost+found dir created by xfs_repair?

Hi all,

I had the same problem this morning (can't mount disks).

I changed the disk.cfg file for no autostart

Now, I'm able to boot in the GUI with the array in maintenance mode

 

Here is what I gen when I run the xfs_repair status command with -nv in the option field

 

 

 

 

After that I proceeded to the disk repair by running again the xfs_repair status command with the option field blank and I got this error message... and I don't know what to do next...

 

I need some help from you guys!

thanks

 

 

 

As it says, just use the -L option in the option box and run it again.  That should fix it!

As it says, just use the -L option in the option box and run it again.  That should fix it!

 

Thanks a lot! This solved my problem...

I was just afraid of running this command because of the last sentence... now everything is back to normal!