• Unraid OS version 6.9.0-rc1 available


    limetech

    As always, prior to updating, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".

     

    Besides bug fixing, most of the work in this release is related to upgrading to the Linux 5.9 kernel where, due to kernel API changes, it has become necessary to move device spin-up/down and spin-up group handling out of the md/unraid driver and have it handled entirely in user space.  This also let us fix an issue where device spin-up of devices in user-defined pools was executed serially instead of in parallel.

     

    We should also now be able to properly support SAS device spin-up/down (finally) and with extraordinary help from @doron we are almost there.  SAS devices are generally designed for enterprise environments where device spin-down is rare, and many devices have inconsistent behavior surrounding this functionality.  This release itself does not include SAS device spin handling built-in but @doron is providing a plugin where we continue to address some nagging details.  We expect to have this ironed out before stable release.

     

    Along with re-work of device spin control, we have also integrated spin-up/down and temperature monitoring for unassigned devices.  We have coordinated with @dlandon to ensure proper integration with the Unassigned Devices plugin.  If you've read this far, and you are using the Unassigned Devices plugin, please remove it first before upgrading and then re-install UD via Community Apps.

     

    Since we have not identified any data loss bugs related to the user-defined pools feature, I have removed the -beta designation and we now enter the -rc phase.  Our plan is for this to be relatively short and limited to squashing bugs.  We are in the process of writing up more thorough release notes in preparation for stable release.

     

    A lot of exciting changes and features are coming to Unraid OS and I want to thank everyone for participating in our Pre-release program!

     


     

    Version 6.9.0-rc1 2020-12-09 (vs -beta35)

    Base distro:

    • aaa_elflibs: version 15.0 build 27
    • hdparm: version 9.60
    • icu4c: version 68.1
    • intel-microcode: version 20201118
    • kernel-firmware: version 20201130_7455a36
    • nginx: version 1.19.5
    • openssh: version 8.4p1
    • pam: version 1.5.1
    • php: version 7.4.13
    • samba: version 4.12.10
    • xfsprogs: version 5.9.0

    Linux kernel:

    • version 5.9.13
    • md/unraid: version 2.9.17
      removed spinup group spinup/spdindown support (functionality moved to emhttpd)
      added configurable sync start offset
    • added iSCSI kernel support:
      CONFIG_ISCSI_TARGET: Linux-iSCSI.org iSCSI Target Mode Stack
      CONFIG_ISCSI_TARGET_CXGB4: Chelsio iSCSI target offload driver
      CONFIG_LOOPBACK_TARGET: TCM Virtual SAS target and Linux/SCSI LDD fabric loopback module
      CONFIG_NVME_TARGET: NVMe Target support
      CONFIG_NVME_TARGET_LOOP: NVMe loopback device support
      CONFIG_NVME_TARGET_PASSTHRU: NVMe Target Passthrough support
      CONFIG_TARGET_CORE: Generic Target Core Mod (TCM) and ConfigFS Infrastructure
      CONFIG_TCM_FILEIO: TCM/FILEIO Subsystem Plugin for Linux/VFS
      CONFIG_TCM_IBLOCK: TCM/IBLOCK Subsystem Plugin for Linux/BLOCK
      CONFIG_TCM_PSCSI: TCM/pSCSI Subsystem Plugin for Linux/SCSI
      CONFIG_TCM_USER2: TCM/USER Subsystem Plugin for Linux
    • added USB/IP kernel support:
      CONFIG_USBIP_CORE: USB/IP support
      CONFIG_USBIP_VHCI_HCD: VHCI hcd

    Management:

    • emhttpd: implement spinup group spinup/spindown; add spinup/spindown callouts
    • emhttpd: get rid of poll_attributes event
    • emhttpd: fix disk "SMART controller type" not being honored when reading temperatures
    • rsyslog: fix broken "Mirror syslog to flash"
    • webgui: Fix wrong docker run URL reference
    • webgui: Fix crash when reading very large log files (limiting output to 1000 lines).
    • webgui: Fix dismiss all notification
    • webgui: Fix Started VMs not appearing in dashboard
    • webgui: VM manager: add virtio-win-0.1.190-1
    • webgui: Notifications: Fix gap on white / black
    • webgui: Do not show CA profiles in Add Container list
    • webgui: support spin-up/down and temperature monitoring of unassigned devices
    • webgui: VM manager: Fix: Changing from VM VNC graphics to GPU passthrough
    • webgui: Change Icon for Motherboard Info from cog (settings) to info

    Edited by limetech

    • Like 22


    User Feedback

    Recommended Comments



    5 minutes ago, limetech said:

    I/O to the devices

    Interesting, I did not see this with beta35.  My drives don't stay asleep with RC1.  SMART queries shouldn't wake up the device.

    Link to comment
    Share on other sites
    3 minutes ago, sivart said:

    I didn't see this on beta35.  SMART queries shouldn't wake up the device.

    post diagnostics

    Link to comment
    Share on other sites

    Seems to have broken my Telegraf container.
    I would have no i would have no idea how to fix it.

     

    Quote

    [telegraf] Error running agent: could not initialize input inputs.smart: smartctl not found: verify that smartctl is installed and it is in your PATH (or specified in config): provided path does not

     

    Link to comment
    Share on other sites
    34 minutes ago, Niklas said:

    Spin down works here but this spins them up from time to time. What could be the cause?

     

     

    May be relate disklocation plugin.

    Link to comment
    Share on other sites

    Updated from -beta35 successfully. Dashboard now displays Docker and VM panes correctly. Thank you.

    Quote

    - webgui: Change Icon for Motherboard Info from cog (settings) to info

    Shouldn't the icon for Memory Info (running processes) also be changed from a cog to info, since there are no settings to change there either?

    Link to comment
    Share on other sites
    5 minutes ago, Vr2Io said:

    May be relate disklocation plugin.

    I uninstalled disklocation and tried to put all my disks to sleep, and it immediately read smart status...

     

    Dec 10 20:41:45 ion emhttpd: spinning down /dev/sdg
    Dec 10 20:41:46 ion emhttpd: spinning down /dev/sdi
    Dec 10 20:41:46 ion emhttpd: spinning down /dev/sde
    Dec 10 20:41:47 ion emhttpd: spinning down /dev/sdf
    Dec 10 20:41:47 ion emhttpd: spinning down /dev/sdj
    Dec 10 20:41:48 ion emhttpd: spinning down /dev/sdk
    Dec 10 20:41:48 ion emhttpd: spinning down /dev/sdl
    Dec 10 20:41:49 ion emhttpd: spinning down /dev/sdd
    Dec 10 20:41:49 ion emhttpd: spinning down /dev/sdm
    Dec 10 20:41:50 ion emhttpd: read SMART /dev/sdm
    Dec 10 20:41:50 ion emhttpd: read SMART /dev/sdj
    Dec 10 20:41:50 ion emhttpd: read SMART /dev/sdk
    Dec 10 20:41:50 ion emhttpd: read SMART /dev/sdg
    Dec 10 20:41:50 ion emhttpd: read SMART /dev/sdd
    Dec 10 20:41:50 ion emhttpd: read SMART /dev/sde
    Dec 10 20:41:50 ion emhttpd: read SMART /dev/sdf
    Dec 10 20:41:50 ion emhttpd: read SMART /dev/sdl
    Dec 10 20:41:50 ion emhttpd: read SMART /dev/sdi
    Dec 10 20:41:56 ion emhttpd: spinning down /dev/sdh
    Dec 10 20:42:00 ion emhttpd: read SMART /dev/sdh

     

    Link to comment
    Share on other sites
    4 minutes ago, sivart said:

    I uninstalled disklocation and tried to put all my disks to sleep, and it immediately read smart status...

    Could you also try safe mode ( no plugin and VM )

    Link to comment
    Share on other sites
    6 minutes ago, Vr2Io said:

    Could you also try safe mode ( no plugin and VM )

    No joy.  I forced the drives to spin down and they came back up almost immediately.  

     

    Dec 10 20:52:40 ion root: unRAID Safe Mode (unraidsafemode) has been set
    <snip>
    Dec 10 20:53:40 ion emhttpd: spinning down /dev/sdf
    Dec 10 20:53:41 ion emhttpd: spinning down /dev/sdj
    Dec 10 20:53:42 ion emhttpd: spinning down /dev/sdk
    Dec 10 20:53:42 ion emhttpd: spinning down /dev/sdl
    Dec 10 20:53:43 ion emhttpd: spinning down /dev/sdd
    Dec 10 20:53:43 ion emhttpd: spinning down /dev/sdm
    Dec 10 20:53:44 ion emhttpd: read SMART /dev/sdj
    Dec 10 20:53:50 ion emhttpd: read SMART /dev/sdm
    Dec 10 20:53:50 ion emhttpd: read SMART /dev/sdk
    Dec 10 20:53:50 ion emhttpd: read SMART /dev/sdd
    Dec 10 20:53:50 ion emhttpd: read SMART /dev/sdf
    Dec 10 20:53:50 ion emhttpd: read SMART /dev/sdl
    Dec 10 20:54:01 ion emhttpd: spinning down /dev/sdh
    Dec 10 20:54:02 ion emhttpd: read SMART /dev/sdh
    Dec 10 20:56:20 ion emhttpd: spinning down /dev/sdg
    Dec 10 20:56:20 ion emhttpd: read SMART /dev/sdg
    Dec 10 20:56:24 ion emhttpd: spinning down /dev/sdi
    Dec 10 20:56:24 ion emhttpd: spinning down /dev/sde
    Dec 10 20:56:25 ion emhttpd: read SMART /dev/sde
    Dec 10 20:56:25 ion emhttpd: read SMART /dev/sdi
    Dec 10 20:56:29 ion emhttpd: spinning down /dev/sdf
    Dec 10 20:56:29 ion emhttpd: spinning down /dev/sdj
    Dec 10 20:56:30 ion emhttpd: read SMART /dev/sdj
    Dec 10 20:56:30 ion emhttpd: read SMART /dev/sdf
    Dec 10 20:56:33 ion emhttpd: spinning down /dev/sdk
    Dec 10 20:56:33 ion emhttpd: spinning down /dev/sdl
    Dec 10 20:56:34 ion emhttpd: spinning down /dev/sdd
    Dec 10 20:56:34 ion emhttpd: spinning down /dev/sdm
    Dec 10 20:56:35 ion emhttpd: read SMART /dev/sdm
    Dec 10 20:56:35 ion emhttpd: read SMART /dev/sdk
    Dec 10 20:56:35 ion emhttpd: read SMART /dev/sdd
    Dec 10 20:56:35 ion emhttpd: read SMART /dev/sdl
    Dec 10 20:56:40 ion emhttpd: spinning down /dev/sdh
    Dec 10 20:56:45 ion emhttpd: read SMART /dev/sdh

     

    Link to comment
    Share on other sites

    So I upgraded just now, and after the reboot via the WebGUI (did not shutdown the server physically) unRaid came back up and said it detected an unclean shutdown and started a parity check. There are errors related to my nvme cache disk on the log, none of this was there prior to the upgrade, I believe.

     

    Any idea what is going on? 

    tower-syslog-20201211-0230.zip

    Edited by abhi.ko
    Link to comment
    Share on other sites

    Could we have a section of the top post defining things that need to be done before upgrading... I'm about to go from 6.8.3 to 6.9.0-RC1 and know that I need to remove and reinstall Unassigned Devices, but I also remember reading about the changes that need to be made to VM's for networking... But I don't remember what the change is...

    • Like 1
    Link to comment
    Share on other sites

    Syslinux configuration <Default> reset function not work, but I can't confirm happen since this release or not.

    Link to comment
    Share on other sites

    I upgraded to this and all my vm’s and dockers disappeared and I had to recreate the xml and link them to the disks etc. Pretty irritating. 

    Link to comment
    Share on other sites

    @limetech Hey Tom, the Dashboard finallay shows the temps of the drives, if i once spin down the hdd's...

    screen07.thumb.PNG.b759458d62b307312ab72f41d332d556.PNG

     

    But now it seems i get no more SmartData shown in Disk -> Settings...

    screen08.thumb.PNG.e1ffb9882160be4b50ecd8d40aa0f7e9.PNG

    Reading Smartdata in console is still fine...

    screen09.thumb.PNG.8c8946f752f73f8f2ec6d824a22a5039.PNG

     

    Dunno if this is related to the temp display fix for dashboard.

    Can anyone confirm, that Smartdata is no more displayed on other controller type than default?

    Edited by DarkMan83
    Link to comment
    Share on other sites
    10 hours ago, Arbadacarba said:

    Could we have a section of the top post defining things that need to be done before upgrading... I'm about to go from 6.8.3 to 6.9.0-RC1 and know that I need to remove and reinstall Unassigned Devices, but I also remember reading about the changes that need to be made to VM's for networking... But I don't remember what the change is...

    Yes, I would like to see a list of things 'to-do' before upgrading. I remember reading about saving the cache drives to the array as the cache drives may be reassigned for the new multi-pool system or something in the lines of that.

    • Like 2
    Link to comment
    Share on other sites
    24 minutes ago, XiuzSu said:

    Yes, I would like to see a list of things 'to-do' before upgrading. I remember reading about saving the cache drives to the array as the cache drives may be reassigned for the new multi-pool system or something in the lines of that.

    @limetech mentioned that in the initial post:

    Quote

    We are in the process of writing up more thorough release notes in preparation for stable release.

    I suppose that it would take some time given the large number of changes between 6.8.3 and 6.9.

    Link to comment
    Share on other sites

    I think I may have seen somewhere that now we can have multiple cache pools? does that mean we don't need data going to unassigned drives anymore?

    Link to comment
    Share on other sites
    28 minutes ago, takkkkkkk said:

    I think I may have seen somewhere that now we can have multiple cache pools? does that mean we don't need data going to unassigned drives anymore?

    UD can still be used, but a pool device is a better way.

    Link to comment
    Share on other sites

    Do I understand correctly that unRAID will support iSCSI with this release or the 6.9 stable release? If not I think this is definitely a welcome feature.

    Link to comment
    Share on other sites
    28 minutes ago, takkkkkkk said:

    I think I may have seen somewhere that now we can have multiple cache pools? does that mean we don't need data going to unassigned drives anymore?

    I setup a second cache pool on beta 35 and it works well.  So in answer to your question, yes depending on your usage scenario.  My second cache pool is setup as RAID1 with two SSD's for all my VM and appdata stuff.

     

    craigr

    Link to comment
    Share on other sites

    If i would like to update from 6.8.3 to this what would i have to look for, or what would i need to read before that?

    Link to comment
    Share on other sites
    17 hours ago, doron said:

    @SimonF, a new version of the SAS spindown plugin is coming shortly, supporting 6.9.0.

    Posting in this thread just to follow up, I've just pushed a new version (0.8) of the SAS Spindown plugin, supporting 6.9.0-rc1 and the new spin up/down mechanisms. It's on CA.

    • Thanks 1
    Link to comment
    Share on other sites
    1 hour ago, craigr said:

    I setup a second cache pool on beta 35 and it works well.  So in answer to your question, yes depending on your usage scenario.  My second cache pool is setup as RAID1 with two SSD's for all my VM and appdata stuff.

     

    craigr

    RAID 1 is still btrfs right? No concerns there? What would be UD usage scenario now? I used it for Plex / SABNZBD staging. If I can have three separate cache pools, I don't think I need UD anymore.

    Edited by takkkkkkk
    Link to comment
    Share on other sites
    13 hours ago, PeteAsking said:

    I upgraded to this and all my vm’s and dockers disappeared and I had to recreate the xml and link them to the disks etc. Pretty irritating. 

    I had just the same problem together with the cache disks not connecting. Reverted to bet 35 fixed this.

    Link to comment
    Share on other sites



    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
    Add a comment...

    ×   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.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.