smoldersonline Posted May 16, 2015 Share Posted May 16, 2015 Awesome, it works OK now. Thanks a lot gents! Link to comment
Walter S Posted May 16, 2015 Share Posted May 16, 2015 Just noticed the RC-1 is released. Updated v6.0beta15. I've just noticed my system upon start up the Array is in the Off (?) position and I have to press the "Start Array button" to bring everything to normal. I can't understand why this is. My configuration is valid, parity is valid. Powerdown Package (2.14) updated. my Go file has the following at the end echo "/sbin/powerdown" | at 01:00 This has worked in the past. I'll include a copy of the syslog before I bring the array on line.. any suggestions would be helpful also I have no scripts in my flash\config\plugins\powerdown\rc.unRAID.d folder so there's nothing to adjust there. syslog.zip Link to comment
trurl Posted May 16, 2015 Share Posted May 16, 2015 Just noticed the RC-1 is released. Updated v6.0beta15. I've just noticed my system upon start up the Array is in the Off (?) position and I have to press the "Start Array button" to bring everything to normal. I can't understand why this is. My configuration is valid, parity is valid. Powerdown Package (2.14) updated. my Go file has the following at the end echo "/sbin/powerdown" | at 01:00 This has worked in the past. I'll include a copy of the syslog before I bring the array on line.. any suggestions would be helpful also I have no scripts in my flash\config\plugins\powerdown\rc.unRAID.d folder so there's nothing to adjust there. Are you sure you have it set to auto start under Disk Settings? Link to comment
Walter S Posted May 16, 2015 Share Posted May 16, 2015 ahh leme look..Duh. =You learn something new every day. sorry for wasting your time.. Link to comment
Freddie Posted May 17, 2015 Share Posted May 17, 2015 Done. 2.14 available. Thanks to both you and Freddie! Very fast work! Maybe a little bit too fast. There is an interaction between powerdown and the Unassigned Devices plugin. Unassigned Devices creates a directory at /mnt/disks/ powerdown now kills all processes using the filesystems of /mnt/disk* /mnt/disks/ fits the /mnt/disk* filename expansion /mnt/disks/ is on the root filesystem all processes using the root filesystem are killed bad things happen (or maybe more precisely, nothing else happens) I'd suggest that a change be made to the file pattern used to kill processes. Maybe this: /mnt/disk{[12][1-9],[1-9]} Or just revert my previous suggestion and live with the less effective process killing until a better solution is found. Link to comment
dlandon Posted May 17, 2015 Author Share Posted May 17, 2015 Done. 2.14 available. Thanks to both you and Freddie! Very fast work! Maybe a little bit too fast. There is an interaction between powerdown and the Unassigned Devices plugin. Unassigned Devices creates a directory at /mnt/disks/ powerdown now kills all processes using the filesystems of /mnt/disk* /mnt/disks/ fits the /mnt/disk* filename expansion /mnt/disks/ is on the root filesystem all processes using the root filesystem are killed bad things happen (or maybe more precisely, nothing else happens) I'd suggest that a change be made to the file pattern used to kill processes. Maybe this: /mnt/disk{[12][1-9],[1-9]} Or just revert my previous suggestion and live with the less effective process killing until a better solution is found. I don't understand the problem. There is a unmounting_disks that is an event for the unassigned_devices plugin. The powerdown plugin walks through all plugin unmounting_disks events and executes the scripts found there. This is done before the 'fuser -mvk' is executed and disks are unmounted. Any processes left need to be terminated by the plugin. It's not appropriate for powerdown to try to make exceptions to unmounting the disks. When the 'fuser -mvk' is executed, all processes should be shut down by the plugins. 'fuser -mvk' is really a last ditch effort to shutdown plugins and is not the normal/proper way of shutting down plugin processes. If this is a problem for powerdown, it will also be a problem for the webgui shutdown. The webgui will get stuck at the "unmounting disks" and hang and never allow a shutdown. I recommend you post your issue to the unassigned_devices thread and have the plugin author come up with a solution. EDIT: I loaded up the unassigned_devices plugin on my test server and did some testing. The webgui shutdown does work properly. Powerdown hangs on the /mnt/dksks processes. I will do some more research on this. I suspect you are right that powerdown should only kill processes on the /mnt/disk[1-9][1-9] mount points. I want powerdown to perform the same shutdown as the webgui but not get stuck in the "unmounting disks" loop. Link to comment
Freddie Posted May 17, 2015 Share Posted May 17, 2015 I don't understand the problem. There is a unmounting_disks that is an event for the unassigned_devices plugin. The powerdown plugin walks through all plugin unmounting_disks events and executes the scripts found there. This is done before the 'fuser -mvk' is executed and disks are unmounted. Any processes left need to be terminated by the plugin. It's not appropriate for powerdown to try to make exceptions to unmounting the disks. When the 'fuser -mvk' is executed, all processes should be shut down by the plugins. 'fuser -mvk' is really a last ditch effort to shutdown plugins and is not the normal/proper way of shutting down plugin processes. I agree with everything you wrote here. I would add a little clarification. When the 'fuser -mvk' is executed, all processes that were started by plugins should be shut down by the plugins. The problem is that powerdown is killing processes that are necessary to continue the shutdown process, not just the processes that are using the array. I can also cause the problem by creating an empty directory named /mnt/disk_maker/. root@uwer:~# fuser -mv /mnt/disk* USER PID ACCESS COMMAND /mnt/disk1: root kernel mount /mnt/disk1 /mnt/disk2: root kernel mount /mnt/disk2 /mnt/disk7: root kernel mount /mnt/disk7 /mnt/disk_maker: root kernel mount / root 1 .rce. init root 2 .rc.. kthreadd root 3 .rc.. ksoftirqd/0 root 5 .rc.. kworker/0:0H root 7 .rc.. rcu_preempt root 8 .rc.. rcu_sched root 9 .rc.. rcu_bh root 10 .rc.. migration/0 root 11 .rc.. migration/1 root 12 .rc.. ksoftirqd/1 root 14 .rc.. kworker/1:0H root 15 .rc.. khelper root 17 .rc.. netns root 20 .rc.. perf root 247 .rc.. writeback root 248 .rc.. ksmd root 249 .rc.. khugepaged root 250 .rc.. crypto root 251 .rc.. kintegrityd root 253 .rc.. bioset root 255 .rc.. kblockd root 372 .rc.. ata_sff root 388 .rc.. devfreq_wq root 486 .rc.. rpciod root 487 .rc.. kworker/1:1 root 488 .rc.. kworker/0:1 root 513 .rc.. kswapd0 root 544 .rc.. kworker/u8:1 root 582 .rc.. fsnotify_mark root 602 .rc.. nfsiod root 606 .rc.. cifsiod root 619 .rc.. xfsalloc root 620 .rc.. xfs_mru_cache root 658 .rc.. acpi_thermal_pm root 762 .rc.. vfio-irqfd-clea root 787 .rc.. kworker/1:3 root 854 .rc.. bioset root 861 .rc.. deferwq root 864 .rc.. scsi_eh_0 root 865 .rc.. scsi_tmf_0 root 866 .rc.. usb-storage root 869 .rc.. kworker/0:2 root 919 .rce. udevd root 968 .rc.. scsi_eh_1 root 969 .rc.. scsi_tmf_1 root 970 .rc.. scsi_eh_2 root 971 .rc.. scsi_tmf_2 root 972 .rc.. scsi_eh_3 root 973 .rc.. scsi_tmf_3 root 974 .rc.. scsi_eh_4 root 975 .rc.. scsi_tmf_4 root 977 .rc.. scsi_eh_5 root 978 .rc.. scsi_tmf_5 root 979 .rc.. scsi_eh_6 root 980 .rc.. scsi_tmf_6 root 997 .rc.. kworker/1:1H root 1004 .rc.. kworker/0:1H root 1093 .rce. rsyslogd root 1249 Frce. dhcpcd bin 1276 Frce. rpc.portmap rpc 1280 Frce. rpc.statd root 1290 .rce. inetd root 1300 .rce. sshd root 1311 .rce. ntpd root 1319 Frce. acpid messagebus 1332 Frce. dbus-daemon root 1334 .rce. crond daemon 1336 Frce. atd root 1341 Frce. nmbd root 1343 Frce. smbd root 1348 .rce. cpuload root 4393 .rc.. kworker/u8:0 root 4525 .rc.. kworker/u9:2 root 7061 .rce. emhttp root 7072 .rc.. md root 7073 .rc.. mdrecoveryd root 7075 .rc.. spinupd root 7076 .rc.. spinupd root 7077 .rc.. spinupd root 7078 .rc.. spinupd root 7251 .rce. apcupsd nobody 7295 Frce. dnsmasq root 7329 .rce. agetty root 7330 .rce. agetty root 7331 .rce. agetty root 7332 .rce. agetty root 7333 .rce. agetty root 7334 .rce. agetty root 7357 .rce. netatalk root 7362 .rce. afpd root 7363 .rce. cnid_metad avahi 7370 Frce. avahi-daemon avahi 7371 .rce. avahi-daemon root 7379 .rce. avahi-dnsconfd root 7399 .rc.. unraidd root 7425 .rc.. reiserfs/md1 root 7435 .rc.. reiserfs/md2 root 7447 .rc.. xfs-buf/md7 root 7448 .rc.. xfs-data/md7 root 7449 .rc.. xfs-conv/md7 root 7450 .rc.. xfs-cil/md7 root 7451 .rc.. xfsaild/md7 root 7462 .rc.. btrfs-worker root 7464 .rc.. btrfs-worker-hi root 7465 .rc.. btrfs-delalloc root 7466 .rc.. btrfs-flush_del root 7467 .rc.. btrfs-cache root 7468 .rc.. btrfs-submit root 7469 .rc.. btrfs-fixup root 7470 .rc.. btrfs-endio root 7471 .rc.. btrfs-endio-met root 7472 .rc.. btrfs-endio-met root 7473 .rc.. btrfs-endio-rai root 7474 .rc.. btrfs-endio-rep root 7475 .rc.. btrfs-rmw root 7476 .rc.. btrfs-endio-wri root 7477 .rc.. btrfs-freespace root 7478 .rc.. btrfs-delayed-m root 7479 .rc.. btrfs-readahead root 7480 .rc.. btrfs-qgroup-re root 7481 .rc.. btrfs-extent-re root 7482 .rc.. btrfs-cleaner root 7483 .rc.. btrfs-transacti root 7495 .rce. shfs root 7506 .rce. shfs root 7527 .rc.. loop0 root 7529 .rc.. btrfs-worker root 7530 .rc.. btrfs-worker-hi root 7531 .rc.. btrfs-delalloc root 7532 .rc.. btrfs-flush_del root 7533 .rc.. btrfs-cache root 7534 .rc.. btrfs-submit root 7535 .rc.. btrfs-fixup root 7536 .rc.. btrfs-endio root 7537 .rc.. btrfs-endio-met root 7538 .rc.. btrfs-endio-met root 7539 .rc.. btrfs-endio-rai root 7540 .rc.. btrfs-endio-rep root 7541 .rc.. btrfs-rmw root 7542 .rc.. btrfs-endio-wri root 7543 .rc.. btrfs-freespace root 7544 .rc.. btrfs-delayed-m root 7545 .rc.. btrfs-readahead root 7546 .rc.. btrfs-qgroup-re root 7547 .rc.. btrfs-extent-re root 7548 .rc.. btrfs-cleaner root 7549 .rc.. btrfs-transacti root 7551 Frce. docker root 7668 .rce. docker root 7729 .rce. docker root 7772 .rce. sleep root 7810 .rce. sleep root 7812 .rce. docker root 7838 .rce. docker root 7903 .rce. docker root 7964 .rce. docker root 8027 .rce. docker root 8096 .rce. docker root 8210 .rc.. kworker/u8:4 root 8971 .rce. cache_dirs root 10636 .rce. sshd root 10642 .rce. bash root 13428 .rc.. kworker/u8:3 root 19642 frce. emhttp root 19643 frce. bash root 19645 frce. tail root 23928 .rc.. kworker/u9:0 root 26527 .rc.. kworker/u9:1 root@uwer:~# fuser -mv /mnt/disk{[12][1-9],[1-9]} Specified filename /mnt/disk[12][1-9] does not exist. USER PID ACCESS COMMAND /mnt/disk1: root kernel mount /mnt/disk1 /mnt/disk2: root kernel mount /mnt/disk2 /mnt/disk7: root kernel mount /mnt/disk7 /mnt/disk_maker is just a directory on the root filesystem, therefor 'fuser -mvk /mnt/disk*' will kill all processes using the root filesystem. I recommend you post your issue to the unassigned_devices thread and have the plugin author come up with a solution. The author of the unassigned_devices plugin could fix the interaction by deleting the /mnt/disks/ directory in the unmounting_disks event (are you listening gfjardim?). But I think powerdown should limit the processes it kills to the ones that are using the array disks. Thats why I posted in this thread. Link to comment
dlandon Posted May 17, 2015 Author Share Posted May 17, 2015 I don't understand the problem. There is a unmounting_disks that is an event for the unassigned_devices plugin. The powerdown plugin walks through all plugin unmounting_disks events and executes the scripts found there. This is done before the 'fuser -mvk' is executed and disks are unmounted. Any processes left need to be terminated by the plugin. It's not appropriate for powerdown to try to make exceptions to unmounting the disks. When the 'fuser -mvk' is executed, all processes should be shut down by the plugins. 'fuser -mvk' is really a last ditch effort to shutdown plugins and is not the normal/proper way of shutting down plugin processes. I agree with everything you wrote here. I would add a little clarification. When the 'fuser -mvk' is executed, all processes that were started by plugins should be shut down by the plugins. The problem is that powerdown is killing processes that are necessary to continue the shutdown process, not just the processes that are using the array. I can also cause the problem by creating an empty directory named /mnt/disk_maker/. root@uwer:~# fuser -mv /mnt/disk* USER PID ACCESS COMMAND /mnt/disk1: root kernel mount /mnt/disk1 /mnt/disk2: root kernel mount /mnt/disk2 /mnt/disk7: root kernel mount /mnt/disk7 /mnt/disk_maker: root kernel mount / root 1 .rce. init root 2 .rc.. kthreadd root 3 .rc.. ksoftirqd/0 root 5 .rc.. kworker/0:0H root 7 .rc.. rcu_preempt root 8 .rc.. rcu_sched root 9 .rc.. rcu_bh root 10 .rc.. migration/0 root 11 .rc.. migration/1 root 12 .rc.. ksoftirqd/1 root 14 .rc.. kworker/1:0H root 15 .rc.. khelper root 17 .rc.. netns root 20 .rc.. perf root 247 .rc.. writeback root 248 .rc.. ksmd root 249 .rc.. khugepaged root 250 .rc.. crypto root 251 .rc.. kintegrityd root 253 .rc.. bioset root 255 .rc.. kblockd root 372 .rc.. ata_sff root 388 .rc.. devfreq_wq root 486 .rc.. rpciod root 487 .rc.. kworker/1:1 root 488 .rc.. kworker/0:1 root 513 .rc.. kswapd0 root 544 .rc.. kworker/u8:1 root 582 .rc.. fsnotify_mark root 602 .rc.. nfsiod root 606 .rc.. cifsiod root 619 .rc.. xfsalloc root 620 .rc.. xfs_mru_cache root 658 .rc.. acpi_thermal_pm root 762 .rc.. vfio-irqfd-clea root 787 .rc.. kworker/1:3 root 854 .rc.. bioset root 861 .rc.. deferwq root 864 .rc.. scsi_eh_0 root 865 .rc.. scsi_tmf_0 root 866 .rc.. usb-storage root 869 .rc.. kworker/0:2 root 919 .rce. udevd root 968 .rc.. scsi_eh_1 root 969 .rc.. scsi_tmf_1 root 970 .rc.. scsi_eh_2 root 971 .rc.. scsi_tmf_2 root 972 .rc.. scsi_eh_3 root 973 .rc.. scsi_tmf_3 root 974 .rc.. scsi_eh_4 root 975 .rc.. scsi_tmf_4 root 977 .rc.. scsi_eh_5 root 978 .rc.. scsi_tmf_5 root 979 .rc.. scsi_eh_6 root 980 .rc.. scsi_tmf_6 root 997 .rc.. kworker/1:1H root 1004 .rc.. kworker/0:1H root 1093 .rce. rsyslogd root 1249 Frce. dhcpcd bin 1276 Frce. rpc.portmap rpc 1280 Frce. rpc.statd root 1290 .rce. inetd root 1300 .rce. sshd root 1311 .rce. ntpd root 1319 Frce. acpid messagebus 1332 Frce. dbus-daemon root 1334 .rce. crond daemon 1336 Frce. atd root 1341 Frce. nmbd root 1343 Frce. smbd root 1348 .rce. cpuload root 4393 .rc.. kworker/u8:0 root 4525 .rc.. kworker/u9:2 root 7061 .rce. emhttp root 7072 .rc.. md root 7073 .rc.. mdrecoveryd root 7075 .rc.. spinupd root 7076 .rc.. spinupd root 7077 .rc.. spinupd root 7078 .rc.. spinupd root 7251 .rce. apcupsd nobody 7295 Frce. dnsmasq root 7329 .rce. agetty root 7330 .rce. agetty root 7331 .rce. agetty root 7332 .rce. agetty root 7333 .rce. agetty root 7334 .rce. agetty root 7357 .rce. netatalk root 7362 .rce. afpd root 7363 .rce. cnid_metad avahi 7370 Frce. avahi-daemon avahi 7371 .rce. avahi-daemon root 7379 .rce. avahi-dnsconfd root 7399 .rc.. unraidd root 7425 .rc.. reiserfs/md1 root 7435 .rc.. reiserfs/md2 root 7447 .rc.. xfs-buf/md7 root 7448 .rc.. xfs-data/md7 root 7449 .rc.. xfs-conv/md7 root 7450 .rc.. xfs-cil/md7 root 7451 .rc.. xfsaild/md7 root 7462 .rc.. btrfs-worker root 7464 .rc.. btrfs-worker-hi root 7465 .rc.. btrfs-delalloc root 7466 .rc.. btrfs-flush_del root 7467 .rc.. btrfs-cache root 7468 .rc.. btrfs-submit root 7469 .rc.. btrfs-fixup root 7470 .rc.. btrfs-endio root 7471 .rc.. btrfs-endio-met root 7472 .rc.. btrfs-endio-met root 7473 .rc.. btrfs-endio-rai root 7474 .rc.. btrfs-endio-rep root 7475 .rc.. btrfs-rmw root 7476 .rc.. btrfs-endio-wri root 7477 .rc.. btrfs-freespace root 7478 .rc.. btrfs-delayed-m root 7479 .rc.. btrfs-readahead root 7480 .rc.. btrfs-qgroup-re root 7481 .rc.. btrfs-extent-re root 7482 .rc.. btrfs-cleaner root 7483 .rc.. btrfs-transacti root 7495 .rce. shfs root 7506 .rce. shfs root 7527 .rc.. loop0 root 7529 .rc.. btrfs-worker root 7530 .rc.. btrfs-worker-hi root 7531 .rc.. btrfs-delalloc root 7532 .rc.. btrfs-flush_del root 7533 .rc.. btrfs-cache root 7534 .rc.. btrfs-submit root 7535 .rc.. btrfs-fixup root 7536 .rc.. btrfs-endio root 7537 .rc.. btrfs-endio-met root 7538 .rc.. btrfs-endio-met root 7539 .rc.. btrfs-endio-rai root 7540 .rc.. btrfs-endio-rep root 7541 .rc.. btrfs-rmw root 7542 .rc.. btrfs-endio-wri root 7543 .rc.. btrfs-freespace root 7544 .rc.. btrfs-delayed-m root 7545 .rc.. btrfs-readahead root 7546 .rc.. btrfs-qgroup-re root 7547 .rc.. btrfs-extent-re root 7548 .rc.. btrfs-cleaner root 7549 .rc.. btrfs-transacti root 7551 Frce. docker root 7668 .rce. docker root 7729 .rce. docker root 7772 .rce. sleep root 7810 .rce. sleep root 7812 .rce. docker root 7838 .rce. docker root 7903 .rce. docker root 7964 .rce. docker root 8027 .rce. docker root 8096 .rce. docker root 8210 .rc.. kworker/u8:4 root 8971 .rce. cache_dirs root 10636 .rce. sshd root 10642 .rce. bash root 13428 .rc.. kworker/u8:3 root 19642 frce. emhttp root 19643 frce. bash root 19645 frce. tail root 23928 .rc.. kworker/u9:0 root 26527 .rc.. kworker/u9:1 root@uwer:~# fuser -mv /mnt/disk{[12][1-9],[1-9]} Specified filename /mnt/disk[12][1-9] does not exist. USER PID ACCESS COMMAND /mnt/disk1: root kernel mount /mnt/disk1 /mnt/disk2: root kernel mount /mnt/disk2 /mnt/disk7: root kernel mount /mnt/disk7 /mnt/disk_maker is just a directory on the root filesystem, therefor 'fuser -mvk /mnt/disk*' will kill all processes using the root filesystem. I recommend you post your issue to the unassigned_devices thread and have the plugin author come up with a solution. The author of the unassigned_devices plugin could fix the interaction by deleting the /mnt/disks/ directory in the unmounting_disks event (are you listening gfjardim?). But I think powerdown should limit the processes it kills to the ones that are using the array disks. Thats why I posted in this thread. Agreed. I'm working on a solution. The author of the unassigned_devices plugin could fix the interaction by deleting the /mnt/disks/ directory in the unmounting_disks event (are you listening gfjardim?). Yes, this should be done also. I can't believe this has not come up before this. Link to comment
gfjardim Posted May 17, 2015 Share Posted May 17, 2015 The author of the unassigned_devices plugin could fix the interaction by deleting the /mnt/disks/ directory in the unmounting_disks event (are you listening gfjardim?). But I think powerdown should limit the processes it kills to the ones that are using the array disks. Thats why I posted in this thread. If the disk is mounted, but "Auto mount" is off, it won't be unmounted, so it's not viable to delete the directory. I can change the default mount point, but some users could still use the current one. Any suggestions? Link to comment
dlandon Posted May 18, 2015 Author Share Posted May 18, 2015 The author of the unassigned_devices plugin could fix the interaction by deleting the /mnt/disks/ directory in the unmounting_disks event (are you listening gfjardim?). But I think powerdown should limit the processes it kills to the ones that are using the array disks. Thats why I posted in this thread. If the disk is mounted, but "Auto mount" is off, it won't be unmounted, so it's not viable to delete the directory. I can change the default mount point, but some users could still use the current one. Any suggestions? I've have implemented a fix to take care of the problem. No matter how you cut it, powerdown should be able to handle this situation. Link to comment
dlandon Posted May 18, 2015 Author Share Posted May 18, 2015 Version 2.15 is available to fix the /mnt/disks problem. I do not have an array over 9 disks so I can't test my /mnt/diskxx on an array with 2 digits in the /mnt/disk parameter to fuser. Can someone with a large array check to be sure that I have covered /mnt/disk1 to /mnt/diskxx? Post a log if there is a problem. Link to comment
Freddie Posted May 18, 2015 Share Posted May 18, 2015 My suggestion for the file expansion pattern was flawed, it left out disk10 and disk20. Better pattern: /mnt/disk{[12][0-9],[1-9]} Sorry I didn't catch that before you updated. If someone with a full complement of disks could post the output of this: ls -d /mnt/disk{[12][0-9],[1-9]} That would probably help. Link to comment
dlandon Posted May 18, 2015 Author Share Posted May 18, 2015 My suggestion for the file expansion pattern was flawed, it left out disk10 and disk20. Better pattern: /mnt/disk{[12][0-9],[1-9]} Ah yes. Another update coming. I did not test for 10 or 20. I tested other numbers. I'll run a test for those before I post another update. Link to comment
interwebtech Posted May 18, 2015 Share Posted May 18, 2015 If someone with a full complement of disks could post the output of this: ls /mnt/disk{[12][0-9],[1-9]} That would probably help. 14 disk array root@Tower:~# ls /mnt/disk{[12][0-9],[1-9]} /mnt/disk1: BACKUPS/ MUSIC/ Movies1/ PICTURES/ /mnt/disk10: Movies1/ /mnt/disk11: Movies1/ /mnt/disk12: Movies1/ /mnt/disk13: Movies1/ /mnt/disk2: Movies1/ /mnt/disk3: Movies1/ /mnt/disk4: Movies1/ /mnt/disk5: Movies1/ /mnt/disk6: Movies1/ /mnt/disk7: Movies1/ /mnt/disk8: Movies1/ /mnt/disk9: Movies1/ Link to comment
dlandon Posted May 18, 2015 Author Share Posted May 18, 2015 Version 2.16 is ready with the fix for disk10 and 20. Link to comment
johnieutah Posted June 17, 2015 Share Posted June 17, 2015 @dlandon You know what I want - and I reckon I am not alone on this one - is a nice big button on the main dashboard "power" or something, that when clicked will allow me to either shutdown the server or reboot it. Unraid needs more WAF Anyone if it's in the pipeline?!? Link to comment
Frank1940 Posted June 17, 2015 Share Posted June 17, 2015 @dlandon You know what I want - and I reckon I am not alone on this one - is a nice big button on the main dashboard "power" or something, that when clicked will allow me to either shutdown the server or reboot it. Unraid needs more WAF Anyone if it's in the pipeline?!? You really need to post this over in this thread: http://lime-technology.com/forum/index.php?topic=36543.0 By the way, you are not the first to request this. Oh, and I admire your courage! There is no way I would allow my wife access to the administration of either of my servers. Link to comment
archedraft Posted June 23, 2015 Share Posted June 23, 2015 Those of you needing to shutdown VMs before shutting down can add those also. The alphabetic file name order is the sequence in which they are processed. The Kxx files are processed when the unRAID array is stopping or a powerdown is occuring. This provides a bit more orderly shutdown of the VM. If the Kxx script is not provided, powerdown will kill the VM and this may not be the cleanest way to shutdown the VM. Do you happen to know if the Kxx script are executed before libvirt is stopped by unRAID? Also, when this plugin is installed, will unRAID also shutdown with these options no matter which method is used to shutdown unRAID (for example, if my UPS sends a shutdown command will the kxx scripts be triggered)? I need to force shut down a VM that I believe is causing my system to hang. Link to comment
mr-hexen Posted July 22, 2015 Share Posted July 22, 2015 Found a typo in the plugin instructions upon installation. # Diagnostic mode for quick syslog dump/save to /boot/logs # call as /etc/rc.d/[glow=red,2,300]e[/glow]c.unRAID diag # call as /etc/rc.d/rc.unRAID syslog Link to comment
dlandon Posted July 22, 2015 Author Share Posted July 22, 2015 Found a typo in the plugin instructions upon installation. # Diagnostic mode for quick syslog dump/save to /boot/logs # call as /etc/rc.d/[glow=red,2,300]e[/glow]c.unRAID diag # call as /etc/rc.d/rc.unRAID syslog Thanks for the heads up. I'll fix and update the plugin. Link to comment
archedraft Posted July 25, 2015 Share Posted July 25, 2015 Does anyone happen to know if the "powerdown" command from this plugin is triggered when the built in APC UPS program tells unRAID to shutdown? Link to comment
dlandon Posted July 25, 2015 Author Share Posted July 25, 2015 Does anyone happen to know if the "powerdown" command from this plugin is triggered when the built in APC UPS program tells unRAID to shutdown? Yes. All powerdown, shutdown, and reboot events are be handled by this plugin. Link to comment
goinsnoopin Posted August 3, 2015 Share Posted August 3, 2015 I have an issue where my webgui has locked up. See this post for info: http://lime-technology.com/forum/index.php?topic=41861.0 I am able to telnet into unraid. I have the powerdown plugin installed, however when I run it, I get the message that powerdown v2.17 is executed (or something like that) its been 3.5 hours and the server has not shut down. Any suggestions? What is the safest way for me to powerdown? Dan Link to comment
Frank1940 Posted August 3, 2015 Share Posted August 3, 2015 I have an issue where my webgui has locked up. See this post for info: http://lime-technology.com/forum/index.php?topic=41861.0 I am able to telnet into unraid. I have the powerdown plugin installed, however when I run it, I get the message that powerdown v2.17 is executed (or something like that) its been 3.5 hours and the server has not shut down. Any suggestions? What is the safest way for me to powerdown? Dan Try a short press of the power switch (or button, if you prefer) on the server. Do NOT hold it down!!! That may do the trick. (If you hold the button down for several seconds, that will force a shutdown but it will be unclean and a parity check will start on restart. Basically, A sort of last resort.) Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.