I've just upgraded my system from RC5 to 5.0 and it's very flakey. When I say upgrade, I actually backed up my flash drive, then formatted it and installed a fresh copy of 5.0. Then I copied my config directory to the flash drive over writing what was on the flash.

 

The Web GUI stops responding, as well as SABNZBD and I can't get SickBeard to work at all now (questions for another thread I fear). When it is responding if I attempt to stop the array it hangs and never stops. attempting to stop the array from the command line doesn't seem to work either. I can't umount the drives and fuser reports an error. If I try to stop mdcmd I get an invalid argument error. Then finally if I try to reboot (shutdown -r -t secs: now) it kicks me off telnet but I don't think it's actually rebooting. I can't see the output from the unRaid box as there's no monitor hooked up.

 

Any ideas?

These sound like add-on issues. Try a clean install with the default config directory. Add only your key file. The shutdown command you've shown is not correct. It looks like a malformed Unix command. Linux does not have -t option and the word "sec" is replaced with a number in Unix. It should read "shutdown -r now".

Well the command I typed doesn't throw and error, it says System is going down now but then nothing appears to happen. If you type shutdown and press enter, -t is one of the options and secs: now is and example. I've used it before on other linux systems.

 

What does the key file do? Will I use any of the other configuration?

You are correct about the -t option but the variable "secs" should be replaced with a number, e.g. "-t 10". The -t option is not required in any case.

Well either way I know it's worked previously.

 

What about the key file?

Here's the command line output if I follow the guide on halting the system.

 

root@Tower:/boot/config/plugins# /root/samba stop

root@Tower:/boot/config/plugins# fuser -mvk /mnt/disk1         

Cannot stat /mnt/disk1: No such file or directory

Cannot stat /mnt/disk1: No such file or directory

Cannot stat /mnt/disk1: No such file or directory

root@Tower:/boot/config/plugins# fuser -mvk /mnt/disk2

Cannot stat /mnt/disk2: No such file or directory

Cannot stat /mnt/disk2: No such file or directory

Cannot stat /mnt/disk2: No such file or directory

root@Tower:/boot/config/plugins# fuser -mvk /mnt/disk3

Cannot stat /mnt/disk3: No such file or directory

Cannot stat /mnt/disk3: No such file or directory

Cannot stat /mnt/disk3: No such file or directory

root@Tower:/boot/config/plugins# umount /dev/md1

umount: /dev/md1: not found

root@Tower:/boot/config/plugins# umount /dev/md2

umount: /dev/md2: not found

root@Tower:/boot/config/plugins# umount /dev/md3

umount: /dev/md3: not found

root@Tower:/boot/config/plugins# /root/mdcmd stop

/root/mdcmd: line 11: echo: write error: Invalid argument

root@Tower:/boot/config/plugins# shutdown -r now

 

root@Tower:/boot/config/plugins# Broadcast message from root (pts/0) (Tue Nov 12 19:15:48 2013):

 

The system is going down for reboot NOW!

How I can't access the system, although it is responding via telnet.

It can take a while to shutdown and the system my not completely shutdown depending on the MB. The key file enables plus or pro version. The basic version does not require a key file. Can you still connect via telnet?

Yes it's just come up and I've managed to shut it down cleanly this time. First time in ages.

 

I have 3 disks and a parity disk so I'll copy the key file. Do I need to backup anything else before I reinstall?

Just make a note of the parity drive serial number. See here: http://download.lime-technology.com/dnld/beta/unRAIDServer-5.0.1-rc1-i386.txt

Thanks I'll give that a try.

OK, reinstalled unRaid but instead of copying the key file alone, I also copied the other config files so I didn't have to set it up from scratch again. I didn't copy over any of the plugins so it's a bare system now. It's decided to do a parity check so I will let it finish doing that before I reinstall any plugins but so far so good.