unRAID Server Release 6.1-rc1 Available


Recommended Posts

We are handling -beta and -rc releases a little differently.  To install 6.1-rc1 navigate to Plugins/Install Plugin and paste the following link into the box and click Install:

 

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

 

This is the URL of "unRAIDServer-6.1-rc.plg" file out on github.  Once you install this plugin, further "check for updates" will check for new 6.1-rc releases, though I don't expect there to be another beyond -rc1 for 6.1.  Once 6.1 'stable' is released, the "check for updates" will return you back onto the 'stable' release path.

 

There are quite a few "under the hood" changes in this release which is one reason why we decided to generate an -rc.  For example, we updated linux kernel, docker, brfs-progs, libvirt, php, and threw in a couple security updates as well.

 

Functional changes include a change in certain defaults to make things easier for new users, such as turning on NTP, and enabling User Shares.  In addition, we added a new config setting on the Global Share Settings page called "Enable disk shares" which can take the value  Yes/No/Auto

 

Yes => all disk shares are exported upon array start just like they do now, provided they are enabled for export in each disk share setting page.

 

No => all disk shares are unconditionally not exported

 

Auto =>

- if 'Enable user shares' is set to No, then this setting acts as if it's set to 'Yes

 

- if 'Enable user shares' is set to Yes, then disks which are marked as participating in user shares (according Included/Excluded disks global share setting) are unconditionally not exported.  Stated another way: if user shares are enabled, then a particular disk share can only possibly be exported if it's not participating or eligible to participate in user shares.

 

The main purpose of this change is to address issue where someone is trying to copy files off a particular disk to a user share for purpose of emptying the disk.  Today if this is done via Network it's possible to clobber data.

 

If someone wants to empty a disk in this manner the procedure is to first 'exclude' that disk in the Global Share Settings page (and ensure this setting is set to 'Auto').  Now when browsing server under Network only that disk share will show up and user can navigate and move files as necessary.

 

This also makes it safe to do such an operation locally, eg, via command line or using 'mc'.  However, since other disk share mount points are still visible, user must be careful to copy files off only the disk which has been excluded as above.

 

Starting with this release, the defaults for Global Share Settings are:

Enable disk shares: Auto

Enable user shares: Yes

Included disks(s): All

Excluded disks(s): None

 

For existing users introduction of this new setting with default 'Auto' will probably result in disk shares which were previously exported are now not exported.  If desired, the 'old' behavior can be restored by setting "Enable disk shares" to "Yes".

 

Another change: all so-called 'hidden' objects - files/directories beginning with dot '.' character - are shown when viewing shares and also visible via SMB.  This makes it easier to see why a particular share is not "empty".

 

Other changes include several dynamix improvements including the ability to upload via browse or drag-n-drop a thumbnail image for users and the 'banner'.  Note: there is something not quite right with this functionality in this release - sometimes it works just fine, other times it doesn't work at all - this will get resoved before 'stable' is released.

 

Another notable addition to this release is the inclusion of the "OpenELEC" template type in VM Manager.

 

For those of you with IOMMU-capable hardware and an add-on graphics card, the OpenELEC VM template is the fastest and easiest way for you to add the capabilities of a media player, directly to your system.  To use it:

 

  • When you click Add VM from the VMs page, you will now notice a new option in the Template drop-down called OpenELEC.
  • Give it a name (e.g. Living Room Media Player).
  • The rest of the form will be reduced to just a download path field and button.  Provide a location (preferably a share that you use to create VMs) and click download and the process will start directly within the webGui.
  • If you navigate off this page while the download is proceeding, you can resume by returning to the Add VM page and selecting the template again.
  • After the download completes, the form will transform again allowing you to optionally configure additional settings for the VM.
  • The version field indicates the version of the VM image you downloaded.  When new releases are created, they will appear as a drop-down item here.  You can download the new image and either keep the old or delete it.
  • If an appdata share already exists on your system, the template form will automatically suggest a Config Folder of /mnt/user/appdata/OpenELEC, which it will create for you when you create the VM.
  • If you do not have an appdata share, you should either create one or provide an alternate path for where Kodi will store its application data (media library, config files, etc.)
  • The minimum CPU and memory required for OpenELEC is 1 core and 512MB of RAM.
  • Different skins / customizations / adjustments may perform better with more resources assigned.  Adjust as necessary
  • Graphics support is limited to physical GPUs only (no on-board GPUs).
  • Some AMD GPUs may not support VDPAU encoding properly for media content.  You can disable this under the System -> Video preferences page in OpenELEC (turn on Expert mode).  This only affects certain media files
  • You can redirect audio through an alternate sound device than what is built into your GPU.  This includes HD audio ports on the motherboard (Optical, HDMI, Digital Coax) as well as analog audio (stereo ports, headphone jacks, microphone ports).
  • Add media content through the normal process for Kodi (we’ve tested SMB protocol and NFS protocol in our use).

 

