unRAID Server Release 5.0-rc13 Available

[peter_sm]

I updated the the RC13 with kernel 3.9.5 and tested in my VM, on the VM the gui never stop responding....., but however I never see that issue on my server .... "knock knock"

//Peter

[drawz]

sorry, I'm sure the answer is here some where, but when you say you got hit with the stopped array issue, what exactly do you mean?  Do you know the cause, like specific to a mb or other hardware?  I did read that some had issues when they stopped the array, and it wouldn't start again.  I guess they reboot to fix.  OR, are you saying that your server will just stop the array on it's own, and won't come back up?

 

This sounds serious, yet only a few people have this issue - why?  I want to know what to look for.

 

I meant the shutdown issue. I have been initiating shut down with the power button since when I tried it from the web GUI it froze. But this morning after shutting down, when I brought it back up the array was stopped and it should not have been. So I reverted back to rc12a for now. No idea what causes it, but I'll check out rc13 back on my primary unRAID to see if that ends up showing the same issue.

 

This is 99.9% likely a plugin issue, not a core release issue. I have had many issues with the web GUI and they are always related to a plugin process hanging or not failing gracefully. Try removing all your pulgins and you'll probably have no issues.

 

When this crops up for me, I can telnet in and look for webGUI hook that is stuck. Since almost all plugins have some shutdown action on array stop, you'll likely see one of your plugins is not shutting down properly and not returning properly, so the GUI is waiting for it to complete - usually a permissions issue, broken download URL, or something like that. From there you can either try and fix the shut-down problem, or alert the plugin author that there is a case that the plugin does not exit gracefully.

 

Cheers,

 

whiteatom

 

Since plugins will be supported in 5.0 final, it would seem that the plugin spec should specify how plugins should handle these scenarios more gracefully and with appropriate error logging. Either that or the webGUI should have a time-out period to go ahead and kill the plugin if it does not respond in a reasonable amount of time. Perhaps both would be the most reliable.

[Frank1940]

I updated the the RC13 with kernel 3.9.5 and tested in my VM, on the VM the gui never stop responding....., but however I never see that issue on my server .... "knock knock"

//Peter

 

While I hope this might be a solution, it scares me to see another another kernel upgrade.  It seems lately that each new kernel upgrade to fix one problem introduces two more... 

[optiman]

ok, I for sure do not have that issue.  I can stop and then reboot, powerdown, or restart without problems. I'm running SF, which will stop responding sometimes, but I can use unmenu or putty to reboot.

 

wow that is scary, glad I don't have that issue (knock on wood)

 

well I hate to say it, but I had to roll back to rc12a.  I really try hard not to rollback, but web gui non responsive issues were more than I could take.  SF would die in almost no time, making me use unmenu to stop the array.  Well, I said above that I could stop and start, well the last couple of days the SF gui would die almost as soon as the server was done booting.  I then had issues with unmenu, were I would Stop the Array and it too would become unresponsive.  I think at this point my server has crashed.  I cannot use Putty, no web gui access, nothing.  Using the console is all I had, so it sounds like I too had the same issues as many of you have reported.  I just used the powerdown via the console, which also didn't fully powedown.  I would then have to run the Reboot.  Nothing seems to work right now..  I saved some logs, but just decided to try rolling back to rc12a.  Well all my issues seem to be gone, rebooted several times with no issues and the SF gui is just fine.  I'm sure SF will still die every now and then as it did before, but whatever rc13 brought to the table messed something up with the Array Management commands and killed SF, and thus my webgui.

 

To test, just try to Stop your Array, assuming you can get to your webgui.  If you still have a webgui after Stopping, and you have options to do anything else, you're ok.  I get no response and even had to hold the power button a couple of times to get the dam thing to restart.

 

 

[sacretagent]

i also went back to 12a

the not shutting down issue is a big deal breaker .....

i attached last syslog but i am affraid it ia a bit of a mess

 

first i did swapoff -a

then /sbin/powerdown

 

then i saw that was not working

so i did another /sbin/shutdown -h now

 

and again not shutting down

so i hold the powerbutton

 

