New powerdown script needed for 5.0 unRAID

But have you let apc do the shutdown

 

A good question.  My understanding (could be wrong) is that the process when shutdown through the Web GUI is NOT the same as when the CleanPowerdown package is invoked by the APC UPS package.    If that's the case, the only real test is to either push the power button (Assuming I'm correct that this is "tied" to the CleanPowerdown package when it's installed);  use Ctrl-Alt-Del on the UnRAID system (which I know IS tied to CleanPowerdown); or simply unplug the UPS and let it do the shutdown as a result of the "power failure."

 

 

I second the question.

If I upgrade to RC14 (from RC12a) and have simplefeatures and the APC plugin installed do I need a new powerdown script?

 

I have just done this gone from 12a to 14 and have SF and APC plugin installed along with the Serviio and transmission plugins and i was able to shut down and restart with out any issues, tried it a few times to be sure.

 

But have you let apc do the shutdown

 

Good question, guess ill try tonight yanking power on the UPS.

This brought to the fore the fact that there is no official way to close down an unRAID system when the GUI stops responding.

 

I believe the power button will do a clean shutdown IF the CleanPowerdown package is installed.  Not absolutely certain of this ... but I do know the power button does the trick on both of my systems.

 

I second the question.

If I upgrade to RC14 (from RC12a) and have simplefeatures and the APC plugin installed do I need a new powerdown script?

 

I have just done this gone from 12a to 14 and have SF and APC plugin installed along with the Serviio and transmission plugins and i was able to shut down and restart with out any issues, tried it a few times to be sure.

 

But have you let apc do the shutdown

 

Good question, guess ill try tonight yanking power on the UPS.

To possibly save yourself a lot of time, before you pull the plug for the first test tonight, stop the array from the management web-page.

Then pull the plug and let APCUPSD power it down.  If it does, great,  then try a second test with the array left started.

 

If by some chance the first test requires you to force the array to power off, you'll not be faced with a lengthy parity check upon power up since the array had been stopped.

 

Joe L.

I second the question.

If I upgrade to RC14 (from RC12a) and have simplefeatures and the APC plugin installed do I need a new powerdown script?

 

I have just done this gone from 12a to 14 and have SF and APC plugin installed along with the Serviio and transmission plugins and i was able to shut down and restart with out any issues, tried it a few times to be sure.

 

But have you let apc do the shutdown

 

Good question, guess ill try tonight yanking power on the UPS.

To possibly save yourself a lot of time, before you pull the plug for the first test tonight, stop the array from the management web-page.

Then pull the plug and let APCUPSD power it down.  If it does, great,  then try a second test with the array left started.

 

If by some chance the first test requires you to force the array to power off, you'll not be faced with a lengthy parity check upon power up since the array had been stopped.

 

Joe L.

 

Thanks for the tip Joe, ill report back tonight with my findings if no one else has.

Thanks for the tip Joe, ill report back tonight with my findings if no one else has.

 

Thanks again Joe -- that's a good tip.  Just tested it and all's well.

 

Stopped the array; yanked the UPS plug;  waited for it to turn everything off.    Plugged the UPS back on ... sent a WOL packet to turn on the system ... and all is well.

 

That's on a SuperMicro X7SPA-H-D525-O, just in case the board/chipset matters (it very well may).    Running v5 RC14 without the 4GB option (board has 8GB installed).

 

From what I remember, the current version of the script was designed as a last ditch effort to power down the system in some safe manner.

 

We'll have to test it with RC14 to see how emhttp behaves with having filesystems mounted from underneath it.

 

Given that we now have events from emhttp, this script is probably not needed any more.

I'll do some investigation over the weekend.

 

Just repeated the earlier test (yanking the UPS power), but this time didn't stop the array first.

 

Same sequence -- yanked the power; waited for all to shut down;  plugged the UPS back in;  sent a WOL to turn on the server; and then tested the result.  Everything's just fine.

 

