My unRaid 4.5.6 installation currently seems to be stuck attempting to power down.  Here is how the issue came to be:

 

After setting up my data drives, I installed a parity drive.  After several days, I ended up doing a forced reboot (I don't remember the circumstances now - I think it may have been a networking setting change).  Everything seemed to be working fine for a little while after that, but then I lost connectivity to the array (via web, telnet, and samba), so I forced another reboot.  On the resulting boot, a parity check was of course begun, but I attempted to cancel that from the web interface.  That's when things started to get really problematic.  I lost access to the web interface, and when I telneted in, some commands did not seem to run properly (I could not list some directories, I could not kill any processes in an attempt to do a semi-clean reboot)  I did yet another forced reboot, after which the array was stuck at "Starting..." according to the web interface.  When I telneted in, I saw that the unraidd and mdrecoveryd processes were actively doing something, so I allowed that to go on.  Eventually, the syslog (attached) showed that a sync had been completed.  I then refreshed the web interface, but it still said the array was starting.  I invoked the powerdown command (I've installed the clean powerdown through unmenu), but the system has not powered down.  The top command doesn't seem to show any processes taking up any CPU%.

 

I'm at a loss as to how to get the system to cleanly power down at this point.  I realize I may have made several mistakes, so I'm holding off on another forced reboot for now.  Any suggestions on what I could do next?

 

By the way, I have one telnet window left open (new connections fail).  Hooking up a monitor and keyboard would be difficult, but I could do it if necessary.

syslog.txt

My installation was also stuck "Starting..." and in fact was stuck in that position for 14 hours. Stupid. I noticed that the Read number on each of my discs was increasing so I figured it was doing something and I would let it run it's course. Turns out the problem was a few plugin's I'd installed from here:

http://lime-technology.com/forum/index.php?topic=14760.0

 

A ps -ef revealed that there were some processes trying to start, first one sick beard plugin. I killed them. Then couch potato, I killed them too - then badda bing, the array came online. Lame!