of course he is running another parity check again.. third or fourth in last 2 days

syslog.zip

[tr0910]

I looked in your "syslog_2013-06-09_01.02_Crashed" log, and it seems like the power-down was done by some third party plugin.

Apparently that plugin makes some incorrect assumptions about unRaid.

If you really need to power-down your server through a script, the proper way to do it would beto use the following powerdown script:

 

I too expected this to be the cause of the problem, however it works fine if rsync is commented out.  Uncommenting the rsync causes the failure, so it would appear that the standard rsync is to blame.  One unRaid box (rc12a) starts another up (rc13) with ipmi and rsyncs updates to it then shuts it (rc13) off.  It is during the shut off that it (rc13) crashes.  If the rsync is commented out it doesn't crash.  Here is what it does:  (check out the script file uploaded earlier for full code details)

 

Startup another unRaid computer (rc13) from 192.168.1.106 (rc12a).  
ipmitool -I lan -H 192.168.1.149 -U ADMIN -P ADMIN chassis power on  (<--- this is starts up rc13 fine)
.
Do some rsync stuff  (this is what causes the failure)
.
ipmitool -I lan -H 192.168.1.149 -U ADMIN -P ADMIN chassis power soft  (<--- tell rc13 that it can do a soft shutdown)
Shutdown the rc13 unRaid computer. (here is where it crashes, but only if rsync was run) 

 

Still I'm interested in your script if it will startup another unRaid box from completely shut down.  Didn't know this was possible without using ipmi.  How do I run your code on server 192.168.1.106 to start up 192.168.1.149 ?

http://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface

[garycase]

Are either of the PowerDown plugins you referenced the one that's installed if you select that package in UnMenu ??

 

[garycase]

... FYI, the UnMenu package manager lists its package as "powerdown-1.02-noarch-unRAID.tgz"

 

[garycase]

Joe L  ==>  Any plan to update the Powerdown in UnMenu?    ... or is there a good reason to leave the older plugin in place?

 

I just did an "Update check" in UnMenu to be sure I didn't just miss a change to a newer version; but it doesn't show any updates for Powerdown.

 

[sacretagent]

i also went back to 12a

the not shutting down issue is a big deal breaker .....

i attached last syslog but i am affraid it ia a bit of a mess

 

From your syslog...

Jun  9 11:04:06 P8H67 kernel: FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

The filesystem on your USB flash disk is corrupted. Take the USB flash disk to a windows machine and fix that with a chkdsk

 

 

then /sbin/powerdown

then i saw that was not working

There's no /sbin/powerdown. Now the powerdown command resides in /usr/local/sbin/ and that's in the searchpath. (If you like, you can use the replacement for it from my signature.)

 

 

so i hold the powerbutton

You too have installed some third-party plugin to do your powerdowns in some unusual way.

Jun  9 23:13:41 P8H67 rc.unRAID[14748]: Killing active pids on the array drives
Jun  9 23:14:09 P8H67 rc.unRAID[15584]: Killing active pids on the array drives

Looks like that plugin hooks itself by means of /etc/rc.d/rc.local_shutdown or something and so it gets itself executed every time you try ro powerdown your computer.  It will be interesting to see if you can reproduce a server crash after removing that plugin.

 

damn will check the flashdrive once the parity check completes in 8 hours or so

the powerdown script is the one from unmenu

have been using it since i started and i know it is not the unraid one but this one stops all plugins before it stops the array and is for 95% doing a good job...

sometimes it takes it a while to close all find demons but otherwise it always worked

 

anyway i tried yesterday one time to stop the array too with the effect that was described from other people aka no acccess to the server any more

but we will see.... i will checkdsk the flashdrive and try again.... pity it is the server with virtualbox so will need to upgrade again

 

[itimpi]

I found that if you get the system crash when trying to stop the array, then you always get this issue of the USB stick being reported as having been not properly unmounted on the next boot.  I guess it is a side-effect of the crash happening at an inappropriate time.

[freekie]

... FYI, the UnMenu package manager lists its package as "powerdown-1.02-noarch-unRAID.tgz"

 

