Hello guys,

 

It's been a long day today, I've been trying for hours to find out what's going on with my unRaid box but I'm unable to. I will try to give as much info as I can but what's happening is very very weird!

 

I've been running unRaid 6.3.2 since its release with no issues at all. Today I was cleaning out some files in my disks and found out that I had a "Dropbox" folder from an old Dropbox docker I installed a few months ago. As this folder was using lots of GB I decided to delete it with MC, after a bit it seems like the remote terminal (through my mac with ssh) crashed so I tried to restart unRaid but it became unresponsive... so I had to force reset

 

After the reset everything is screwed. I can boot the flash drive in gui mode but I can't access the web interface (not even locally) but typing 

ps aux | grep -i emhttp

returns what you can see on this image (Terminal screenshot), however I get an infinite "Connecting" state in the browser tab (not getting error though). I tried to boot the flash in another PC and it boots up fine

 

I've also tried disconnecting all the disks in the unRaid box except the cache SSD and I'm able to get into the web interface but I can't do much as all my disks are disconnected so I can't mount the array.

 

This is interesting: then I tried to connect one drive at a time and boot to see if I'm able to get into the web interface. I found out one of the disks (I have 4) was, presumably the reason of the problems. So disconnected that one, booted up with the other 3 disks, I was able to click on start array and again it crashes/become unresponsive. Now I'm basically when I started.

 

I'm will now try to disconnect all the disks and boot again to see if I can get the web ui to download the diagnostics

 

BTW, I have been doing all this through the gui boot mode, I can't access the web server from another PC, not even through SSH (SSH is up but it's not accepting the password O_O). I've also tried to use xfs_repair on /dev/md2 but again it looks like it was just unresponsive

 

Also tried to copy files from "previous" folder on the flash drive to see if that would help but no luck either >_<

 

Anyone got any ideas on what I can do/test/try? I'm totally clueless. Thanks!

Edited March 22, 20179 yr by bluepr0

I was able to boot and access the web ui with only 1 disk connected (parity) at least I can download the diagnostic

unbeast-diagnostics-20170322-1759.zip

I went ahead and re-installed from ground up unraid on the flash drive, booted a new fresh unraid and set up disks as per the screenshot I took. Clicked on start array and it got unresponsive with the "Mounting disks..." message at the bottom... I'm just not sure what else I can do

 

Screenshot http://d.pr/i/K7AA/FPvlzynm

1 hour ago, bluepr0 said:

"Mounting disks..." message at the bottom

 

Probably a file system problem, can you use the console, if yes get the diags by typing diagnostics, they will saved on your flash.

thank you! Im uploading the new diagnostics

tower-diagnostics-20170322-1435.zip

I can see some weird stuff on the logs, is it a problem with the filesystem? a kernel panic? any way to fix it?

File system issues on disk2 (md2), see here:

 

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

I actually executed this when doing my first tests xfs_repair -v /dev/md2 but I dont get any feedback or progress, feels like it becomes unresponsive

 

Thanks a lot, btw!

Edited March 22, 20179 yr by bluepr0

7 minutes ago, bluepr0 said:

but I dont get any feedback or progress

 

This happens if array is not started in maintenance mode.

3 minutes ago, johnnie.black said:

 

This happens if array is not started in maintenance mode.

oh I see, so as I cant  start the array in maintenance through console I guess I should leave the command until it returns the prompt again and hopefully restarting should work?

You already have array autostart disable, so you'll need to reboot and start the array in maintenance mode.

umm but is there a way to do it through console? because I can't access the web ui to start the array in maintenance mode

powerdown -r

 

If may not work, if it doesn't you need to do a hard reboot,

thanks a lot! everything is up and running again!