Jump to content
limetech

unRAID Server Release 6.1-rc2 Available

168 posts in this topic Last Reply

Recommended Posts

Any chance this will make it into 6.1 FINAL:  http://lime-technology.com/forum/index.php?topic=41079.msg388890#msg388890

 

Interesting.  When we changed the network startup script to wait in-line (up to 60 sec) for a dhcp lease, I almost added a 'brctl setfd br0 0' to the default initialization for the root bridge, but I wasn't sure about how that would affect down-link virtual bridges.  Replies in the redhat bug report you found seem to imply setting fwd delay to 0 is ok.  I think what we'll do is add this as a configurable setting on the Network Page.

Have you checked rc2?  It's already there...

 

Just wanted to report back that the setting is working as expected.  In my case I have to set a non-zero value or my OE VMs won't boot.  I set it to 4 (just as I was doing in my GO script) and they boot without issue.

 

John

Share this post


Link to post

OE has a setting "wait for network for xx seconds" in the settings sections within OE. I always have to set mine otherwise I run the risk of OE not finding an IP before it loads up, therefore losing all networked data locations.

 

Have you tried this instead?

Share this post


Link to post

Hi everyone - I had thought that I read that this issue was solved - perhaps not for my CPU.

I have:  Intel® Pentium® CPU G3258 @ 3.20GHz

 

No matter what - the Frequency seems to never get throttled down below 3200MHz on either of the 2 cores.  This wasn't the case back on unRaid 5 .

I recall there being some issues w/ Haswell frequency scaling, but as I said, I had believed I had read that this was resolved.

 

Perhaps my CPU is showing something that we haven't seen before and was therefore not addressed in prior fixes for this?

Please let me know if you need any additional details from me.

 

-Jim

Share this post


Link to post

OE has a setting "wait for network for xx seconds" in the settings sections within OE. I always have to set mine otherwise I run the risk of OE not finding an IP before it loads up, therefore losing all networked data locations.

 

Have you tried this instead?

 

I always have this checked but this issue exists before OE even starts to load...when the VM is attempting to obtain an IP.  It's not an OE issue.  It is a KVM/DHCP/PXE issue.

Share this post


Link to post

 

No matter what - the Frequency seems to never get throttled down below 3200MHz on either of the 2 cores.  This wasn't the case back on unRaid 5 .

I recall there being some issues w/ Haswell frequency scaling, but as I said, I had believed I had read that this was resolved.

 

 

It's the fact that you're looking at the dashboard that makes the CPU step up to 3200MHz.  Haswell seems much faster to step up to full speed than older Ivy/Sandy chips. 

 

I see something a bit similar on my AMD machine - each core cycles up to 4GHz in turn, so 3 cores sit always at 1700MHz (the chip's slowest speed). 

 

Share this post


Link to post

Hi - due to the existing issues with spinup/down (some drives don't even react on GUI klicks at all - while at the same time spinning up/down via unmenu still works) and the temps (which might be related?) I'd like to go back to 6.0.1 until this is fixed. Can I simply copy bzimage etc. to downgrade or will there be issues with the 6.1rc2 konfig files used with 6.0.1?

Share this post


Link to post

Hi - due to the existing issues with spinup/down (some drives don't even react on GUI klicks at all - while at the same time spinning up/down via unmenu still works) and the temps (which might be related?) I'd like to go back to 6.0.1 until this is fixed. Can I simply copy bzimage etc. to downgrade or will there be issues with the 6.1rc2 konfig files used with 6.0.1?

 

You can just replace bzroot & bzimage.  Have done it myself, although now on RC2 again and sticking with it.

Share this post


Link to post

Well, that won't install here :(

 

plugin: installing: https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg

plugin: downloading https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg

plugin: downloading: https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg ... done

 

Warning: simplexml_load_file(): /tmp/plugins/unRAIDServer.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): /tmp/plugins/unRAIDServer.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

plugin: xml parse error

 

Copied/pasted the plg url from post #1 to avoid mistyping and all..

Share this post


Link to post

Well, that won't install here :(

 

plugin: installing: https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg

plugin: downloading https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg

plugin: downloading: https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg ... done

 

Warning: simplexml_load_file(): /tmp/plugins/unRAIDServer.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): /tmp/plugins/unRAIDServer.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

plugin: xml parse error

 

Copied/pasted the plg url from post #1 to avoid mistyping and all..

Could be a bad download.  Problem now is that *I believe* that unRaid caches plg downloads, so it won't retry to download it unless you reset

Share this post


Link to post

Well, that won't install here :(

 

plugin: installing: https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg

plugin: downloading https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg

plugin: downloading: https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg ... done

 

Warning: simplexml_load_file(): /tmp/plugins/unRAIDServer.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): /tmp/plugins/unRAIDServer.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

 

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193