So ... at least on my system, the current CleanPowerdown installed by UnMenu is doing its job nicely 

 

I do NOT know, of course, if this would work as nicely if emhttp had stopped running -- but my understanding is that the CleanPowerdown script does not depend on any emhttp functions ... is that correct?

 

From what I remember, the current version of the script was designed as a last ditch effort to power down the system in some safe manner.

 

We'll have to test it with RC14 to see how emhttp behaves with having filesystems mounted from underneath it.

 

Given that we now have events from emhttp, this script is probably not needed any more.

I'll do some investigation over the weekend.

 

is emhttp a web server developed by tom? a lot of result coming from unraid on google

From what I remember, the current version of the script was designed as a last ditch effort to power down the system in some safe manner.

 

We'll have to test it with RC14 to see how emhttp behaves with having filesystems mounted from underneath it.

 

Given that we now have events from emhttp, this script is probably not needed any more.

I'll do some investigation over the weekend.

 

is emhttp a web server developed by tom? a lot of result coming from unraid on google

 

emhttp is the UnRAID Web GUI

 

I do NOT know, of course, if this would work as nicely if emhttp had stopped running -- but my understanding is that the CleanPowerdown script does not depend on any emhttp functions ... is that correct?

 

That was it's design years ago.

A fail safe to issue the correct mdcmd to stop the array so the superblock on the flash was updated.

 

It kills active pids

umounts filesystems

stops the md driver, which in turn updates the superblock on the flash drive.

 

From what I remember, the current version of the script was designed as a last ditch effort to power down the system in some safe manner.

 

We'll have to test it with RC14 to see how emhttp behaves with having filesystems mounted from underneath it.

 

Given that we now have events from emhttp, this script is probably not needed any more.

I'll do some investigation over the weekend.

 

is emhttp a web server developed by tom? a lot of result coming from unraid on google

basically, the answer to that is "yes"  (although I think I once found an old reference from an obscure site to something with the same name, they may come from the same roots)

 

I think it stands for "Event Machine HTTP" a simple event driven HTTP server.

Just repeated the earlier test (yanking the UPS power)

I'm not going to go into a long EE dissertation of why that is bad practice, just know you are risking the creation of a bad surge with nothing to absorb it. Next time just pop the breaker and leave the UPS grounded.

http://tldp.org/HOWTO/UPS-HOWTO/testing.html

I have personally seen equipment let the magic smoke out when someone just yanked the UPS supply cord.

Just repeated the earlier test (yanking the UPS power)

I'm not going to go into a long EE dissertation of why that is bad practice, just know you are risking the creation of a bad surge with nothing to absorb it. Next time just pop the breaker and leave the UPS grounded.

http://tldp.org/HOWTO/UPS-HOWTO/testing.html

I have personally seen equipment let the magic smoke out when someone just yanked the UPS supply cord.

 

I'm well aware of electrical spiking and grounding issues -- I actually did exactly what you noted (turned off the breaker).    "Yanking the plug" was a figurative term :-)    I don't even use the soft power switch on the PC unless I have to ... a WOL packet does the same thing.

 

"Yanking the plug" was a figurative term :-)

Perhaps you should be more careful with your phrasing to avoid misleading someone into an expensive mistake.

"Yanking the plug" was a figurative term :-)

Perhaps you should be more careful with your phrasing to avoid misleading someone into an expensive mistake.

 

Agree 

To possibly save yourself a lot of time, before you pull the plug for the first test tonight, stop the array from the management web-page.

 

...

 

If by some chance the first test requires you to force the array to power off, you'll not be faced with a lengthy parity check upon power up since the array had been stopped.

 

Joe ... I was thinking about this a bit more.  Does this mean that if the array is stopped [via either the button on the Web GUI or the button on the Array Management page in UnMenu], that you can safely do a FORCED system power-down [hold power button for 5 seconds] and there won't be a parity check on the next reboot ??

 

Also ...

 