Well, that package is from Oct 26, 2008.  Many things have changed since then.  The package may be making some incorrect assumptions about the current unRaid.  It may, or may not have anyhing to do with the problem.  It is just an interesting coincidence that of all the people who've reported this problem so far, they've all been using that plugin.

 

I've not got it installed and I have the shutdown problem!

 

I'll try replacing all of the files on the flash-drive when I get home to see if that solves it. It appears to have worked for others.

[NAS]

Does anyone else find it frustrating that almost every oddball bug report can be traced back to something other than stock unRAID.

 

We are never going to get anywhere at this rate

[Chris Pollard]

Does anyone else find it frustrating that almost every oddball bug report can be traced back to something other than stock unRAID.

 

We are never going to get anywhere at this rate

 

/agree

[GrantR]

Thats fantastic, looking forward to the final release.

 

I take it that ipv6 support is not going to make 5 final if no other major additions are to come? I saw it in IssueList for version 5.x

Right, didn't want to delay the release further since this will involve a lot of extra testing.

 

Understood, happy to help with testing when you get around to implementing ipv6,

[Joe L.]

Joe L  ==>  Any plan to update the Powerdown in UnMenu?    ... or is there a good reason to leave the older plugin in place?

 

I just did an "Update check" in UnMenu to be sure I didn't just miss a change to a newer version; but it doesn't show any updates for Powerdown.

I was not the author.  I don't think it has ever been updated. I do know some download it directly.  Do you know of an updated version? Or an alternative?

 

You might be correct in that it does not hook into the current unRAID's event system.

 

A lot may have to do with HOW the shutdown is being initiated.

 

Questions that might give more clues are:

  Do you have SimpleFeatures web-interface installed?

  Do you have the "clean-powerdown" package installed?

  What is the output when you type: 'which powerdown'

  Do you have the apcupsd UPS package installed (through unMENU, or directly downloaded)?

  Do you have the apcupsd UPS plugin installed (through SimpleFeatues)?

  Are you stopping the array first using the web-interface?

  Are you using the web-interface to power down the array?

  Are you using the server chassis "power button" (short press) to initiate a power down?

  Are you using "control-Alt-delete" to initiate a power down?

 

Joe L.

[sacretagent]

well make a gui that allows us to boot in unraid without plugins and one normal boot ??

removing all plugins is simply not practical takes too much time and disabling them in the gui is not same as without loading them

(wife want the latest tvshow, kid wants the latest cartoon )

so all time that is left is a quick reboot to activate the new version

if there would be some cooperation from lime tech on the plugin standards with a dependency checking then a lot of issues would not arrize

also we all thought RC13 would be a quick update from rc12a..... not a kernel upgrade that fucks up everything again

anyway it is proven already that it is not the shutdown plugin

 

... FYI, the UnMenu package manager lists its package as "powerdown-1.02-noarch-unRAID.tgz"

 

Well, that package is from Oct 26, 2008.  Many things have changed since then.  The package may be making some incorrect assumptions about the current unRaid.  It may, or may not have anyhing to do with the problem.  It is just an interesting coincidence that of all the people who've reported this problem so far, they've all been using that plugin.

 

I've not got it installed and I have the shutdown problem!

 

I'll try replacing all of the files on the flash-drive when I get home to see if that solves it. It appears to have worked for others.

 

Barzija

 

no crash ... just the server not shutting down properly which results in a parity check.....

 

anyhow ... what does this powerdown script from yours do and how to install it ?

 

 

[garycase]

I was not the author. 

 

Ah, I wasn't aware of that.  I run as close to "stock" UnRAID as you can get with UPS support ... or at least I thought that was the case.  Both of my systems are just UnRAID plus UnMenu with the APC package and the Clean Powerdown package.  I guess I trusted that UnMenu would ensure those two packages were up-to-date if I occasionally use the "Check for Updates" feature.

 

I don't know if I have the shutdown issue or not ... I've never shut down since installing RC13 

And at this point probably won't unless we have a power outage ... otherwise I'll wait for a fix.

 