plugin: xml parse error

 

Copied/pasted the plg url from post #1 to avoid mistyping and all..

Could be a bad download.  Problem now is that *I believe* that unRaid caches plg downloads, so it won't retry to download it unless you reset

Or flash drive read-only due to corruption.

Share this post


Link to post

Well, I'm gonna be old fashioned then and download it and put the plg file into the plug-ins directory and reboot the server or use an ssh command

Share this post


Link to post

Hi, I am running 6.0rc3.

What is the best way to upgrade my production server to 6.1-rc2.

Should I upgrade before to 6.0.1-x86_64?

Rgds.

Share this post


Link to post

Hi, I am running 6.0rc3.

What is the best way to upgrade my production server to 6.1-rc2.

Should I upgrade before to 6.0.1-x86_64?

 

I suspect you could just install the plugin from the first version, and jump straight to it.  If it were me though, I'd feel better by upgrading from the Plugins page to the stable version, v6.0.1, then checking it out and making sure everything works correctly, then install the plugin for 6.1-rc2.

Share this post


Link to post

Is NUT UPS support still planned for 6.1? Really looking forward to this.

Since lime-tech is in release-candidate-2 of 6.1, I'd not expect new features, but instead just tiny bug-fixes so they can get to 6.1 final.

(I can't speak for lime-tech, as I'm a customer, just like you, so it is always possible they would throw in something at the last moment... but I would look to a community plugin rather than something in 6.1 natively)

 

Joe L.

Share this post


Link to post

Is NUT UPS support still planned for 6.1? Really looking forward to this.

I do not think that the version numbers in the Roadmap part of the forum are meaningful any more.  The list of features probably still is, but not what release they are scheduled for.

 

We know that 6.1 is meant to be near release and that is largely a tidy up/bug fix of the 6.0 release.  We also know that a major new feature being worked on for 6.2 is dual parity, and I suspect many other new features will slip to later version numbered releases on the assumption that new releases are more frequent than has been the case in the past.

Share this post


Link to post

Just updated to 6.1-rc2 and the "Info" popup is right but still wrong on dashboard page.

 

Info popup:

Memory: 16384 MB (max. installable capacity 16 GB)*

 

pic for dashboard...

Screenshot_1.png.755a6d6e4094ced6546d46d152d10b37.png

Share this post


Link to post

Just updated to 6.1-rc2 and the "Info" popup is right but still wrong on dashboard page.

 

Info popup:

Memory: 16384 MB (max. installable capacity 16 GB)*

 

pic for dashboard...

 

Correction also made for dashboard, thanks for reporting.

Share this post


Link to post

Is NUT UPS support still planned for 6.1? Really looking forward to this.

 

I´m running nut on my unRAID, with an Eaton ups.

Running it from the "/extra" folder and a line in the "GO" script thats starts a script with all the nut conf.

 

It shuts down the server if power is lost more then 3 minutes(and turns it on when power is restored), sends email and unraid notifications and has a status page in the unRAID webui for ups stats,

 

So it should be pretty easy to incorpatate into unRAID.

 

// When proper testing has been made (working on an plugin though php for dummies is cool =P)

 

Share this post


Link to post

+1 for adding this feature.  I still get occasional instances (on both my servers) where the temperature is displayed but the 'Device' status indicator says it is spun down.  From the temperature of the disk, it appears that the Disk is really spun up.  I can then manually spin the disk(s) down and things come back into 'sync'.  I have never make an issue of it as I can't identify what is causing the disk to spin up and why it didn't get spun down.  By adding this feature, it might provide a clue as to what is causing this behavior.

 

