• Unraid OS version 6.9.0-beta29 available


    limetech

    Back in the saddle ... Sorry for the long delay in publishing this release.  Aside from including some delicate coding, this release was delayed due to several team members, chiefly myself, having to deal with various non-work-related challenges which greatly slowed the pace of development.  That said, there is quite a bit in this release, LimeTech is growing and we have many exciting features in the pipe - more on that in the weeks to come.  Thanks to everyone for their help and patience during this time.

    Cheers,

    -Tom

     

    IMPORTANT: This is Beta software.  We recommend running on test servers only!

     

    KNOWN ISSUE: with this release we have moved to the latest Linux 5.8 stable kernel.  However, we have discovered that a regression has been introduced in the mtp3sas driver used by many LSI chipsets, e.g., LSI 9201-16e.  Typically looks like this on System Devices page:

    Serial Attached SCSI controller: Broadcom / LSI SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] (rev 02)

    The problem is that devices are no longer recognized.  There are already bug reports pertaining to this issue:

    https://bugzilla.kernel.org/show_bug.cgi?id=209177

    https://bugzilla.redhat.com/show_bug.cgi?id=1878332

     

    We have reached out to the maintainer to see if a fix can be expedited, however we feel that we can neither revert back to 5.7 kernel nor hold the release due to this issue.  We are monitoring and will publish a release with fix asap.

     

    ANOTHER known issue: we have added additional btrfs balance options:

    • raid1c3
    • raid1c4
    • and modified the raid6 balance operation to set meta-data to raid1c3 (previously was raid1).

     

    However, we have noticed that applying one of these balance filters to a completely empty volume leaves some data extents with the previous profile.  The solution is to simply run the same balance again.  We consider this to be a btrfs bug and if no solution is forthcoming we'll add the second balance to the code by default.  For now, it's left as-is.

     

    THE PRIMARY FOCUS of this release is to put tools in place to help users migrate data off SSD-based pools so that those devices may be re-partitioned if necessary, and then migrate the data back.

     

    What are we talking about?  For several years now, storage devices managed by Unraid OS are formatted with an "Unraid Standard Partition Layout".  This layout has partition 1 starting at offset 32KiB from the start of the device, and extending to the end of the device.  (For devices with 512-byte sectors, partition 1 starts in sector 64; for 4096-byte sector size devices, partition 1 starts in sector 8.)  This layout achieves maximum storage efficiency and ensures partition 1 starts on a 4096-byte boundary.

     

    Through user reports and extensive testing however, we have noted that many modern SSD devices, in particular Samsung EVO, do not perform most efficiently using this partition layout, and the devices seem to write far more than one would expect, and with SSD, one wants to minimize writes to SSD as much as possible.

     

    The solution to the "excessive SSD write" issue is to position partition 1 at offset 1MiB from the start of the device instead of at 32KiB.  The will both increase performance and decrease writes with affected devices.  Do you absolutely need to re-partition your SSD's?  Probably not depending on what devices you have.  Click on a device from Main, scroll down to Attributes and take a look at Data units written.  If this is increasing very rapidly then you probably would benefit by re-partitioning.

     

    Note: if you have already (re)Formatted using previous 6.9-beta release, for SSD smaller than 2TiB the proper partition layout will appear like this on the Device Information page:

    Partition format:   MBR: 1MiB-aligned

    For SSD larger than 2TiB:

    Partition format:   GPT: 1MiB-aligned

     

    Here's what's in this release to help facilitate re-partitioning of SSD devices:

     

    An Erase button which appears in the Device Information page.

     

    The Erase button may be used to erase (delete) content from a volume. A volume is either the content of an unRAID array data disk, or the content of a pool. In the case of an unRAID disk, only that device is erased; in the case of a multiple-device pool ALL devices of the pool are erased.

    The extent of Erase varies depending on whether the array is Stopped, or Started in Maintenance mode (if started in Normal mode, all volume Erase buttons are disabled).

    Started/Maintenance mode: in this case the LUKS header (if any) and any file system within partition 1 is erased. The MBR (master boot record) is not erased.

    Stopped - in this case, unRAID array disk volumes and pool volumes are treated a little differently:

    • unRAID array disk volumes - if Parity and/or Parity2 is valid, then operation proceeds exactly as above, that is, content of only partition 1 is erased but the MBR (master boot record) is left as-is; but, if there is no valid parity, then the MBR is also erased.
    • Pool volumes - partition 1 of all devices within the pool are erased, and then the MBR is also erased.


    The purpose of erasing the MBR is to permit re-partitioning of the device if required.  Upon format, Unraid OS will position partition 1 at 32KiB for HDD devices and at 1MiB for SSD devices.

     

    Note that erase does not overwrite the storage content of a device, it simply clears the LUKS header if present (which effectively makes the device unreadable), and file system and MBR signatures.  A future Unraid OS release may include the option of overwriting the data.

     

    Additional "Mover" capabilities.

     

    Since SSD pools are commonly used to store vdisk images, shfs/mover is now aware of:

    • sparse files - when a sparse file is moved from one volume to another, it's sparseness is preserved
    • NoCOW attribute - when a file or directory in a btrfs volume has the NoCOW attribute set, the attribute is preserved when the file or directory is moved to another btrfs volume.

     

    Note that btrfs subvolumes are not preserved.  A future Unraid OS release may include preservation of btrfs subvolumes.

     

    Ok how do I re-partition my SSD pools?

     

    Outlined here are two basic methods:

    1. "Mover" method - The idea is to use the Mover to copy all data from the pool to a target device in the unRAID array.  Then erase all devices of the pool, and reformat.  Finally use the Mover to copy all the data back.
    2. "Unassign/Re-assign" method - The idea here is, one-by-one, remove a device from a btrfs pool, balance the pool with reduced device count, then re-assign the device back to the pool, and balance pool back to include the device.  This works because Unraid OS will re-partition new devices added to an existing btrfs pool.  This method is not recommended for a pool with more than 2 devices since the first balance operation may be write-intensive, and writes are what we're trying to minimize.  Also it can be tricky to determine if enough free space really exists after removing a device to rebalance the pool.  Finally, this method will introduce a time window where your data is on non-redundant storage.

     

    No matter which method, if you have absolutely critical data in the pool we strongly recommend making an independent backup first (you are already doing this right?).

     

     

    Mover Method

    This procedure presumes a multi-device btrfs pool containing one or more cache-only or cache-prefer shares.

     

    1. With array Started, stop any VM's and/or Docker applications which may be accessing the pool you wish to re-partition.  Make sure no other external I/O is targeting this pool.

     

    2. For each share on the pool, go to the Share Settings page and make some adjustments:

    • change from cache-only (or cache-prefer) to cache-yes
    • assign an array disk or disks via Include mask to receive the data.  If you  wish to preserve the NoCOW attribute (Copy-on-write set to No) on files and directories, these disks should be formatted with btrfs.  Of course ensure there is enough free space to receive the data.

     

    3. Now go back to Main and click the Move button.  This will move the data of each share to the target array disk(s).

     

    4. Verify no data left on the pool, Stop array, click on the pool and then click the Erase button.

     

    5. Start the array and the pool should appear Unformatted - go ahead and Format the pool (this is what will re-write the partition layout).

     

    6. Back to Share Settings page; for each above share:

    • change from cache-yes to cache-prefer

     

    7. On Main page click Move button.  This will move data of each share back to the pool.

     

    8. Finally, back to Share Settings page; for each share:

    • change from cache-prefer back to cache-only if desired

     

    Unassign/Re-assign Method

    1. Stop array and unassign one of the devices from your existing pool; leave device unassigned.
    2. Start array.  A balance will take place on your existing pool.  Let the balance complete.
    3. Stop array.  Re-assign the device, adding it back to your existing pool.
    4. Start array.  The added device will get re-partitioned and a balance will start moving data to the new device.  Let the balance complete.
    5. Repeat steps 1-4 for the other device in your existing pool.

     

    Whats happening here is this:

    At the completion of step 2, btrfs will 'delete' the missing device from the volume and wipe the btrfs signature from it.

    At the beginning of step 4, Unraid OS will re-partition the new device being added to an existing pool.

     

    I don't care about preserving data in the pool.  In this case just Stop array, click on the pool and then click Erase.  Start array and Format the pool - done.  Useful to know: when Linux creates a file system in an SSD device, it will first perform a "blkdiscard" on the entire partition.  Similarly, "blkdisard" is initiated on partition 1 on a new device added to an existing btrfs pool.

     

    What about array devices?  If you have SSD devices in the unRAID array the only  way to safely re-partition those devices is to either remove them from the array, or remove parity devices from the array.  This is because re-partitioning will invalidate parity.  Note also the volume size will be slightly smaller.

     


     

    Version 6.9.0-beta29 2020-09-27 (vs -beta25)

    Base distro:

    • at-spi2-core: version 2.36.1
    • bash: version 5.0.018
    • bridge-utils: version 1.7
    • brotli: version 1.0.9
    • btrfs-progs: version 5.6.1
    • ca-certificates: version 20200630
    • cifs-utils: version 6.11
    • cryptsetup: version 2.3.4
    • curl: version 7.72.0 (CVE-2020-8231)
    • dbus: version 1.12.20
    • dnsmasq: version 2.82
    • docker: version 19.03.13
    • ethtool: version 5.8
    • fribidi: version 1.0.10
    • fuse3: version 3.9.3
    • git: version 2.28.0
    • glib2: version 2.66.0 build 2
    • gnutls: version 3.6.15
    • gtk+3: version 3.24.23
    • harfbuzz: version 2.7.2
    • haveged: version 1.9.13
    • htop: version 3.0.2
    • iproute2: version 5.8.0
    • iputils: version 20200821
    • jasper: version 2.0.21
    • jemalloc: version 5.2.1
    • libX11: version 1.6.12
    • libcap-ng: version 0.8
    • libevdev: version 1.9.1
    • libevent: version 2.1.12
    • libgcrypt: version 1.8.6
    • libglvnd: version 1.3.2
    • libgpg-error: version 1.39
    • libgudev: version 234
    • libidn: version 1.36
    • libpsl: version 0.21.1 build 2
    • librsvg: version 2.50.0
    • libssh: version 0.9.5
    • libvirt: version 6.6.0 (CVE-2020-14339)
    • libxkbcommon: version 1.0.1
    • libzip: version 1.7.3
    • lmdb: version 0.9.26
    • logrotate: version 3.17.0
    • lvm2: version 2.03.10
    • mc: version 4.8.25
    • mpfr: version 4.1.0
    • nano: version 5.2
    • ncurses: version 6.2_20200801
    • nginx: version 1.19.1
    • ntp: version 4.2.8p15 build 2
    • openssl-solibs: version 1.1.1h
    • openssl: version 1.1.1h
    • p11-kit: version 0.23.21
    • pango: version 1.46.2
    • php: version 7.4.10 (CVE-2020-7068)
    • qemu: version 5.1.0 (CVE-2020-10717, CVE-2020-10761)
    • rsync: version 3.2.3
    • samba: version 4.12.7 (CVE-2020-1472)
    • sqlite: version 3.33.0
    • sudo: version 1.9.3
    • sysvinit-scripts: version 2.1 build 35
    • sysvinit: version 2.97
    • ttyd: version 1.6.1
    • util-linux: version 2.36
    • wireguard-tools: version 1.0.20200827
    • xev: version 1.2.4
    • xf86-video-vesa: version 2.5.0
    • xfsprogs: version 5.8.0
    • xorg-server: version 1.20.9 build 3
    • xterm: version 360
    • xxHash: version 0.8.0

    Linux kernel:

    • version 5.8.12
    • kernel-firmware: version kernel-firmware-20200921_49c4ff5
    • oot: Realtek r8152: version 2.13.0
    • oot: Tehuti tn40xx: version 0.3.6.17.3

    Management:

    • btrfs: include 'discard=async' mount option
    • emhttpd: avoid using remount to set additional mount options
    • emhttpd: added wipefs function (webgui 'Erase' button)
    • shfs: move: support spares files
    • shfs: move: preserve ioctl_iflags when moving between same file system types
    • smb: remove setting 'aio' options in smb.conf, use samba defaults
    • webgui: Update noVNC to v1.2.0
    • webgui: Docker: more intuitive handling of images
    • webgui: VMs: more intuitive handling of image selection
    • webgui: VMs: Fixed: rare cases vdisk defaults to Auto when it should be Manual
    • webgui: VMs: Fixed: Adding NICs or VirtFS mounts to a VM is limited
    • webgui: VM manager: new setting "Network Model"
    • webgui: Added new setting "Enable user share assignment" to cache pool
    • webgui: Dashboard: style adjustment for server icon
    • webgui: Update jGrowl to version 1.4.7
    • webgui: Fix ' appearing
    • webgui: VM Manager: add 'virtio-win-0.1.189-1' to VirtIO-ISOs list
    • webgui: Prevent bonded nics from being bound to vfio-pci too
    • webgui: better handling of multiple nics with vfio-pci
    • webgui: Suppress WG on Dashboard if no tunnels defined
    • webgui: Suppress Autofan link on Dashboard if plugin not installed
    • webgui: Detect invalid session and logout current tab
    • webgui: Added support for private docker registries with basic auth or no auth, and improvements for token based authentication
    • webgui: Fix notifications continually reappearing
    • webgui: Support links on notifications
    • webgui: Add raid1c3 and raid1c4 btrfs pool balance options.
    • webgui: For raid6 btrfs pool data profile use raid1c3 metadata profile.
    • webgui: Permit file system configuration when array Started for Unmountable volumes.
    • webgui: Fix not able to change parity check schedule if no cache pool present
    • webgui: Disallow "?" in share names
    • webgui: Add customizable timeout when stopping containers

    Edited by limetech

    • Like 6
    • Thanks 6


    User Feedback

    Recommended Comments



    On 9/28/2020 at 9:59 PM, Squid said:

    Wouldn't hurt to check.  The only reports thus far with this issue are 9201-16e's.  If it doesn't work, all of your drives connected won't be detected.  A simple roll back to beta 25 and everything will be back to normal.

    Ok, updated to 6.9.0-beta29 and my 9201-16i (based on 2116 chip) seemingly works fine. @limetech @Squid

    • Thanks 1
    Link to comment
    Share on other sites
    23 minutes ago, SpuddyUK said:

    Ok, updated to 6.9.0-beta29 and my 9201-16i (based on 2116 chip) seemingly works fine. @limetech @Squid

    Awesome.  Weird though that what amounts to just a slightly different population of the board (16e vs 16i) accounts for the problem...

    • Like 1
    Link to comment
    Share on other sites
    13 hours ago, cdoublejj said:

    so i've had my unraid for a few years now and am looking at blowing away my array and replacing all my drives and starting new.

     

    can i use this new mover function?  ....other wise i was going to copy all my data over to some 10TB external drives over the network and copy it back once i rebuild my array (any my shares?)

     

    does share configuration go away when i delete my array?

    The .cfg file for each share is stored on flash in config/shares. For a share to actually exist, though, it must have a top level folder on pool or array named for the share. Top level folders are always shares, but any top level folder that doesn't have a .cfg file has default settings (highwater, split any, minimum 0, include all, cache-no).

     

    mover still only moves from array to pool, or pool to array, so unless you have a very large pool it isn't likely to help with moving your array files somewhere.

     

    Unassigned Devices can mount external drives so no need to do it over the network. As long as you have a single (possibly empty) array data disk you can start Unraid and use plugins and even dockers and VMs.

    Link to comment
    Share on other sites
    9 minutes ago, Frank1940 said:

    Personally, I would replace the parity drive first with a new larger one and then replace each drive with a new one and use the rebuild using parity process.   See here:

       https://wiki.unraid.net/UnRAID_6/Storage_Management#Normal_replacement

    I guess it depends on what @cdoublejj means by "blowing away my array". In any case, this is getting off-topic for this thread so for more advice start a new thread in General Support.

    • Like 1
    Link to comment
    Share on other sites

    @limetech which version of wsdd is used in this beta?
    Today after 2 month uptime I noticed 1 core is at 100%, ... wsdd
    I don't know which version is used in Unraid but I found an old issue which was fixed:
    https://github.com/christgau/wsdd/pull/42

    This was at version 6.8.3, but on this thread people are complaining also for 6.9 beta 25:

     

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

    Plans to address this.  How long to next release-- days or Soon(TM)?   If Soon(TM), I will have to roll back as I really want the E-mail notifications to work.  (Thinking perhaps, a    -beta29a   release might be in order...)

    To fix this now, download attached file and put it on your flash, then add a command in your 'go' file like this:

    cp /boot/statuscheck /usr/local/emhttp/plugins/dynamix/scripts

    (be sure to get rid of that when next release comes out)

    statuscheck

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

    I have found some odd behaviour around the VM piece. So i updated to beta 29 to help resolve many of the issues seen around passing through devices on a AMD Ryzen 3000 based system (3800x, Gigabyte gaming B350 v1).

     

    The new kernel changes in the backend fix many of issues seen with that type of build and QEMU meaning i can pass through a 1060 3GB geforce card without a problem. No see code 43 and so is a major step forward.

     

    However the audio devices will not passthrough correctly to the windows 10 VM. Under device manager the audio devices show without error installed (geforce audio, amd starship/matisse hd audio controller and a USB based sound device) however under sound and output/input devices it will not show any of them.

     

    Doesn't matter if its pci-e or USB based none of these work or result in a usable output device in sounds inputs/outputs. However if i roll back to 6.8.3 then the USB device above instantly works for example.

     

    Yet booting/running and passing through a GPU on a Ryzen 3000 based system without "vfio-pci.ids=10de:1c02,10de:10f1 video=vesafb:off video=efifb:off" was working fine.

     

    So its really odd its just the audio based devices. I doubt theres a easy fix right now so for now i may revert.

     

    Cheers

     

     

    tower-diagnostics-20200930-2101.zip

    Link to comment
    Share on other sites
    23 hours ago, L0rdRaiden said:

    What was this problem about?

    Does it require qemu 5.1?

    A problem with host passthrough. Spaceinvader One made a video about it a few days ago.

     

    • Like 1
    Link to comment
    Share on other sites

    Not very impressed this was released without testing something as fundamental as VM disk passthrough 

    Link to comment
    Share on other sites
    8 minutes ago, Dave31337 said:

    Not very impressed this was released without testing something as fundamental as VM disk passthrough 

    We don't use raw disk passthrough - we use vdisks for everything.  Certain functions like this are being tested via these beta releases.  Stuff happens, example: the mpt3sas driver issue introduced into Linux 5.8 kernel which has been "stable" for 12 patch releases now.

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

    I have found some odd behaviour around the VM piece. So i updated to beta 29 to help resolve many of the issues seen around passing through devices on a AMD Ryzen 3000 based system (3800x, Gigabyte gaming B350 v1).

     

    The new kernel changes in the backend fix many of issues seen with that type of build and QEMU meaning i can pass through a 1060 3GB geforce card without a problem. No see code 43 and so is a major step forward.

     

    However the audio devices will not passthrough correctly to the windows 10 VM. Under device manager the audio devices show without error installed (geforce audio, amd starship/matisse hd audio controller and a USB based sound device) however under sound and output/input devices it will not show any of them.

     

    Doesn't matter if its pci-e or USB based none of these work or result in a usable output device in sounds inputs/outputs. However if i roll back to 6.8.3 then the USB device above instantly works for example.

     

    Yet booting/running and passing through a GPU on a Ryzen 3000 based system without "vfio-pci.ids=10de:1c02,10de:10f1 video=vesafb:off video=efifb:off" was working fine.

     

    So its really odd its just the audio based devices. I doubt theres a easy fix right now so for now i may revert.

     

    Cheers

     

     

    tower-diagnostics-20200930-2101.zip 107.2 kB · 0 downloads

     

    Does it make any difference which virtio-win drivers are installed, or put anther way, have you installed the latest windows drivers?  Under Settings/VM Manager we do try to keep that current, and at present it does let you select the latest "virtio-win-0.1.189".  The direct downloads from Fedora are kept here:

    https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/?C=M;O=D

    Link to comment
    Share on other sites

    Just wanted to report my SAS drive is working.

    [1000:0087] 01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05)

     

    I am also migrating my cache drives to 1Mb partitions using the Unassign/Re-assign Method.  2 drives down, 1 to go.  

    • Like 1
    Link to comment
    Share on other sites
    18 minutes ago, sittingmongoose said:

    Should I be concerned if after I balance my Cache drives and it completes, it says no balance found?

    That's how BTRFS describes that the balance operation is not running, so it's perfectly fine.

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

    Not very impressed this was released without testing something as fundamental as VM disk passthrough 

    Really man?  It's beta for a reason...

    Link to comment
    Share on other sites

    I have to be "that guy" for a second... any idea when this might go to RC?  I don't have a test server and I'm really looking forward to the benefits of 6.9.  I do have an LSI card though, only 4 ports.  Any idea if this is impacted by the current bug?

    Serial Attached SCSI controller: Broadcom / LSI SAS2004 PCI-Express Fusion-MPT SAS-2 [Spitfire] (rev 03)

     

    Thanks!

    Link to comment
    Share on other sites

    Is there a way to run beta-25?  I am currently on stable release (6.8.3) and jumping to beta-29 results in the SAS issue as described.  

    Link to comment
    Share on other sites

    Seeing some weird things now.  Upgraded from beta 25.  My server completely crashed, hasn't done that in many months. Not seeing any errors anywhere.  Had to pull the power to reboot it.

     

    Then there are some issues with docker.  A bunch of the dockers say "not available" under the version.

     

    Andddd NZBget no longer works.  But it did before the crash.  Attaching diagnostics and Syslog.

    syslog.txt 9900k-diagnostics-20201001-0016.zip

    Edited by sittingmongoose
    Link to comment
    Share on other sites
    4 hours ago, nickp85 said:

    Any idea if this is impacted by the current bug?

    No, only some SAS2116 based models are affected.

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

    Seeing some weird things now.  Upgraded from beta 25.  My server completely crashed, hasn't done that in many months. Not seeing any errors anywhere.  Had to pull the power to reboot it.

     

    Then there are some issues with docker.  A bunch of the dockers say "not available" under the version.

     

    Andddd NZBget no longer works.  But it did before the crash.  Attaching diagnostics and Syslog.

    syslog.txt 326.7 kB · 1 download 9900k-diagnostics-20201001-0016.zip 276.58 kB · 1 download

    That happened with me before and i solved it by recreatig the "proxynet" network (created from spaceinvader's video instructions for reverse proxy)

    Link to comment
    Share on other sites



    Guest
    This is now closed for further comments

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