Please post feedback on the use of this VM in this thread for now.  Thanks!!

 

Note to plugin authors: Some Dynamix internal file restructuring in v6.1 may break plugins when they rely on files under the folders dynamix and dynamix.docker.manager.  Also, Dynamix now takes cares of the Apply and Done buttons. By default Apply is disabled and Done is present. When a change is made in the settings then Apply will be enabled while Done changes to a Reset button.

 

For consistency reasons all plugin settings pages should do the same, i.e. no need to modify the buttons on the page itself. Please ask bonienl for details.

 

unRAID Server Version 6.1-rc1 Release Notes
===============================================

Security Advisory updates
-------------------------
- ntp: 4.2.8p3 (SSA:2015-188-03)
- openssl: 1.0.1p (SSA:2015-190-01)

Other changes
-------------
- btrfs-progs: version 4.1.0
- docker: version 1.7.1
- docker: less verbose logging by default
- emhttp: fix: let Pro start regardless of attached device count
- emhttp: bridge forward delay configurable
- emhttp: support disk share export Yes/No/Auto
- libvirt: version 1.2.17
- linux: version 4.1.1
- ntp: enable by default
- php: version 5.4.42
- php: enable pcntl
- smb: include linux "hidden" objects in directory listings
- unRAIDServer.plg: improvements in unRAID-5 update: ping google instead of local gateway to determine if network up
- vm.manager: support OpenELEC template
- webGui: include linux "hidden" objects in directory listings
- webGui: integrate latest dynamix changes; many changes, refer to github
- webGui: install key: accept pre-keyserver links to key files
- webGui: rearrange columns on Main page

Link to comment
  • Replies 114
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

Nice progress.

 

Looking forward to Brian's feedback on this fix:  "emhttp: fix: let Pro start regardless of attached device count"

