dlandon

It is the right place. This is just more convenient than having to do a copy in your 'go' file. Put these on the flash drive in the /boot/config/powerdown/custom/ directory and powerdown will take care of putting them in the /etc/rc.d/rc.unRAID.d/ directory for you.

Version 2.02 of powerdown is available. A directory on the flash drive is now available for your custom shutdown scripts. The directory is /boot/config/plugins/powerdown/custom/. Place any script files you want processed at the beginning of powerdown. The files should be named Kxx - where xx is 00-99. For those of you running VMs, you will need to provide a custom script so powerdown can shut them down before unRAID tries to stop Xen. I know you'd rather just have powerdown do that, but powerdown is being kept generic for both v5 and v6 (plain vanilla, and Xen). Because each user has unique needs, this is the best way to handle the situation.

All feedback is greatly appreciated. That's what Beta testing is all about. Thank you.

It appears that powerdown ran through it's process and completed. While I appreciate your frustration, both unRAID v6 and powerdown are Beta. This means that there will be issues to sort out. If you are not prepared to deal with any issues, you should wait until it is all sorted out.

There is a new version (2.02) of powerdown that handles your custom scripts. Powerdown creates a directory on the flash drive (/boot/config/plugins/powerdown/custom/) where you can put your Kxx scripts. Powerdown will manage them from there. This way you don't have to add any entries in your 'go' file.

It does not look like powerdown ran. There are no messages from powerdown. The first message you should see is "Powerdown initiated". Can you get a syslog? Send a syslog of your system once it boots before you powerdown. Run the system without plugins (except for powerdown), stop the array in the webgui, and then run powerdown. Verify you see the "Powerdown initiated" message and a version number. If you don't, post a syslog.

How do you place the script in /etc/rc.d/rc.unRAID.d/ on the flash drive? I'd suggest that you create the script file you want to use in the /boot/custom/ directory of the flash drive. Then you will need to add a line to the go file like this: cp /boot/custom/k00 /etc/rc.d/rc.unRAID.d/k00 That way the file will be copied on each boot.

The package is not installed automatically from there. On the OP is a plugin that you can put in /boot/config/plugins and the package will be installed on each boot. If you have apcupsd, then that can be used to install the package.

No. You create a script and add it to the /etc/rc.d/rc.unRAID.d/ directory with a name Kxx where xx - 00-99 and it will be run on shutdown. The reason this capability was added was to prevent lots of customization to powerdown. Each user has unique needs.

No. The powerdown package will create it. It doesn't look like the package is installed.

Yes. Yes. All required packages will be re-downloaded. Yes. But use the new 2.01 version. Correct.

I need some help from one of you Linux gurus. I am trying to have the powerdown script execute when the power button is pressed. I am doing this to the acpi_handler.sh script: sed -i -e "s/init 0/powerdown/" /etc/acpi/acpi_handler.sh #!/bin/sh # Default acpi script that takes an entry for all actions IFS=${IFS}/ set $@ case "$1" in button) case "$2" in power) /sbin/powerdown ;; *) logger "ACPI action $2 is not defined" ;; esac ;; *) logger "ACPI group $1 / action $2 is not defined" ;; esac When the power button is pressed, it appears to be running the init 0 runtime level. And executing "shutdown" and not my "powerdown" script. EDIT: I got it. When the power button is pressed, echo messages do not show up on the tty, but the script is running anyway.

Ok. I think I've found a potential race condition. The custom scripts in /etc/rc.d/rc.unRAID.d/ are processed after unraid tries to shut down Xen. The rc.unRAID script is called after that occurs so Xen shutdown is waiting, and rc.unRAID doesn't run and process the scripts to shutdown the VMs. i.e a race condition where everyone is stuck. I'm making a change to handle this situation and will release the fix as 2.01 after I do some testing.

I am not that familiar with VMs. Apparently powerdown cannot shut it down. You will have to provide a script to shut it down and put it in the /etc/rc.d/rc.unRAID.d/ directory. The name should be Kxx where xx is 00-99. VMware was previously stopped in powerdown because of a special need of a user. The way powerdown handles it now is to use custom scripts in the /etc/rc.d/rc.unRAID.d/ directory. The VMware stop was removed from powerdown. Can you also provide a syslog so I can see where powerdown is pausing?

There is a new feature in powerdown 2.00 to enable shutting down VMs. Please read the OP and you can see the instructions on how to do that. Basically you add your own script to perform the VM shutdown.

It should do that. If you happened to get the wrong version 2.00 I first uploaded, you can download it again by deleting the .tgz from the /boot/packages and rebooting.

There was a situation where some plugins were not shutdown properly and the array drives would not be unmounted forcing a parity check on the next start up. Doesn't sound like it affected you. There is a new feature added for handling shutting down VMs or other special shutdown circumstances. Thanks for testing it.

Do you have a link as well? Here: https://github.com/dlandon/unraid-snap/raw/master/powerdown-2.00-noarch-unRAID.tgz

The correct 2.00 version is now uploaded to GitHub.

unMenu is maintained by Joe L and he will probably update unMenu for the new powerdown package when it is confirmed to be working properly. Because powerdown is still being Beta tested, it's best to not use it until more confidence in its operation is gained. Yes. Joe L will have to do that. You should probably wait until unMenu and apcupsd are updated and not try to make any modifications at this point.

I uploaded the wrong version of powerdown to GitHub. I'm working on it now.

Version 2.00 of powerdown is available. Please read the OP for more details.

I have implemented a fix for this. This is the classic case of fixing one problem and creating another. The problem I fixed was when powerdown would hang up on shutdown. That has been fixed. An older bug in the script then showed up and created this problem. The new version will fix it. I am still testing because there have been quite a few changes and I want to be sure there are minimum problems. Going back to version 1.02 for the moment will keep this from happening.

Sure ... You seem to have multiple versions of the powerdown package installing. Modify your apcupsd plugin lines that install powerdown 1.02 to the following. <FILE Name="/boot/packages/powerdown-1.05-noarch-unRAID.tgz" Run="CTRLALTDEL=YES upgradepkg --install-new"> <URL>--no-check-certificate https://github.com/dlandon/unraid-snap/raw/master/powerdown-1.05-noarch-unRAID.tgz</URL> </FILE> This will install powerdown 1.05. Remove the plugin to install powerdown 1.05 if you installed that. Apcupsd takes care of the powerdown package installation.

Can you attach the full log?