October 11, 201411 yr Author I have your APC plugin installed. If I am not mistaken, unRAID has powerdown installed by default, correct? If so what are the differences with this plugin? The difference is that this plugin saves logs to the flash drive, gives more control with start and stop scripts (K and S), and does not have the tendency to get in the unmounting loop when some process is preventing an unmount. If you can shut down and re-boot or power off from the webgui, you really don't need this plugin unless you want some of the features of the plugin. The OP has more information.
October 11, 201411 yr I have your APC plugin installed. If I am not mistaken, unRAID has powerdown installed by default, correct? If so what are the differences with this plugin? The difference is that this plugin saves logs to the flash drive, gives more control with start and stop scripts (K and S), and does not have the tendency to get in the unmounting loop when some process is preventing an unmount. If you can shut down and re-boot or power off from the webgui, you really don't need this plugin unless you want some of the features of the plugin. The OP has more information. I was doing some php testing the other day and had removed most my plugins including this one. Needless to say emhttp didn't crash but was unresponsive. I stopped my vm's manually and used unraid's built in powerdown. Rebooted to a parity check. I forgot I had docker installed but no dockers. So that was probably it. But I won't uninstall this again . And thanks for all your work on powerdown and apcupsd.
October 12, 201411 yr Author A new powerdown plugin is available. The powerdown package has not changed. I put the emhttp files in a bundle and changed the icon to be compatible with the Dynamix black theme.
November 23, 201411 yr Author The powerdown plugin has been updated. The plugin installed the powerdown package in the wrong order and the powerdown events got clobbered. The events are the K and S scripts. Only the plugin has changed.
November 24, 201411 yr Author Powerdown 2.13 is available. I found there were some issues with the K and S scripts. These have been fixed. I also added additional script processing for the stopping_svcs event that is ahead of the unmounting event. I have a VM that refuses to stop properly in the normal shutdown sequence. If I shut down the VM at the stopping_svcs event, the VM will shut down and unraid will shutdown properly. The stopping_svcs scripts are KSV*.
November 25, 201411 yr Powerdown 2.13 is available. thank you for your work on this script. It was invaluable when I could not get a clean shutdown and allowed for troubleshooting that didn't require a parity check every reboot
November 28, 201411 yr Is this a new features ;-) or a bug :-) see the line with usage ... powerdown Powerdown initiated Powerdown V2.12 usage /etc/rc.d/rc.unRAID version|start|stop|status|kill|diag|syslog|update|msg Broadcast message from root@Tower (pts/2) (Fri Nov 28 17:20:41 2014): The system is going down for system halt NOW!
November 28, 201411 yr Author Ok. There was an update issue with 2.12 that is solved in 2.13. You can either reboot, or uninstall powerdown and re-install. Hopefully this will fix it for you. The situation you ran into is a new feature I implemented that executes scripts in the 'stopping_svcs' event of powerdown. The error you see is not a problem.
November 29, 201411 yr Upgrade to version 2.13 went without a glitch, thanks for providing 'powerdown'.
December 4, 201411 yr I had issues with unclean powerdowns when I used 2.12 It occured twice until now. I post the last lines of each log. 1st time Nov 27 17:51:24 Tuerke powerdown[32266]: Powerdown initiated Nov 27 17:51:25 Tuerke powerdown[32270]: Powerdown V2.12 Nov 27 17:51:25 Tuerke rc.unRAID[32272][32273]: Processing /etc/rc.d/rc.unRAID.d/ kill scripts. Nov 27 17:51:25 Tuerke powerdown[32278]: Initiating Shutdown with '' Nov 27 17:51:25 Tuerke shutdown[32279]: shutting down for system halt Nov 27 17:53:02 Tuerke init: Switching to runlevel: 0 Nov 27 17:53:02 Tuerke atd[14550]: Exec failed for mail command: No such file or directory Nov 27 17:53:05 Tuerke rc.unRAID[1564][1565]: Powerdown V2.12 Nov 27 17:53:05 Tuerke rc.unRAID[1564][1570]: Stopping Plugins. Nov 27 17:53:05 Tuerke rc.unRAID[1564][1571]: Running: "/usr/local/emhttp/plugins/cache_dirs/event/unmounting_disks" Nov 27 17:53:05 Tuerke rc.unRAID[1564][1577]: Running: "/usr/local/emhttp/plugins/powerdown/event/unmounting_disks" Nov 27 17:53:05 Tuerke rc.unRAID[1564][1582]: Stopping unRAID. Nov 27 17:53:05 Tuerke avahi-daemon[2916]: Got SIGTERM, quitting. Nov 27 17:53:05 Tuerke avahi-daemon[2916]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.178.157. Nov 27 17:53:05 Tuerke avahi-daemon[2916]: avahi-daemon 0.6.31 exiting. Nov 27 17:53:05 Tuerke avahi-dnsconfd[2925]: read(): EOF Nov 27 17:53:06 Tuerke rc.unRAID[1564][1606]: Killing active pids on the array drives Nov 27 17:53:06 Tuerke rc.unRAID[1564][1609]: /mnt/disk1: 1544c 3283c Nov 27 17:53:06 Tuerke rc.unRAID[1564][1609]: /mnt/disk10: 1561c 3284c Nov 27 17:53:06 Tuerke rc.unRAID[1564][1609]: /mnt/disk11: 1550c 3285c Nov 27 17:53:06 Tuerke rc.unRAID[1564][1609]: /mnt/disk2: 1542c 3286c Nov 27 17:53:06 Tuerke rc.unRAID[1564][1609]: /mnt/disk3: 1558c 3287c Nov 27 17:53:06 Tuerke rc.unRAID[1564][1609]: /mnt/disk4: 1546c 3288c Nov 27 17:53:06 Tuerke rc.unRAID[1564][1609]: /mnt/disk5: 1557c 3289c Nov 27 17:53:06 Tuerke rc.unRAID[1564][1609]: /mnt/disk6: 1562c 3290c Nov 27 17:53:06 Tuerke rc.unRAID[1564][1609]: /mnt/disk7: 1549c 3291c Nov 27 17:53:06 Tuerke rc.unRAID[1564][1609]: /mnt/disk8: 1553c 3292c Nov 27 17:53:06 Tuerke rc.unRAID[1564][1609]: /mnt/disk9: 1554c 3293c Nov 27 17:53:06 Tuerke rc.unRAID[1564][1609]: /mnt/cache: 1541c 3294c Nov 27 17:53:06 Tuerke rc.unRAID[1564][1623]: Sync filesystems Nov 27 17:53:07 Tuerke rc.unRAID[1564][1625]: Umounting the drives Nov 27 17:53:07 Tuerke rc.unRAID[1564][1628]: umount2: Device or resource busy Nov 27 17:53:07 Tuerke rc.unRAID[1564][1628]: umount: /mnt/disk1: device is busy. Nov 27 17:53:07 Tuerke rc.unRAID[1564][1628]: (In some cases useful info about processes that use Nov 27 17:53:07 Tuerke rc.unRAID[1564][1628]: the device is found by lsof( or fuser(1)) Nov 27 17:53:07 Tuerke rc.unRAID[1564][1628]: umount2: Device or resource busy Nov 27 17:53:07 Tuerke rc.unRAID[1564][1628]: /dev/md10 umounted Nov 27 17:53:08 Tuerke rc.unRAID[1564][1628]: /dev/md11 umounted Nov 27 17:53:08 Tuerke rc.unRAID[1564][1628]: /dev/md2 umounted Nov 27 17:53:08 Tuerke rc.unRAID[1564][1628]: /dev/md3 umounted Nov 27 17:53:08 Tuerke rc.unRAID[1564][1628]: /dev/md4 umounted Nov 27 17:53:08 Tuerke rc.unRAID[1564][1628]: /dev/md5 umounted Nov 27 17:53:08 Tuerke rc.unRAID[1564][1628]: /dev/md6 umounted Nov 27 17:53:09 Tuerke rc.unRAID[1564][1628]: /dev/md7 umounted Nov 27 17:53:09 Tuerke rc.unRAID[1564][1628]: /dev/md8 umounted Nov 27 17:53:09 Tuerke rc.unRAID[1564][1628]: /dev/md9 umounted Nov 27 17:53:09 Tuerke rc.unRAID[1564][1641]: Stopping the Array Nov 27 17:53:09 Tuerke rc.unRAID[1564][1647]: /root/mdcmd: line 11: echo: write error: Device or resource busy Nov 27 17:53:09 Tuerke kernel: mdcmd (65): stop Nov 27 17:53:09 Tuerke kernel: md: 2 devices still in use. Nov 27 17:53:11 Tuerke cache_dirs: Suspending cache_dirs for 120 seconds to allow for clean shutdown of array Nov 27 17:53:11 Tuerke cache_dirs: While suspended, pressing "Stop" on the unRAID management web-interface will shutdown the array 2nd time Nov 18 01:11:07 Tuerke auto_s3_sleep: ---------------- powering down now ------------------------- Nov 18 01:11:07 Tuerke powerdown[31775]: Powerdown initiated Nov 18 01:11:07 Tuerke powerdown[31783]: Powerdown V2.12 Nov 18 01:11:07 Tuerke rc.unRAID[31785][31786]: Processing /etc/rc.d/rc.unRAID.d/ kill scripts. Nov 18 01:11:07 Tuerke powerdown[31791]: Initiating Shutdown with '' Nov 18 01:11:07 Tuerke shutdown[31792]: shutting down for system halt Nov 18 01:12:45 Tuerke init: Switching to runlevel: 0 Nov 18 01:12:45 Tuerke atd[14155]: Exec failed for mail command: No such file or directory Nov 18 01:12:47 Tuerke rc.unRAID[1203][1204]: Powerdown V2.12 Nov 18 01:12:47 Tuerke rc.unRAID[1203][1209]: Stopping Plugins. Nov 18 01:12:47 Tuerke rc.unRAID[1203][1210]: Running: "/usr/local/emhttp/plugins/cache_dirs/event/unmounting_disks" Nov 18 01:12:47 Tuerke rc.unRAID[1203][1218]: Running: "/usr/local/emhttp/plugins/powerdown/event/unmounting_disks" Nov 18 01:12:47 Tuerke rc.unRAID[1203][1223]: Stopping unRAID. Nov 18 01:12:47 Tuerke avahi-daemon[2983]: Got SIGTERM, quitting. Nov 18 01:12:47 Tuerke avahi-daemon[2983]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.178.157. Nov 18 01:12:47 Tuerke avahi-daemon[2983]: avahi-daemon 0.6.31 exiting. Nov 18 01:12:47 Tuerke avahi-dnsconfd[2992]: read(): EOF Nov 18 01:12:48 Tuerke rc.unRAID[1203][1307]: Killing active pids on the array drives Nov 18 01:12:48 Tuerke rc.unRAID[1203][1310]: /mnt/disk1: 1290c 3349c Nov 18 01:12:48 Tuerke rc.unRAID[1203][1310]: /mnt/disk10: 1241c 3350c Nov 18 01:12:48 Tuerke rc.unRAID[1203][1310]: /mnt/disk11: 1186c 3351c Nov 18 01:12:48 Tuerke rc.unRAID[1203][1310]: /mnt/disk2: 1196c 3352c Nov 18 01:12:48 Tuerke rc.unRAID[1203][1310]: /mnt/disk3: 1201c 3353c Nov 18 01:12:48 Tuerke rc.unRAID[1203][1310]: /mnt/disk4: 1195c 3354c Nov 18 01:12:48 Tuerke rc.unRAID[1203][1310]: /mnt/disk5: 1235c 3355c Nov 18 01:12:48 Tuerke rc.unRAID[1203][1310]: /mnt/disk6: 1184c 3356c Nov 18 01:12:48 Tuerke rc.unRAID[1203][1310]: /mnt/disk7: 1237c 3357c Nov 18 01:12:48 Tuerke rc.unRAID[1203][1310]: /mnt/disk8: 1239c 3358c Nov 18 01:12:48 Tuerke rc.unRAID[1203][1310]: /mnt/disk9: 1288c 3359c Nov 18 01:12:48 Tuerke rc.unRAID[1203][1310]: /mnt/cache: 1199c 3360c Nov 18 01:12:48 Tuerke rc.unRAID[1203][1324]: Sync filesystems Nov 18 01:12:49 Tuerke rc.unRAID[1203][1326]: Umounting the drives Nov 18 01:12:49 Tuerke rc.unRAID[1203][1329]: umount2: Device or resource busy Nov 18 01:12:49 Tuerke rc.unRAID[1203][1329]: umount: /mnt/disk1: device is busy. Nov 18 01:12:49 Tuerke rc.unRAID[1203][1329]: (In some cases useful info about processes that use Nov 18 01:12:49 Tuerke rc.unRAID[1203][1329]: the device is found by lsof( or fuser(1)) Nov 18 01:12:49 Tuerke rc.unRAID[1203][1329]: umount2: Device or resource busy Nov 18 01:12:49 Tuerke rc.unRAID[1203][1329]: /dev/md10 umounted Nov 18 01:12:50 Tuerke rc.unRAID[1203][1329]: /dev/md11 umounted Nov 18 01:12:50 Tuerke rc.unRAID[1203][1329]: /dev/md2 umounted Nov 18 01:12:50 Tuerke rc.unRAID[1203][1329]: /dev/md3 umounted Nov 18 01:12:50 Tuerke rc.unRAID[1203][1329]: /dev/md4 umounted Nov 18 01:12:50 Tuerke rc.unRAID[1203][1329]: /dev/md5 umounted Nov 18 01:12:50 Tuerke rc.unRAID[1203][1329]: /dev/md6 umounted Nov 18 01:12:51 Tuerke rc.unRAID[1203][1329]: /dev/md7 umounted Nov 18 01:12:51 Tuerke rc.unRAID[1203][1329]: /dev/md8 umounted Nov 18 01:12:51 Tuerke rc.unRAID[1203][1329]: /dev/md9 umounted Nov 18 01:12:51 Tuerke rc.unRAID[1203][1374]: Stopping the Array Nov 18 01:12:51 Tuerke rc.unRAID[1203][1380]: /root/mdcmd: line 11: echo: write error: Device or resource busy Nov 18 01:12:51 Tuerke kernel: mdcmd (65): stop Nov 18 01:12:51 Tuerke kernel: md: 2 devices still in use. Nov 18 01:12:54 Tuerke cache_dirs: Suspending cache_dirs for 120 seconds to allow for clean shutdown of array Nov 18 01:12:54 Tuerke cache_dirs: While suspended, pressing "Stop" on the unRAID management web-interface will shutdown the array Example of a good shutdown: Nov 16 11:22:18 Tuerke powerdown[24642]: Powerdown initiated Nov 16 11:22:18 Tuerke powerdown[24646]: Powerdown V2.12 Nov 16 11:22:18 Tuerke rc.unRAID[24648][24649]: Processing /etc/rc.d/rc.unRAID.d/ kill scripts. Nov 16 11:22:18 Tuerke powerdown[24654]: Initiating Shutdown with '' Nov 16 11:22:18 Tuerke shutdown[24655]: shutting down for system halt Nov 16 11:23:56 Tuerke init: Switching to runlevel: 0 Nov 16 11:23:56 Tuerke atd[14846]: Exec failed for mail command: No such file or directory Nov 16 11:23:58 Tuerke rc.unRAID[26302][26303]: Powerdown V2.12 Nov 16 11:23:58 Tuerke rc.unRAID[26302][26308]: Stopping Plugins. Nov 16 11:23:58 Tuerke rc.unRAID[26302][26309]: Running: "/usr/local/emhttp/plugins/cache_dirs/event/unmounting_disks" Nov 16 11:23:58 Tuerke rc.unRAID[26302][26315]: Running: "/usr/local/emhttp/plugins/powerdown/event/unmounting_disks" Nov 16 11:23:58 Tuerke rc.unRAID[26302][26320]: Stopping unRAID. Nov 16 11:23:58 Tuerke avahi-daemon[2897]: Got SIGTERM, quitting. Nov 16 11:23:58 Tuerke avahi-daemon[2897]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.178.157. Nov 16 11:23:58 Tuerke avahi-daemon[2897]: avahi-daemon 0.6.31 exiting. Nov 16 11:23:58 Tuerke avahi-dnsconfd[2906]: read(): EOF Nov 16 11:23:59 Tuerke rc.unRAID[26302][26368]: Killing active pids on the array drives Nov 16 11:23:59 Tuerke rc.unRAID[26302][26371]: /mnt/disk1: 3255c 26341c Nov 16 11:23:59 Tuerke rc.unRAID[26302][26371]: /mnt/disk10: 3256c 26350c Nov 16 11:23:59 Tuerke rc.unRAID[26302][26371]: /mnt/disk11: 3257c 26352c Nov 16 11:23:59 Tuerke rc.unRAID[26302][26371]: /mnt/disk2: 3258c 26354c Nov 16 11:23:59 Tuerke rc.unRAID[26302][26371]: /mnt/disk3: 3259c 26346c Nov 16 11:23:59 Tuerke rc.unRAID[26302][26371]: /mnt/disk4: 3260c 26338c Nov 16 11:23:59 Tuerke rc.unRAID[26302][26371]: /mnt/disk5: 3261c 26332c Nov 16 11:23:59 Tuerke rc.unRAID[26302][26371]: /mnt/disk6: 3262c 26343c Nov 16 11:23:59 Tuerke rc.unRAID[26302][26371]: /mnt/disk7: 3263c 26345c Nov 16 11:23:59 Tuerke rc.unRAID[26302][26371]: /mnt/disk8: 3264c 26348c Nov 16 11:23:59 Tuerke rc.unRAID[26302][26371]: /mnt/disk9: 3265c 26336c Nov 16 11:23:59 Tuerke rc.unRAID[26302][26371]: /mnt/cache: 3266c 26334c Nov 16 11:23:59 Tuerke rc.unRAID[26302][26372]: Sync filesystems Nov 16 11:24:00 Tuerke rc.unRAID[26302][26374]: Umounting the drives Nov 16 11:24:01 Tuerke rc.unRAID[26302][26377]: /dev/md1 umounted Nov 16 11:24:01 Tuerke rc.unRAID[26302][26377]: /dev/md10 umounted Nov 16 11:24:01 Tuerke rc.unRAID[26302][26377]: /dev/md11 umounted Nov 16 11:24:01 Tuerke rc.unRAID[26302][26377]: /dev/md2 umounted Nov 16 11:24:02 Tuerke rc.unRAID[26302][26377]: /dev/md3 umounted Nov 16 11:24:02 Tuerke rc.unRAID[26302][26377]: /dev/md4 umounted Nov 16 11:24:02 Tuerke rc.unRAID[26302][26377]: /dev/md5 umounted Nov 16 11:24:02 Tuerke rc.unRAID[26302][26377]: /dev/md6 umounted Nov 16 11:24:02 Tuerke rc.unRAID[26302][26377]: /dev/md7 umounted Nov 16 11:24:02 Tuerke rc.unRAID[26302][26377]: /dev/md8 umounted Nov 16 11:24:03 Tuerke rc.unRAID[26302][26377]: /dev/md9 umounted Nov 16 11:24:03 Tuerke rc.unRAID[26302][26390]: Stopping the Array Nov 16 11:24:03 Tuerke kernel: mdcmd (65): stop Nov 16 11:24:03 Tuerke kernel: md1: stopping Nov 16 11:24:03 Tuerke kernel: md2: stopping Nov 16 11:24:03 Tuerke kernel: md3: stopping Nov 16 11:24:03 Tuerke kernel: md4: stopping Nov 16 11:24:03 Tuerke kernel: md5: stopping Nov 16 11:24:03 Tuerke kernel: md6: stopping Nov 16 11:24:03 Tuerke kernel: md7: stopping Nov 16 11:24:03 Tuerke kernel: md8: stopping Nov 16 11:24:03 Tuerke kernel: md9: stopping Nov 16 11:24:03 Tuerke kernel: md10: stopping Nov 16 11:24:03 Tuerke kernel: md11: stopping Nov 16 11:24:04 Tuerke cache_dirs: Suspending cache_dirs for 120 seconds to allow for clean shutdown of array Nov 16 11:24:04 Tuerke cache_dirs: While suspended, pressing "Stop" on the unRAID management web-interface will shutdown the array Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: --- /tmp/mdcmd.26302.1^I2014-11-16 11:24:03.173506203 +0100 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: +++ /tmp/mdcmd.26302.2^I2014-11-16 11:24:08.443583625 +0100 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: @@ -1,14 +1,14 @@ Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: sbName=/boot/config/super.dat Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: sbVersion=2.1.6 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: sbCreated=1374256257 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: -sbUpdated=1416128176 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: -sbEvents=649 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: -sbState=0 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: +sbUpdated=1416133443 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: +sbEvents=650 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: +sbState=1 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: sbNumDisks=12 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: sbSynced=1415202777 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: sbSyncErrs=1 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: mdVersion=2.2.0 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: -mdState=STARTED Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: +mdState=STOPPED Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: mdNumProtected=12 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: mdNumDisabled=0 Nov 16 11:24:08 Tuerke mdstatusdiff[26412]: mdDisabledDisk=0 I never had issues with previous versions of powerdown. Can't tell if there is a difference in 2.13, but I will come back if this happens!
December 4, 201411 yr Author Are you running v6b12? Cache_dirs does not look like it shut down. Upgrade to v6b12 if you haven't already and use the dynamix version of cache_dirs. If you're on v5, the cache_dirs plugin needs to be updated.
December 4, 201411 yr Thanks a lot for your help dlandon. Syslog is attached - your script was working well until the update to b12 (it was even gracefully shutting down a Win7 VM). The issue seems to be around disk1: Dec 3 22:22:27 Tower rc.unRAID[30246][30830]: umount2: Device or resource busy Dec 3 22:22:27 Tower rc.unRAID[30246][30830]: umount: /mnt/disk1: device is busy. Dec 3 22:22:27 Tower rc.unRAID[30246][30830]: (In some cases useful info about processes that use Dec 3 22:22:27 Tower rc.unRAID[30246][30830]: the device is found by lsof( or fuser(1)) Dec 3 22:22:27 Tower rc.unRAID[30246][30830]: umount2: Device or resource busy Dec 3 22:22:54 Tower rc.unRAID[30246][30848]: Active pids left on the array drives Dec 3 22:22:54 Tower rc.unRAID[30246][30851]: USER PID ACCESS COMMAND Dec 3 22:22:54 Tower rc.unRAID[30246][30851]: /dev/md1: root kernel mount /mnt/disk1 Dec 3 22:22:54 Tower rc.unRAID[30246][30852]: Stopping the Array Dec 3 22:22:54 Tower rc.unRAID[30246][30858]: /root/mdcmd: line 11: echo: write error: Device or resource busy Dec 3 22:22:54 Tower kernel: mdcmd (138): stop Dec 3 22:22:54 Tower kernel: md: 1 devices still in use. This disk drive is exclusively dedicated for two Mac's using it as Time Machine device.
December 4, 201411 yr Author I see in the log you had a parity check running, but drives were spun down and you were changing the disk settings. Was the parity check running when you powered down? The other thing I see is that the Windows 7 VM didn't shut down and had to be destroyed. Can you clarify more of what was going on when you powered down? I think you said you pushed the power button. Is that true?
December 4, 201411 yr I'm on v6b12, I had my server's web interface get unresponsive overnight, but I could get to the console with putty, I just installed this plugin, It's my understanding that I need it to shut down from the command prompt? Does it also change the behavior of the server's power button, I would like to be able to do a clean shutdown in case I have another freeze of the web ui
December 4, 201411 yr Author I'm on v6b12, I had my server's web interface get unresponsive overnight, but I could get to the console with putty, I just installed this plugin, It's my understanding that I need it to shut down from the command prompt? No. The stock shutdown works fine. It can be initiated from the command line. The difference is that the stock shutdown issues a shutdown to emhttp. Powerdown does the same shutdown procedure but does not use emhttp to perform the shutdown. Does it also change the behavior of the server's power button, I would like to be able to do a clean shutdown in case I have another freeze of the web ui No. The power button event is mapped to 'powerdown'. The stock powerdown will do a clean shutdown of the server. The powerdown plugin doesn't use emhttp to do a shutdown, allows custom start and stop event processing scripts, adds additional logging so the shutdown process can be followed, and logs are saved on each shutdown to the flash drive for historical purposes like evaluating why a shutdown may not have gone properly. Currently the power button event is not passed to unRAID when booted in Xen. Neither the stock powerdown nor the powerdown plugin will respond to the power button event when booted in Xen.
December 4, 201411 yr I see in the log you had a parity check running, but drives were spun down and you were changing the disk settings. Was the parity check running when you powered down? The other thing I see is that the Windows 7 VM didn't shut down and had to be destroyed. Can you clarify more of what was going on when you powered down? I think you said you pushed the power button. Is that true? Thanks dlandon, here is a little bit of background you were asking for: I came back home, pushed the power button and expected a clean shutdown I wasn't aware that parity check was running as it was late and I didn't checked the web gui I was changing disk settings hours before I pushed the power button
December 4, 201411 yr Author I see in the log you had a parity check running, but drives were spun down and you were changing the disk settings. Was the parity check running when you powered down? The other thing I see is that the Windows 7 VM didn't shut down and had to be destroyed. Can you clarify more of what was going on when you powered down? I think you said you pushed the power button. Is that true? Thanks dlandon, here is a little bit of background you were asking for: I came back home, pushed the power button and expected a clean shutdown I wasn't aware that parity check was running as it was late and I didn't checked the web gui I was changing disk settings hours before I pushed the power button Looking back at the log I see where the parity check failed. Probably because you stopped it when you were making your changes. The only other thing I see is this: Dec 3 22:15:58 Tower afpd[18320]: read: No route to host Dec 3 22:15:58 Tower afpd[18320]: dsi_stream_read: len:-1, No route to host Dec 3 22:18:44 Tower kernel: mdcmd (137): spindown 1 Dec 3 22:21:19 Tower powerdown[30188]: Powerdown initiated Dec 3 22:21:19 Tower powerdown[30191]: Powerdown V2.13 I don't know much about afp, but it looks like there was an issue about 3 minutes before the powerdown event. Maybe someone more familiar with afp can chime in here and offer some suggestions on what this means.
December 4, 201411 yr I think that this could be ignored. This is an issue with Time Machine and sometimes it is just not working and producing these syslog entries.
December 5, 201411 yr Are you running v6b12? Cache_dirs does not look like it shut down. Upgrade to v6b12 if you haven't already and use the dynamix version of cache_dirs. If you're on v5, the cache_dirs plugin needs to be updated. I'm on v5 and won't upgrade this server to a beta version. I will check for an update of cache_dirs, but I don't think there is one available.
December 5, 201411 yr Author Are you running v6b12? Cache_dirs does not look like it shut down. Upgrade to v6b12 if you haven't already and use the dynamix version of cache_dirs. If you're on v5, the cache_dirs plugin needs to be updated. I'm on v5 and won't upgrade this server to a beta version. I will check for an update of cache_dirs, but I don't think there is one available. Show me where you got the cache_dirs plugin.
December 5, 201411 yr Show me where you got the cache_dirs plugin. You mean where it is located on my thumb drive?
Archived
This topic is now archived and is closed to further replies.