Is there any functional difference between what happens with the Web GUI's STOP button and the Stop Array button in Unmenu ??

 

... same question r.e. the Power Down buttons on the Web GUI vs. the Power Down button on the User Scripts page in UnMenu ?

 

stock unraid

stop array in GUI and stop computer works fine

 

what doesn't work is the powerdown script any more

 

here is what happens with RC15

 

1. swapoff -a ... swap file gets disabled no issues

2. /sbin/powerdown

 

array gets disabled the right way

but seems after the array shuts down that the other addons get activated again

i see plex and python in top

also the console says going for shutdown .. but the console continues working

i had to shutdown the server by keeping the power button till he shutdown

 

this was working well till rc12.a

so not sure what has changed ... how can i put my server of gracefully from a cron setting ?

To possibly save yourself a lot of time, before you pull the plug for the first test tonight, stop the array from the management web-page.

 

...

 

If by some chance the first test requires you to force the array to power off, you'll not be faced with a lengthy parity check upon power up since the array had been stopped.

 

Joe ... I was thinking about this a bit more.  Does this mean that if the array is stopped [via either the button on the Web GUI or the button on the Array Management page in UnMenu], that you can safely do a FORCED system power-down [hold power button for 5 seconds] and there won't be a parity check on the next reboot ??

correct.  It the array is stopped, there will NOT be a parity check upon reboot if you force the power off.

Also ...

 

Is there any functional difference between what happens with the Web GUI's STOP button and the Stop Array button in Unmenu ??

Yes.  unRAID will NOT stop the array if any disk assigned to the array is "busy"

 

... same question r.e. the Power Down buttons on the Web GUI vs. the Power Down button on the User Scripts page in UnMenu ?

Yes, there are differences.

Power down button on user-scripts page simply invokes /sbin/powerdown 

unRAID web-interface never invokes powerdown.  It is all internal to emhttp.

 

Thanks Joe ... nice to know that all you really have to do is Stop the array to be "safe" when turning off the system ... even if you have to force it by holding in the soft-power button on the system.

 

ok why is this old script "working" on garycase setup and not on mine ?

don't understand that ...

 

like i said array shuts down ok but computer doesn't turn off ....

 

here is syslog from last night

 

started at 23:40 .. disabled swap

at 23:43

Jun 15 23:43:09 P8H67 root: Powerdown initiated

Jun 15 23:43:09 P8H67 rc.unRAID[20144]: Stopping unRAID.

 

and it seems he tried unmounting everything

Jun 15 23:43:20 P8H67 status[20263]: No active PIDS on the array

Jun 15 23:43:21 P8H67 rc.unRAID[20449]: Killing active pids on the array drives

Jun 15 23:43:21 P8H67 rc.unRAID[20452]: root    19426 19196 10 19:51 ?        00:24:26 /opt/VirtualBox/VBoxHeadless --comment Musicbrainz --startvm af78805d-8bd4-40c7-b079-a470da01ca5d --vrde config

Jun 15 23:43:21 P8H67 kernel: device eth0 left promiscuous mode

Jun 15 23:43:21 P8H67 kernel: vboxnetflt: dropped 0 out of 8180903 packets

Jun 15 23:44:13 P8H67 rc.unRAID[21307]: Umounting the drives

Jun 15 23:44:14 P8H67 rc.unRAID[21311]: /dev/md1 umounted

Jun 15 23:44:14 P8H67 rc.unRAID[21311]: /dev/md10 umounted

Jun 15 23:44:14 P8H67 rc.unRAID[21311]: /dev/md11 umounted

Jun 15 23:44:15 P8H67 rc.unRAID[21311]: /dev/md12 umounted

Jun 15 23:44:15 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Other.Video No such file or directory

Jun 15 23:44:15 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Thumbnails No such file or directory

Jun 15 23:44:15 P8H67 rc.unRAID[21311]: /dev/md13 umounted