Is there a "better" Powerdown package that I should be using?

 

[sacretagent]

Joe

 

answers underneath

 

 

  Do you have SimpleFeatures web-interface installed? YES

  Do you have the "clean-powerdown" package installed? YES

  What is the output when you type: 'which powerdown' /sbin/powerdown

  Do you have the apcupsd UPS package installed (through unMENU, or directly downloaded)?NOPE

  Do you have the apcupsd UPS plugin installed (through SimpleFeatues)?NOPE

  Are you stopping the array first using the web-interface?NOPE

  Are you using the web-interface to power down the array?NOPE

  Are you using the server chassis "power button" (short press) to initiate a power down?NOPE

  Are you using "control-Alt-delete" to initiate a power down?NOPE

 

I use cron to

1. swapoff -a

5 minutes wait

2./sbin/powerdown

 

it works like i said 95% of the time in 12a

and the 5% it doesn't it seems that something else is keeping the array busy....

most of the time find demons still running

in an oddball case old samba threads that do not close for some reason

normally powerdown should stop swap too but i noticed depending how much swap usage you have it doesn't always work

so i give it some extra time to turn off

 

[Joe L.]

anyhow ... what does this powerdown script from yours do and how to install it ?

Oh, it's nothing special really. It's mostly the stock powerdown, just slightly modified to make it a little more general. It doesn't (yet) have functionality like that old plugin that you're using. And no special installation is needed, you can simply copy it over the stock powerdown from the go script.

It is slightly more complicated than at first glance.

 

Lime-technology distributes a "powerdown" command in /usr/local/sbin/powerdown.  It is a shell script that looks like this:

#!/bin/bash
#
# Helper script to gracefully power-down unRAID server.
# Works only if webGui is running and listening on port 80.

# Access a blank page in case this is first request since startup.
/usr/bin/wget -q -O - localhost/update.htm >/dev/null

# Have emhttp do all the work as if user clicked 'shutdown' in webGui.
/usr/bin/wget -q -O - localhost/update.htm?shutdown=apply >/dev/null

The stock script depends on emhttp responding.

 

The clean powerdown command package is installed at /sbin/powerdown

 

Unfortunately, the PATH for unRAID has /usr/local/sbin before /sbin so just invoking "powerdown" will get the lime-tech supplied command. 

To eliminate any confusion, the unMENU clean-powerdown package re-names the lime-tech supplied command to "/usr/local/sbin/unraid_powerdown"  after installing itself as /sbin/powerdown.

 

If unRAID was explicitly calling /usr/local/sbin/powerdown, using a full path, it would not be found.  (To my knowledge, it is called with a relative path, so it is found)

Joe L.

 

 

[garycase]

# Works only if webGui is running and listening on port 80.

 

Joe ... My understanding is that the script installed via UnMenu (the "Clean PowerDown" script) does not have this restriction -- right?

 

I know that's the script that's called by the APC UPS package if it needs to shut down;  and I assume it's also "tied" to the power button (is that right??);  but which script runs when you click on the Web GUI Shutdown button?    I had thought that was the original UnRAID one; but from your description it seems like it's not (since the original one has been renamed).

 

And the real Bottom Line:  Do you think this script is responsible for the RC13 shutdown issues

 

[itimpi]

And the real Bottom Line:  Do you think this script is responsible for the RC13 shutdown issues

I am getting RC13 shutdown issues with NO plugins installed so if there is a problem it with the unRAID version.

[WeeboTech]

While it could be that script (which is mine). It looks like emhttp is going into some kind of loop unloading and reloading the driver.

Jun  9 23:14:04 P8H67 status[15375]: SMART overall-health self-assessment test result: PASSED
Jun  9 23:14:04 P8H67 emhttp: shcmd (122): rmmod md-mod |& logger
Jun  9 23:14:04 P8H67 emhttp: shcmd (123): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger
Jun  9 23:14:04 P8H67 emhttp: shcmd (124): udevadm settle
Jun  9 23:14:04 P8H67 kernel: md: unRAID driver removed
Jun  9 23:14:04 P8H67 kernel: md: unRAID driver 2.1.6 installed
Jun  9 23:14:04 P8H67 emhttp: Device inventory:


