unRAID OS version 6.4.0-rc7a available


155 posts in this topic Last Reply

Recommended Posts

Upgrading: We have changed the way one checks for new unRAID OS releases.  Please refer to Update OS below.

 

Bugs: If you want to report an issue, please start a new topic in this board.

 

Sorry it took so long for this release.  We've been busy addressing several issues, including possible fix to Ryzen freeze issue.  Lots more changes under the hood, for example, webGui should be a bit snappier now...

 

USB Flash boot device backup function (-rc7)

Added "Flash backup" button on the flash device info page (Main/flash).  Click this button to download a zip file with the entire contents of your USB Flash boot device.  This zip file may be used to restore to a new unRAID USB Flash boot device either manually, or using our nifty new unRAID USB Creator tool.

 

Linux 4.12 kernel (-rc7) - should provide better Ryzen support among other improvements.

 

UEFI support (-rc5)

It is now possible configure UEFI boot mode to boot unRAID OS.  The make_bootable.bat (Windows), make_bootable_mac (MacOS) and make_bootable_linux (Linux) scripts will output a prompt:

 

  Permit UEFI boot mode [Y/N]:

 

If answered with 'Y' a new directory is included on the USB flash boot device called 'EFI'.  The presence of this directory along with its contents, and along with some additional linux kernel options permit UEFI boot.  This is done in such a way that you could choose either BIOS (legacy) or UEFI to boot off your USB flash device (that is, even if you answer 'Y' here you can still configure your motherboard to use Legacy boot).

 

If answered with 'N' the directory and contents are still created, but named 'EFI-' (a dash at the end).  This will prevent UEFI firmware from considering this device.  You can manually rename the 'EFI-' directory to 'EFI' and permit possible UEFI boot (and rename back to 'EFI-' to prevent it again).

 

Note: Even if the 'EFI' directory exists, whether or not your motherboard actually uses UEFI to boot is determined by BIOS settings.  In addition, some motherboards may present a strongly worded warning along the lines of "The system found unauthorized changes on the firmware, operating system or UEFI drivers."  In this case look for a "Secure Boot" BIOS setting and change to "Other OS" or "Disable".

 

If you update your server using Check for updates on the Plugin page, an 'EFI-' directory and files will be automatically created on your USB flash boot device.  If you prepare a new USB flash using this release, the 'EFI-' directory and files will also be included.  If you use the "manual" method of updating by copying the bz* files from the release zip, beware you will need to manually also copy over the 'EFI-' directory (and modify the first line of syslinux.cfg and copy it to 'EFI-/boot' directory).

 

There is also a webGui setting to permit UEFI boot located on the 'flash' device information page in the 'Syslinux Configuration' section.

 

Update OS (-rc5)

Instead of bundling an "unRAID Server" plugin on the Plugins page, there is a new page on the Tools menu in the About section called 'Update OS'.  Here you can check for a new unRAID OS release as well as switch between the latest release in the stable branch or the next branch.  In addition there is a separate control on the Notification Settings page that configures whether or not to automatically check for updates.


enabling https (-rc3)

To enable https support it's necessary to edit your 'config/go' file on your USB flash boot device.  Use the -p option to specify the port(s) and optionally include the -r option to redirect http request from your browser to using https.  Here's the detailed usage:

# Usage:
#   emhttp [-r] [-p port [,sslport]] [OPER]

# OPER is start or stop.  Default is start.
# By default nginx will be setup to listen only at port 80 (http).
# The -p option may be used to define different listening ports and/or setup nginx
# to listen at a specified port for https.  The -r option may be used to setup
# nginx so that any http request is redirected to https (this requires that both
# ports have been specified with -p option).  For example, to have nginx listen
# at both standard ports but redirect all http to https use:
#   emhttp -rp 80,443
# To listen at only port 443 use:
#   emhttp -p ,443

# Note: the stop operation is only "safe" if the array has already been stopped
# (this will be fixed).

Improved shfs/mover (-rc1)

 

The LimeTech user share file system (shfs) has been improved in two areas.  First, we now make use of FUSE read_buf/write_buf methods.  This should result in significant throughput increases.  Second, the mover script/move program no longer uses rsync to move files/directories between the cache pool and the parity array.  Instead the move program invokes a new shfs ioctl() call.  This should result in complete preservation of all metadata including atime and mtime.

 

While this function has been fairly extensively tested, please keep an eye on mover activities - there shouldn't be any data loss, but it's a fairly significant code change.

 

nginx http server (-rc1)

