• Unraid OS version 6.8.0-rc1 available


    limetech

    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.  There is still a 'sync' command at the end, which causes each device to spin up serially as Linux kernel syncs each device (why does kernel do this serially? I have no idea).  I am tempted to remove this because a Reboot of course spins everything up in parallel, but I'm concerned about users out there who might just hit Reset button and USB flash write data is not fully written. 

     

    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.  We have auto-logout set to 1 hour.

     

    Linux kernel 5.3

    • default scheduler now 'mq-deadline'
    • enabled Huge Page support, though no UI control yet
    • binfmt_misc support
    • added "Vega 10 Reset bug" patch
    • 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 can be 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

     

    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)".  The default is 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.

     

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

     

    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

    Edited by limetech

    • Like 6
    • Thanks 4



    User Feedback

    Recommended Comments



    It would be really awesome to see a File Browser in the Unraid GUI boot (yep i use it, and love it!), cut/copy files through terminal/ssh is going to irritate me ;)

    and working though the VM or an another device is way to slow, just want to do file control stuff direct on Unraid it self.

    Link to comment
    11 minutes ago, sjaak said:

    It would be really awesome to see a File Browser in the Unraid GUI boot (yep i use it, and love it!), cut/copy files through terminal/ssh is going to irritate me ;)

    and working though the VM or an another device is way to slow, just want to do file control stuff direct on Unraid it self.

    I agree, however I find using the binhex Krusader docker to work pretty well in GUI mode.

    Link to comment
    12 minutes ago, cobhc said:

    I agree, however I find using the binhex Krusader docker to work pretty well in GUI mode.

    i know Krusader, but i just not want to use a 3rd party thing for a pretty basic gui OS thing, and sometimes a docker container kills the /mnt/user share so Unraid is than pretty much unusable... (looking at you Radarr...fixed by change the appdata mount to direct disk route)

    Link to comment
    1 hour ago, sjaak said:

    i know Krusader, but i just not want to use a 3rd party thing for a pretty basic gui OS thing, and sometimes a docker container kills the /mnt/user share so Unraid is than pretty much unusable... (looking at you Radarr...fixed by change the appdata mount to direct disk route)

    Have you tried midnight commander (MC) in the terminal? Works pretty well for the basic things.

    • Like 2
    Link to comment

    Upgraded from 6.7.2 Last night. So far, all is good. Dockers, VM's all running. No errors in System Log.

     

    Thanks for all of the work to get this released.

     

    Great Work!

    Link to comment

    I upgraded two unraid servers (one on Esxi and the other baremetal) last night running 6.7.3 rc2 to 6.8 rc1 and no issues encountered so far. I was able to get wireguard working on the baremetal but not on the unraid running on Esxi. Still trying to troubleshoot my wireguard issue. My two servers are located in two different houses and the wireguard issue is behind a PFsense firewall. 

    Link to comment
    1 minute ago, SCSI said:

    I upgraded two unraid servers (one on Esxi and the other baremetal) last night running 6.7.3 rc2 to 6.8 rc1 and no issues encountered so far. I was able to get wireguard working on the baremetal but not on the unraid running on Esxi. Still trying to troubleshoot my wireguard issue. My two servers are located in two different houses and the wireguard issue is behind a PFsense firewall. 

    Probably to best post here for help

     

    Link to comment

    Just updated from 6.7.1 to 6.8.0 RC1 and getting this in my log file, repeatedly. 

     

    Quote

    ErrorWarningSystemArrayLogin


    Oct 14 16:14:45 FS kernel: ata4: SATA link down (SStatus 1 SControl 310)
    Oct 14 16:14:45 FS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Oct 14 16:14:45 FS kernel: ata4.00: failed to IDENTIFY (I/O error, err_mask=0x100)
    Oct 14 16:14:51 FS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Oct 14 16:14:51 FS kernel: ata4.00: failed to IDENTIFY (I/O error, err_mask=0x100)
    Oct 14 16:14:51 FS kernel: ata4: limiting SATA link speed to 1.5 Gbps
    Oct 14 16:14:58 FS kernel: ata4: SATA link down (SStatus 1 SControl 310)
    Oct 14 16:14:59 FS kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

    Guessing whatever my ata4 is has a dying drive? Nothing is reporting as SMART errors on my server. 

    Link to comment
    2 minutes ago, Sparkyy said:

    Just updated from 6.7.1 to 6.8.0 RC1 and getting this in my log file, repeatedly. 

     

    Guessing whatever my ata4 is has a dying drive? Nothing is reporting as SMART errors on my server. 

    Post the diagnostics

    Link to comment
    29 minutes ago, Squid said:

    Post the diagnostics

    I would but logged back in and more than 1/2 my drivers were missing, array was in status that bounced between green and orange. 

     

    Had to stop the array as it wouldn't even let me click on Diagnostics. Now that the array is stopped, it says array undefined and won't let me download Diagnostics. 

     

     

    Seeing these errors now; 

     

    Warning: file_put_contents(): Only 4096 of 25512 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Warning: file_put_contents(): Only 0 of 11872 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Warning: file_put_contents(): Only 0 of 10720 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Warning: file_put_contents(): Only 0 of 3518 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Warning: file_put_contents(): Only 0 of 521 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Warning: file_put_contents(): Only 0 of 7240 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Warning: file_put_contents(): Only 0 of 2768 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Warning: file_put_contents(): Only 0 of 1690 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Warning: file_put_contents(): Only 0 of 5987 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Warning: file_put_contents(): Only 0 of 53286 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Warning: file_put_contents(): Only 0 of 1593 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Warning: file_put_contents(): Only 0 of 860 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Warning: file_put_contents(): Only 0 of 4403 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/include/ShowPlugins.php on line 135

    Edited by Sparkyy
    Link to comment

    Does this build support 9th Gen Intel iGPU's?  I am new to unraid and have an Intel i9-9900k CPU that as i understand it unraid doesn't support its iGPU yet for docker or vm passthrough.

    Link to comment
    1 hour ago, Jeramie said:

    Does this build support 9th Gen Intel iGPU's?  I am new to unraid and have an Intel i9-9900k CPU that as i understand it unraid doesn't support its iGPU yet for docker or vm passthrough.

    The issue wasn't unRAID per se, rather it was the Linux kernel (4.19.x) used in prior versions of unRAID.  The 6.8.0-RC1 release uses the 5.3.6 Linux kernel in which 9th gen iGPUs should be supported. 

     

    If you care about this for Plex transcoding purposes, a recent Plex Media Server release now also supports 9th generation iGPUs.

    Link to comment

    awesome, thanks for the info hoopster!  I have a p2000 for plex, i'm hoping to have a vm that i can use locally as a daily driver i believe its called.. a local workstation basically. but haven't been able to use the i9's gpu yet in vm's successfully.  hopefully it'll do it with 5.3.6's linux kernel.

    Link to comment

    Just upgraded to 6.8.0-RC-1.  Syslog contains a bunch of the following errors:

     

    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 7: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' resumed (module 'builtin:omfwd') [v8.1908.0 try https://www.rsyslog.com/e/2359 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd/udp: socket 2: sendto() error: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: omfwd: socket 2: error 101 sending via udp: Network is unreachable [v8.1908.0 try https://www.rsyslog.com/e/2354 ]
    Oct 14 23:03:24 MediaNAS rsyslogd: action 'action-2-builtin:omfwd' suspended (module 'builtin:omfwd'), retry 0. There should be messages before this one giving the reason for suspension. [v8.1908.0 try https://www.rsyslog.com/e/2007 ]

     

    Also, I get a call trace that seems to be related to the i915 video module:

     

    Oct 14 23:04:52 MediaNAS kernel: Console: switching to colour dummy device 80x25
    Oct 14 23:04:52 MediaNAS kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    Oct 14 23:04:52 MediaNAS kernel: [drm] Driver supports precise vblank timestamp query.
    Oct 14 23:04:52 MediaNAS kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
    Oct 14 23:04:52 MediaNAS kernel: [drm] Disabling framebuffer compression (FBC) to prevent screen flicker with VT-d enabled
    Oct 14 23:04:52 MediaNAS kernel: [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27)
    Oct 14 23:04:52 MediaNAS kernel: [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 48: Can't calculate constants, dotclock = 0!
    Oct 14 23:04:52 MediaNAS kernel: WARNING: CPU: 2 PID: 7789 at drivers/gpu/drm/drm_vblank.c:638 drm_calc_vbltimestamp_from_scanoutpos+0x129/0x29c [drm]
    Oct 14 23:04:52 MediaNAS kernel: Modules linked in: i915(+) iosf_mbi drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nct6775 hwmon_vid e1000e igb i2c_algo_bit sr_mod cdrom x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd mpt3sas glue_helper raid_class i2c_i801 intel_cstate intel_uncore mxm_wmi i2c_core ahci intel_rapl_perf video wmi scsi_transport_sas backlight libahci acpi_pad button ie31200_edac [last unloaded: e1000e]
    Oct 14 23:04:52 MediaNAS kernel: CPU: 2 PID: 7789 Comm: modprobe Not tainted 5.3.6-Unraid #1
    Oct 14 23:04:52 MediaNAS kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./C236 WSI, BIOS P2.60 03/06/2018
    Oct 14 23:04:52 MediaNAS kernel: RIP: 0010:drm_calc_vbltimestamp_from_scanoutpos+0x129/0x29c [drm]
    Oct 14 23:04:52 MediaNAS kernel: Code: 43 20 8b 80 78 01 00 00 23 43 50 a8 10 75 1b 48 8b 83 28 03 00 00 48 85 c0 0f 84 5b ff ff ff 48 83 78 28 00 0f 84 50 ff ff ff <0f> 0b e9 44 01 00 00 48 8b 43 20 48 8d 55 c0 41 57 44 89 f6 52 4c
    Oct 14 23:04:52 MediaNAS kernel: RSP: 0018:ffffc90003dff7e8 EFLAGS: 00010002
    Oct 14 23:04:52 MediaNAS kernel: RAX: 000000000000003f RBX: ffff888815b00000 RCX: ffffc90003dff888
    Oct 14 23:04:52 MediaNAS kernel: RDX: 0000000000000000 RSI: ffffffffa0314379 RDI: 0000000000000001
    Oct 14 23:04:52 MediaNAS kernel: RBP: ffffc90003dff850 R08: 0000000000000000 R09: 0000000000000000
    Oct 14 23:04:52 MediaNAS kernel: R10: 0000000000000002 R11: ffff88884678e000 R12: 0000000000000000
    Oct 14 23:04:52 MediaNAS kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffff888846789080
    Oct 14 23:04:52 MediaNAS kernel: FS:  0000153176da5b80(0000) GS:ffff88884de80000(0000) knlGS:0000000000000000
    Oct 14 23:04:52 MediaNAS kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Oct 14 23:04:52 MediaNAS kernel: CR2: 000000000052a020 CR3: 0000000848700005 CR4: 00000000003606e0
    Oct 14 23:04:52 MediaNAS kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    Oct 14 23:04:52 MediaNAS kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
    Oct 14 23:04:52 MediaNAS kernel: Call Trace:
    Oct 14 23:04:52 MediaNAS kernel: ? idr_alloc+0x41/0x63
    Oct 14 23:04:52 MediaNAS kernel: ? drm_calc_timestamping_constants+0xac/0x12c [drm]
    Oct 14 23:04:52 MediaNAS kernel: drm_get_last_vbltimestamp+0x54/0x73 [drm]
    Oct 14 23:04:52 MediaNAS kernel: drm_reset_vblank_timestamp+0x58/0xc2 [drm]
    Oct 14 23:04:52 MediaNAS kernel: drm_crtc_vblank_on+0x8f/0xcf [drm]
    Oct 14 23:04:52 MediaNAS kernel: intel_modeset_setup_hw_state+0x786/0x1059 [i915]
    Oct 14 23:04:52 MediaNAS kernel: intel_modeset_init+0x11a9/0x16e8 [i915]
    Oct 14 23:04:52 MediaNAS kernel: ? fwtable_write32+0x8f/0x11f [i915]
    Oct 14 23:04:52 MediaNAS kernel: ? fwtable_write32+0x8f/0x11f [i915]
    Oct 14 23:04:52 MediaNAS kernel: i915_driver_load+0x108b/0x133f [i915]
    Oct 14 23:04:52 MediaNAS kernel: ? idr_alloc_cyclic+0x53/0xa7
    Oct 14 23:04:52 MediaNAS kernel: ? rpm_resume+0x9b/0x409
    Oct 14 23:04:52 MediaNAS kernel: i915_pci_probe+0x108/0x12a [i915]
    Oct 14 23:04:52 MediaNAS kernel: local_pci_probe+0x3c/0x7a
    Oct 14 23:04:52 MediaNAS kernel: pci_device_probe+0x13c/0x196
    Oct 14 23:04:52 MediaNAS kernel: ? sysfs_do_create_link_sd.isra.0+0x80/0xad
    Oct 14 23:04:52 MediaNAS kernel: really_probe+0x145/0x283
    Oct 14 23:04:52 MediaNAS kernel: driver_probe_device+0x9c/0xd1
    Oct 14 23:04:52 MediaNAS kernel: device_driver_attach+0x37/0x50
    Oct 14 23:04:52 MediaNAS kernel: __driver_attach+0x95/0x9d
    Oct 14 23:04:52 MediaNAS kernel: ? device_driver_attach+0x50/0x50
    Oct 14 23:04:52 MediaNAS kernel: bus_for_each_dev+0x70/0xa6
    Oct 14 23:04:52 MediaNAS kernel: bus_add_driver+0xfb/0x1a9
    Oct 14 23:04:52 MediaNAS kernel: driver_register+0x99/0xcf
    Oct 14 23:04:52 MediaNAS kernel: ? 0xffffffffa04c6000
    Oct 14 23:04:52 MediaNAS kernel: do_one_initcall+0x71/0x166
    Oct 14 23:04:52 MediaNAS kernel: ? __vunmap+0x1c2/0x1e0
    Oct 14 23:04:52 MediaNAS kernel: ? _cond_resched+0x1b/0x1e
    Oct 14 23:04:52 MediaNAS kernel: ? kmem_cache_alloc+0x30/0x128
    Oct 14 23:04:52 MediaNAS kernel: do_init_module+0x51/0x1da
    Oct 14 23:04:52 MediaNAS kernel: load_module+0x19a1/0x1f95
    Oct 14 23:04:52 MediaNAS kernel: ? __se_sys_init_module+0xd5/0x116
    Oct 14 23:04:52 MediaNAS kernel: __se_sys_init_module+0xd5/0x116
    Oct 14 23:04:52 MediaNAS kernel: do_syscall_64+0x57/0xfd
    Oct 14 23:04:52 MediaNAS kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
    Oct 14 23:04:52 MediaNAS kernel: RIP: 0033:0x153176ee013a
    Oct 14 23:04:52 MediaNAS kernel: Code: 48 8b 0d 59 7d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 26 7d 0c 00 f7 d8 64 89 01 48
    Oct 14 23:04:52 MediaNAS kernel: RSP: 002b:00007ffcdf22fde8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
    Oct 14 23:04:52 MediaNAS kernel: RAX: ffffffffffffffda RBX: 0000000000427e30 RCX: 0000153176ee013a
    Oct 14 23:04:52 MediaNAS kernel: RDX: 000000000041b400 RSI: 00000000002c38a8 RDI: 0000000000d3f810
    Oct 14 23:04:52 MediaNAS kernel: RBP: 000000000041b400 R08: 000000000042501a R09: 0000000000000000
    Oct 14 23:04:52 MediaNAS kernel: R10: 0000000000425010 R11: 0000000000000246 R12: 0000000000d3f810
    Oct 14 23:04:52 MediaNAS kernel: R13: 0000000000427f40 R14: 0000000000040000 R15: 0000000000427e30
    Oct 14 23:04:52 MediaNAS kernel: ---[ end trace c13b68bd66095883 ]---
    Oct 14 23:04:52 MediaNAS kernel: [drm] Initialized i915 1.6.0 20190619 for 0000:00:02.0 on minor 0
    Oct 14 23:04:52 MediaNAS kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
    Oct 14 23:04:52 MediaNAS kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
    Oct 14 23:04:52 MediaNAS kernel: fbcon: i915drmfb (fb0) is primary device
    Oct 14 23:04:52 MediaNAS kernel: Console: switching to colour frame buffer device 128x48
    Oct 14 23:04:54 MediaNAS kernel: i915 0000:00:02.0: fb0: i915drmfb frame buffer device
    Oct 14 23:04:56 MediaNAS kernel: [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful
    Oct 14 23:04:58 MediaNAS root: Starting emhttpd

     

    System seems to currently be running OK, but, I have not really tried to do anything other than install the WireGuard plugin (not currently configured or active).

     

    Of course, I don't consider these things to be the result of any "bug" but is there something I can look at to track down the cause of these issues that only began with 6.8.0-RC1?

     

    Diagnostics attached.

    medianas-diagnostics-20191015-0512.zip

    Edited by Hoopster
    Link to comment

    Updated yesterday to kill this "streaming-bug" when writing to a disk - its working perfekt - thanks a lot.

    And also nice: When i send my server to sleep, it goes immediately to sleep. With 6.7 it takes up to 2min's.

    All is working fine so far 😉

    Edited by Zonediver
    Link to comment

    I installed it and I wasn't able to hardlink. It said something like:

     

    Cannot create hardlink: Function not implemented yet.

     

    It wasn't a crash, it was a message saying it's not implemented.

     

    Why does that happen? Is that going to be like that in the final release?

    Link to comment
    4 minutes ago, Jeffarese said:

    I installed it and I wasn't able to hardlink. It said something like:

     

    Cannot create hardlink: Function not implemented yet.

     

    It wasn't a crash, it was a message saying it's not implemented.

     

    Why does that happen? Is that going to be like that in the final release?

    Same problem as this person? The solution is there too.
     

     

    Edited by Niklas
    Link to comment

    Are some of my issues a few posts back possibly related to 'go' file entries?

     

    #Setup drivers for hardware decoding in Plex
    modprobe i915
    sleep 4
    chown -R nobody:users /dev/dri
    chmod -R 777 /dev/dri
    
    # Copy SSH files back to /root/.ssh folder and set permissions for files
    mkdir -p /root/.ssh
    cp /boot/config/ssh/medianas_key /root/.ssh/id_rsa
    cp /boot/config/ssh/known_hosts /root/.ssh/known_hosts
    cat /boot/config/ssh/backupnas_key.pub > /root/.ssh/authorized_keys
    chmod g-rwx,o-rwx -R /root/.ssh
    
    #!/bin/bash
    # Start the Management Utility
    /usr/local/sbin/emhttp &

    That is where modprobe i915 is executed.  I am also setting up ssh keys for doing an unattended backup via rsync between two unRAID servers.

     

    I know the permissions/security on the flash drive have changed.  Is this causing problems?  Go file is copied to /tmp and executed there, correct?

     

    I also see several of these errors in the syslog:

    Oct 14 23:40:36 MediaNAS kernel: [drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training Unsuccessful

     

    As far as I can tell, i915 loads and functions as Plex still claims it is hardware decoding and encoding.  I watched a few shows last night after upgrading and forced transcoding and Plex/Tautulli claimed (hw) transcoding was happening.

     

    I have not yet tried to execute the unattended backup as a parity sync kicked off at 1am and is about 50% complete.  The backup runs on Monday at 1am and executed properly (as it always does) yesterday before the upgrade to 6.8.0-RC1.

     

    Again, as far as I can tell, the server appears to be functioning normally, but, I really have not done too much with it yet since the upgrade late last night.

    Edited by Hoopster
    Link to comment

    Wire Guard seems to be pegging a specfic core (changes after service or system restart) rather than load balancing across cores. Is this to be expected?895676041_2019-10-1510_39_58-Unraid1_Dashboardand8morepages-MicrosoftEdge.png.565ec542661a4cbea048d8302fddfb3b.png

    Link to comment
    45 minutes ago, eagle470 said:

    Wire Guard seems to be pegging a specfic core

    How do you know it is WG?

    Link to comment

    Not sure if this is a 6.8RC1 issue or some other temporary docker image repository issue but all my dockers shows they have an update and won't update.  The previous script fix for this in 6.7.2 doesn't fix it.  Diagnostics attached.

     

    beast-diagnostics-20191015-1731.zip

    Edited by IamSpartacus
    Link to comment
    5 minutes ago, IamSpartacus said:

    Not sure if this is a 6.8RC1 issue or some other temporary docker image repository issue but all my dockers shows they have an update and won't update.  The previous script fix for this in 6.7.2 doesn't fix it.  Diagnostics attached.

    beast-diagnostics-20191015-1716.zipUnavailable

    Im getting the same thing now too.  And as you said the script isn't fixing it.

    Link to comment

    twice now, i've had all my shares disappear.. no idea what's wrong or what i've changed. basically everything stops working as you'd expect. Reboot fixes it though. I was up 3 days previously since the patch no problems, not twice today i've had this issue.

     

    This diagnostic file is after they disappeared, and after array manually stopped but not yet restarted,

    server.lan-diagnostics-20191015-1822.zip

    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.