...
Jun  9 23:14:04 P8H67 status[15375]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
Jun  9 23:14:04 P8H67 status[15375]: SMART overall-health self-assessment test result: PASSED
Jun  9 23:14:04 P8H67 emhttp: shcmd (125): /usr/local/sbin/emhttp_event driver_loaded
Jun  9 23:14:04 P8H67 kernel: mdcmd (13): import 12 8,64 976762552 Hitachi_HDS721010KLA330_GTF000PBH2M1ZF
...
Jun  9 23:14:04 P8H67 kernel: mdcmd (24): import 23 0,0
Jun  9 23:14:04 P8H67 emhttp_event: driver_loaded
...
jun  9 23:14:07 P8H67 status[15375]: SMART overall-health self-assessment test result: PASSED
Jun  9 23:14:08 P8H67 emhttp: shcmd (126): rmmod md-mod |& logger
Jun  9 23:14:08 P8H67 emhttp: shcmd (127): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger
Jun  9 23:14:08 P8H67 emhttp: shcmd (128): udevadm settle
Jun  9 23:14:08 P8H67 emhttp: Device inventory:
...
Jun  9 23:14:08 P8H67 emhttp: WDC_WD10EADS-00L5B1_WD-WCAU4C868508 (sdp) 976762584
Jun  9 23:14:08 P8H67 kernel: md: unRAID driver removed
Jun  9 23:14:08 P8H67 kernel: md: unRAID driver 2.1.6 installed
Jun  9 23:14:08 P8H67 kernel: mdcmd (1): import 0 8,48 1953514552 ST2000DM001-1CH164_W1E25MDK
Jun  9 23:14:08 P8H67 kernel: md: import disk0: [8,48] (sdd) ST2000DM001-1CH164_W1E25MDK size: 1953514552
Jun  9 23:14:08 P8H67 kernel: mdcmd (2): import 1 8,80 1953514552 SAMSUNG_HD204UI_S2H7J9BB209255
...
Jun  9 23:14:08 P8H67 kernel: md: import disk11: [65,0] (sdq) ST2000DL004_HD204UI_S2H7JX0D100186 size: 1953514552
Jun  9 23:14:08 P8H67 emhttp: shcmd (129): /usr/local/sbin/emhttp_event driver_loaded
Jun  9 23:14:08 P8H67 emhttp_event: driver_loaded
...
Jun  9 23:14:08 P8H67 status[15375]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
Jun  9 23:14:08 P8H67 status[15375]: SMART overall-health self-assessment test result: PASSED
Jun  9 23:14:08 P8H67 status[15375]: No active PIDS on the array
Jun  9 23:14:09 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Adult No such file or directory
Jun  9 23:14:09 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/BIN No such file or directory
Jun  9 23:14:09 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Backup Home No such file or directory
Jun  9 23:14:09 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Ebooks No such file or directory
Jun  9 23:14:09 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Music No such file or directory
Jun  9 23:14:09 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Music.Clips No such file or directory
Jun  9 23:14:09 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Operating.systems No such file or directory
Jun  9 23:14:09 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Other.Video No such file or directory
Jun  9 23:14:09 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Stand.Up.Comedy No such file or directory
Jun  9 23:14:09 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Thumbnails No such file or directory
Jun  9 23:14:09 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Toolbox No such file or directory
Jun  9 23:14:09 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Work No such file or directory
Jun  9 23:14:09 P8H67 emhttp: shcmd (130): rmmod md-mod |& logger
Jun  9 23:14:09 P8H67 kernel: md: unRAID driver removed
Jun  9 23:14:09 P8H67 emhttp: shcmd (131): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger
Jun  9 23:14:09 P8H67 emhttp: shcmd (132): udevadm settle
Jun  9 23:14:09 P8H67 emhttp: Device inventory:
...
Jun  9 23:14:09 P8H67 kernel: md: import disk3: [8,128] (sdi) WDC_WD20EARX-00ZUDB0_WD-WCC1H0580698 size: 1953514552
Jun  9 23:14:09 P8H67 rc.unRAID[15584]: Killing active pids on the array drives
Jun  9 23:14:09 P8H67 kernel: mdcmd (5): import 4 8,192 976762552 Hitachi_HDT721010SLA360_STF6L7MS38PHNK
Jun  9 23:14:09 P8H67 kernel: mdcmd (24): import 23 0,0
Jun  9 23:14:09 P8H67 emhttp_event: driver_loaded
Jun  9 23:14:10 P8H67 rc.unRAID[15725]: Umounting the drives
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk1: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk1 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk10: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk10 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk11: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk11 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk12: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk12 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk13: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk13 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk14: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk14 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk15: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk15 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk16: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk16 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk2: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk2 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk3: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk3 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk4: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk4 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk5: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk5 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk6: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk6 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk7: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk7 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk8: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk8 in mtab
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: umount: /mnt/disk9: not mounted
Jun  9 23:14:10 P8H67 rc.unRAID[15729]: Could not find /mnt/disk9 in mtab
Jun  9 23:14:10 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Adult No such file or directory
Jun  9 23:14:10 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/BIN No such file or directory
Jun  9 23:14:10 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Backup Home No such file or directory
Jun  9 23:14:10 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Ebooks No such file or directory
Jun  9 23:14:10 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Music No such file or directory
Jun  9 23:14:10 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Music.Clips No such file or directory
Jun  9 23:14:10 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Operating.systems No such file or directory
Jun  9 23:14:10 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Other.Video No such file or directory
Jun  9 23:14:10 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Stand.Up.Comedy No such file or directory
Jun  9 23:14:10 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Thumbnails No such file or directory
Jun  9 23:14:10 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Toolbox No such file or directory
Jun  9 23:14:10 P8H67 emhttp: get_filesystem_status: statfs: /mnt/user/Work No such file or directory
Jun  9 23:14:10 P8H67 rc.unRAID[15749]: Stopping the Array
Jun  9 23:14:10 P8H67 kernel: mdcmd (25): stop 
Jun  9 23:14:10 P8H67 kernel: md: stop_array: not started
Jun  9 23:14:13 P8H67 emhttp: shcmd (134): rmmod md-mod |& logger
Jun  9 23:14:13 P8H67 emhttp: shcmd (135): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger
Jun  9 23:14:13 P8H67 emhttp: shcmd (136): udevadm settle
Jun  9 23:14:13 P8H67 kernel: md: unRAID driver removed
Jun  9 23:14:13 P8H67 kernel: md: unRAID driver 2.1.6 installed
Jun  9 23:14:13 P8H67 emhttp: Device inventory:
...
Jun  9 23:14:13 P8H67 kernel: mdcmd (24): import 23 0,0
Jun  9 23:14:13 P8H67 emhttp: shcmd (137): /usr/local/sbin/emhttp_event driver_loaded
Jun  9 23:14:13 P8H67 emhttp_event: driver_loaded
...

[garycase]

And the real Bottom Line:  Do you think this script is responsible for the RC13 shutdown issues

I am getting RC13 shutdown issues with NO plugins installed so if there is a problem it with the unRAID version.

 

Just to confirm ... you mean absolutely NO plugins => no UnMenu, no SimpleFeatures, etc.  Just plain, stock UnRAID.  Is that correct?

 

... and does it happen every time?

 

[garycase]

While it could be that script (which is mine).

 

It would seem from itimpi's post above that it's NOT the script 

 

Sorry for my incorrect attribution of the script to Joe in an earlier post.  For some reason I had always thought that was his, since it's one of the key scripts in UnMenu.   

 

From my perspective, it's always worked very well ... my systems have certainly shut down as they should whenever we've had extended power outages  ==>  Usually once or twice a year ... although based on my v4.7 runtime at the moment, we're doing pretty good this year -- I'm at 185 days and counting.

 

My v5 RC13 system is only at 6+ days (since I updated to RC13).    I haven't shut it down since installing RC13 ... not sure I want to take the chance !!