We now use the nginx webserver as the front-end to the unRAID OS Management Utility (aka, webGui).  The emhttp process has been changed to a daemon (emhttpd) listening at a unix socket.  Incorporating nginx provides several features:

  • Multi-threaded access, though emhttpd is still single-threaded.
  • https (SSL) support.  At present unRAID OS will generate a self-signed certificate.  https works but you will get a scary warning from your browser about not being able to verify the certificate.  No worries.
  • nchan (websocket) support.  We have only just begun the process of converting many of the browser javascript polling functions to an event-driven websocket paradigm.  This opens the door for  us to create something like a process manager where we can have several background operations in process, all monitored in real-time via webGui dashboard.

 

IPv6 support (-rc1)

We want to again, give a big "thank you" to bonienl who has greatly improved unRAID OS networking with the addition of IPv6 support.  Give it a try and report any issues.

 

Other (-rc1)

  • Two new webGUI themes: Azure and Gray.  Again, thanks to bonienl.
  • Expanded driver support (QLogic) and more hardware monitoring support.
  • Kernel modules and firmware are left on the Flash in a squashfs loopback and loaded into RAM on demand.
  • Many more misc. improvements

 

Changes (-rc7a)

 

Base distro:

  • aaa_elflibs: version 14.2 (rev30)
  • at: version 3.1.20
  • at-spi2-atk: version 2.24.1
  • at-spi2-core: version 2.24.1
  • bash: version 4.4.012
  • ca-certificates: version 20161130
  • cairo: version 1.14.10
  • curl: version 7.54.1
  • diffutils: version 3.6
  • dnsmasq: version 2.77
  • eudev: version 3.2.2 (patched to correct /dev/disk/by-id entries)
  • ethtool: version 4.11
  • file: version 5.31
  • fontconfig: version 2.12.4
  • freetype: version 2.8
  • glew: version 2.0.0
  • glibc: version 2.25 (rev3) (CVE-2017-1000366)
  • glibc-solibs: version 2.25 (rev3)
  • gmp: version 6.1.2
  • gnutls: version 3.5.14
  • grep: version 3.1
  • gtk+3: version 3.22.16
  • hdparm: version 9.52
  • iproute2: version 4.11.0
  • jemalloc: version 5.0.1
  • less: version 487
  • libaio: version 0.3.110
  • libcap-ng: version 0.7.8
  • libdrm: version 2.4.81
  • libepoxy: version 1.4.3
  • libevdev: version 1.5.7
  • libfastjson: version 0.99.6
  • libgcrypt: version 1.7.8 (CVE-2017-7526)
  • libgpg-error: version 1.27
  • libmnl: version 1.0.4
  • libnl3: version 3.3.0
  • libpng: version 1.6.30
  • libtasn1: version 4.12
  • libtool: version 2.4.6 (rev5)
  • libunistring: version 0.9.7
  • libvirt: version 3.5.0
  • libvirt-php: version 0.5.3
  • logrotate: version 3.12.2
  • lvm2: version 2.02.171
  • mesa: version 17.1.4
  • nano: version 2.8.5
  • network-scripts: version 14.2 (rev6)
  • nginx: version 1.12.1 (CVE-2017-7529)
  • pango: version 1.40.6
  • pcre: version 8.41
  • php: version 7.1.7 (CVE-2017-9224, CVE-2017-9226, CVE-2017-9227, CVE-2017-9228, CVE-2017-9229)
  • reiserfsprogs: version 3.6.26
  • rsyslog: version 8.28.0
  • samba: version 4.6.6 (CVE-2017-11103)
  • shared-mime-info: version 1.8
  • sqlite: version 3.19.3
  • sudo: version 1.8.20p2 (CVE-2017-1000367)
  • sysvinit-scripts: version 2.0 (rev37)
  • util-linux: version 2.30
  • wget: verion 1.19.1 (rev2)
  • xfsprogs: version 4.11.0
  • xkbcomp: version 1.4.0
  • xkeyboard-config: version 2.21
  • xterm: version 330

Linux kernel:

  • version 4.12.3
  • additional modules:
    • CONFIG_AQTION: aQuantia AQtion(tm) Support
    • CONFIG_AQUANTIA_PHY: Aquantia PHYs
    • CONFIG_INTEL_RDT_A: Intel Resource Director Technology Allocation support
    • CONFIG_X86_AMD_PLATFORM_DEVICE: AMD ACPI2Platform devices support
  • possible kernel fix for Ryzen freezes:
    • CONFIG_RCU_NOCB_CPU: Offload RCU callback processing from boot-selected CPUs
    • CONFIG_RCU_NOCB_CPU_ALL: All CPUs are build_forced no-CBs CPUs
  • added IA32 support
  • added crypto support
  • restore in-tree aacraid driver

