So, the upgrade to Plus may or may not have anything to do with it.  Here is what happened. 

 

I had been using Unraid basic with an old Flash drive for about a week.  Rebooted at least 10 times in that week.  For all intents and purposes it was pretty rock solid.  I decided to get a new flash, and upgrade to Plus. 

 

I had some issues getting the new flash to work right, but when I finally did it seemed to work.  The first time it booted successfully, the array wouldn't start for about 5 minutes, then it wanted to re-check parity.  I thought, OK maybe thats normal.  And it worked fine after that.  That was on Sunday.

 

I rebooted the server at least once or twice between Sunday and Wednesday.  Moved about a terabytes worth of stuff to it.  Wednesday morning before work, I purchased my unraid plus key, and by that evening(tonight), I had the key waiting for me in my inbox. 

 

I copied the key up to the flash.  When I went to stop the array before power down, it came up saying that it wanted to reformat, but that I wouldn't lose any data.  It hadn't done this before but as someone who is used to working with Windows, the word Format scared me.  So I hit the power down button, thinking that if it still wanted to do that after reboot, I would worry about it then.  Haven't been able to bring the array back up since.  On the Main screen it just says starting.  I waited once on this screen for about an hour, before deciding to reboot manually.  This may have been a mistake, but I never saw any drive activity lights twinkle. 

 

I'm now on the second reboot.  Web interface is still the same, Command Area just says Starting....  Its been about 3 hours.  1 difference is that I do see drive lights twinkling every so often now. 

 

What should I do?  Are there any telnet or console commands I can type in to see what the thing is actually doing right now. 

Did a little digging on this forum.  Came across this command to see what the unraid is doing.

 

tail -f /var/log/syslog

 

Here is the output so far  (by the way, I renamed my server from tower to unraid)

 

Mar  5 01:49:14 unraid last message repeated 60 times

Mar  5 01:50:15 unraid last message repeated 60 times

Mar  5 01:50:53 unraid last message repeated 38 times

Mar  5 01:50:53 unraid in.telnetd[1408]: connect from

)

Mar  5 01:50:54 unraid emhttp[1115]: synchronizing wit

Mar  5 01:51:23 unraid last message repeated 29 times

Mar  5 01:51:24 unraid login[1409]: ROOT LOGIN  on `pt

Mar  5 01:51:24 unraid emhttp[1115]: synchronizing wit

Mar  5 01:51:55 unraid last message repeated 30 times

Mar  5 01:52:56 unraid last message repeated 61 times

^H

Mar  5 01:53:57 unraid last message repeated 60 times

 

 

Mar  5 01:54:58 unraid last message repeated 61 times

Mar  5 01:55:59 unraid last message repeated 60 times

Mar  5 01:57:00 unraid last message repeated 60 times

Mar  5 01:58:01 unraid last message repeated 61 times

Mar  5 01:59:02 unraid last message repeated 60 times

Mar  5 02:00:03 unraid last message repeated 60 times

Mar  5 02:01:04 unraid last message repeated 61 times

Mar  5 02:02:05 unraid last message repeated 60 times

Mar  5 02:03:06 unraid last message repeated 61 times

Mar  5 02:04:07 unraid last message repeated 60 times

Mar  5 02:05:08 unraid last message repeated 60 times

 

 

I just stopped and powered off the array from telnet.  I've rebooted and I think the tail command is giving me some better info now. 

root@unraid:~# tail -f /var/log/syslog

Mar  5 02:12:39 unraid kernel: [  73.013377] ReiserFS: md2: Using r5 hash to so

rt names

Mar  5 02:12:39 unraid kernel: [  73.013462] ReiserFS: md1: Using r5 hash to so

rt names

Mar  5 02:12:39 unraid kernel: [  73.123234] can't shrink filesystem on-line

Mar  5 02:12:39 unraid kernel: [  73.173187] can't shrink filesystem on-line

Mar  5 02:12:39 unraid emhttp[1116]: shcmd (13): mkdir /mnt/user

Mar  5 02:12:39 unraid emhttp[1116]: shcmd (14): shfs /mnt/user 0

Mar  5 02:12:39 unraid ifplugd(eth0)[1096]: Executing '/etc/ifplugd/ifplugd.acti

on eth0 up'.

Mar  5 02:12:39 unraid ifplugd(eth0)[1096]: Program executed successfully.

Mar  5 02:12:51 unraid in.telnetd[1203]: connect from 192.168.0.52 (192.168.0.52

)

Mar  5 02:13:17 unraid login[1207]: ROOT LOGIN  on `pts/0' from `192.168.0.52'

Mar  5 02:15:10 unraid shfs: make_link: symlink: No space left on device

Mar  5 02:15:10 unraid emhttp[1116]: synchronizing with shfs...

Mar  5 02:15:41 unraid last message repeated 31 times

Mar  5 02:16:42 unraid last message repeated 60 times

Mar  5 02:17:43 unraid last message repeated 61 times

Looks like an issue with user shares.  Plug your flash into a PC and delete the file 'config/share.cfg'.  Then plug back into server and reboot.  System should come up with user shares disabled - see if this improves start up time.  If so, we'll have to analyze what's happening with your user shares.

Sure enough.  The array came up when I removed the share.cfg file.  Of course, my shares were gone.  Then when I put it back, the array wouldn't start again.  Here is the contents of the file.

 

# Share settings

shareFlash=eh

shareDisk=eh

shareUser=e

shareSecurity=none

How much RAM do you have?

 

Also it might be more efficient to troubleshoot this via email (and then we can post the final outcome here).

 

[email protected]