Jump to content
  • Unraid OS version 6.9.0-beta22 available


    limetech

    Welcome (again) to 6.9 release development!

     

    This release marks hopefully the last beta before moving to -rc phase.  The reason we still mark beta is because we'd like to get wider testing of new multiple-pool feature, as well as perhaps sneak in a couple more refinements.  With that in mind, the obligatory disclaimer:

     

    Important: Beta code is not fully tested and not feature-complete.  We recommend running on test servers only!

     

    That said, here's what's new in this release...

     

    Multiple Pools

    This features permits you to define up to 35 named pools, of up to 30 storage devices/pool.  The current "cache pool" is now simply a pool named "cache".  Pools are created and managed via the Main page.

     

    Note: When you upgrade a server which has a cache pool defined, a backup of config/disk.cfg will be saved to config/disk.cfg.bak, and then cache device assignment settings are moved out of disk.cfg and into a new file, config/pools/cache.cfg.  If later you revert back to a pre-6.9 Unraid OS release you will lose your cache device assignments and you will have to manually re-assign devices to cache.  As long as you reassign the correct devices, data should remain intact.

     

    When you create a user share, or edit an existing user share, you can specify which pool should be associated with that share.  The assigned pool functions identically to current cache pool operation.

     

    Something to be aware of: when a directory listing is obtained for a share, the unRAID array disk volumes and all pools which contain that share are merged in this order:

      pool assigned to share

      disk1

      :

      disk28

      all the other pools in strverscmp() order.

     

    As with the current "cache pool", a single-device pool may be formatted with either xfs, btrfs, or reiserfs.  A multiple-device pool may only be formatted with btrfs.  A future release will include support for multiple "unRAID array" pools.  We are also considering zfs support.

     

    Something else to be aware of: Let's say you have a 2-device btrfs pool. This will be what btrfs calls "raid1" and what most people would understand to be "mirrored disks". Well this is mostly true in that the same data exists on both disks but not necessarily at the block-level.  Now let's say you create another pool, and what you do is unassign one of the devices from the existing 2-device btrfs pool and assign it to this pool.  Now you have x2 1-device btrfs pools.  Upon array Start user might understandably assume there are now x2 pools with exactly the same data.  However this is not the case. Instead, when Unraid OS sees that a btrfs device has been removed from an existing multi-device pool, upon array Start it will do a 'wipefs' on that device so that upon mount it will not be included in the old pool.  This of course effectively deletes all the data on the moved device.

     

    Language Translation

    A huge amount of work and effort has been implemented by @bonienl to provide multiple-language support in the Unraid OS Management Utility, aka, webGUI.  There are several language packs now available, and several more in the works.  Thanks to @Squid, language packs are installed via the Community Applications plugin - look for a new category entitled Language.

     

    Note: Community Applications HAS to be up to date to install languages.  Versions of CA prior to 2020.05.12 will not even load on this release.  As of this writing, the current version of CA is 2020.06.13a.  See also here.

     

    Each language pack exists in public Unraid organization github repos.  Interested users are encouraged to clone and issue Pull Requests to correct translations errors.  Language translations and PR merging is managed by @SpencerJ.

     

    Linux Kernel

    Upgraded to 5.7.

     

    Unfortunately, none of the out-of-tree drivers compile with this kernel.  In particular, these drivers are omitted:

    • Highpoint RocketRaid r750
    • Highpoint RocketRaid rr3740a
    • Tehuti Networks tn40xx

    If you require one of these drivers, please create a Bug Report and we'll spend some time looking for alternatives.  Better yet, pester the manufacturer of the controller and get them to update their drivers.

     

    Base Packages

    All updated to latest versions.  In addition, Linux PAM has been integrated.  This will permit us to install 2-factor authentication packages in a future release.

     

    Docker

    Updated to version 19.03.11

     

    Also now possible to select different icons for multiple containers of the same type.  This change necessitates a re-download of the icons for all your installed docker applications.  A delay when initially loading either the dashboard or the docker tab while this happens is to be expected prior to the containers showing up.

     

    Virtualization

    libvirt updated to version 6.4.0

    qemu updated to version 5.0.0

     

    In addition, integrated changes to System Devices page by user @Skitals with modifications by user @ljm42.  You can now select PCI devices to isolate from Linux upon boot simply by checking some boxes.  This makes it easier to reserve those devices for assignment to VM's.

     

    Note: If you had the VFIO-PCI Config plugin installed, you should remove it as that functionality is now built-in to Unraid OS 6.9.  Refer also @ljm42's excellent guide.

     

    In a future release we will include the NVIDIA and AMD GPU drivers natively into Unraid OS.  The primary use case is to facilitate accelerated transcoding in docker containers.  For this we require Linux to detect and auto-install the appropriate driver.  However, in order to reliably pass through an NVIDIA or AMD GPU to a VM, it's necessary to prevent Linux from auto-installing a GPU driver for those devices upon boot, which can be easily done now through System Devices page.  Users passing GPU's to VM's are encouraged to set this up now.

     

    "unexpected GSO errors"

     

    If your system log is being flooded with errors such as:

    Jun 20 09:09:21 Tower kernel: tun: unexpected GSO type: 0x0, gso_size 31, hdr_len 66

    You need to edit each VM and change the model type for the Ethernet bridge from "virtio" to "virtio-net".  In most cases this can be accomplished simply by clicking Update in "Form View" on the VM Edit page.  For other network configs it may be necessary to directly edit the xml.  For example:

    <interface type='bridge'>
          <mac address='xx:xx:xx:xx:xx:xx'/>
          <source bridge='br0'/>
          <model type='virtio-net'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>

     

    Other

    • AFP support has been removed.
    • Numerous other Unraid OS and webGUI bug fixes and improvements.

     

    Version 6.9.0-beta22 2020-06-16

     

    Caution! This is beta sofware, consider using on test servers only.

     

    Base distro:

    • aaa_base: version 14.2
    • aaa_elflibs: version 15.0 build 23
    • acl: version 2.2.53
    • acpid: version 2.0.32
    • apcupsd: version 3.14.14
    • at: version 3.2.1
    • attr: version 2.4.48
    • avahi: version 0.8
    • bash: version 5.0.017
    • beep: version 1.3
    • bin: version 11.1
    • bluez-firmware: version 1.2
    • bridge-utils: version 1.6
    • brotli: version 1.0.7
    • btrfs-progs: version 5.6.1
    • bzip2: version 1.0.8
    • ca-certificates: version 20191130 build 1
    • celt051: version 0.5.1.3
    • cifs-utils: version 6.10
    • coreutils: version 8.32
    • cpio: version 2.13
    • cpufrequtils: version 008
    • cryptsetup: version 2.3.3
    • curl: version 7.70.0
    • cyrus-sasl: version 2.1.27
    • db48: version 4.8.30
    • dbus: version 1.12.18
    • dcron: version 4.5
    • devs: version 2.3.1 build 25
    • dhcpcd: version 8.1.9
    • diffutils: version 3.7
    • dmidecode: version 3.2
    • dnsmasq: version 2.81
    • docker: version 19.03.11
    • dosfstools: version 4.1
    • e2fsprogs: version 1.45.6
    • ebtables: version 2.0.11
    • eject: version 2.1.5
    • elvis: version 2.2_0
    • etc: version 15.0
    • ethtool: version 5.7
    • eudev: version 3.2.5
    • file: version 5.38
    • findutils: version 4.7.0
    • flex: version 2.6.4
    • floppy: version 5.5
    • fontconfig: version 2.13.92
    • freetype: version 2.10.2
    • fuse3: version 3.9.1
    • gawk: version 4.2.1
    • gd: version 2.2.5
    • gdbm: version 1.18.1
    • genpower: version 1.0.5
    • getty-ps: version 2.1.0b
    • git: version 2.27.0
    • glib2: version 2.64.3
    • glibc-solibs: version 2.30
    • glibc-zoneinfo: version 2020a build 1
    • glibc: version 2.30
    • gmp: version 6.2.0
    • gnutls: version 3.6.14
    • gptfdisk: version 1.0.5
    • grep: version 3.4
    • gtk+3: version 3.24.20
    • gzip: version 1.10
    • harfbuzz: version 2.6.7
    • haveged: version 1.9.8
    • hdparm: version 9.58
    • hostname: version 3.23
    • htop: version 2.2.0
    • icu4c: version 67.1
    • inetd: version 1.79s
    • infozip: version 6.0
    • inotify-tools: version 3.20.2.2
    • intel-microcode: version 20200609
    • iproute2: version 5.7.0
    • iptables: version 1.8.5
    • iputils: version 20190709
    • irqbalance: version 1.6.0
    • jansson: version 2.13.1
    • jemalloc: version 4.5.0
    • jq: version 1.6
    • keyutils: version 1.6.1
    • kmod: version 27
    • lbzip2: version 2.5
    • lcms2: version 2.10
    • less: version 551
    • libaio: version 0.3.112
    • libarchive: version 3.4.3
    • libcap-ng: version 0.7.10
    • libcgroup: version 0.41
    • libdaemon: version 0.14
    • libdrm: version 2.4.102
    • libedit: version 20191231_3.1
    • libestr: version 0.1.11
    • libevent: version 2.1.11
    • libfastjson: version 0.99.8
    • libffi: version 3.3
    • libgcrypt: version 1.8.5
    • libgpg-error: version 1.38
    • libgudev: version 233
    • libidn: version 1.35
    • libjpeg-turbo: version 2.0.4
    • liblogging: version 1.0.6
    • libmnl: version 1.0.4
    • libnetfilter_conntrack: version 1.0.8
    • libnfnetlink: version 1.0.1
    • libnftnl: version 1.1.7
    • libnl3: version 3.5.0
    • libpcap: version 1.9.1
    • libpciaccess: version 0.16
    • libpng: version 1.6.37
    • libpsl: version 0.21.0
    • librsvg: version 2.48.7
    • libseccomp: version 2.4.3
    • libssh2: version 1.9.0
    • libssh: version 0.9.4
    • libtasn1: version 4.16.0
    • libtirpc: version 1.2.6
    • libunistring: version 0.9.10
    • libusb-compat: version 0.1.5
    • libusb: version 1.0.23
    • libuv: version 1.34.0
    • libvirt-php: version 0.5.5
    • libvirt: version 6.4.0
    • libwebp: version 1.1.0
    • libwebsockets: version 3.2.2
    • libx86: version 1.1
    • libxml2: version 2.9.10
    • libxslt: version 1.1.34
    • libzip: version 1.7.0
    • lm_sensors: version 3.6.0
    • logrotate: version 3.16.0
    • lshw: version B.02.17
    • lsof: version 4.93.2
    • lsscsi: version 0.31
    • lvm2: version 2.03.09
    • lz4: version 1.9.1
    • lzip: version 1.21
    • lzo: version 2.10
    • mc: version 4.8.24
    • miniupnpc: version 2.1
    • mpfr: version 4.0.2
    • nano: version 4.9.3
    • ncompress: version 4.2.4.6
    • ncurses: version 6.2
    • net-tools: version 20181103_0eebece
    • nettle: version 3.6
    • network-scripts: version 15.0 build 9
    • nfs-utils: version 2.1.1
    • nghttp2: version 1.41.0
    • nginx: version 1.16.1
    • nodejs: version 13.12.0
    • nss-mdns: version 0.14.1
    • ntfs-3g: version 2017.3.23
    • ntp: version 4.2.8p14
    • numactl: version 2.0.11
    • oniguruma: version 6.9.1
    • openldap-client: version 2.4.49
    • openssh: version 8.3p1
    • openssl-solibs: version 1.1.1g
    • openssl: version 1.1.1g
    • p11-kit: version 0.23.20
    • patch: version 2.7.6
    • pciutils: version 3.7.0
    • pcre2: version 10.35
    • pcre: version 8.44
    • php: version 7.4.7 (CVE-2019-11048)
    • pixman: version 0.40.0
    • pkgtools: version 15.0 build 33
    • pm-utils: version 1.4.1
    • procps-ng: version 3.3.16
    • pv: version 1.6.6
    • qemu: version 5.0.0
    • qrencode: version 4.0.2
    • reiserfsprogs: version 3.6.27
    • rpcbind: version 1.2.5
    • rsync: version 3.1.3
    • rsyslog: version 8.2002.0
    • samba: version 4.12.3 (CVE-2020-10700, CVE-2020-10704)
    • sdparm: version 1.11
    • sed: version 4.8
    • sg3_utils: version 1.45
    • shadow: version 4.8.1
    • shared-mime-info: version 2.0
    • smartmontools: version 7.1
    • spice: version 0.14.1
    • sqlite: version 3.32.2
    • ssmtp: version 2.64
    • sudo: version 1.9.0
    • sysfsutils: version 2.1.0
    • sysvinit-scripts: version 2.1 build 31
    • sysvinit: version 2.96
    • talloc: version 2.3.1
    • tar: version 1.32
    • tcp_wrappers: version 7.6
    • tdb: version 1.4.3
    • telnet: version 0.17
    • tevent: version 0.10.2
    • traceroute: version 2.1.0
    • tree: version 1.8.0
    • ttyd: version 20200606
    • usbredir: version 0.7.1
    • usbutils: version 012
    • utempter: version 1.2.0
    • util-linux: version 2.35.2
    • vbetool: version 1.2.2
    • vsftpd: version 3.0.3
    • wget: version 1.20.3
    • which: version 2.21
    • wireguard-tools: version 1.0.20200513
    • wsdd: version 20180618
    • xfsprogs: version 5.6.0
    • xkeyboard-config: version 2.30
    • xorg-server: version 1.20.8
    • xterm: version 356
    • xz: version 5.2.5
    • yajl: version 2.1.0
    • zlib: version 1.2.11
    • zstd: version 1.4.5

    Linux kernel:

    • version 5.7.2
    • CONFIG_WIREGUARD: WireGuard secure network tunnel
    • CONFIG_IP_SET: IP set support
    • CONFIG_SENSORS_DRIVETEMP: Hard disk drives with temperature sensors
    • enabled additional hwmon native drivers
    • enabled additional hyperv drivers
    • firmware added:
    • BCM20702A1-0b05-180a.hcd
    • out-of-tree driver status:
    • igb: using in-tree version
    • ixgbe: using in-tree version
    • r8125: using in-tree version
    • r750: (removed)
    • rr3740a: (removed)
    • tn40xx: (removed)

    Management:

    • AFP support removed
    • Multiple pool support added
    • Multi-language support added
    • avoid sending spinup/spindown to non-rotational devices
    • get rid of 'system' plugin support (never used)
    • integrate PAM
    • integrate ljm42 vfio-pci script changes
    • webgui: turn off username autocomplete in login form
    • webgui: Added new display setting: show normalized or raw device identifiers
    • webgui: Add 'Portuguese (pt)' key map option for libvirt
    • webgui: Added "safe mode" one-shot safemode reboot option
    • webgui: Tabbed case select window
    • webgui: Updated case icons
    • webgui: Show message when too many files for browsing
    • webgui: Main page: hide Move button when user shares are not enabled
    • webgui: VMs: change default network model to virtio-net
    • webgui: Allow duplicate containers different icons
    • webgui: Allow markdown within container descriptions
    • webgui: Fix Banner Warnings Not Dismissing without reload of page
    • webgui: Network: allow metric value of zero to set no default gateway
    • webgui: Network: fix privacy extensions not set
    • webgui: Network settings: show first DNSv6 server
    • webgui: SysDevs overhaul with vfio-pci.cfg binding
    • webgui: Icon buttons re-arrangement
    • webgui: Add update dialog to docker context menu
    • webgui: Update Feedback.php
    • webgui: Use update image dialog for update entry in docker context menu
    • webgui: Task Plugins: Providing Ability to define Display_Name

    Edited by limetech

    • Like 23
    • Thanks 7


    User Feedback

    Recommended Comments



    Also, I have always assumed this is broken and not specific to me - so raising it here as it's probably a good time to do so, but could be wrong.  Specifically:

     

    I assume there should not be 'no balance found' on BTRFS, and running the balance via either the GUI or the console does not change this.  We've had issues before where two BTRFS devices did not actually create a redundant RAID-1 equivalent, (which was noted in changelog as fixed) but I still find it hard to trust it's working properly if there's no balance found.

     

    I also assume the 'no stats available' should be populated with something, but it isn't.

     

    Something to fix?  Or something I don't understand?

     

    363635198_ScreenShot2020-06-19at17_48_58.thumb.png.bb7decfddc65c358e646905ee3d24ae3.png

    Share this comment


    Link to comment
    Share on other sites
    32 minutes ago, Marshalleq said:

    Also, I have always assumed this is broken and not specific to me - so raising it here as it's probably a good time to do so, but could be wrong.  Specifically:

     

    I assume there should not be 'no balance found' on BTRFS

    Wording has always been a little misleading, it means there is no balance job running

    Share this comment


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

    Wording has always been a little misleading, it means there is no balance job running

    Yes it is, it's not "broken", it's just displaying what btrfs outputs for "btrfs balance status /mountpoint", and that's the output when no balace is running.

    • Like 1

    Share this comment


    Link to comment
    Share on other sites
    2 hours ago, Marshalleq said:

    I've got a triple FAN water cooler on it

    Please tell me it's not a Enermax Liqtech TR4 360 AIO

    • Haha 1

    Share this comment


    Link to comment
    Share on other sites

    Is the AMD onboard audio/usb controller flr patch included in this beta for x570 motherboards? Will it be included in a future beta if it isn't? Currently, if on board audio is passed through to a VM on 6.8.3 w/ a non patched kernel Unraid will experience a full system crash.

    Edited by lzrdking71
    • Like 3

    Share this comment


    Link to comment
    Share on other sites
    2 hours ago, lzrdking71 said:

    Is the AMD onboard audio/usb controller flr patch included in this beta for x570 motherboards? Will it be included in a future beta if it isn't? Currently, if on board audio is passed through to a VM on 6.8.3 w/ a non patched kernel Unraid will experience a full system crash.

    Got link?

    Share this comment


    Link to comment
    Share on other sites
    13 hours ago, tjb_altf4 said:

    Wording has always been a little misleading, it means there is no balance job running

    Thanks for pointing that out - and now that you mention it, I've seen that!  Perhaps since we're in beta we can convince @limetech to consider naming it something slightly more specific such as balance status, or somehow surpessing it if inactive.  I can see that might not be particularly easy though.  I assume the 'no stats available' under scrub status is a similar issue.

    Edited by Marshalleq

    Share this comment


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

    Please tell me it's not a Enermax Liqtech TR4 360 AIO

    I've been googling this one to see what the joke is - please share!

     

    No, it's a Corsair H110i v2 - which did / does get pretty great reviews. 

    Share this comment


    Link to comment
    Share on other sites
    3 hours ago, lzrdking71 said:

    Link talking about the patch:

    Took a while but found the patches submitted upstream for kernel 5.8:

     

    https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?id=0d14f06cd6657ba3446a5eb780672da487b068e7

    and

    https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?id=5727043c73fdfe04597971b5f3f4850d879c1f4f

     

    These patches will not work against 5.7 (or earlier) kernels as-is because the file they patch has several other changes.

     

    However I see what they're doing and adding this to our 5.7 kernel is pretty easy BUT how crucial is it add this now?  Meaning, from your forum link people have added several other patches besides this set - have to say, not much time to analyze all those as well.  If this set of patches by itself will be useful to a alot of folks we can do it, otherwise I'd say wait until 5.8 kernel is released.

     

    • Like 1

    Share this comment


    Link to comment
    Share on other sites
    41 minutes ago, limetech said:

    Took a while but found the patches submitted upstream for kernel 5.8:

     

    https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?id=0d14f06cd6657ba3446a5eb780672da487b068e7

    and

    https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/commit/?id=5727043c73fdfe04597971b5f3f4850d879c1f4f

     

    These patches will not work against 5.7 (or earlier) kernels as-is because the file they patch has several other changes.

     

    However I see what they're doing and adding this to our 5.7 kernel is pretty easy BUT how crucial is it add this now?  Meaning, from your forum link people have added several other patches besides this set - have to say, not much time to analyze all those as well.  If this set of patches by itself will be useful to a alot of folks we can do it, otherwise I'd say wait until 5.8 kernel is released.

     

    I appreciate you looking into it so quickly (really wow), it looks like that first reddit post I linked was updated just today to reflect those upstream changes to 5.8. I personally work around it currently by passing through a usb headset to the VM for sound because I didn't feel comfortable running a custom kernel even though it looks like many have with success. It isn't ideal but it works. I am sure there are a lot of people who would find these patches useful with the popularity of the new Ryzen processors and X570 motherboards. Thank you for your time.

    • Like 2

    Share this comment


    Link to comment
    Share on other sites
    On 6/18/2020 at 10:22 AM, tr0910 said:

    So the new multi-cache pool nibbles away at UD territory.  Is the plan to continue this direction rather than include UD as part of native unRaid as was originally mentioned several years ago?

    The pool feature removes from UD the one thing that always belonged in Unraid itself.  The other features of UD are more of what UD was designed to do - mount disks for temporary use i.e. backups, mount remote shares, and ISO images.  I can't speak for LT, but there really is no reason now to add UD to Unraid.  It just adds complication to Unraid and additonal support issues for LT that keeps them from concentrating on more important things.

    Share this comment


    Link to comment
    Share on other sites

    Thanks @dlandon.  I love UD and had used it to mount VM's on a UD SSD.  Having multiple cache pools now, I can leave UD for my temporary disks rather than using it for mission critical VM use.  Still UD never broke on me. 

     

    Thanks for your support, and especially your adding encryption support to UD.  Some day it would be nice to have multiple encryption key support so we could mount a disk with UD that had a different encryption key than the current array.

    Share this comment


    Link to comment
    Share on other sites
    15 minutes ago, tr0910 said:

    Some day it would be nice to have multiple encryption key support so we could mount a disk with UD that had a different encryption key than the current array.

    That feature is already there.  Look at the UD settings.  You can set a per disk password.

    • Like 1

    Share this comment


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

    If this set of patches by itself will be useful to a alot of folks we can do it, otherwise I'd say wait until 5.8 kernel is released.

    Is 5.8 planned for another point release or are you guys thinking it could be a drop-in during the 6.9.0RC?  Not sure if .0 is planned to go stable before Aug/Sept.

    Share this comment


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

    I appreciate you looking into it so quickly (really wow), it looks like that first reddit post I linked was updated just today to reflect those upstream changes to 5.8. I personally work around it currently by passing through a usb headset to the VM for sound because I didn't feel comfortable running a custom kernel even though it looks like many have with success. It isn't ideal but it works. I am sure there are a lot of people who would find these patches useful with the popularity of the new Ryzen processors and X570 motherboards. Thank you for your time.

    Same for me, using x570 auros master and it is a pity i cant use the onboard sound as passthrough and im really not comfortable with running a custom kernel.

    i was hoping for unraid 6.9 to be the version that could unleash the power of my new ryzen system, without the need for custom kernels

    • Like 2

    Share this comment


    Link to comment
    Share on other sites
    cobhc

    Posted (edited)

    Really hoping that the 5.8 kernel makes it into a release not too far down the line. As I understand it, the combination of the GPU reset patches which were submitted for 5.8 alongside the team working on amdgpu driver support should hopefully fix the Navi reset issue without a custom kernel being required.

    Edited by cobhc
    • Like 2

    Share this comment


    Link to comment
    Share on other sites
    19 minutes ago, cobhc said:

    Really hoping that the 5.8 kernel makes it into a release not too far down the line

    Kernel 5.8 is expected in second half of August, history has also shown not to jump immediately on a new kernel (better wait a couple of revisions to iron out regression errors)

     

    Share this comment


    Link to comment
    Share on other sites
    bastl

    Posted (edited)

    12 hours ago, Marshalleq said:

    I've been googling this one to see what the joke is - please share!

    It was the "best performing" AIO special made for first gen Threadrippers. And indeed it performed really well for 3-4 months. During the time of use lots of people reported something growing in their rads what ended in a failing cooling solution. I had 2 of them. One of the first gen, dead after 4 months and a RMA unit V2 version dead after 5 months.

     

    https://www.youtube.com/watch?v=nttKqzQiZEo

     

    If you search you will find lots of videos and forum threads of broken devices like in this video.

    Edited by bastl
    • Like 1

    Share this comment


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

    Kernel 5.8 is expected in second half of August, history has also shown not to jump immediately on a new kernel (better wait a couple of revisions to iron out regression errors)

     

    I understand that, I more meant that I hope that there isn't too many issues encountered to be able to move to 5.8 relatively swiftly.

    Share this comment


    Link to comment
    Share on other sites

    hi, may someone else came accross stopping the array and it hangs

     

    i tried to install a macinabox install for some purpose, so docker created etc ... 

     

    now, when i hit stop array, mashine stays very long at

     

    image.png.a4c6d9ef2f8891f684974027bb265160.png

     

    looks like unmounting a UD disk takes very long, also UD shares etc, log attached

    alsserver-syslog-20200620-0909.zip

    Share this comment


    Link to comment
    Share on other sites

    I'm not really understanding the new Cache Pool feature.

     

    User Shares set to Cache Only are now showing as All Files Protected in the Shares tab.

    I only have the 1 cache drive. Are cache shares now part of parity? 

     

    When you go down to Disk Shares it is still showing the whole drive is unprotected.

    Capture.PNG

    • Thanks 1

    Share this comment


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

    That feature is already there.  Look at the UD settings.  You can set a per disk password.

    Awesome.  My apologies for missing this.  Just to confirm, this only works with typed passwords, not a keyfile correct?

    Share this comment


    Link to comment
    Share on other sites
    24 minutes ago, tr0910 said:

    Awesome.  My apologies for missing this.  Just to confirm, this only works with typed passwords, not a keyfile correct?

    Yes.  But you can use the array keyfile, just not one specific to the disk.

    Share this comment


    Link to comment
    Share on other sites
    16 hours ago, Dephcon said:

    Is 5.8 planned for another point release or are you guys thinking it could be a drop-in during the 6.9.0RC?  Not sure if .0 is planned to go stable before Aug/Sept.

    If it is that far out then some time before the 5.8 kernel is included into Unraid, I would think adding the patches that prevent a Unraid system crash to the 5.7 kernel would be a really good thing. I wasn’t aware of the issue or workaround until creating and starting the vm and experiencing the crash which I am sure is and will be the case with many current and future Unraid users.  

    Edited by lzrdking71

    Share this comment


    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.