Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Can't shutdown server, Unix geek requested :)

Featured Replies

;D

 

Soooooo, my Unraid server was up for ~45 days before I went to take it down. We had a bad storm roll through here and I figured I ought to shut all my machines down in case the power failed . I went to the web interface and tried to stop the array but it wouldn't refresh after clicking stop. I had seen this on occasion before and figured I'd have to telnet in and issue a remote "shutdown -h now". It appeared to like the command (issued 5~10 minutes after trying to stop the array via the web) and let me know the system was going down via that telnet session. However, it never shutdown. Power was still on and I was able to still telnet in. I tried a few different variations of the shutdown command but still no luck. I also passed a "/root/samba stop" command and was informed, "No process killed".

 

I took a look at the tail of the syslog and here's what's scrolling:

 

Apr 18 15:42:40 (none) kernel: vs-3050: wait_buffer_until_released: nobody relea
ses buffer (dev 09:01, size 4096, blocknr 7962624, count 3, list 0, state 0x1001
9, page c17e2df4, (UPTODATE, CLEAN, UNLOCKED)). Still waiting (-1920000000)  JDI
RTY !JWAIT

 

Now I'm not sure if that tells you anything (other than the date being wrong  ::) ) but there it is.

 

I'm able to umount all my data drives except for /dev/md1, which is my parity drive. Umount tells me the drive is busy. I'm going to assume for a minute that's why it won't shutdown. A google search revealed a couple of cool alternatives to fix that but either the command didn't exist in this flavor of Unix or it just didn't work. Incidentally, I tried to kill a few of the processes but most wouldn't die (kill -n PID, right?). Here's my process list:

 

root@(none):~# ps -e
  PID TTY          TIME CMD
    1 ?        00:00:06 init
    2 ?        00:00:00 keventd
    3 ?        00:00:55 ksoftirqd_CPU0
    4 ?        00:01:49 kswapd
    5 ?        00:00:03 bdflush
    6 ?        00:04:51 kupdated
    9 ?        00:00:00 khubd
   15 ?        00:00:00 usb-storage-0
   16 ?        00:00:00 scsi_eh_0
   66 ?        00:00:03 syslogd
   69 ?        00:00:03 klogd
  244 ?        00:00:00 scsi_eh_1
  245 ?        00:00:00 scsi_eh_2
  246 ?        00:00:00 scsi_eh_3
  247 ?        00:00:00 scsi_eh_4
  261 ?        00:00:00 scsi_eh_5
  262 ?        00:00:00 scsi_eh_6
  917 ?        00:00:00 inetd
  923 ?        00:00:00 crond
  926 ?        00:00:00 acpid
  939 ?        00:00:00 emhttp
  947 ?        00:00:00 ifplugd
  957 ?        00:00:00 mdrecoveryd <defunct>
  976 tty1     00:00:00 agetty
  977 tty2     00:00:00 agetty
  978 tty3     00:00:00 agetty
  979 tty4     00:00:00 agetty
  980 tty5     00:00:00 agetty
  981 tty6     00:00:00 agetty
  982 ?        00:16:17 mdrecoveryd
  997 ?        00:00:00 emhttp
1020 ?        00:00:00 emhttp
1116 ?        01:04:09 unraidd
1157 ?        00:00:00 kreiserfsd
26859 ?        2-04:18:09 smbd
27750 ?        00:00:00 smbd
27773 ?        00:00:00 smbd
27775 ?        00:00:00 smbd
27777 ?        00:00:00 smbd
27779 ?        00:00:00 smbd
27780 ?        00:00:00 smbd
27781 ?        00:00:00 smbd
28541 ?        00:00:00 shutdown
28542 ?        00:00:00 shutdown <defunct>
28566 ?        00:00:00 shutdown
28567 ?        00:00:00 shutdown <defunct>
28699 ?        00:00:00 shutdown
28700 ?        00:00:00 shutdown <defunct>
28765 ?        00:00:00 shutdown
28766 ?        00:00:00 shutdown <defunct>
28769 ?        00:00:00 bash
28820 ?        00:00:00 shutdown
28821 ?        00:00:00 shutdown <defunct>
29179 ?        00:00:00 in.telnetd
29181 ttyp7    00:00:00 bash
29233 ttyp7    00:00:00 bash
29238 ?        00:00:00 sync
29241 ttyp7    00:00:00 ps

 

So other than just pulling the cord, is there any graceful way to shut it down from here? Any help would be greatly appreciated.

 

Thanks,

 

Ryan

P.S. I'm runnign the last stable release of Unraid 3.0.

 

 

pretty sure there was a "stop" command in 3.0 that could be run when you log in as root.

 

So, log in and type

stop

 

It is a shell script that issues the following commands, so if it does not exist, just type these commands in turn.

samba stop

sync

umount /mnt/disk1

umount /mnt/disk2

umount /mnt/disk3

umount /mnt/disk4

umount /mnt/disk5

umount /mnt/disk6

umount /mnt/disk7

umount /mnt/disk8

umount /mnt/disk9

umount /mnt/disk10

umount /mnt/disk11

umount /mnt/disk12

umount /mnt/disk13

mdcmd stop

 

Then type "poweroff"

 

That should shut down Linux, although I don't think it turns off the power supplies on 3.0... that you will need to do on your own.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.