WeeboTech Posted June 10, 2013 Share Posted June 10, 2013 FWIW, the rc.unRAID script should be practically one of the last things called as it's hooked into the system shutdown via /etc/rc.d/rc.local_shutdown it should be one of the last things called. grep 'Installing' syslog.txt Jun 9 11:04:06 P8H67 kernel: Installing knfsd (copyright (C) 1996 [email protected]). Jun 9 11:04:21 P8H67 logger: | Installing new package /boot/plugins/simpleFeatures/simpleFeatures.active.streams-1.0.10-i486-1.txz Jun 9 11:04:21 P8H67 logger: Installing package simpleFeatures.active.streams-1.0.10-i486-1.txz: Jun 9 11:04:21 P8H67 logger: | Installing new package /boot/plugins/simpleFeatures/simpleFeatures.activity.monitor-1.0.11-i486-1.txz Jun 9 11:04:22 P8H67 logger: Installing package simpleFeatures.activity.monitor-1.0.11-i486-1.txz: Jun 9 11:04:22 P8H67 logger: | Installing new package /boot/plugins/simpleFeatures/simpleFeatures.cache.dirs-1.0.11-i486-1.txz Jun 9 11:04:22 P8H67 logger: Installing package simpleFeatures.cache.dirs-1.0.11-i486-1.txz: Jun 9 11:04:22 P8H67 logger: | Installing new package /boot/plugins/simpleFeatures/simpleFeatures.core.webGUI-1.0.11-i486-1.txz Jun 9 11:04:22 P8H67 logger: Installing package simpleFeatures.core.webGUI-1.0.11-i486-1.txz: Jun 9 11:04:22 P8H67 logger: | Installing new package /boot/plugins/simpleFeatures/simpleFeatures.disk.health-1.0.11-i486-1.txz Jun 9 11:04:22 P8H67 logger: Installing package simpleFeatures.disk.health-1.0.11-i486-1.txz: Jun 9 11:04:23 P8H67 logger: | Installing new package /boot/plugins/simpleFeatures/simpleFeatures.log.viewer-1.0.10-i486-1.txz Jun 9 11:04:23 P8H67 logger: Installing package simpleFeatures.log.viewer-1.0.10-i486-1.txz: Jun 9 11:04:23 P8H67 logger: | Installing new package /boot/plugins/simpleFeatures/simpleFeatures.system.info-1.0.10-i486-1.txz Jun 9 11:04:23 P8H67 logger: Installing package simpleFeatures.system.info-1.0.10-i486-1.txz: Jun 9 11:04:23 P8H67 logger: | Installing new package /boot/plugins/simpleFeatures/simpleFeatures.system.stats-1.0.10-i486-1.txz Jun 9 11:04:23 P8H67 logger: Installing package simpleFeatures.system.stats-1.0.10-i486-1.txz: Jun 9 11:04:23 P8H67 logger: | Installing new package /boot/plugins/simpleFeatures/simpleFeatures.web.server-1.0.11-i486-1.txz Jun 9 11:04:24 P8H67 logger: Installing package simpleFeatures.web.server-1.0.11-i486-1.txz: Jun 9 11:04:25 P8H67 logger: | Installing new package /boot/packages/openssl-1.0.1c-i486-3.txz Jun 9 11:04:26 P8H67 logger: Installing package openssl-1.0.1c-i486-3.txz: Jun 9 11:04:28 P8H67 logger: | Installing new package /boot/packages/openssl-solibs-1.0.1c-i486-3.txz Jun 9 11:04:29 P8H67 logger: Installing package openssl-solibs-1.0.1c-i486-3.txz: Jun 9 11:04:29 P8H67 logger: | Installing new package /boot/packages/libmcrypt-2.5.8-i486-1.txz Jun 9 11:04:29 P8H67 logger: Installing package libmcrypt-2.5.8-i486-1.txz: Jun 9 11:04:29 P8H67 logger: | Installing new package /boot/packages/m4-1.4.16-i486-1.txz Jun 9 11:04:29 P8H67 logger: Installing package m4-1.4.16-i486-1.txz: Jun 9 11:04:29 P8H67 logger: | Installing new package /boot/packages/libtool-2.4.2-i486-1.txz Jun 9 11:04:30 P8H67 logger: Installing package libtool-2.4.2-i486-1.txz: Jun 9 11:04:30 P8H67 logger: | Installing new package /boot/packages/pcre-8.12-i486-1.txz Jun 9 11:04:30 P8H67 logger: Installing package pcre-8.12-i486-1.txz: Jun 9 11:04:30 P8H67 logger: | Installing new package /boot/packages/libzip-0.9.3-i486-1.txz Jun 9 11:04:30 P8H67 logger: Installing package libzip-0.9.3-i486-1.txz: Jun 9 11:04:30 P8H67 logger: | Installing new package /boot/packages/sqlite-3.7.14.1-i486-1.txz Jun 9 11:04:30 P8H67 logger: Installing package sqlite-3.7.14.1-i486-1.txz: Jun 9 11:04:31 P8H67 logger: | Installing new package /boot/packages/freetype-2.4.10-i486-1.txz Jun 9 11:04:31 P8H67 logger: Installing package freetype-2.4.10-i486-1.txz: Jun 9 11:04:31 P8H67 logger: | Installing new package /boot/packages/libjpeg-v8a-i486-1.txz Jun 9 11:04:31 P8H67 logger: Installing package libjpeg-v8a-i486-1.txz: Jun 9 11:04:31 P8H67 logger: | Installing new package /boot/packages/libpng-1.4.12-i486-1.txz Jun 9 11:04:31 P8H67 logger: Installing package libpng-1.4.12-i486-1.txz: Jun 9 11:04:31 P8H67 logger: | Installing new package /boot/packages/libX11-1.5.0-i486-1.txz Jun 9 11:04:32 P8H67 logger: Installing package libX11-1.5.0-i486-1.txz: Jun 9 11:04:33 P8H67 logger: | Installing new package /boot/packages/libXau-1.0.7-i486-1.txz Jun 9 11:04:33 P8H67 logger: Installing package libXau-1.0.7-i486-1.txz: Jun 9 11:04:33 P8H67 logger: | Installing new package /boot/packages/libxcb-1.8.1-i486-1.txz Jun 9 11:04:33 P8H67 logger: Installing package libxcb-1.8.1-i486-1.txz: Jun 9 11:04:33 P8H67 logger: | Installing new package /boot/packages/libXdmcp-1.1.1-i486-1.txz Jun 9 11:04:33 P8H67 logger: Installing package libXdmcp-1.1.1-i486-1.txz: Jun 9 11:04:33 P8H67 logger: | Installing new package /boot/packages/libXpm-3.5.10-i486-1.txz Jun 9 11:04:33 P8H67 logger: Installing package libXpm-3.5.10-i486-1.txz: Jun 9 11:04:34 P8H67 logger: | Installing new package /boot/packages/t1lib-5.1.2-i486-3.txz Jun 9 11:04:34 P8H67 logger: Installing package t1lib-5.1.2-i486-3.txz: Jun 9 11:04:34 P8H67 logger: | Installing new package /boot/packages/openssh-5.8p1-i486-1.txz Jun 9 11:04:34 P8H67 logger: Installing package openssh-5.8p1-i486-1.txz: Jun 9 11:04:38 P8H67 logger: Installing package openssl-0.9.8r-i486-3.txz: Jun 9 11:04:40 P8H67 logger: | Installing new package /boot/packages/cpio-2.11-i486-1.txz Jun 9 11:04:41 P8H67 logger: Installing package cpio-2.11-i486-1.txz: Jun 9 11:04:41 P8H67 logger: | Installing new package /boot/packages/mysql-5.5.25-i486-1gds.txz Jun 9 11:04:43 P8H67 logger: Installing package mysql-5.5.25-i486-1gds.txz: Jun 9 11:04:44 P8H67 logger: | Installing new package /boot/packages/libaio-0.3.109-i486-1.txz Jun 9 11:04:44 P8H67 logger: Installing package libaio-0.3.109-i486-1.txz: Jun 9 11:04:44 P8H67 logger: | Installing new package /boot/packages/python-2.6.6-i486-1.txz Jun 9 11:04:47 P8H67 logger: Installing package python-2.6.6-i486-1.txz: Jun 9 11:04:49 P8H67 logger: | Installing new package /boot/packages/zlib-1.2.5-i486-4.txz Jun 9 11:04:49 P8H67 logger: Installing package zlib-1.2.5-i486-4.txz: Jun 9 11:04:50 P8H67 logger: Installing package sqlite-3.7.5-i486-1.txz: Jun 9 11:04:50 P8H67 logger: | Installing new package /boot/packages/curl-7.21.4-i486-1.txz Jun 9 11:04:50 P8H67 logger: Installing package curl-7.21.4-i486-1.txz: Jun 9 11:04:50 P8H67 logger: | Installing new package /boot/packages/git-1.7.4.4-i486-1.txz Jun 9 11:04:51 P8H67 logger: Installing package git-1.7.4.4-i486-1.txz: Jun 9 11:07:15 P8H67 rc.virtualbox[26134]: Installing VirtualBox packages during array mount ... Jun 9 11:07:15 P8H67 rc.virtualbox[26160]: Installing Virtualbox package (v4.2.12)... Jun 9 11:07:23 P8H67 rc.virtualbox[26640]: Installing Virtualbox Extension package (v4.2.12)... grep /usr/local/sbin/emhttp_event syslog.txt Jun 9 11:04:53 P8H67 emhttp: shcmd (3): /usr/local/sbin/emhttp_event driver_loaded Jun 9 11:04:55 P8H67 emhttp: shcmd (27): /usr/local/sbin/emhttp_event array_started Jun 9 11:06:33 P8H67 emhttp: shcmd (101): /usr/local/sbin/emhttp_event disks_mounted Jun 9 11:07:32 P8H67 emhttp: shcmd (105): /usr/local/sbin/emhttp_event svcs_restarted Jun 9 23:13:54 P8H67 emhttp: shcmd (109): /usr/local/sbin/emhttp_event driver_loaded Jun 9 23:13:58 P8H67 emhttp: shcmd (113): /usr/local/sbin/emhttp_event driver_loaded Jun 9 23:13:59 P8H67 emhttp: shcmd (117): /usr/local/sbin/emhttp_event driver_loaded Jun 9 23:14:03 P8H67 emhttp: shcmd (121): /usr/local/sbin/emhttp_event driver_loaded Jun 9 23:14:04 P8H67 emhttp: shcmd (125): /usr/local/sbin/emhttp_event driver_loaded Jun 9 23:14:08 P8H67 emhttp: shcmd (129): /usr/local/sbin/emhttp_event driver_loaded Jun 9 23:14:09 P8H67 emhttp: shcmd (133): /usr/local/sbin/emhttp_event driver_loaded Jun 9 23:14:13 P8H67 emhttp: shcmd (137): /usr/local/sbin/emhttp_event driver_loaded grep 'md: unRAID' syslog.txt Jun 9 11:04:52 P8H67 kernel: md: unRAID driver 2.1.6 installed Jun 9 23:13:54 P8H67 kernel: md: unRAID driver removed Jun 9 23:13:54 P8H67 kernel: md: unRAID driver 2.1.6 installed Jun 9 23:13:58 P8H67 kernel: md: unRAID driver removed Jun 9 23:13:58 P8H67 kernel: md: unRAID driver 2.1.6 installed Jun 9 23:13:59 P8H67 kernel: md: unRAID driver removed Jun 9 23:13:59 P8H67 kernel: md: unRAID driver 2.1.6 installed Jun 9 23:14:03 P8H67 kernel: md: unRAID driver removed Jun 9 23:14:03 P8H67 kernel: md: unRAID driver 2.1.6 installed 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: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:09 P8H67 kernel: md: unRAID driver removed Jun 9 23:14:09 P8H67 kernel: md: unRAID driver 2.1.6 installed 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 Quote Link to comment
Joe L. Posted June 10, 2013 Share Posted June 10, 2013 # 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? Correct, the package installed via unMENU does not use the powerdown "button" built into unRAID's emhttp. 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??);That is my understanding... 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).No "script" named "powerdown" is run when the "Power Down" button on emhttp's interface is run. Eventually, after stopping the array, the script in /etc/rc.d/rc.0 is invoked. It will invoke /etc/rc.d/rc.local_shutdown if it exists as well as stop other services via their own rc.XXXXXXXXX (service name) script. In rc.local_shutdown I have a line added by the clean-powerdown install script that invokes "rc.unRAID stop" rc.unRAID is where the bulk of the "clean-powerdown" script exists. Then, it performs several "sync" commands, turns off swap, un-mounts any remaining mounted file-systems, The last thing it does is invoke /sbin/poweroff And the real Bottom Line: Do you think this script is responsible for the RC13 shutdown issues That is what we are trying to determine. Quote Link to comment
WeeboTech Posted June 10, 2013 Share Posted June 10, 2013 Some brave soul needs to capture the syslog of a rc13 clean shutdown, then post it. I would do it, only I just started a preclear on 4 4tb drives this morning. Quote Link to comment
prostuff1 Posted June 10, 2013 Share Posted June 10, 2013 well make a gui that allows us to boot in unraid without plugins and one normal boot ?? just rename the plugins folder to plugins_old... That will stop them from loading on a reboot. Quote Link to comment
garycase Posted June 10, 2013 Share Posted June 10, 2013 Some brave soul needs to capture the syslog of a rc13 clean shutdown, then post it. I would do it, only I just started a preclear on 4 4tb drives this morning. Tell me how to do it and I'll give it a shot Quote Link to comment
garycase Posted June 10, 2013 Share Posted June 10, 2013 Never mind Seems Barzija was braver (and quicker) than me Quote Link to comment
aiden Posted June 10, 2013 Share Posted June 10, 2013 well make a gui that allows us to boot in unraid without plugins and one normal boot ?? just rename the plugins folder to plugins_old... That will stop them from loading on a reboot. Hm... this is an interesting idea though. Basically like a "Safe Mode" for unRAID. Could be as simple as adding an extra option at the MemTest / Boot unRAID screen, and even a "Reboot into Safe Mode" button on the GUI. Much more user friendly than trying to rename a folder in Linux if you don't know the proper commands, or trying to rename a folder via Windows when SMB is down. Quote Link to comment
garycase Posted June 10, 2013 Share Posted June 10, 2013 well make a gui that allows us to boot in unraid without plugins and one normal boot ?? just rename the plugins folder to plugins_old... That will stop them from loading on a reboot. Well ... I don't think that's all that's needed. I don't have a "plugins" folder on my flash drive ... but I DO run one add-in [unMenu], which loads a couple of packages (CleanPowerDown and APC). I think I'd have to change my GO file to run "stock" UnRAID .. is that right? What you COULD fairly easily do is have two batch files in Windows [unRAID-Stock.bat and UnRAID-Normal.bat] that copied the appropriate GO file to the flash drive and renamed the plugins folder as appropriate. i.e. UnRAID-Normal.bat could be: Copy D:\UnRAID Setups\Normal\GO \\tower\flash\config Ren \\tower\flash\plugins_old plugins and UnRAID-Stock.bat might be: Copy D:\UnRAID Setups\Stock\GO \\tower\flash\config Ren \\tower\flash\plugins plugins_old If any other changes are necessary they could be incorporated as well. Then a simple double-click would change the flash drive so all you had to do was reboot UnRAID. Quote Link to comment
garycase Posted June 10, 2013 Share Posted June 10, 2013 well make a gui that allows us to boot in unraid without plugins and one normal boot ?? just rename the plugins folder to plugins_old... That will stop them from loading on a reboot. Hm... this is an interesting idea though. Basically like a "Safe Mode" for unRAID. Could be as simple as adding an extra option at the MemTest / Boot unRAID screen, and even a "Reboot into Safe Mode" button on the GUI. Much more user friendly than trying to rename a folder in Linux if you don't know the proper commands, or trying to rename a folder via Windows when SMB is down. Your point about SMB being down is something that would obviously keep my little batch files from working I like the idea of a button on the GUI for "Reboot into Safe Mode" ... although I'd probably suggest something like "Reboot with NO Add-ons" ("Safe Mode" may not be meaningful to many) The idea of an option at the initial boot screen along with the MemTest and UnRAID options (similar to the 4K boot option) is much less desirable, as many of us tend to run "headless". I actually have a monitor I can conveniently turn on; but many don't. Quote Link to comment
WeeboTech Posted June 10, 2013 Share Posted June 10, 2013 There's an easy way to do this via syslinux. emhttp would need to read the CMDLINE paramters and see DEBUG or SAFE mode. I've done it for a long time with a DEBUG and SAFE mode via the config/go script. We could do it with some kind of flag file. In fact that's how RH does it with .autofsck (something we need also). Ok, Barzija's shutdown seems clean, no issues. But there's only a couple disks. Each has been shutdown via different wayS. Barzija's via browser, and the other via command line. It could be that the filesystems being unmounted underneath emhttp is now making emhttp go bonkers. Quote Link to comment
tr0910 Posted June 10, 2013 Share Posted June 10, 2013 Some brave soul needs to capture the syslog of a rc13 clean shutdown, then post it. I would do it, only I just started a preclear on 4 4tb drives this morning. See it here. Post has both a crashed and an OK syslog, running the exact same powerdown process. Only when uncommenting out the rsync part of the also posted (sync_t3cron_tstRC13.zip (1.4 kB - downloaded 9 times.)) does it fail. http://lime-technology.com/forum/index.php?topic=27720.msg246113#msg246113 More explanation about what is happening in this process is here: http://lime-technology.com/forum/index.php?topic=27720.msg246219#msg246219 When I type "which powerdown" I get /sbin/powerdown which is dated Sept 2008 and it looks like: powerdown 524/524 100% #!/bin/bash alias logger="/usr/bin/logger -is -plocal7.info -tpowerdown" if [ ${DEBUG:=0} -gt 0 ] then set -x -v fi if [ -z "${1}" ] then OPT="-h" else OPT="${1}" fi logger "Powerdown initiated" if [ -f /var/run/powerdown.pid ] then logger "Powerdown already active, this one is exiting" exit else echo $$ > /var/run/powerdown.pid fi trap "rm -f /var/run/powerdown.pid" EXIT HUP INT QUIT /etc/rc.d/rc.unRAID stop # /sbin/poweroff logger "Initiating Shutdown with ${1}" /sbin/shutdown -t5 ${OPT} now unMenu is installed and that powerdown script is installed. Cleaning it out right now and will reboot and retest... http://unraid-powercontrol.googlecode.com/files/powerdown-1.02-noarch-unRAID.tgz Quote Link to comment
itimpi Posted June 10, 2013 Share Posted June 10, 2013 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. Yes to both! I formatted my USB stick; extracted a RC13 to it; ran make_bootable.bat; copied across my key; and then added all my drives to the array (without parity) so that it was as clean as I could get. The array started up OK, and the system crashed a few seconds after I hit the Stop button. 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? Quote Link to comment
tr0910 Posted June 10, 2013 Share Posted June 10, 2013 unMenu is installed and that powerdown script is installed. Cleaning it out right now and will reboot and retest... Now which powerdown points to /boot/powerdown dated Jun 3 2013 and it looks like: powerdown 393/393 100% #!/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 Rebooting and retesting failing script to see what happens now.... Quote Link to comment
Joe L. Posted June 10, 2013 Share Posted June 10, 2013 unMenu is installed and that powerdown script is installed. Cleaning it out right now and will reboot and retest... Now which powerdown points to /boot/powerdown dated Jun 3 2013 and it looks like: powerdown 393/393 100% #!/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 Rebooting and retesting failing script to see what happens now.... sorry, but the default unRAID distribution does not include a /boot/powerdown command. It must be something you've put there. Quote Link to comment
tr0910 Posted June 10, 2013 Share Posted June 10, 2013 sorry, but the default unRAID distribution does not include a /boot/powerdown command. It must be something you've put there. Sorry /root/powerdown, not /boot/powerdown.... :-) Oh and by the way, running the offending script without the rsync component now fails with a "Kernel panic" Before killing the powerdown command this worked fine. Things are getting worse not better.... :-) Quote Link to comment
aiden Posted June 10, 2013 Share Posted June 10, 2013 I like the idea of a button on the GUI for "Reboot into Safe Mode" ... although I'd probably suggest something like "Reboot with NO Add-ons" ("Safe Mode" may not be meaningful to many) I agree, although I would submit there's more to running in a purely clean evironment than disabling plugins. I mean running a default go script, disabling unMenu, etc. Purely a stock unRAID boot. This would remove any ambiguity when trying to diagnose issues. The idea of an option at the initial boot screen along with the MemTest and UnRAID options (similar to the 4K boot option) is much less desirable, as many of us tend to run "headless". I actually have a monitor I can conveniently turn on; but many don't. Yes, I agree here too, which is why I suggested putting it as another reboot option on the GUI as well. But I've derailed this thread enough. Quote Link to comment
Joe L. Posted June 10, 2013 Share Posted June 10, 2013 sorry, but the default unRAID distribution does not include a /boot/powerdown command. It must be something you've put there. Sorry /root/powerdown, not /boot/powerdown.... :-) And what do you see when you type: ls -l /root/powerdown Quote Link to comment
tr0910 Posted June 10, 2013 Share Posted June 10, 2013 sorry, but the default unRAID distribution does not include a /boot/powerdown command. It must be something you've put there. Sorry /root/powerdown, not /boot/powerdown.... :-) Oh and by the way, running the offending script without the rsync component now fails with a "Kernel panic" Before killing the powerdown command this worked fine. Things are getting worse not better.... :-) ls -l /root/powerdown gives: lrwxrwxrwx 1 root root 25 2013-06-03 19:43 /root/powerdown -> /usr/local/sbin/powerdown* Quote Link to comment
Joe L. Posted June 10, 2013 Share Posted June 10, 2013 sorry, but the default unRAID distribution does not include a /boot/powerdown command. It must be something you've put there. Sorry /root/powerdown, not /boot/powerdown.... :-) Oh and by the way, running the offending script without the rsync component now fails with a "Kernel panic" Before killing the powerdown command this worked fine. Things are getting worse not better.... :-) ls -l /root/powerdown gives: lrwxrwxrwx 1 root root 25 2013-06-03 19:43 /root/powerdown -> /usr/local/sbin/powerdown* you are indeed linked to the stock unRAID powerdown. Quote Link to comment
sacretagent Posted June 10, 2013 Share Posted June 10, 2013 well it seems to be the script it is midnight here and everybody is asleep so i followed what the conclusions were this is what i did 1 swapoff -a 2. waited to be sure that swap file was unmounted 3. pressed stop on the SF gui 4. waited till all drives unmounted (took again a bit of time since find had spawned 3 threads) 5. typed /usr/local/sbin/unraid_powerdown (as this would be the stock unraid powerdown script) and hey my server powered off cleanly so yep in my case it might be the powerdown script i will send the syslog tomorrow morning when i wake up not going to start the machine again to collect the log now.... need ZZZZZzzzzZZZ Quote Link to comment
dikkiedirk Posted June 10, 2013 Share Posted June 10, 2013 Been fooling around a bit with RC13 and stumbled upon a problem: The mover doesn't start when I try to invoke it with the Move now button in Share settings. I enclose the syslog, I tried to invoke the mover on June 10th after 20:56 It does start a night though. syslog-20130610-222726.zip Quote Link to comment
johnodon Posted June 10, 2013 Share Posted June 10, 2013 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 The NFS issues I have seen happen on a vanilla (no plugins or 3rd party webgui) version of RC13 and can be reproduced at will. John Quote Link to comment
NAS Posted June 10, 2013 Share Posted June 10, 2013 Good thats exactly the kind of report that helps. What doesnt help is when 5 posts in you find out a bug report against stock unraid actually includes something else as well that the poster discounted as unrelated Nice work Quote Link to comment
garycase Posted June 10, 2013 Share Posted June 10, 2013 Agree -- getting the main issues with "stock" UnRAID is all that really matters. If it's rock-solid, then it's ready for prime time (i.e. v5.0 "final"). Issues with plug-ins and add-ons can be resolved another day !! ... although I must confess I'd be very disappointed if we didn't at least have UPS support !! (the only reason I install UnMenu is for this & the related CleanPowerDown package) Quote Link to comment
axeman Posted June 11, 2013 Share Posted June 11, 2013 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 The NFS issues I have seen happen on a vanilla (no plugins or 3rd party webgui) version of RC13 and can be reproduced at will. John When you get the NFS issues on your VM, check ESXi to see if the balloon driver is activated? I noticed that a lot of times my balloon was inflated because I had over committed memory, and reserved more than I should have. Could it be that the balloon driver is so aggressive that UnRaid dumps a lot of sensitive/important bits? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.