Management:

  • update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt}
  • network: The parameter BONDING_MIIMON was missing when multiple bond interfaces are created.
  • network: Fixed typo in the create_network_ini file: IPV4ALL should be IPV4LL
  • emhttpd: introduce inotify MOVE_TO /var/local/emhttp event to autowrite to websocket publisher endpoint
  • emhttpd: eliminate cmdStatus requirement on page load
  • shfs: fix regression: share free space calculation not taking into account "potential" storage
  • webgui: Fixed regression error in logging.htm and make coloring the same as all themes
  • webgui: Changed popup windows to higher contrast and the same for all themes
  • webgui: Aligned logging.htm buttons with popup buttons
  • webgui: webGui: use JSON for Slack notifications since it is preferred and may work better for 3rd party webhooks (e.g. Discord)
  • webgui: Auto-width reversed (not a good idea)
  • webgui: Changed slider-width to auto - this allows for longer titles
  • webgui: Made sidebar slide-out a little wider
  • webgui: Fixed display of APPS on Dashboard for themes AZURE and GRAY
  • webgui: Motion improvement of sidebar in themes AZURE and GRAY
  • webgui: Show cpu pairs in VM creator and VM overview
  • webgui: Added "shared" option to container path creation
  • webgui: Automatic 2 or 3 column display on Dashboard page based on screen width
  • webgui: Fixed missing server name in docker update notifications
  • webgui: Fixed IP calculation in docker settings
  • webgui: Suppress plugin online check when actions are done from plugin page itself
  • webgui: Add LOG rotation option to docker settings
  • webgui: Added "USB backup" function
  • webgui: Added 'Description' field to VMs page.
  • webgui: Prevent unassigned devices from spinning up unnecessary
  • webgui: Remove '' header.
  • webgui: Make unused columns invisible for Array Status on Dashboard page
  • webgui: Add outstanding enhancements to diagnostics
  • webgui: Fix virtio iso, libreelec and openelec download progress display
  • webgui: Correct noVNC links to account for stricter same-origin policy.
Link to post
  • Replies 154
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Upgrading: We have changed the way one checks for new unRAID OS releases.  Please refer to Update OS below.   Bugs: If you want to report an issue, please start a new topic in this board.

The flash drive backup integrated into the OS instead of via a plugin is a good idea.  But I would like one change to take place:   On the backup disk.cfg, can you please set startArray to b

I can confirm there is a bug that makes it impossible to choose cores if you have 8 or less cores when creating a new VM. If there are more than 8 cores available the first 8 are grayed out until

Posted Images

Didn't see anything about it in the release notes but nice to see that my NVMe cache device is correctly identified once again, shame about the temperature still not working, last time it did was on v6.2.x

Link to post
29 minutes ago, johnnie.black said:

Didn't see anything about it in the release notes but nice to see that my NVMe cache device is correctly identified once again, shame about the temperature still not working, last time it did was on v6.2.x

 

Huh, a change that sneaked past the change log... we'll fix that, about to release -rc7a which fixes a little bug someone else saw.

 

DId you open another topic for the temperature issue?

Link to post
7 minutes ago, limetech said:

DId you open another topic for the temperature issue?

 

I mentioned it during v6.3rc when I thought is was an easy fix:

 

 

Eric took a look and it turns out it wasn't so easy, still strange that it worked fine on v6.2 and hasn't since.

Link to post
1 hour ago, limetech said:

USB Flash boot device backup function (-rc7)

Added "Flash backup" button on the flash device info page (Main/flash).  Click this button to download a zip file with the entire contents of your USB Flash boot device.  This zip file may be used to restore to a new unRAID USB Flash boot device either manually, or using our nifty new unRAID USB Creator tool.

I didn't notice it stopping the array before creating the backup, so does this mean config/super.dat in the zip file would show the array as started when it is read on bootup and so trigger a parity check for unclean shutdown?

Link to post

FYI, changelog reports Kernel 4.12.2 

 

root@Raptor:~# uname -a
Linux Raptor 4.12.3-unRAID #1 SMP PREEMPT Fri Jul 21 17:03:15 PDT 2017 x86_64 Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz GenuineIntel GNU/Linux

Looks like changelog is a .1 behind? ;)

