• 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



    Just now, limetech said:

    These spinning issues are addressed in -rc2

    Great.

     

    Also, in case it's new/useful info, when drives are spun down with hdparm -y the web interface shows them active despite smartctl and hdparm reporting standby.

    Link to comment
    Share on other sites
    8 hours ago, SimonF said:

    If using spin all up/down drives state refreshes, but the UD ones doesn't unless you do a full page reload.

    I'll have a fix for this in the next release of UD,

    • Thanks 1
    Link to comment
    Share on other sites
    On 12/11/2020 at 11:22 AM, takkkkkkk said:

    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.

    Yes, BTRSF.  I only use UD for discs that I want to drop in and pull out later at the moment.

     

    craigr

    Link to comment
    Share on other sites
    11 hours ago, ich777 said:

    Can you tell me which plugins that you have installed?

    CA Backup / Restore Appdata

    Community Applications

    Custom Tab

    Disable Mitigation Settings

    Dynamix Cache Directories

    Dynamix Local Master

    Dynamix Schedules

    Dynamix SSD TRIM

    Dynamix System Information

    File Activity

    Fix Common Problems

    IPMI support

    Libvirt Hotplug USB

    Nerd Tools

    Parity Check Tuning

    Preclear Disks

    Tips and Tweaks

    Unassigned Devices

    Unassigned Devices Plus

    User Scripts

    VFIO-PCI CFG

     

    There you have it.

     

    Kind regards,

    craigr

    Edited by craigr
    • Thanks 1
    Link to comment
    Share on other sites
    5 hours ago, CS01-HS said:

    Also, in case it's new/useful info, when drives are spun down with hdparm -y the web interface shows them active despite smartctl and hdparm reporting standby.

    You shouldn't spin down the disks this way.  Unraid needs to manage the spin up/down.  It keeps track of the disk spindown status so it doesn't have to query the disks.  Use the UI to spin up/down disks.

    Link to comment
    Share on other sites

    I don't seem to have many of the issues reported with discs improperly spinning up and I am still having correct spindown. Maybe because the LSI card is well supported?

     

    What I am seeing however is that my SATA SSD's are not "spinning down" or entering power saving mode.  They are plugged into the motherboard SATA ports, not the LSI controller.

     

    Thanks,

    caigr

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

    What I am seeing however is that my SATA SSD's are not "spinning down" or entering power saving mode.  They are plugged into the motherboard SATA ports, not the LSI controller.

    SSD's are "non-rotational" media and thus not subject to spin-down, or more generally, standby mode.  Perhaps a feature request?  How many solid-state devices have a "standby mode" anyway?

    Link to comment
    Share on other sites

    Can't say that I see less writes on my Samsung SSDs recreated with 1MiB-aligned... 

     

    But one question:

    How can I check if my docker.img still has the no-cow attribute? chattr does not seem to work ("Inappropriate ioctl for device While reading flags on docker.img"). And is there a way to correct this without recreating the docker.img?

    Link to comment
    Share on other sites
    5 hours ago, limetech said:

    SSD's are "non-rotational" media and thus not subject to spin-down, or more generally, standby mode.  Perhaps a feature request?  How many solid-state devices have a "standby mode" anyway?

    Both my Samsung 850 and 840 PRO drives support standby.  In that state they consume less than 0.07 watts.

    Quote

    Special Feature

     

    DEVICE SLEEP MODE SUPPORT

    Yes

    https://www.samsung.com/semiconductor/minisite/ssd/product/consumer/850pro/

     

    It had been working in v6.8 so I suspect the new spindown functionality upgrades?  The only beta of 6.9 I tried was Beta35, but it was so brief that I am not sure if the issue was present in Beta35 as well or not.

     

    Kind regards,

    craigr

    Link to comment
    Share on other sites
    6 hours ago, dlandon said:

    You shouldn't spin down the disks this way.  Unraid needs to manage the spin up/down.  It keeps track of the disk spindown status so it doesn't have to query the disks.  Use the UI to spin up/down disks.

    I have a USB drive mounted with unassigned devices and 3 SATA disks in 2nd pool that don't spin down on their own, so I wrote a script to spin them down which runs periodically.

     

    Is there a risk? I've been running it for months but not on the array disks which (prior to rc1) spun down on their own.

     

    Edited by CS01-HS
    Link to comment
    Share on other sites

    All right, I am getting weird spinups now too:

     

    Dec 12 20:14:00 unRAID emhttpd: spinning down /dev/sde
    Dec 12 20:15:28 unRAID emhttpd: spinning down /dev/sdn
    Dec 12 20:55:49 unRAID emhttpd: spinning down /dev/sdv
    Dec 12 20:59:41 unRAID emhttpd: read SMART /dev/sdn
    Dec 12 21:37:57 unRAID emhttpd: read SMART /dev/sdt
    Dec 12 22:00:33 unRAID emhttpd: spinning down /dev/sdn
    Dec 12 22:13:47 unRAID emhttpd: read SMART /dev/sde
    Dec 12 22:21:25 unRAID emhttpd: spinning down /dev/sds
    Dec 12 22:43:40 unRAID emhttpd: read SMART /dev/sdv
    Dec 12 22:54:15 unRAID emhttpd: spinning down /dev/sdh
    Dec 12 23:11:13 unRAID emhttpd: read SMART /dev/sdh
    Dec 12 23:14:34 unRAID emhttpd: spinning down /dev/sde
    Dec 12 23:15:40 unRAID emhttpd: read SMART /dev/sde

    I wasn't even in the unRAID GUI or doing anything with unRAID except typing on forums with my VM.

     

    craigr

    Link to comment
    Share on other sites
    6 hours ago, CS01-HS said:

    I have a USB drive mounted with unassigned devices and 3 SATA disks in 2nd pool that don't spin down on their own, so I wrote a script to spin them down which runs periodically.

     

    Is there a risk? I've been running it for months but not on the array disks which (prior to rc1) spun down on their own.

     

    Prior to RC1, UD set a timer in each disk that would spin the disk down after 15 minutes.  This was not that reliable because some disks would not respect it.  With RC1, Unraid has taken over disk spin up/down control.  RC1 only has manual spin up/down by clicking on the disk status ball.  RC2 will have spin down control of UD devices so disks will spin down after inactivity.

     

    The only risk is that the UD webpage and the Dashboard will not show the correct running status.

    • Like 1
    • Thanks 2
    Link to comment
    Share on other sites

    I want to revert the SSH "Improvements".

     

    If you change something like this, atleast document what exactly has changed. I have modified my ssh configurations in the past and now everything is broken from the update. How can I revert ssh back to the way it was before?

     

     

    I also now have a problem with docker:

    WARNING: Error loading config file: /root/.docker/config.json: stat /root/.docker/config.json: permission denied
     

    no idea how to fix this. there is no such config file but I guess there should be, but it wasn't created before because of all the permission changes

    Edited by Draic
    Link to comment
    Share on other sites

    If you are seeing unexplained disk activity, it may be due to cache dirs caching all folders.  For those of you using the Cache Dirs plugin, you need to specify folders to be included so all folders do not get included automatically.  This can also apply to pool disks.  It's really the best practice to specify the included folders so you control what is being cached.

    • Thanks 2
    Link to comment
    Share on other sites
    5 hours ago, Draic said:

    I want to revert the SSH "Improvements".

     

    If you change something like this, atleast document what exactly has changed. I have modified my ssh configurations in the past and now everything is broken from the update. How can I revert ssh back to the way it was before?

     

     

    I also now have a problem with docker:

    WARNING: Error loading config file: /root/.docker/config.json: stat /root/.docker/config.json: permission denied
     

    no idea how to fix this. there is no such config file but I guess there should be, but it wasn't created before because of all the permission changes

    Please open a separate report for this.

    Link to comment
    Share on other sites
    30 minutes ago, SplitHoirzon said:

    Anyone else running 6.9.0-rc1 having issues accessing mounted Network shares from their containers?

     

    • Like 2
    Link to comment
    Share on other sites

    Just updated from 6.8.3 and I noticed that I can't login to root directly (keyboard connects to my machine, not via ssh or webui terminal). Once I enter in "root" then return button, nothing happens, no password prompt. Even if I tap return several times, I don't see any new lines or anything about wrong password. Any idea what's going on? 

    Link to comment
    Share on other sites

    just upgraded my server to RC1 and now it doesnt boot anymore for some reason.

    it also doesnt seem to even connect to my network anymore, it would get a static IP assigned by my router but its not showing up at all.

     

    EDIT: just swapped the LAN cable over to another port, it seems like its not detecting my 10G NIC anymore, i can get into the interface with the onboard port.

    EDIT2: had to manually set my 10G NIC as eth0 again so it was used as the primary, now everything seems fine for now.

    Edited by Pixel5
    Link to comment
    Share on other sites
    On 12/10/2020 at 8:10 PM, sivart said:

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

    Hi,
    I have just tried to spin down three WD RED and one Seagate drives. They had stayed spun down for two mins. However, I did see them spun up. However, there is a log msg that Fix Comon Problem plugin had found a warning, and right after that disks had spun up. See below:
    Dec 14 03:27:02 HomeNAS emhttpd: spinning down /dev/sdd
    Dec 14 03:27:02 HomeNAS emhttpd: spinning down /dev/sde
    Dec 14 03:27:02 HomeNAS emhttpd: spinning down /dev/sdb
    Dec 14 03:27:02 HomeNAS emhttpd: spinning down /dev/sdc
    Dec 14 03:29:00 HomeNAS root: Fix Common Problems Version 2020.12.05
    Dec 14 03:29:00 HomeNAS root: Fix Common Problems: Warning: Plugin Update Check not enabled ** Ignored
    Dec 14 03:29:00 HomeNAS root: Fix Common Problems: Warning: Docker Update Check not enabled ** Ignored
    Dec 14 03:29:01 HomeNAS emhttpd: read SMART /dev/sde
    Dec 14 03:29:05 HomeNAS emhttpd: read SMART /dev/sdd
    Dec 14 03:29:05 HomeNAS emhttpd: read SMART /dev/sdb
    Dec 14 03:29:05 HomeNAS emhttpd: read SMART /dev/sdc

    Link to comment
    Share on other sites
    5 hours ago, RusmanCool said:

    However, there is a log msg that Fix Comon Problem plugin had found a warning, and right after that disks had spun up. See below:

    FCP has an option to avoid spinning up disks

    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.