(I don't have a system with enough devices to test it)

Yeah I sent him a -beta but he hasn't reported - busy guy.  It should work though...  ;)

Link to comment

Played around a bit with the new "Enable disk shares" parameter.  Works pretty nice, but I did note that even if there are no cached shares, the cache drive is not exported.    I'd think if there are no shares using it, it would be desirable to be able to "see" it on the network.    [The parameter was set to "Auto"]

 

Personally, I'd prefer that the disk shares be effectively "Yes - Hidden" instead of "No" when they're participating in a share; but if I understand the underlying mechanism you described, the "No" actually eliminates the "user share copy" problem, so that's a very good rationale for it.

 

This will likely cause some complaints from folks who are trying to move data around their server ... but they can always change the setting to "Yes" and let it behave like it did before this release.

 

Link to comment

Notice: in this release email notifications is broken.

 

Workaround: Settings -> Notification Settings -> SMTP Settings toggle Priority in header Yes/No/Yes and press Apply.

 

@Tom: in rc.local change "notify init" to "notify smtp-init"

 

Ouch!  That's a fairly notable "break".  Perhaps a v6.1-RC1a ??

 

Link to comment

Well, the update broke Community Applications because the DockerClient.php file moved from /usr/local/emhttp/plugins/dynamix.docker.manager to /usr/local/emhttp/plugins/dynamix.docker.manager/include

 

Now I'm going to have to figure out which version of unRaid is running and then require_once the appropriate path

Link to comment

Yeah, need to add a remark to the release notes that internal file restructuring in v6.1 may break plugins when they rely on files under the folders dynamix and dynamix.docker.manager.

After every single update to unRaid, the absolute first thing I do (after verifying unRaid basically works) is check all the plugins I wrote.  At least it was easier in my case since I only update one of my server's at a time so I could easily compare between 6.01 and 6.1rc-1

 

Update now available for CA

Link to comment

Another notable addition to this release is the inclusion of the "OpenELEC" template type in VM Manager.

 

It may be prudent to note in the OP which version of OE is being pulled (latest stable, latest beta/RC, legacy stable, user choice, etc.)...especially for those that are using a shared mysql database.

 

Also, how are OE upgrades handled?

 

Nice work!

 

John

Link to comment

Yeah, need to add a remark to the release notes that internal file restructuring in v6.1 may break plugins when they rely on files under the folders dynamix and dynamix.docker.manager.

After every single update to unRaid, the absolute first thing I do (after verifying unRaid basically works) is check all the plugins I wrote.  At least it was easier in my case since I only update one of my server's at a time so I could easily compare between 6.01 and 6.1rc-1

 

Update now available for CA

 

Another thing to address:  in v6.1 Dynamix takes cares of the Apply and Done buttons. By default Apply is disabled and Done is present. When a change is made in the settings then Apply will be enabled while Done changes to a Reset button.

 

For consistency reasons the CA settings page should do the same, i.e. no need to modify the buttons on the page itself.

 

Link to comment

is this ok?

 

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

 

Link to comment

is this ok?

 

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

 

Looks like a bad download of the PLG file.

 

Try again by pasting the URL in the install box and press install.

 

Link to comment

Played around a bit with the new "Enable disk shares" parameter.  Works pretty nice, but I did note that even if there are no cached shares, the cache drive is not exported.    I'd think if there are no shares using it, it would be desirable to be able to "see" it on the network.    [The parameter was set to "Auto"]

 

Personally, I'd prefer that the disk shares be effectively "Yes - Hidden" instead of "No" when they're participating in a share; but if I understand the underlying mechanism you described, the "No" actually eliminates the "user share copy" problem, so that's a very good rationale for it.

 

This will likely cause some complaints from folks who are trying to move data around their server ... but they can always change the setting to "Yes" and let it behave like it did before this release.

I normally had all disks exported hidden, but I think I like it this new way just fine. I can still see my cache-only shares so I don't need to see cache, and flash is still exported. I almost never looked at the disks over the network, mostly using mc for this. If this fixes the user share copy bug then I think this is a very good change.
Link to comment

Nice changes! One question though, does this mean the 6.1 "roadmap" items are now essentially "unscheduled" items? Not complaining, genuinely curious.

Yes, we are changing our release process to release based on what's done in a time window as opposed to what's done against a roadmap.  We are also focusing on not only making things better with new features, but also on making things much easier for new users.

Link to comment

Another notable addition to this release is the inclusion of the "OpenELEC" template type in VM Manager.

 

It may be prudent to note in the OP which version of OE is being pulled (latest stable, latest beta/RC, legacy stable, user choice, etc.)...especially for those that are using a shared mysql database.

 

Also, how are OE upgrades handled?

 

Nice work!

 

John

The version number is indicated in the webgui before you download and create a VM, so don't think we need to mention that in the OP. For those curious, its just OE 6.0.0 beta 2 for right now.

 

Upgrades are handled by downloading a new image file when we release it and then starting the VM. Same config folder used.

Link to comment

Has Unassigned devices stopped working in 6.1rc1?

 

The display is not working,  anything you had to auto-mount is still working (  i just checked mine and my auto-mounts are fine ),  you just cant see anything if you have to manually mount something

Link to comment

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.