Jun 15 23:44:15 P8H67 rc.unRAID[21311]: /dev/md14 umounted

Jun 15 23:44:16 P8H67 rc.unRAID[21311]: /dev/md15 umounted

Jun 15 23:44:16 P8H67 rc.unRAID[21311]: /dev/md16 umounted

Jun 15 23:44:16 P8H67 rc.unRAID[21311]: umount: /mnt/disk2: device is busy.

Jun 15 23:44:16 P8H67 rc.unRAID[21311]:        (In some cases useful info about processes that use

Jun 15 23:44:16 P8H67 rc.unRAID[21311]:          the device is found by lsof( or fuser(1))

Jun 15 23:44:16 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Backup Home No such file or directory

Jun 15 23:44:16 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Operating.systems No such file or directory

Jun 15 23:44:16 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Other.Video No such file or directory

Jun 15 23:44:16 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Stand.Up.Comedy No such file or directory

Jun 15 23:44:16 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Thumbnails No such file or directory

Jun 15 23:44:16 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Toolbox No such file or directory

Jun 15 23:44:16 P8H67 rc.unRAID[21311]: /dev/md3 umounted

Jun 15 23:44:17 P8H67 rc.unRAID[21311]: /dev/md4 umounted

Jun 15 23:44:17 P8H67 rc.unRAID[21311]: /dev/md5 umounted

Jun 15 23:44:17 P8H67 rc.unRAID[21311]: /dev/md6 umounted

Jun 15 23:44:17 P8H67 rc.unRAID[21311]: /dev/md7 umounted

Jun 15 23:44:17 P8H67 rc.unRAID[21311]: /dev/md8 umounted

Jun 15 23:44:17 P8H67 rc.unRAID[21311]: /dev/md9 umounted

Jun 15 23:44:18 P8H67 rc.unRAID[21404]: Stopping the Array

Jun 15 23:44:18 P8H67 kernel: mdcmd (157): stop

Jun 15 23:44:18 P8H67 kernel: md: 2 devices still in use.

 

but disk 2 was still in use

 

Jun 15 23:44:33 P8H67 status[21651]: No active PIDS on the array

Jun 15 23:44:34 P8H67 rc.unRAID[21804]: Killing active pids on the array drives

Jun 15 23:44:35 P8H67 rc.unRAID[21931]: Umounting the drives

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk1: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk1 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk10: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk10 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk11: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk11 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk12: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk12 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk13: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk13 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk14: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk14 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk15: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk15 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk16: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk16 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: /dev/md2 umounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk3: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk3 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk4: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk4 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk5: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk5 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk6: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk6 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk7: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk7 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk8: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk8 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: umount: /mnt/disk9: not mounted

Jun 15 23:44:35 P8H67 rc.unRAID[21935]: Could not find /mnt/disk9 in mtab

Jun 15 23:44:35 P8H67 rc.unRAID[21975]: Stopping the Array

Jun 15 23:44:35 P8H67 kernel: mdcmd (158): stop

Jun 15 23:44:35 P8H67 kernel: md1: stopping

Jun 15 23:44:35 P8H67 kernel: md2: stopping

Jun 15 23:44:35 P8H67 kernel: md3: stopping

Jun 15 23:44:35 P8H67 kernel: md4: stopping

Jun 15 23:44:35 P8H67 kernel: md5: stopping

Jun 15 23:44:35 P8H67 kernel: md6: stopping

Jun 15 23:44:35 P8H67 kernel: md7: stopping

Jun 15 23:44:35 P8H67 kernel: md8: stopping

Jun 15 23:44:35 P8H67 kernel: md9: stopping

Jun 15 23:44:35 P8H67 kernel: md10: stopping

Jun 15 23:44:35 P8H67 kernel: md11: stopping

Jun 15 23:44:35 P8H67 kernel: md12: stopping

Jun 15 23:44:35 P8H67 kernel: md13: stopping

Jun 15 23:44:35 P8H67 kernel: md14: stopping

Jun 15 23:44:35 P8H67 kernel: md15: stopping

Jun 15 23:44:35 P8H67 kernel: md16: stopping

Jun 15 23:44:36 P8H67 emhttp: shcmd (106): rmmod md-mod |& logger

Jun 15 23:44:36 P8H67 emhttp: shcmd (107): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger

Jun 15 23:44:36 P8H67 kernel: md: unRAID driver removed

Jun 15 23:44:36 P8H67 emhttp: shcmd (108): udevadm settle

Jun 15 23:44:36 P8H67 emhttp: Device inventory:

Jun 15 23:44:38 P8H67 init: no more processes left in this runlevel

Jun 15 23:44:39 P8H67 emhttp: shcmd (110): rmmod md-mod |& logger

Jun 15 23:44:39 P8H67 kernel: md: unRAID driver removed

Jun 15 23:44:39 P8H67 emhttp: shcmd (111): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger

Jun 15 23:44:39 P8H67 emhttp: shcmd (112): udevadm settle

 

he unmounted disk 2 finally

and unmounted the array as i said before

he didn't shut down so at

Jun 15 23:47:51 P8H67 root: Powerdown initiated

Jun 15 23:47:51 P8H67 rc.unRAID[27082]: Stopping unRAID.

i tried calling the original powerdoen script from unraid

/usr/local/sbin/unraid_powerdown

 

but somehow he still didn't want to shut down

you can clearly see the drives were not mounted

Jun 15 23:48:03 P8H67 rc.unRAID[27537]: Killing active pids on the array drives

Jun 15 23:48:04 P8H67 rc.unRAID[27645]: Umounting the drives

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk1: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk1 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk10: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk10 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk11: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk11 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk12: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk12 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk13: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk13 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk14: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk14 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk15: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk15 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk16: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk16 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk2: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk2 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk3: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk3 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk4: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk4 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk5: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk5 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk6: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk6 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk7: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk7 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk8: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk8 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: umount: /mnt/disk9: not mounted

Jun 15 23:48:04 P8H67 rc.unRAID[27649]: Could not find /mnt/disk9 in mtab

Jun 15 23:48:04 P8H67 rc.unRAID[27666]: Stopping the Array

Jun 15 23:48:04 P8H67 kernel: mdcmd (25): stop

Jun 15 23:48:04 P8H67 kernel: md: stop_array: not started

 

this went on till i stopped the server by pushing the powerbutton till he stopped

with as result that he didn't wol this morning ..... but no parity check as the array was unmounted

so what is preventing the system to shutdown ?

this is driving me bonkers that other people say it works and it won't work here ...... and also that it worked till rc12A only from rc13 it doesn't work any more

 

for those interested the issue is on the P8H67 in my signature

Unraid.zip

ok why is this old script "working" on garycase setup and not on mine ?

don't understand that ...

 

 

You may need to re-engineer your system so that addons/plugins gracefully shutdown via the rc scripts.

This script is hooked into those also

 

How is virtual box started and shutdown?

 

Maybe it needs to use the emhttp event system, or a script for it needs to be put there.

 

The power down script is a last ditch effort.

While it's been safe for all these years, the complexity of various configurations makes it difficult.

 

I can add a hook to call unRAID's original powerdown script or not replace it at all.

 

However, I'm not sure how to deal with all the other addons and plugins that people use.

 

If there are apps mounted on an array disk, emhttp is going to hang and retry until that is satisfied.

Which means, that the apps using array disks, need to really be part of emhttp events.

 

What happens if you don't install the powerdown script?

ok why is this old script "working" on garycase setup and not on mine ?

don't understand that ...

 

The simple answer is I don't know

 

A more complete -- and likely correct - answer is that my configuration isn't as complex as yours.  I run a very stock UnRAID system, with UnMenu as the only add-on, and only the APC UPS and PowerDown packages installed from the package manager.  NOTHING ELSE.