Link to post
6 minutes ago, nexusmaniac said:

FYI, changelog reports Kernel 4.12.2 

 


root@Raptor:~# uname -a
Linux Raptor 4.12.3-unRAID #1 SMP PREEMPT Fri Jul 21 17:03:15 PDT 2017 x86_64 Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz GenuineIntel GNU/Linux

Looks like changelog is a .1 behind? ;)

 

Yeah same reason the nvme fix wasn't in the log.  Someone pushed a last-minute changelog change after I built the actual release - I'm going to blame @eschultz  :ph34r:

Though prob I neglected a final PR check.

Link to post
28 minutes ago, CHBMB said:

Whilst you're around Tom, which out of tree drivers are present in this release?

Sent from my LG-H815 using Tapatalk
 

 

Only one now is the Rocket Raid driver.

Link to post
14 hours ago, limetech said:

6.4.0-rc7a released.  Just corrects the change log and fixes a minor bug.

I'm running this now on my Ryzen build.  New drivers are greatly appreciated, as is the fix for assigning the cache drive.

 

I did experience at least 1 Kernel Panic, snapped a pic you can see here (plus a write-up on my general experiences with -rc6/-rc7a):

 

 

17 hours ago, johnnie.black said:

Didn't see anything about it in the release notes but nice to see that my NVMe cache device is correctly identified once again, shame about the temperature still not working, last time it did was on v6.2.x

Huh, I had kinda noticed that the temps weren't displaying on my NVMe drive, but I was attributing that to my general cache drive assignment problems.  Now that those are resolved, I can confirm that temps are not displaying.

 

 

8 hours ago, methanoid said:

@limetech  "should provide better Ryzen support among other improvements" - does this mean Ryzen is now properly compatible? Or just less incompatible ;) ??

A very important configuration change has been applied that may eliminate the need for disabling Global C-state Control.  My system typically crashes in a matter of hours with C-states enabled.  I'm testing this now.  Early reports are promising, though absolute confirmation may take some time.  Here's the change (quoted from the release notes above):

18 hours ago, limetech said:

possible kernel fix for Ryzen freezes:

  • CONFIG_RCU_NOCB_CPU: Offload RCU callback processing from boot-selected CPUs
  • CONFIG_RCU_NOCB_CPU_ALL: All CPUs are build_forced no-CBs CPUs

 

If you are looking for better VM performance, that will probably have to wait on fixes destined for a newer Linux kernel, though there may be some general improvements in 4.12.  This is out of Lime-Tech's control.

 

3 hours ago, Frank1940 said:

I have an issue with my cache drive being 'missing'--- Details here:

 

I had similar experiences, though technically mine started on v6.3 with my new Ryzen build when I swapped out my cache drive - I could never assign the new one until -rc7a.

 

Thank you Lime-Tech.

 

Paul

 

Edited by Pauven
Type-O's
Link to post
3 hours ago, Frank1940 said:

I have an issue with my cache drive being 'missing'--- Details here:

 

39 minutes ago, Pauven said:

I had similar experiences, though technically mine started on v6.3 with my new Ryzen build when I swapped out my cache drive - I could never assign the new one until -rc7a.

 

 

After reading @Pauven's comment, I decided to try an reboot.  This time the cache drive was properly assigned when the server came back up.  So, at this point, this appears to be an non-issue.  (Possible scramble in the super.dat file???)

Link to post
8 minutes ago, Frank1940 said:

 

 

After reading @Pauven's comment, I decided to try an reboot.  This time the cache drive was properly assigned when the server came back up.  So, at this point, this appears to be an non-issue.  (Possible scramble in the super.dat file???)

 

That again aligns with my experience.  Under -rc7a, assigning the drive and starting the array once weren't enough.  I had to stop/start multiple times, and the last reboot really helped sync things up.  I also had Mover issues, as the share.cfg file had lost some settings related to the cache drive.  Be sure to check Mover on your server, and if you're having problems, the solution was documented in the forum link in my previous post above.

 

I can't tell if it is the new GUI misreporting what the system is doing (possibly caching old info), or the system misbehaving.  Either way, this is the first time I've experienced this type of behavior in 8+ years of using unRAID.

 

Paul

Link to post

GUI boot is much more responsive, typically had to wait up to a minute to get the webui to load on initial login after a reboot/powerup. 3 tests so far today on this had the webUI working by the time I was able to login to the GUI boot. MUCH improved, awesome job!!!

Link to post
Guest
This topic is now closed to further replies.