• Unraid OS version 6.7.0-rc1 available


    limetech

    New in Unraid OS 6.7 release:

     

    New Dashboard layout, along with new Settings and Tools icons.  Designed by user @Mex and implemented in collaboration with @bonienl.  We think you will find this is a big step forward.

     

    Time Machine support via SMB.  To enable this feature it is necessary to first turn on Enhanced OS X interoperability on the Settings/SMB page.  Next, select a share to Export for Time Machine in the share SMB Security Settings section.  AFP support is deprecated.

     

    Linux kernel 4.19.  This is the latest Long Term Support kernel.  We will go with this for a while but anticipate
    updating to 4.20 or even 5.0 for Unraid 6.7.0 stable.  Here are some other kernel-related updates:

    • Added TCP "BBR Congestion control" and made it the default.  This should improve network throughput but probably not too many users will notice anything different.
    • Added Bluetooth support in the Linux kernel.  We did not add the user-space tools so this will be mostly useful to support Bluetooth in docker containers.
    • AMD firmware update for Threadripper.

     

    Ignore case in validating user share names.  If there are multiple top-level directories which differ only in case, then we use the first such share name encountered, checking in order: cache, disk1, disk2, ..., diskN.  Additional top-level directories encountered will be ignored.  For example, suppose we have:

    /mnt/cache/ashare
    /mnt/disk1/Ashare
    /mnt/disk2/ashare

    The name of the exported share will be 'ashare' and will consist of a union of /mnt/cache/ashare and /mnt/disk2/ashare.  The contents of /mnt/disk1/Ashare will not show up in /mnt/user/ashare.

     

    If you then delete the contents of /mnt/user/ashare followed by deleting the 'ashare' share itself, this will result in share 'Ashare' becoming visible.  Similar, if you delete the contents of /mnt/cache/ashare (or gets moved), then you will now see share 'Ashare' appear, and it will look like the contents of 'ashare' are missing!  Thankfully very few (if any) users should be affected by this, but handles a corner case in both the presentation of shares in windows networking and storage of share config data on the USB flash boot device.

     

    New vfio-bind method.  Since it appears that the xen-pciback/pciback kernel options no longer work, we introduced an alternate method of binding, by ID, selected PCI devices to the vfio-pci driver. This is accomplished by specifying the PCI ID(s) of devices to bind to vfio-pci in the file 'config/vfio-pci.cfg' on the USB flash boot device.  This file should contain a single line that defines the devices:

    BIND=<device> <device> ...

    Where <device> is a Domain:Bus:Device.Function string, for example,

    BIND=02:00.0

    Multiple device should be separated with spaces.

     

    The script /usr/local/sbin/vfio-pci is called very early in system start-up, right after the USB flash boot device is
    mounted but before any kernel modules (drivers) have been loaded.  The function of the script is to bind each specified device to the vfio-pci driver, which makes them available for assignment to a virtual machine, and also prevents the Linux kernel from automatically binding them to any present host driver.

     

    In addition, and importantly, this script will bind not only the specified device(s), but all other devices in the same IOMMU group as well.  For example, suppose there is an NVIDIA GPU which defines both a VGA device at 02:00.0 and an audio device at 02.00.1.  Specifying a single device (either one) on the BIND line is sufficient to bind both device to vfio-pci.  The implication is that either all devices of an IOMMU group are bound to vfio-pci or none of them are.

     

    Added 'telegram' notification agent support - thank you @realies

     

    Finally, we updated several base packages, including move to Samba 4.9 and docker 18.09, and fixed a number of minor bugs.

     

    Version 6.7.0-rc1 2019-01-21

    Base distro:

    • aaa_elflibs: version 15.0 (rev 3)
    • acpid: version 2.0.31
    • adwaita-icon-theme: version 3.30.1
    • at: version 3.1.23
    • at-spi2-atk: version 2.30.0
    • at-spi2-core: version 2.30.0
    • atk: version 2.30.0
    • bin: version 11.1 (rev 3)
    • bluez: version 4.101
    • bluez firmware: version 1.2
    • bridge-utils: version 1.6
    • btrfs-progs: version v4.19.1
    • ca-certificates: version 20181210
    • cairo: version 1.16.0
    • cifs-utils: version 6.8
    • coreutils: version 8.30 (rev 4)
    • curl: version 7.63.0
    • cyrus-sasl: version 2.1.27
    • dbus: version 1.12.12
    • dhcpcd: version 7.0.8
    • diffutils: version 3.7
    • dmidecode: version 3.2
    • dnsmasq: version 2.80
    • docker: version 18.09.1
    • e2fsprogs: version 1.44.5
    • etc: version 15.0 (rev 9)
    • ethtool: version 4.19
    • file: version 5.35
    • findutils: version 4.6.0
    • fribidi: version 1.0.5
    • gdbm: version 1.18.1
    • gdk-pixbuf2: version 2.38.0
    • git: version 2.20.1
    • glibc-zoneinfo: version 2018g
    • glib2: version 2.58.2
    • gnutls: version 3.6.5 (CVE-2018-16868)
    • gptfdisk: version 1.0.4
    • graphite2: version 1.3.13
    • grep: version 3.3
    • gtk+3: version 3.24.2
    • gzip: version 1.10
    • harfbuzz: version 2.3.0
    • haveged: version 1.9.4
    • hdparm: version 9.58
    • hostname: version 3.21
    • hwloc: version 1.11.11
    • icu4c: version 63.1
    • inotify-tools: version 3.20.1
    • intel-microcode: version 20180807a
    • iproute2: version 4.19.0
    • iptables: version 1.8.2
    • iputils: version s20180629
    • irqbalance: version 1.5.0
    • jansson: version 2.12
    • kernel-firmware: version 20181218_0f22c85
    • keyutils: version 1.6
    • libSM: version 1.2.3
    • libX11: version 1.6.7
    • libarchive: version 3.3.3
    • libcap-ng: version 0.7.9
    • libdrm: version 2.4.96
    • libedit: version 20181209_3.1
    • libepoxy: version 1.5.3
    • libestr: version 0.1.11
    • libevdev: version 1.6.0
    • libgcrypt: version 1.8.4
    • libgpg-error: version 1.33
    • libjpeg-turbo: version 2.0.1
    • libnftnl: version 1.1.2
    • libpcap: version 1.9.0
    • libpng: version 1.6.36
    • libpsl: version 0.20.2
    • libpthread-stubs: version 0.4 (rev 3)
    • librsvg: version 2.44.11
    • libtirpc: version 1.1.4
    • libvirt: version 4.10.0
    • libwebp: version 1.0.1
    • libxcb: version 1.13.1
    • lm_sensors: version 3.5.0
    • logrotate: version 3.15.0
    • lvm2: version 2.03.02
    • lzip: version 1.20
    • lz4: version 1.8.3
    • mc: version 4.8.22
    • mesa: version 18.3.0
    • miniupnpc version: 2.1
    • nano: version 3.2
    • ncurses: version 6.1_20181110
    • netatalk: version 3.1.12 (CVE-2018-1160)
    • nettle: version 3.4.1 (CVE-2018-16869)
    • nghttp2: version 1.35.1
    • nginx: version 1.14.2 (+ nchan 1.2.3) (CVE-2018-16843, CVE-2018-16844, CVE-2018-16845)
    • ntp: version 4.2.8p12 (rev 5)
    • openldap-client: version 2.4.47
    • pciutils: version 3.6.2
    • perc2: version 10.32
    • php: version 7.2.13
    • pixman: version 0.36.0
    • pkgtools: version 15.0 (rev 23)
    • pv: version 1.6.6
    • qemu: version 3.1.0
    • rpcbind: version 1.2.5
    • rsyslog: version 8.40.0
    • samba: version 4.9.4 (CVE-2018-14629, CVE-2018-16841, CVE-2018-16851, CVE-2018-16852, CVE-2018-16853, CVE-2018-16857)
    • sed: version 4.7
    • shadow: version 4.6
    • shared-mime-info: version 1.10
    • smartmontools: version 7.0
    • spice: version 0.14.1
    • spice-protocol: version 0.12.14
    • sqlite: version 3.26.0
    • sudo: version 1.8.26
    • sysvinit-scripts: version 2.1 (rev 24)
    • sysvinit: version 2.93
    • tar: version 1.30 (rev 3)
    • tree: version 1.8.0
    • ttyd: version 1.4.2
    • util-linux: version 2.33
    • wget: version 1.20
    • xauth: version 1.0.10 (rev 3)
    • xfsprogs: version 4.19.0
    • wget: version 1.20.1
    • xkeyboard-config: version 2.25
    • xterm: version 341
    • zstd: version 1.3.8

    Linux kernel:

    • version: 4.19.16
    • OOT Intel 10Gbps network driver: ixgbe: version 5.5.3
    • OOT Tehuti 10Gbps network driver: tn40xx: version 0.3.6.17
    • added drivers:
    • CONFIG_USB_SERIAL_CH341: USB Winchiphead CH341 Single Port Serial Driver
    • added TCP BBR congestion control kernel support and set as default:
    • CONFIG_NET_KEY: PF_KEY sockets
    • CONFIG_TCP_CONG_BBR: BBR TCP
    • CONFIG_NET_SCH_FQ: Fair Queue
    • CONFIG_NET_SCH_FQ_CODEL: Fair Queue Controlled Delay AQM (FQ_CODEL)
    • added Bluetooth kernel support:
    • CONFIG_BT: Bluetooth subsystem support
    • CONFIG_BT_BREDR: Bluetooth Classic (BR/EDR) features
    • CONFIG_BT_RFCOMM: RFCOMM protocol support
    • CONFIG_BT_RFCOMM_TTY: RFCOMM TTY support
    • CONFIG_BT_BNEP: BNEP protocol support
    • CONFIG_BT_BNEP_MC_FILTER: Multicast filter support
    • CONFIG_BT_BNEP_PROTO_FILTER: Protocol filter support
    • CONFIG_BT_HIDP: HIDP protocol support
    • CONFIG_BT_HS: Bluetooth High Speed (HS) features
    • CONFIG_BT_LE: Bluetooth Low Energy (LE) features
    • CONFIG_BT_HCIBTUSB: HCI USB driver
    • CONFIG_BT_HCIBTUSB_AUTOSUSPEND: Enable USB autosuspend for Bluetooth USB devices by default
    • CONFIG_BT_HCIBTUSB_BCM: Broadcom protocol support
    • CONFIG_BT_HCIBTUSB_RTL: Realtek protocol support
    • CONFIG_BT_HCIUART: HCI UART driver
    • CONFIG_BT_HCIUART_H4: UART (H4) protocol support
    • CONFIG_BT_HCIUART_BCSP: BCSP protocol support
    • CONFIG_BT_HCIUART_ATH3K: Atheros AR300x serial support
    • CONFIG_BT_HCIUART_AG6XX: Intel AG6XX protocol support
    • CONFIG_BT_HCIUART_MRVL: Marvell protocol support
    • CONFIG_BT_HCIBCM203X: HCI BCM203x USB driver
    • CONFIG_BT_HCIBPA10X: HCI BPA10x USB driver
    • CONFIG_BT_HCIVHCI: HCI VHCI (Virtual HCI device) driver
    • CONFIG_BT_MRVL: Marvell Bluetooth driver support
    • CONFIG_BT_ATH3K: Atheros firmware download driver
    • md/unraid: version 2.9.5 (kernel BUG if read phase of read/modify/write with FUA flag set fails on stripe with multiple read failures)
    • patch: PCI: Quirk Silicon Motion SM2262 NVMe controller reset
    • patch: support Mozart 395S chip

    Management:

    • add early vfio-bind utility
    • fix: docker log rotation
    • fix: inconsistent share name case
    • fix: terminal instances limited to 8 (now lifted)
    • restore PHP E_WARNING in /etc/php/php.ini
    • support Apple Time Machine via SMB
    • update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt}
    • webgui: New icon reference
    • webgui: Added new font icons
    • webgui: added new case icons
    • webgui: Revamped dashboard page
    • webgui: Replaced orb png icons by font-awesome
    • webgui: Position context menu always left + below icon
    • webgui: Do not capitalize path names in title of themes Azure and Gray
    • webgui: Allow plugins to use font awesome for icon
    • webgui: sort notification agents alphabetically, add telegram notifications
    • webgui: Dashboard: use disk thresholds for utlization bars
    • webgui: VM manager: remove and rebuild USB controllers
    • webgui: Fixed: slots selection always disabled after "New Config"
    • webgui: Fix Background color when installing container
    • webgui: Fixed share/disk size calculation when names include space
    • webgui: Add log-size and log-file options to docker run command
    • webgui: Escape quotes on a containers template
    • webgui: Prevent update notification if plugin is not compatible
    • webgui: other GUI enhancements

    Edited by limetech

    • Like 5
    • Upvote 6



    User Feedback

    Recommended Comments



    36 minutes ago, zoggy said:

    any way to make to change that on the dashboard from 'warning'+'error' to just 'error' ?

    made me think oh crap something bad.. but no I just have a few drives over 70% because of split folders

    You can set the thresholds for all disks in Disk Settings and override that threshold for a particular disk by clicking on the disk in Main to get to its page. This feature has been there for a very long time.

    Link to comment
    1 hour ago, Stef-dk said:

     

    Network Type: from HOST to Brigde

    INTERFACE:  from BOND0 to ETH0

    Hopes this helps somebody :)

     

    Updated two servers and no issues except no Open-VPN connection on one of the servers. I changed the Open-VPN network type from HOST to Bridge and I already have interface set to ETH0. The fix suggested by Stef-dk works. Thanks!

     

    Awesome new dashboard!! Great job guys!

    Edited by SCSI
    • Like 1
    Link to comment
    5 minutes ago, bonienl said:

    Sorry, it is not clear to me what you like to see.

    right now the dashboard shows anything over warning level. I want to only show critical.

    Link to comment
    2 minutes ago, zoggy said:

    right now the dashboard shows anything over warning level. I want to only show critical.

    Just set the warning as high as you want as I explained above.

    Link to comment

    @trurl I'm well aware of changing thresholds. But I do not want to make the warning match the critical to solve the dashboard gui. This will cause negative effects for notifications and other places.

    Edited by zoggy
    Link to comment
    5 hours ago, Jerky_san said:

    The UPS plugin on the dashboard no longer shows the wattage consumption only % load. It would be nice if it could still show that. 

    I had the same issue using the NUT plugin. I fixed it by uninstalling and reinstalling the NUT plugin. I now have the UPS watt usage display on the dashboard.

    Edited by MisterWolfe
    added words
    Link to comment
    Just now, zoggy said:

    I'm well aware of changing thresholds. But I do not want to make the warning match the critical to solve the dashboard gui. This will cause negative effects for notifications and other places. Your solution is not welcomed.

    May I suggest you add a feature request for this? With the details about what you would like. 

     

    I try my best to design a system that works for most people, but I admit I don't know every use case/situation and this is a piece of software that is used in a huge number of ways, with loads of different configurations.

     

    Link to comment
    18 minutes ago, zoggy said:

    right now the dashboard shows anything over warning level. I want to only show critical.

    set warning level to zero and it is disabled

    Link to comment
    39 minutes ago, MisterWolfe said:

    I had the same issue using the NUT plugin. I fixed it by uninstalling and reinstalling the NUT plugin. I now have the UPS watt usage display on the dashboard.

    I think i am just using the stock ups thing that comes with unraid.

    Link to comment
    5 minutes ago, Jerky_san said:

    I think i am just using the stock ups thing that comes with unraid.

    Can you post a screenshot of the dashboard page

    Edited by bonienl
    Link to comment

    Updated to 6.7RC1.  Nerd tools and Dev Pack both stuck at "receiving plugin information."  Anyone else experience this?  Otherwise works well and looks great.

    Edited by Woodpusherghd
    Link to comment
    12 minutes ago, bonienl said:

    Can you post a screenshot of the dashboard page

    While I am not @Jerky_san, This is what I see on the Dashboard:

     

    Capture.JPG.6f32fea0948cd9470a275e8f86d11365.JPG

     

    While I know I can grab my calculator to do the simple multiplication, I can't believe anyone is truly interested in knowing the percentage load.   

    Link to comment

    It should give the UPS load both in percentage and wattage, e.g.

     

    UPS load: 14.0 % (200 W)

     

    I'll try to figure out why it isn't working, may need your help for testing (I don't have a UPS myself)

    Link to comment
    24 minutes ago, Woodpusherghd said:

    Updated to 6.7RC1.  Nerd tools and Dev Pack both stuck at "receiving plugin information."  Anyone else experience this?  Otherwise works well and looks great.

    Yes i have seen the same with Nerd Tools and also SNMP plugin doesnt work

    Link to comment
    9 minutes ago, bonienl said:

    It should give the UPS load both in percentage and wattage, e.g.

     

    UPS load: 14.0 % (200 W)

     

    I'll try to figure out why it isn't working, may need your help for testing (I don't have a UPS myself)

    this sounds ideal.  I'm happy to help test too.

    Link to comment
    26 minutes ago, bonienl said:

    It should give the UPS load both in percentage and wattage, e.g.

     

    UPS load: 14.0 % (200 W)

     

    I'll try to figure out why it isn't working, may need your help for testing (I don't have a UPS myself)

     

    thats shocking to hear... figured everyone would be using an UPS on their nas in this day and age

     

    Link to comment

    My install has been booting just fine, and then I upgraded to 6.7.0-rc1 from 6.6.6 and am getting the following when I try to boot from any of my options:

     

    Loading /bzimage... ok

    Loading /bzroot... ok

    Loading /bzroot-gui... ok

    exit_boot() failed!

    efi_main() failed!

     

    I have moved my vfio-pci arguments over to the new config file, but other than that, I haven't touched anything since the last reboot. I'm on UEFI. Any ideas? I'm going to go remove that config file and see if that helps any.

     

    EDIT: It didn't change anything. Also, my syslinux.cfg file entry is as follows:

     

    label unRAID...

    kernel /bzimage

    append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui

    Edited by bamhm182
    Link to comment

    Since the upgrade I'm randomly getting these BTRFS errors.

     

    Downgraded to 6.6.6, errors are gone, upgrade back to 6.7.0rc1, errors return.

     

     

    Capture.PNG

    Link to comment
    8 hours ago, Jerky_san said:

    Yeah I tried a lot of different things.. It doesn't make sense though as the topology fixes were technically in 3.0 so don't understand why I can't let it pass through and instead have to emulate an EPYC which does show the proper topology.

    looks like we're waiting for QEMU 4.0.... https://wiki.qemu.org/Planning/4.0
    I dont think the unraid guys compile from source, they'll just grab the latest stable version... which is currently 3.1 :(

     

    The commits im interested in got pushed after the 3.1 release now ive cross referenced all the dates! :(

     

    @jonpIs there any way we could get a 'bleeding edge' build of QEMU built from the master git branch in the next rc maybe? Being able to test threadripper and PCIe root port lane size fixes would be great :). Looking at the current schedule for 4.0, it looks like we'll be waiting a few months before the next official release.... 

     

     

    Link to comment
    12 minutes ago, Outcasst said:

    Since the upgrade I'm randomly getting these BTRFS errors.

     

    Downgraded to 6.6.6, errors are gone, upgrade back to 6.7.0rc1, errors return.

     

     

    Capture.PNG

    Please open a bug report for this along with posting diagnostics.zip

    Link to comment
    1 hour ago, bonienl said:

    It should give the UPS load both in percentage and wattage, e.g.

     

    UPS load: 14.0 % (200 W)

     

    I'll try to figure out why it isn't working, may need your help for testing (I don't have a UPS myself)

    backend returns:

    <tr><td class='green-text'>Online</td><td class='green-text'>100.0 Percent</td><td class='green-text'>61.9 Minutes</td><td class='green-text'>865 Watts</td><td class='green-text'>86 Watts</td><td class='green-text'>10.0 Percent</td></tr>

     

    which webgui parses:

        $('#ups_loadpct').html(data[5]+(data[5].search('-')==-1 ? '%':'')+(data[4].search('-')==-1 ? ' ('+data[4].replace(' Watts','W')+')':''));

    but as you can see from my sample data there is no '-' in it.

    if I replace that line to just do data[5] + data[4] then it appears just fine.

     

    in case you need it:

    # /sbin/apcaccess | egrep "STATUS|BCHARGE|TIMELEFT|NOMPOWER|LOADPCT"
    STATUS   : ONLINE 
    LOADPCT  : 9.0 Percent
    BCHARGE  : 100.0 Percent
    TIMELEFT : 61.9 Minutes
    NOMPOWER : 865 Watts
    

     

    Edited by zoggy
    Link to comment
    46 minutes ago, Outcasst said:

    Since the upgrade I'm randomly getting these BTRFS errors.

     

    Downgraded to 6.6.6, errors are gone, upgrade back to 6.7.0rc1, errors return.

     

     

    Capture.PNG

    As am I

     

    Jan 22 15:49:32 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 16, flush 0, corrupt 0, gen 0
    Jan 22 15:49:43 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 17, flush 0, corrupt 0, gen 0
    Jan 22 15:50:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 15:50:33 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 18, flush 0, corrupt 0, gen 0
    Jan 22 15:50:41 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 19, flush 0, corrupt 0, gen 0
    Jan 22 15:50:46 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 20, flush 0, corrupt 0, gen 0
    Jan 22 15:51:00 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 21, flush 0, corrupt 0, gen 0
    Jan 22 15:51:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 15:51:21 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 22, flush 0, corrupt 0, gen 0
    Jan 22 15:52:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 15:52:23 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 23, flush 0, corrupt 0, gen 0
    Jan 22 15:52:28 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 24, flush 0, corrupt 0, gen 0
    Jan 22 15:52:28 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 25, flush 0, corrupt 0, gen 0
    Jan 22 15:52:32 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 26, flush 0, corrupt 0, gen 0
    Jan 22 15:52:34 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 27, flush 0, corrupt 0, gen 0
    Jan 22 15:52:34 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 28, flush 0, corrupt 0, gen 0
    Jan 22 15:52:39 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 29, flush 0, corrupt 0, gen 0
    Jan 22 15:52:59 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 30, flush 0, corrupt 0, gen 0
    Jan 22 15:53:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 15:53:45 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 31, flush 0, corrupt 0, gen 0
    Jan 22 15:53:45 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 32, flush 0, corrupt 0, gen 0
    Jan 22 15:53:52 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 33, flush 0, corrupt 0, gen 0
    Jan 22 15:53:52 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 34, flush 0, corrupt 0, gen 0
    Jan 22 15:54:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 15:54:11 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 35, flush 0, corrupt 0, gen 0
    Jan 22 15:54:15 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 36, flush 0, corrupt 0, gen 0
    Jan 22 15:54:26 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 37, flush 0, corrupt 0, gen 0
    Jan 22 15:54:26 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 38, flush 0, corrupt 0, gen 0
    Jan 22 15:54:31 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 39, flush 0, corrupt 0, gen 0
    Jan 22 15:54:37 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 40, flush 0, corrupt 0, gen 0
    Jan 22 15:54:39 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 41, flush 0, corrupt 0, gen 0
    Jan 22 15:55:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 15:55:29 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 42, flush 0, corrupt 0, gen 0
    Jan 22 15:55:32 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 43, flush 0, corrupt 0, gen 0
    Jan 22 15:55:48 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 44, flush 0, corrupt 0, gen 0
    Jan 22 15:55:48 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 45, flush 0, corrupt 0, gen 0
    Jan 22 15:55:54 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 46, flush 0, corrupt 0, gen 0
    Jan 22 15:55:54 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 47, flush 0, corrupt 0, gen 0
    Jan 22 15:56:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 15:56:02 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 48, flush 0, corrupt 0, gen 0
    Jan 22 15:56:19 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 49, flush 0, corrupt 0, gen 0
    Jan 22 15:56:29 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 50, flush 0, corrupt 0, gen 0
    Jan 22 15:56:29 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 51, flush 0, corrupt 0, gen 0
    Jan 22 15:56:37 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 52, flush 0, corrupt 0, gen 0
    Jan 22 15:56:37 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 53, flush 0, corrupt 0, gen 0
    Jan 22 15:56:52 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 54, flush 0, corrupt 0, gen 0
    Jan 22 15:56:57 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 55, flush 0, corrupt 0, gen 0
    Jan 22 15:57:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 15:57:19 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 56, flush 0, corrupt 0, gen 0
    Jan 22 15:58:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 15:58:05 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 57, flush 0, corrupt 0, gen 0
    Jan 22 15:58:12 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 58, flush 0, corrupt 0, gen 0
    Jan 22 15:58:12 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 59, flush 0, corrupt 0, gen 0
    Jan 22 15:58:18 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 60, flush 0, corrupt 0, gen 0
    Jan 22 15:58:18 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 61, flush 0, corrupt 0, gen 0
    Jan 22 15:58:25 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 62, flush 0, corrupt 0, gen 0
    Jan 22 15:59:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 15:59:02 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 63, flush 0, corrupt 0, gen 0
    Jan 22 16:00:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 16:00:22 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 64, flush 0, corrupt 0, gen 0
    Jan 22 16:00:44 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 65, flush 0, corrupt 0, gen 0
    Jan 22 16:00:44 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 66, flush 0, corrupt 0, gen 0
    Jan 22 16:00:53 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 67, flush 0, corrupt 0, gen 0
    Jan 22 16:01:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 16:01:43 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 68, flush 0, corrupt 0, gen 0
    Jan 22 16:01:43 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 69, flush 0, corrupt 0, gen 0
    Jan 22 16:01:49 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 70, flush 0, corrupt 0, gen 0
    Jan 22 16:02:00 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 71, flush 0, corrupt 0, gen 0
    Jan 22 16:02:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 16:02:40 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 72, flush 0, corrupt 0, gen 0
    Jan 22 16:02:40 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 73, flush 0, corrupt 0, gen 0
    Jan 22 16:02:45 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 74, flush 0, corrupt 0, gen 0
    Jan 22 16:03:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 16:03:40 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 75, flush 0, corrupt 0, gen 0
    Jan 22 16:03:45 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 76, flush 0, corrupt 0, gen 0
    Jan 22 16:03:45 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 77, flush 0, corrupt 0, gen 0
    Jan 22 16:03:47 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 78, flush 0, corrupt 0, gen 0
    Jan 22 16:03:47 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 79, flush 0, corrupt 0, gen 0
    Jan 22 16:03:54 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 80, flush 0, corrupt 0, gen 0
    Jan 22 16:04:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 16:04:09 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 81, flush 0, corrupt 0, gen 0
    Jan 22 16:04:25 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 82, flush 0, corrupt 0, gen 0
    Jan 22 16:04:25 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 83, flush 0, corrupt 0, gen 0
    Jan 22 16:05:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 16:05:25 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 84, flush 0, corrupt 0, gen 0
    Jan 22 16:05:25 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 85, flush 0, corrupt 0, gen 0
    Jan 22 16:06:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 16:07:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 16:07:43 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 86, flush 0, corrupt 0, gen 0
    Jan 22 16:07:43 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 87, flush 0, corrupt 0, gen 0
    Jan 22 16:07:46 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 88, flush 0, corrupt 0, gen 0
    Jan 22 16:07:56 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 89, flush 0, corrupt 0, gen 0
    Jan 22 16:08:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 16:08:11 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 90, flush 0, corrupt 0, gen 0
    Jan 22 16:08:21 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 91, flush 0, corrupt 0, gen 0
    Jan 22 16:08:25 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 92, flush 0, corrupt 0, gen 0
    Jan 22 16:08:32 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 93, flush 0, corrupt 0, gen 0
    Jan 22 16:08:38 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 94, flush 0, corrupt 0, gen 0
    Jan 22 16:08:38 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 95, flush 0, corrupt 0, gen 0
    Jan 22 16:08:56 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 96, flush 0, corrupt 0, gen 0
    Jan 22 16:08:56 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 97, flush 0, corrupt 0, gen 0
    Jan 22 16:09:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 16:09:05 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 98, flush 0, corrupt 0, gen 0
    Jan 22 16:09:05 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 99, flush 0, corrupt 0, gen 0
    Jan 22 16:09:07 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 100, flush 0, corrupt 0, gen 0
    Jan 22 16:10:01 Tower crond[1646]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
    Jan 22 16:10:15 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 101, flush 0, corrupt 0, gen 0
    Jan 22 16:10:15 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 102, flush 0, corrupt 0, gen 0
    Jan 22 16:10:22 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 103, flush 0, corrupt 0, gen 0
    Jan 22 16:10:31 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 104, flush 0, corrupt 0, gen 0
    Jan 22 16:10:31 Tower kernel: BTRFS error (device md6): bdev /dev/md6 errs: wr 0, rd 105, flush 0, corrupt 0, gen 0

     

    Link to comment
    1 hour ago, Outcasst said:

    Since the upgrade I'm randomly getting these BTRFS errors.

     

    Downgraded to 6.6.6, errors are gone, upgrade back to 6.7.0rc1, errors return.

     

     

    Capture.PNG

     

    I have the same issue, I can confirm.

    The files copied to the array or read cause those warnings.

    Link to comment



    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.