PS---  I don't consider this behavior a real big 'deal' as I seriously doubt if it reduces the life of the disk but it does cause unneeded power consumption and it would be nice to get to the bottom of the 'problem'.

Attributes (temperature) are only polled every 30 minutes by default.  This means that if a disk spins down, it can take up to 30 minutes for the temperature to turn to "*".  I have mine set to poll every 5 minutes, for more responsive updates.  You can tune this under Disk Settings.

 

Not the issue here.  I usually find the 'problem' in the morning when I get the Status Reports e-mails.  The report, with a time stamp of 20 minutes after midnight, will say the disk(s) are active. I will then start the GUI (this now being after 7:00AM), the disk temperature(s) are there and the indicator says the disk(s) are in the 'Stand By Mode (spundown)'.  So it is not a matter of Attributes polling not having time to 'synced up' with the actual disk state.  PLUS, I have set the Polling time to 60 seconds since I don't keep the GUI open unless I am actively using it!

 

There are 2 things I know of that cause the out-of-sync temps to spin status -

* using s3 sleep plugin and waking up causes the drives to be spun up without informing emhttp, so the drives show temps but also show spun down

* clicking on a drive brings up the drive info, Check Filesystem, and SMART info sections; it will often briefly indicate something about only showing SMART info when drive is spun up, then will apparently spin the drive up(!) and show all of the SMART info; on return to the Main page, drive still appears spun down but the temp is showing

* I'm sure there are other causes, be good to identify them

 

Mine too is set to 60 second update.  It looks like emhttp assumes it knows all, and trusts all other agents to inform it of spin up or down, which obviously isn't happening.  It needs to check for itself the true physical state, much more often, or find ways to be better informed of spin ups.

 

 

i upgraded to RC2 last night, and are having similar issues. about 5 of my Western digital drives (3TB) shows temperature, but according to dashboard it is spun-down. i usually run s3_sleep to shutdown  (not sleep..) the server after detecting that the drives is spun down..  this is however not happening.

 

i have set the polling frequency under disk settings to 60 seconds, and forced a spin-down. it still shows one drive with a temperature, and s3_debug shows the following :

 

Aug 9 10:27:38 Storage emhttp: shcmd (115): /usr/sbin/hdparm -y /dev/sdp &> /dev/null

Aug 9 10:28:03 Storage emhttp: /usr/local/sbin/follow /var/log/syslog 2>&1

Aug 9 10:28:10 Storage s3_sleep: Disk activity on going: sdc

Aug 9 10:28:10 Storage s3_sleep: Disk activity detected. Reset timers.

 

any other way to troubleshoot this bug further?

 

i'll roll-back to stable in about 2 days.

 

 

*edit*

 

attached diagnostics zip, although i believe more focused troubleshooting might be needed? added some ps -elf captures.

 

root@Storage:~# ps -elf | grep mnt

1 S root      5002    1  0  80  0 - 38195 futex_ 09:10 ?        00:00:00 /usr/local/sbin/shfs /mnt/user0 -disks 32766 -o noatime,big_writes,allow_other

1 S root      5013    1  0  80  0 - 55160 futex_ 09:10 ?        00:00:00 /usr/local/sbin/shfs /mnt/user -disks 32767 2048000000 -o noatime,big_writes,allow_other -o remember=0

0 S root    24439 23741  0  80  0 -  1276 pipe_w 10:37 pts/0    00:00:00 grep mnt

 

 

root@Storage:~# ps -elf | grep disk

1 S root      5002    1  0  80  0 - 38195 futex_ 09:10 ?        00:00:00 /usr/local/sbin/shfs /mnt/user0 -disks 32766 -o noatime,big_writes,allow_other

1 S root      5013    1  0  80  0 - 72091 futex_ 09:10 ?        00:00:05 /usr/local/sbin/shfs /mnt/user -disks 32767 2048000000 -o noatime,big_writes,allow_other -o remember=0

0 S root    25433 23741  0  80  0 -  1276 pipe_w 10:38 pts/0    00:00:00 grep disk

 

 

 

storage-diagnostics-20150809-1033.zip

Share this post


Link to post

There are 2 things I know of that cause the out-of-sync temps to spin status -

* using s3 sleep plugin and waking up causes the drives to be spun up without informing emhttp, so the drives show temps but also show spun down

