• Unraid OS version 6.8.0-rc4 available

    limetech

    By limetech

      • Closed

    Misc. bug fixes and more changes to try and track down source of 'SQLite DB Corruption' issue.

     

    Specific changes in [-rcN] are indicated in bold below.

     

    New in Unraid OS 6.8 release:

     

    The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device.  You will probably notice a slight difference in speed of extract messages. [-rc2] The 'sync' command at the end has been replaced with 'sync -f /boot'.

     

    Forms based authentication
    If you have set a root password for your server, upon boot you'll now see a nice login form.  There still is only one user for Unraid so for username enter root.  This form should be compatible with all major password managers out there.  We always recommend using a strong password.  [-rc2] There is no auto-logout implemented yet, please click Logout on menu bar or completely close your browser to logout.

     

    Linux kernel 5.3

    • default scheduler now 'mq-deadline' [-rc2] but this can be changed via Settings/Disk Settings/Scheduler setting.
    • enabled Huge Page support, though no UI control yet
    • binfmt_misc support
    • added "Vega 10 Reset bug" [-rc2] and 'navi-reset' patches
    • [-rc2] added oot: Realtek r8125: version 9.002.02
    • [-rc3] additional md/unraid changes and instrumentation
    • more device drivers

     

    Some out-of-tree (oot) drivers are currently omitted either because the source code doesn't compile or driver doesn't work with the 5.3 kernel:

    • Intel ixgbe [does not build] (using in-tree driver)
    • Highpoint r750 [does not work]
    • Highpoint rr3740a [does not build]

     

    This is always the risk with including vendor-supplied drivers.  Until the vendor fixes their code we must omit their driver.

     

    md/unraid driver
    Introduced "multi-stream" support:

    • Reads on devices which are not being written should run at full speed.  In addition, if you have set the md_write_method tunable to "reconstruct write", then while writing, if any read streams are detected, the write method is switched to "read/modifywrite".
    • Parity sync/check should run at full speed by default.
    • Parity sync/check is throttled back in presence of other active streams.
    • The "stripe pool" resource is automatically shared evenly between all active streams.

     

    As a result got rid of some Tunables:

    • md_sync_window
    • md_sync_thresh

    and added some tunables:

    • md_queue_limit
    • md_sync_limit
    • [-rc2] md_scheduler

     

    Please refer to Settings/Disk Settings help text for description of these settings.

     

    Remaining issue: some users have reported slower parity sync/check rates for very wide arrays (20+ devices) vs. 6.7 and earlier releases - we are still studying this problem.


    WireGuard support - available as a plugin via Community Apps.  Our WireGuard implementation and UI is still a work-in-process; for this reason we have made this available as a plugin, though the latest WireGuard module is included in our Linux kernel.  Full WireGuard implementation will be merged into Unraid OS itself in a future release.  I want to give special thanks to @bonienl who wrote the plugin with lots of guidance from @ljm42 - thank you!  I also should give a shout out to @NAS who got us rolling on this.  If you don't know about WireGuard it's something to look into!

     

    Guide here:


    WS-Discovery support - Finally you can get rid of SMBv1 and get reliable Windows network discovery.  This feature is configured on the Settings/SMB Settings page and enabled by default.

    • Also on same settings page is Enable NetBIOS setting.  This is enabled by default, however if you no longer have need for NetBIOS discovery you can turn it off.  When turned off, Samba is configured to accept only SMBv2 protocol and higher.
    • Added mDNS client support in Unraid OS.  This means, for example, from an Unraid OS terminal session to ping another Unraid OS server on your network you can use (e.g., 'tower'): 
      ping tower.local
      instead of 
      ping tower
      Note the latter will still work if you have NetBIOS enabled.

     

    User Share File System (shfs) changes:

    • Integrated FUSE-3 - This should increase performance of User Share File System somewhat.
    • Fixed bug with hard link support.  Previously a 'stat' on two directory entries referring to same file would return different i-node numbers, thus making it look like two independent files.  This has been fixed however there is a config setting on Settings/Global Share Settings called "Tunable (support hard links)".  [-rc2 ] Fixed the default value Yes, but with certain very old media and DVD players which access shares via NFS, you may need to set this to No.
    • Note: if you have custom config/extra.cfg file, get rid of it.


    Other improvements/bug fixes:

    • Format - during Format any running parity sync/check is automatically Paused and then resumed upon Format completion.
    • Encryption - an entered passphrase is not saved to any file.  Also included an API for Unassigned devices plugin to open encrypted volumes.
    • Fixed bug where multi-device btrfs pool was leaving metadata set to dup instead of raid1.
    • Several other small bug fixes and improvements.
    • Numerous base package updates [-rc2] including updating PHP to version 7.3.x, Samba to version 4.11.x.

     

    Finally - please note that AFP is now deprecated and we plan to remove in Unraid 6.9 release.

     

    Version 6.8.0-rc4 2019-10-23

    Base distro:

    • aaa_elflibs: version 15.0 build 13
    • at: version 3.2.1
    • btrfs-progs: version 5.3
    • ca-certificates: version 20191018
    • dhcpcd: version 8.1.1
    • docker: version 19.03.4
    • glib2: version 2.62.2
    • kernel-firmware: version 20191022_2b016af
    • lm_sensors: version 3.6.0
    • network-scripts: version 15.0
    • pkgtools: version 15.0
    • samba: version 4.11.1
    • shadow: version 4.7
    • sudo: version 1.8.28p1

    Linux kernel:

    • version 5.3.7
    • oot: md/unraid: version 2.9.11 (use bio_reset(), more tunables)

    Management:

    • samba: if netbios enabled, set 'server min protocol = NT1'
    • webgui: Dashboard: show titles without text-transform
    • webgui: Enable notifications by default
    • webgui: Only create session when user successfully logs in; also enable session.use_strict_mode to prevent session fixation attacks
    • webgui: Dashboard: fix WG direction arrows
    • webgui: Dashboard: adjust column width for themes azure/gray
    • webgui: Fixed popup window in foreground
    • webgui: Expanded help for Use Cache setting

     

    Version 6.8.0-rc3 2019-10-17

    Management:

    • php: set very long session timeout

     

    Version 6.8.0-rc2 2019-10-17

    Base distro:

    • aaa_elflibs: version 15.0 build 15
    • at-spi2-atk: version 2.34.1
    • binutils: version 2.33.1
    • gdk-pixbuf2: version 2.40.0
    • glib2: version 2.62.1
    • harfbuzz: version 2.6.2
    • icu4c: version 65.1
    • kernel-firmware: version 20191008_aa95e90
    • libX11: version 1.6.9
    • librsvg: version 2.46.1
    • libvirt-php: version 20190803
    • openssh: version 8.1p1
    • php: version 7.3.10
    • pkgtools: version 15.0 build 25
    • samba: version 4.11.0 (CVE-2019-10197)
    • sqlite: version 3.30.1
    • ttyd: version 20191001
    • wireguard: version 0.0.20191012
    • xfsprogs: version 5.2.1

    Linux kernel:

    • change schedulers from modules to built-ins
    • patch: navi_reset (user request)
    • oot: Realtek r8125: version 9.002.02

    Management:

    • add 'scheduler' tunable for array devices
    • fix shfs hard link initially reported as enabled but not actually enabled
    • nginx: disable php session expiration
    • unRAIDServer.plg (update OS) now executes 'sync -f /boot' instead of full sync at end of update
    • webgui: Improve Use Cache option
    • webgui: other minor text corrections
    • webgui: Dashboard: add up/down arrows to VPN tunnel traffic

     

    Version 6.8.0-rc1 2019-10-11

    Base distro:

    • aaa_elflibs: version 15.0 build 11
    • acpid: version 2.0.32
    • at-spi2-atk: version 2.34.0
    • at-spi2-core: version 2.34.0
    • atk: version 2.34.1
    • bash: version 5.0.011
    • btrfs-progs: version 5.2.2
    • bzip2: version 1.0.8
    • ca-certificates: version 20190826
    • cifs-utils: version 6.9
    • cryptsetup: version 2.2.1
    • curl: version 7.66.0
    • dbus: version 1.12.16
    • dbus-glib: version 0.110
    • dhcpcd: version 8.0.6
    • docker: version 19.03.3
    • e2fsprogs: version 1.45.4
    • encodings: version 1.0.5
    • etc: version 15.0
    • ethtool: version 5.3
    • expat: version 2.2.9
    • file: version 5.37
    • findutils: version 4.7.0
    • freetype: version 2.10.1
    • fuse3: version 3.6.2
    • gdbm: version 1.18.1
    • gdk-pixbuf2: version 2.38.2
    • git: version 2.23.0
    • glib2: version 2.62.0
    • glibc-solibs: version 2.30
    • glibc-zoneinfo: version 2019c
    • glibc: version 2.30
    • glu: version 9.0.1
    • gnutls: version 3.6.10
    • gtk+3: version 3.24.10
    • harfbuzz: version 2.6.0
    • haveged: version 1.9.8
    • hostname: version 3.22
    • hwloc: version 1.11.13
    • icu4c: version 64.2
    • intel-microcode: version 20190918
    • iproute2: version 5.3.0
    • iptables: version 1.8.3
    • iputils: version 20190709
    • irqbalance: version 1.6.0
    • less: version 551
    • libICE: version 1.0.10
    • libX11: version 1.6.8
    • libXi: version 1.7.10
    • libXt: version 1.2.0
    • libarchive: version 3.4.0
    • libcap-ng: version 0.7.10
    • libcroco: version 0.6.13
    • libdrm: version 2.4.99
    • libedit: version 20190324_3.1
    • libevdev: version 1.7.0
    • libevent: version 2.1.11
    • libgcrypt: version 1.8.5
    • libgudev: version 233
    • libjpeg-turbo: version 2.0.3
    • libnftnl: version 1.1.4
    • 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.44.14
    • libseccomp: version 2.4.1
    • libssh2: version 1.9.0
    • libtasn1: version 4.14
    • libusb: version 1.0.23
    • libvirt-php: version 0.5.5
    • libvirt: version 5.7.0 (CVE-2019-10161, CVE-2019-10166, CVE-2019-10167, CVE-2019-10168)
    • libwebp: version 1.0.3
    • libzip: version 1.5.2
    • logrotate: version 3.15.1
    • lsof: version 4.93.2
    • lsscsi: version 0.30
    • lvm2: version 2.03.05
    • lz4: version 1.9.1
    • mkfontscale: version 1.2.1
    • mozilla-firefox: version 68.0.2 (CVE-2019-11751, CVE-2019-11746, CVE-2019-11744, CVE-2019-11742, CVE-2019-11736, CVE-2019-11753, CVE-2019-11752, CVE-2019-9812, CVE-2019-11741, CVE-2019-11743, CVE-2019-11748, CVE-2019-11749, CVE-2019-5849, CVE-2019-11750, CVE-2019-11737, CVE-2019-11738, CVE-2019-11747, CVE-2019-11734, CVE-2019-11735, CVE-2019-11740, CVE-2019-11754, CVE-2019-9811, CVE-2019-11711, CVE-2019-11712, CVE-2019-11713, CVE-2019-11714, CVE-2019-11729, CVE-2019-11715, CVE-2019-11716, CVE-2019-11717, CVE-2019-1 1718, CVE-2019-11719, CVE-2019-11720, CVE-2019-11721, CVE-2019-11730, CVE-2019-11723, CVE-2019-11724, CVE-2019-11725, CVE-2019-11727, CVE-2019-11728, CVE-2019-11710, CVE-2019-11709)
    • nano: version 4.5
    • ncurses: version 6.1_20190720
    • net-tools: version 20181103_0eebece
    • nettle: version 3.5.1
    • nghttp2: version 1.39.2
    • nginx: version 1.16.1 (CVE-2019-9511, CVE-2019-9513, CVE-2019-9516)
    • nodejs: version 10.16.3
    • nss-mdns: version 0.14.1
    • ntp: version 4.2.8p13
    • openldap-client: version 2.4.48
    • openssh: version 8.0p1
    • openssl-solibs: version 1.1.1d
    • openssl: version 1.1.1d
    • p11-kit: version 0.23.18.1
    • pcre2: version 10.33
    • php: version 7.2.23 (CVE-2019-11042, CVE-2019-11041)
    • pixman: version 0.38.4
    • pkgtools: version 15.0
    • procps-ng: version 3.3.15
    • qemu: version 4.1.0 (CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091)
    • qrencode: version 4.0.2
    • rpcbind: version 1.2.5
    • rsyslog: version 8.1908.0
    • samba: version 4.10.8 (CVE-2019-10197)
    • sdparm: version 1.10
    • sessreg: version 1.1.2
    • setxkbmap: version 1.3.2
    • sg3_utils: version 1.44
    • shadow: version 4.7
    • shared-mime-info: version 1.12
    • sqlite: version 3.29.0
    • sysvinit-scripts: version 2.1
    • sysvinit: version 2.96
    • talloc: version 2.3.0
    • tdb: version 1.4.2
    • tevent: version 0.10.1
    • ttyd: version 1.5.2
    • usbutils: version 012
    • util-linux: version 2.34
    • wget: version 1.20.3
    • wireguard: version 0.0.20190913
    • wsdd: version 20180618 build 2
    • xauth: version 1.1
    • xclock: version 1.0.9
    • xfsprogs: version 5.2.1
    • xkeyboard-config: version 2.27
    • xorg-server: version 1.20.5
    • xrandr: version 1.5.1
    • xterm: version 348
    • xwininfo: version 1.1.5
    • zstd: version 1.4.3

    Linux kernel:

    • version 5.3.6
    • default scheduler now mq-deadline
    • CONFIG_BINFMT_MISC: Kernel support for MISC binaries
    • CONFIG_DEBUG_FS: Debug Filesystem
    • CONFIG_HUGETLBFS: HugeTLB file system support
    • CONFIG_ICE: Intel(R) Ethernet Connection E800 Series Support
    • CONFIG_IGC: Intel(R) Ethernet Controller I225-LM/I225-V support
    • CONFIG_MLX5_CORE_IPOIB: Mellanox 5th generation network adapters (connectX series) IPoIB offloads support
    • CONFIG_SCSI_SMARTPQI: Microsemi PQI Driver
    • CONFIG_WIREGUARD: IP: WireGuard secure network tunnel
    • patch: fix_vega_reset (user request)
    • patch: increase BLK_MAX_REQUEST_COUNT from 16 to 32
    • oot: LimeTech md/unraid: version 2.9.10 (multi-stream support)
    • oot: Highpoint rsnvme: version v1.2.16_19_05_06
    • oot: Tehuti tn40xx: version 0.3.6.17.2
    • oot: omitted: Intel ixgbe [does not build] (using in-tree driver)
    • oot: omitted: Highpoint r750 [does not work]
    • oot: omitted: Highpoint rr3740a [does not build]

    Management:

    • fix btrfs bug where converting from single to multiple pool did not balance metadata to raid1, and converting from multiple to single did not balance metadata back to single.
    • auto-mount hugetlbfs to support kernel huge pages
    • emhttpd: do not write /root/keyfile if encryption passphrase provided via webGUI
    • fstab: mount USB flash boot device with root-only access
    • nginx.conf: configure all nginx worker threads to run as 'root'.
    • start/stop WireGuard upon server start/shutdown
    • support forms-based authentication
    • shfs: support FUSE3 API changes; hard links report same st_ino; hard link support configurable
    • support disabling NetBIOS, and set Samba 'min server procotol' and 'min client protocol' to SMB2 if disabled
    • support WS-Discovery method
    • support mDNS local name resolution via avahi
    • extract OS upgrade directly to USB flash
    • webgui: Revamp Banner Warning System
    • webgui: Fix custom case png not surviving reboot
    • webgui: Enhanced display of network settings
    • webgui: Open banner system to 3rd party apps
    • webgui: Modified notify script to allow overriding email recipients in notification settings
    • webgui: Allow Safari to use websockets
    • webgui: Select case correction + replace MD1510 for AVS-10/4
    • webgui: Font, Icon and image cleanup
    • webgui: Added AFP deprecated notice
    • webgui: Changed config folder of TELEGRAM
    • webgui: Add share access to user edit
    • webgui: Added cache and disk type to shares page
    • webgui: Aligned management page layout
    • webgui: Added conditional UPnP setting on Management page
    • webgui: Support wireguard plugin in download.php
    • webgui: Added UPnP to access script (to support WireGuard plugin)
    • webgui: Made notify script compatible with 6.8 new security scheme
    • webgui: Fixed misalignment of absent disk on Main page
    • webgui: Update ArrayDevices.page help text
    • webgui: show warning on login page when browser cookies are disabled
    • webgui: Fixed docker container update state
    • webgui: Added VM XML files to diagnostics
    • webgui: Telegram notification agent: enable group chat IDs, update helper description
    • webgui: Integrate CAs Plugin Helper
    • webgui: Switch download routine to be PHP Curl
    • webgui: Change PluginHelpers download to be PHP Curl
    • webgui: dockerMan - Deprecate TemplateURL
    • webgui: Fixed: footer always on foreground
    • webgui: Plugin Helpers: Follow redirects on downloads
    • webgui: dockerMan: Redownload Icon if URL changes
    • webgui: If a page is loaded via https, prevent it from loading resources via http (ie, block mixed content)
    • webgui: Ensure spinner always ontop
    • webgui: Allow outside click to close popups
    • webgui: Use complete HTML documents in popups
    • webgui: Standardize on lang="en"
    • webgui: Added 'F1' key to toggle help text
    • webgui: Main page: consolidate spin up/down action and device status into one
    • webgui: support changed tunables on Disk Settings page
    • Like 1
    • Thanks 4
    Go to reports Prereleases

    User Feedback

    Recommended Comments



    testdasi

    Don't know if it's a bug or not but all my Shares switched to High Water mode instead of my usual Most Free. No big deal - I just switch stuff back manually but I reckon it might be a major annoyance for some.

    Edited by testdasi
    Link to comment
    Lev
    3 hours ago, testdasi said:

    Don't know if it's a bug or not but all my Shares switched to High Water mode instead of my usual Most Free. No big deal - I just switch stuff back manually but I reckon it might be a major annoyance for some.

    I checked mine, I can't reproduce this.

    Link to comment
    Young_Max

    1、 Array Stopped•Starting services..

    2、The lm-sensors update is useless.

     

    Use Unraid lm-sensors 3.6 run 

    sensors-detect

    , I can get : 

    Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found unknown chip with ID 0xd121
    (logical device B has address 0x290, could be sensors)