* clicking on a drive brings up the drive info, Check Filesystem, and SMART info sections; it will often briefly indicate something about only showing SMART info when drive is spun up, then will apparently spin the drive up(!) and show all of the SMART info; on return to the Main page, drive still appears spun down but the temp is showing

* I'm sure there are other causes, be good to identify them

 

Mine too is set to 60 second update.  It looks like emhttp assumes it knows all, and trusts all other agents to inform it of spin up or down, which obviously isn't happening.  It needs to check for itself the true physical state, much more often, or find ways to be better informed of spin ups.

 

i upgraded to RC2 last night, and are having similar issues. about 5 of my Western digital drives (3TB) shows temperature, but according to dashboard it is spun-down. i usually run s3_sleep to shutdown  (not sleep..) the server after detecting that the drives is spun down..  this is however not happening.

 

i have set the polling frequency under disk settings to 60 seconds, and forced a spin-down. it still shows one drive with a temperature, and s3_debug shows the following :

 

Aug 9 10:27:38 Storage emhttp: shcmd (115): /usr/sbin/hdparm -y /dev/sdp &> /dev/null

Aug 9 10:28:03 Storage emhttp: /usr/local/sbin/follow /var/log/syslog 2>&1

Aug 9 10:28:10 Storage s3_sleep: Disk activity on going: sdc

Aug 9 10:28:10 Storage s3_sleep: Disk activity detected. Reset timers.

 

any other way to troubleshoot this bug further?

 

i'll roll-back to stable in about 2 days.

 

Unfortunately, s3 sleep is not officially supported, and that is stated somewhere (hardware support is too inconsistent).  Which means that we can't actually call this a bug, when it's related to s3 sleep.  But if we lump it in with other instances of out-of sync temps/spin status, then we could say it's *related* to a known bug.  Just semantics, but important if we want Tom to put a higher priority on it.

 

I'd like to see a function added, that when called, a physical check is made on all attached drives in order to verify their current status.  It would also be nice if this function was callable by other agents such as the s3_sleep plugin, so when a system awakes, it could call this function, to reset all states and drive status'.

 

I wonder if the sync function would work, as I believe it goes through the normal I/O channels that Tom probably is intercepting.  The sync command always seems to spin up all my drives.  I'm sure the s3_sleep plugin must call sync before sleeping, perhaps if it also called it on awaking would reset all drive states?  Worth a test by someone using the s3_sleep plugin (run sync at the command prompt after system awaking).

Share this post


Link to post

Two kernel panics within 24 hours of installing v.6.1-rc2.... Is there a way to revert to my previous 6.0.x stable???

 

Cannot save logs as the server completely locks up... errors were all similar to something like

 

btrfs_run_delayed

 

On both occasions I was doing inside an Ubuntu VM, running the following command:

 

myisamchk -o -f name-of-nZEDb-database.MYI

 

VM file stored in cache drive which is btrfs format.... my array drives are Reiserfs.

 

Thanks.

 

H.

Share this post


Link to post

Two kernel panics within 24 hours of installing v.6.1-rc2.... Is there a way to revert to my previous 6.0.x stable???

 

Cannot save logs as the server completely locks up... errors were all similar to something like

 

btrfs_run_delayed

 

On both occasions I was doing inside an Ubuntu VM, running the following command:

 

myisamchk -o -f name-of-nZEDb-database.MYI

 

VM file stored in cache drive which is btrfs format.... my array drives are Reiserfs.

 

Thanks.

 

H.

 

Might be worth Tools ==> Diagnostics ==> Collect

 

Then you can either upgrade to RC3 and see if that helps or download Unraid 6.0.1 from the LT website extract the zip and copy bzimage & bzroot to your flash and reboot.

 

The logs will at least help debug what's happening..

Share this post


Link to post

Might be worth Tools ==> Diagnostics ==> Collect

 

Then you can either upgrade to RC3 and see if that helps or download Unraid 6.0.1 from the LT website extract the zip and copy bzimage & bzroot to your flash and reboot.

 

The logs will at least help debug what's happening..

 

Thanks N.

 

I just noticed rc3 and I upgraded. I will let it run overnight and hope for the best. I am also not doing the table fix inside the VM in case that was the culprit...

Share this post


Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.