Probing for Super-I/O at 0x4e/0x4f

     

     

    But I download from https://github.com/lm-sensors/lm-sensors. Run 

    sensors-detect

     I can get:

      

    Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT6793D Super IO Sensors'                   Success!
    (address 0x290, driver `nct6775')
Probing for Super-I/O at 0x4e/0x4f


    It's just what I need. My motherboards is ASUS TUF Z370-PLUS GAMING

     

    So Why?

     

     

    tower-diagnostics-20191026-0556.zip

    Edited by Young_Max
    Link to comment
    dalben

    I have a couple of modeprobe commands in my go file.  Can they still be run from there or should they be somewhere else?  the system temp plugin isn't working with rc1 and rc 4

     

    # start sensors
    modprobe coretemp
    modprobe nct6775

    Link to comment
    WCA

    Since (atleast) 6.8rc2 I've been getting read errors on multiple disks in my array (across controllers, both on my HBA (Dell H200) and my integrated controller (Intel), I spin down my disks after 4 hours, and the problem seems to only occur when disks are spun down.

    It's the same problem this user on reddit seems to have:

    https://www.reddit.com/r/unRAID/comments/dmxcr5/am_i_playing_with_fire/

     



    My Specs are:
     

    Quote

     

    i5 4590
    ASRock B85m Pro 4

    Dell PERC H200 HBA
    Seasonic Focus + Gold 550 PSU
    32GB DDR3 RAM

     



    Storage consists of the following:

    Quote

     

    [0:0:0:0]disk Samsung Flash Drive 1100 /dev/sda 32.0GB

    [1:0:0:0]disk ATA WDC WD40EFRX-68N 0A82 /dev/sdb 4.00TB

    [2:0:0:0]disk ATA WDC WD40EFRX-68N 0A82 /dev/sdc 4.00TB

    [3:0:0:0]disk ATA Samsung SSD 840 6B0Q /dev/sdd 512GB

    [4:0:0:0]disk ATA Samsung SSD 840 6B0Q /dev/sde 512GB

    [5:0:0:0]disk ATA WDC WD40EFRX-68N 0A82 /dev/sdf 4.00TB

    [6:0:0:0]disk ATA WDC WD40EFRX-68N 0A82 /dev/sdg 4.00TB

    [7:0:0:0]disk ATA MB4000GDUPB HPG4 /dev/sdh 4.00TB

    [7:0:1:0]disk ATA MB4000GDUPB HPG4 /dev/sdi 4.00TB

    [7:0:2:0]disk ATA MB4000GDUPB HPG4 /dev/sdj 4.00TB

    [7:0:3:0]disk ATA MB4000GDUPB HPG4 /dev/sdk 4.00TB

     



    And for what it's worth, here is the entire hardware map:

    Quote

     

    [8086:0c00]00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)

    [8086:0c01]00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)

    [8086:0412]00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)

    [8086:8c31]00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)

    [8086:8c3a]00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)

    [8086:153b]00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 05)

    [8086:8c2d]00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)

    [8086:8c10]00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)

    [8086:244e]00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d5)

    [8086:8c26]00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)

    [8086:8c50]00:1f.0 ISA bridge: Intel Corporation B85 Express LPC Controller (rev 05)

    [8086:8c02]00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)

    [8086:8c22]00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)

    [1000:0072]01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

    [1b21:1080]03:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 03)

     

     

     

     

     

    I will attach logs for the last few hours: 

    Oct 24 23:46:52 PLEXSCH kernel: blk_update_request: critical medium error, dev sdh, sector 4026569360 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569296
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569304
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569312
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569320
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569328
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569336
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569344
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569352
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569360
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569368
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569376
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569384
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569392
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569400
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569408
Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569416
Oct 24 23:47:04 PLEXSCH kernel: blk_update_request: critical medium error, dev sdj, sector 4026569360 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569296
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569304
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569312
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569320
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569328
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569336
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569344
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569352
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569360
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569368
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569376
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569384
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569392
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569400
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569408
Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569416
Oct 24 23:47:05 PLEXSCH kernel: blk_update_request: critical medium error, dev sdk, sector 4026569360 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569296
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569304
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569312
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569320
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569328
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569336
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569344
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569352
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569360
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569368
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569376
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569384
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569392
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569400
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569408
Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569416


     

    Edited by WCA
    Link to comment
    testdasi
    3 hours ago, WCA said:

    Since (atleast) 6.8rc2 I've been getting read errors on multiple disks in my array (across controllers, both on my HBA (Dell H200) and my integrated controller (Intel), I spin down my disks after 4 hours, and the problem seems to only occur when disks are spun down.

    It's the same problem this user on reddit seems to have:

    https://www.reddit.com/r/unRAID/comments/dmxcr5/am_i_playing_with_fire/
     

    Did it happen on 6.8.0-rc1? If it didn't then I don't think it's related to 6.8-rc - you might have an actual problem at hand and not just a bug.

    Link to comment
    limetech
    4 hours ago, WCA said:

    Since (atleast) 6.8rc2 I've been getting read errors on multiple disks in my array

    Please open a separate bug report and included your diagnostics.zip.

    Link to comment
    limetech
    6 hours ago, dalben said:

    have a couple of modeprobe commands in my go file.  Can they still be run from there

    Yes

    Link to comment
    WCA
    1 hour ago, testdasi said:

    Did it happen on 6.8.0-rc1? If it didn't then I don't think it's related to 6.8-rc - you might have an actual problem at hand and not just a bug.

    I went straight from 6.7.2 to RC2 or RC3 i think

    I downgraded back to 6.7.2, issues are gone now.

    Link to comment
    limetech
    1 hour ago, WCA said:

    I downgraded back to 6.7.2, issues are gone now.

    Posting snippets of stuff doesn't help.  Please post diagnostics.zip

    Link to comment
    phbigred

    @limetechAny plans on putting in the fixes done by this person's recompile?

     

     

    This custom kernel fixes the VM VFIO bug with no GPU passthrough that @SpaceInvaderOne likely documented. This works for my MSI x370 sli plus with ryzen 3000 compatibility AGESA 1.0.0.3 ABBA code. 

     

    Also were there any NIC changes with this version 6.8 branch that would affect VM br0 passthrough? Noticing an issue with gateway routing for my VPN traffic. I have to put my entire server outside the VPN as I can't individually route now.

    Edited by phbigred
    Link to comment
    sittingmongoose

    So I am not sure if this is from a bug from RC1 or not.....But I had a very weird troubling thing happen to me last night.  I opened the disk location pluggin to assign my two new 10TB drives I just installed.  I hit the scan all button and it discovered I had a 5TB drive not installed.

     

    The 5TB drive then showed up in my unassigned devices.  I precleared it thinking it was an extra drive I forgot to put in the array....Well I was wrong, it was already in my array running?!?!?  Then Unraid reported a disk error because obviously it was wiping.

     

    TLDR; one of my drives from my array showed up as an unsigned device and told me to preclear it.  WTF? (Running Nvidia RC1 because array performance has been worse on RC3 so I'm afraid to go to RC4).  I am posting my diags just in case it matters.

    9900k-diagnostics-20191026-2157.zip

    Link to comment
    emuhack

    I have upgraded from RC2 to RC4 - and nothing but issues. I know its a pre release but i would skip this release

     

    - HBA issues (RAID bus controller: Adaptec Series 7 6G SAS/PCIe 3) 

    - Drive Errors in the upwords of 5k

    - I had my docker image corrupt (I had a backup, thank goodness)

    - my permissions corrupted on my array. 

    - IO errors when writing to the Array

     

    I downgraded to 6.7.2 - and will wait :)

    Link to comment
    trott
    2 hours ago, emuhack said:

    I have upgraded from RC2 to RC4 - and nothing but issues. I know its a pre release but i would skip this release

     

    - HBA issues (RAID bus controller: Adaptec Series 7 6G SAS/PCIe 3) 

    - Drive Errors in the upwords of 5k

    - I had my docker image corrupt (I had a backup, thank goodness)

    - my permissions corrupted on my array. 

    - IO errors when writing to the Array

     

    I downgraded to 6.7.2 - and will wait :)

    I don't think RC2 to RC4 changes that much enough to cause all your issues, it must be something else here

    Link to comment
    dgriff

     

    I'm having tons of strange I/O hangs on any of the 6.8 RCs, network performance will completely freeze and all I/O will stop from unraid to my PC. This only causes a problem with SMB shares over the network, doesn't appear to be a problem with internal array use. Absolutely unusable over the network.

     

    Edit: Reverted to 6.7.2, all back to normal, totally usable again.  Apologies in advance for a lack of a diagnostic file, had to get things up and running again before my users (wife) freaked out over her lack of Plex, if it appears again in next RC, I'll pull a diagnostic before I revert back.

     

    Quick system config: IBM 1015 HBA, Intel® Core™ i3-6100 CPU @ 3.70GHz, 24GB RAM, 80TB mix of WD Reds and Seagate 8TBs.

    Edited by dgriff
    Link to comment
    testdasi
    1 hour ago, dgriff said:

    Edit: Reverted to 6.7.2, all back to normal, totally usable again.  Apologies in advance for a lack of a diagnostic file, had to get things up and running again before my users (wife) freaked out over her lack of Plex, if it appears again in next RC, I'll pull a diagnostic before I revert back.

    For one second I read that as "users (wives)" 😅

     

    On serious note, I wonder if it's HBA-related (maybe new kernel doesn't like the driver?) since the other user reporting strange issues also appears to use a HBA too. This seems to happen every time there's a major kernel upgrade. Defo need Diagnostics.

    Link to comment
    trott
    1 hour ago, testdasi said:

    For one second I read that as "users (wives)" 😅

     

    On serious note, I wonder if it's HBA-related (maybe new kernel doesn't like the driver?) since the other user reporting strange issues also appears to use a HBA too. This seems to happen every time there's a major kernel upgrade. Defo need Diagnostics.

    might be samba issue, I remember I have a strange issue after update to RC1,  I copy a file from PC to share and try to rename the file, it told me the file is already open and cannot rename the file

    Link to comment
    WCA
    13 hours ago, limetech said:

    Posting snippets of stuff doesn't help.  Please post diagnostics.zip

    Can I post diagnostics.zip from 6.7.2? I'm hesistant to upgrade to RC4 again in fear of data loss

    Link to comment
    itimpi
    24 minutes ago, WCA said:

    Can I post diagnostics.zip from 6.7.2? I'm hesistant to upgrade to RC4 again in fear of data loss

    Not much point!  The whole idea is to try and work out what is happening in the 6.8.0 rc.

    • Thanks 1
    Link to comment
    emuhack

    I have the same errors now on 6.7.2, not as many rc4 was over 5k over 6 drives now its 80 over 6 drives ... I'm ordering new sata cables tonight... Unless someone has a better thought on this... 

      

    ct 27 09:43:54 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:43:55 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:43:56 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:43:57 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:43:58 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:43:59 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:01 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:02 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:03 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:04 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:05 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:06 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:07 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:07 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:07 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:07 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:07 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:07 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:08 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:09 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:10 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:11 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:12 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:13 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:15 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:16 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:17 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:18 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:19 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:20 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:22 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:23 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:24 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:25 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:25 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5
Oct 27 09:44:25 eMu-Unraid kernel: XFS (md4): metadata I/O error in "xfs_trans_read_buf_map" at daddr 0x89fdce20 len 8 error 5

     

    Link to comment
    Squid
    1 hour ago, emuhack said:

    Unless someone has a better thought on this...

    Open a new thread, and include your diagnostics in it.

    Link to comment
    John_M
    1 hour ago, emuhack said:

    I'm ordering new sata cables tonight... Unless someone has a better thought on this... 

    Looks like file system corruption to me.

    Link to comment
    WCA
    7 hours ago, itimpi said:

    Not much point!  The whole idea is to try and work out what is happening in the 6.8.0 rc.

    I get that, but I think it's safe to say it's a better idea to go back to stable than to keep messing around on a release that potentially corrupts my data right?

    I regret having updated to a beta release already, I'm not doing that again. Hoping it will be fixed by the final release. I won't be able to provide diagnostics, so I hope that someone else will be able to provide them.

    I'm sorry, but I just don't want to lose any data. If a Limetech employee would confirm that these errors are not destroying any data, I'd be willing to upgrade temporarily to provide the diagnostics though.

    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.