• Unraid OS version 6.10.0-rc4 available


    limetech

    This is primarily a bug fix release.  We have not addressed every issue that has been reported.  In the past we would typically delay releases until most things were addressed; however, we are committed to producing releases as quickly as possible as issues are fixed and small improvements are made.

     

    It would be extremely helpful to us to report issues by creating separate Reports here rather than creating a reply in this topic.

     

    The main issues addressed here have to do with nchan errors, DNS Rebinding Protection check, and XFS formatting issue.

     

     

    6.10.0 Summary of Changes and New Features

     

    As always, prior to updating, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".

     

    [rc3] Plugin Authors:  We patched the upgradepkg script to prevent it from replacing an installed package with an earlier version of the same package, i.e., no downgrading.  If a plugin really needs to replace a package with a downgraded version it can include the '--reinstall' option.

     

    Also be sure to check out the Dynamix File Manager plugin available now through Community Apps!

     

    UPC and My Servers Plugin

    The most visible new feature is located in the upper right corner of the webGUI header.  We call this the User Profile Component, or UPC.  The UPC allows a user to associate their server(s) and license key(s) with their Unraid Community forum account, also known as an Unraid.net account.

     

    Starting with this release, it will be necessary for a new user to either sign-in with existing forum credentials or sign-up, creating a new account via the UPC in order to download a Trial key.  All key purchases and upgrades are also handled exclusively via the UPC.

     

    Signing-in provides these benefits:

    1. My Servers Dashboard - when logged into the forum a new My Servers menu item appears. Clicking this brings up a Dashboard which displays a set of tiles representing servers associated with this account.  Each tile includes a link to bring up the servers webGUI on your LAN.  Install the My Servers plugin to provide real-time status and other advanced features (see below).
    2. Notification of critical security-related updates.  In the event a serious security vulnerability has been discovered and patched, we will send out a notification to all email addresses associated with registered servers.
    3. Posting privilege in a new set of My Servers forum boards.
    4. No more reliance on email and having to copy/paste key file URLs in order to install a license key - keys are delivered and installed automatically to your server.

     

    Once a license key has been provisioned, it is not necessary to remain signed-in, though there is no particular reason to sign-out.

     

    My Servers Plugin

    My Servers is what we call our set of cloud-based or cloud-enabled services and features that integrate with your Unraid server(s).  Once installed here are some of the features of My Servers:

    • Real-time Status - with the plugin installed each server tile on the My Servers Dashboard will display real-time status such as whether the server is online or offline, storage utilization and other information. 
    • Remote Access link - if enabled, a link is displayed on the My Servers Dashboard to bring up a server webGUI remotely and over the Internet.
    • Automatic Flash Backup - every registered server is provided with a private git repo initially populated with the contents of your USB flash boot device (except for certain files which contain private information such as passwords).  Thereafter, configuration changes are automatically committed.  A link is provided to download a custom zip file that can be fed as input to the USB Flash Creator tool to move your configuration to a new USB flash device.

     

    My Servers is an optional add-on, installed through Community Apps or via direct plugin URL.  Detailed instructions can be found here.

     

    If you have installed the My Servers plugin, signed-in servers will maintain a websocket connection to a cloud-based Lime Technology proxy server for the purpose of relaying real-time status.

     

    Security Changes

    • It is now mandatory to define a root password.  We also created a division in the Users page to distinguish root from other user names.  The root UserEdit page includes a text box for pasting SSH authorized keys.
    • For new configurations, the flash share default export setting is No.
    • For all new user shares, the default export setting is No.
    • For new configurations, SMBv1 is disabled by default.
    • For new configurations, telnet, ssh, and ftp are disabled by default.
    • We removed certain strings from Diagnostics such as passwords found in the 'go' file.

     

    Virtualization

    Both libvirt and qemu have been updated.  In addition, qemu has been compiled with OpenGL support, and [rc2] ARM emulation (experimental).

     

    [rc2] To support Windows 11 which requires TPM and Secure boot, we have added TPM emulation; and, added a "Windows 11" VM template which automatically selects TPM-aware OVMF bios.  Also, here are instructions for upgrading a Windows 10 VM to Windows 11.  Special thanks to @ich777 who researched and determined what changes and components were necessary to provide this functionality.

     

    The built-in Firefox browser available in GUI-mode boot is built as an AppImage and located in the bzfirmware compressed file system image.  This saves approximately 60MB of RAM.

     

    The Wireguard plugin has been integrated into webGUI, that is, no need for the plugin.  If you had the plugin installed previously, it will be uninstalled and moved to the "Plugins/Plugin File Install Errors" page. No action is needed unless you want to press the Delete button to remove it from that page. Your WireGuard tunnels and settings will be preserved.

     

    Simplified installation of the Community Apps plugin.  The webGUI automatically includes the Apps menu item, and if CA is not already installed, the page offers an Install button.  No need to hunt for the plugin link.

     

    [rc3] Moving to Let's Encrypt wildcard SSL certificates. 

    Starting with this release, we no longer issue new single-host SSL certificates (which we're calling legacy certificates).  Instead, all new Unraid.net SSL certificates are wildcard certificates (still provided by Let's Encrypt).  In order to provision a new wildcard certificate, or upgrade a legacy certificate, you must be signed-in to Unraid.net.  You do not need to be signed-in however, to have either type of certificate automatically renewed when it is within 30 days of expiration.

     

    The URL used to access your server making use of a wildcard certificate has this form:

    • https://[lan-ip].[hash].myunraid.net

    where,

    • [lan-ip] is your severs LAN IP address with dots changed to dashes
    • [hash] is a 40-character hex string (160 bits) unique to this server (and different from similar [hash] in legacy certificates)

    example:

     

    We added a new DDNS server which listens at "myunraid.net".  This server extracts [lan-ip] from the domain name and returns the IP address where the dashes are changed back into dots.  There are several benefits to this approach for both our users and for us:

    • Eliminates DNS propagation delays when you first provision a certificate or when a server LAN IP address (or WAN IP address) changes.  Since the domain name includes the IP address, any IP address change also changes the domain name, hence will not be contained in any intermediate DNS cache.  We also changed the TTL from 1 hour to 7 days further reducing overhead and alleviating issues where someone's internet goes down for brief periods.
    • Improves privacy because your remote access WAN IP address can't be determined by simply prepending "www" to your local access URL.
    • Moves DNS functionality off the 'unraid.net' domain and isolates it on 'myunraid.net' domain.

     

    In previous releases code that provisions (allocates and downloads) an Unraid.net SSL certificate would first test if DNS Rebinding Protection was enforced on the user's LAN; and, if so, would not provision the certificate.  Since there are other uses for a LE certificate we changed the code so that provision would always proceed.  Next, we changed the logic behind the Auto selection of "Use SSL/TLS" setting on the Management Access page.  Now it is only possible to select Auto if both a LE certificate has been provisioned and DNS Rebinding Protection is not enforced.  This is a subtle change but permits certain My Servers features such as Remote Access.

     

    Upon upgrading, you will need to modify any server bookmarks with new the URL; however, if you server is signed-in to Unraid.net then the My Servers dashboard maintains the correct Local Access URL for each of your servers.

     

    More information including use cases may be found in Documentation here.

     

    Linux Kernel

    Upgrade to [rc4] Linux 5.15.30 kernel which includes so-called Sequoia and Dirty Pipe vulnerability mitigations.

     

    In-tree GPU drivers are now loaded by default if corresponding hardware is detected:

    • amdgpu
    • ast
    • i915
    • radeon

     

    These drivers are required mostly for motherboard on-board graphics used in GUI boot mode.  Loading of a driver can be prohibited by creating the appropriate file named after the driver:

    echo "blacklist i915" > /boot/config/modprobe.d/i915.conf

    Alternately, the device can be isolated from Linux entirely via the System Devices page.  Note that in Unraid OS 6.9 releases the in-tree GPU drivers are blacklisted by default and to enabling loading a driver you need to create an empty "conf" file.  After upgrading to Unraid OS 6.10 you may delete those files, or leave them as-is.  This change was made to greatly improve the Desktop GUI experience for new users.

     

    Added support for Intel GVT-g, which lets you split your Intel i915 iGPU into multiple virtual GPUs and pass them through to multiple VMs, using @ich777's Intel-GVT-g plugin.

     

    Added support for gnif/vendor-reset.  This simplifies @ich777's AMD Vendor Reset plugin which permits users to get their AMD video cards to reset properly.

     

    [rc2] Added so-called "add-relaxable-rmrr-5_8_and_up.patch" modified for our kernel
      https://github.com/kiler129/relax-intel-rmrr/blob/master/patches/add-relaxable-rmrr-5_8_and_up.patch

    Thanks to @ich777 for pointing this out.

     

    [rc2] Enabled additional ACPI kernel options
    [rc2] Enabled TPM kernel modules (not utilized yet) - note this is for Unraid host utilizing physical TPM, not emulated TPM support for virtual machnes.

    [rc4] Updated out-of-tree drivers

     

    Base Packages

    Virtually the entire base package set has been updated.

     

    [rc2] For SMB: Samba version 4.15 SMB3 multi-channel is no longer marked "experimental" and is enabled by default.

     

    [rc2] Per request we added the mcelog package.  With inclusion of this package, if you have an AMD processor you may see this error message in the system log:

    mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead.

    We're not sure what to make of this.  It appears mcelog is being deprecated in favor of rasdaemon.  This is something we need to research further.

     

    Other improvements available in 6.10, which are maybe not so obvious to spot from the release notes and some of these improvements are internal and not really visible:

     

    Event driven model to obtain server information and update the webGUI in real-time

    • The advantage of this model is its scalability. Multiple browsers can be opened simultaneously to the webGUI without much impact
    • In addition stale browser sessions won't create any CSRF errors anymore
    • People who keep their browser open 24/7 will find the webGUI stays responsive at all times
    • [rc3] Consistent state information is maintained across all browser instances open to a particular server

     

    Docker labels

    • Docker labels are added to allow people using Docker compose to make use of icons and GUI access
    • Look at a Docker 'run' command output to see exactly what labels are used

     

    Docker custom networks

    • A new setting for custom networks is available. Originally custom networks are created using the macvlan mode, and this mode is kept when upgrading to version 6.10
    • The new ipvlan mode is introduced to battle the crashes some people experience when using macvlan mode. If that is your case, change to ipvlan mode and test. Changing of mode does not require to reconfigure anything on Docker level, internally everything is being taken care off.

     

    Docker bridge network (docker0)

    • docker0 now supports IPv6. This is implemented by assigning docker0 a private IPv6 subnet (fd17::/64), similar to what is done for IPv4 and use network translation to communicate with the outside world
    • Containers connected to the bridge network now have both IPv4 and IPv6 connectivity (of course the system must have IPv6 configured in the network configuration)
    • In addition several enhancements are made in the IPv6 implementation to better deal with the use (or no-use) of IPv6

     

    Plugins page

    • The plugins page now loads information in two steps. First the list of plugins is created and next the more time consuming plugin status field is retrieved in the background. The result is a faster loading plugins page, especially when you have a lot of plugins installed

     

    Dashboard graphs

    • The dashboard has now two graphs available. The CPU graph is displayed by default, while the NETWORK graph is a new option under Interface (see the 'General Info' selection)
    • The CPU graph may be hidden as well in case it is not desired
    • Both graphs have a configurable time-line, which is by default 30 seconds and can be changed independently for each graph to see a longer or shorter history.
    • Graphs are updated in real-time and are useful to observe the behavior of the server under different circumstances

     

    Scheduler Improvements

    • [rc3] You can now split a parity check into smaller pieces and let it run over multiple days or weeks.  For example a check can be performed in a time frame of 01:00am to 06:00am for several days in a row until it is completed.  This way a long parity check won’t interfere with the normal day activities, like watching a movie.
    • [rc3] Added ability to schedule pool 'balance' and 'scrub' operations and calculate whether a full balance is recommended.

     

    Other Changes

    • We switched to a better-maintained version of the WSD server component called wsdd2 in an effort to eliminate instances where the wsd daemon would start consuming 100% of a CPU core.  [rc2] Automatically restrict wsdd to listen only at the primary network interface (br0, bond0, or eth0, depending on config).
    • Fixed issue where you couldn't create a docker image on a share name that contains a space.
    • Fixed issue where 'mover' would not move to a pool name that contains a space.
    • Fixed issue in User Share file system where permissions were not being honored.
    • We increased the font size in Terminal and [rc2] fixed issue with macOS Monterey.
    • [rc2] Fixed jumbo frames not working.
    • [rc2] sysctl: handle net.netfilter.nf_conntrack_count max exceeded (increase setting to 131072) - hattip to Community Member @DieFalse

    • [rc2] Mover will create '.partial' file and then rename upon completion.

    • [rc2] Check bz file sha256sums at boot time.

    • [rc3] Fixed bug found by @thohell where md_sync_limit was not being honored to limit stripe_head cache usage when other I/O is active.  The effect of this fix is to drastically slow down parity operations if other I/O is happening (such as streaming a video).  Throttling of parity sync operations can be adjusted by changing the 'Settings/Disk Settings/Tunable (md_sync_limit)' value.

    • [rc3] Fixed btrfs pool device replace corner cases.  Important note: if you 'unassign' a device from a btrfs multiple-device pool, and that device is still physically present, upon array Start we will erase the LUKS header on the device if present, and delete the partition structure, thereby effectively erasing all the data contained on the device.  This is necessary in order to convince btrfs to no longer use the device and to free it for assignment to another pool.

    • [rc3] For cookies managed by webGUI, changed sameSite cookie attribute from 'strict' to 'lax'.  This change was made to solve an issue with Terminal window not opening in Safari.

     

    Credits

    Special thanks to all our beta testers and especially:

    @bonienl for his continued refinement and updating of the Dynamix webGUI.

    @Squid for continued refinement of Community Apps and associated feed.

    @dlandon for continued refinement of Unassigned Devices plugin and patience as we change things under the hood.

    @ich777 for assistance and passing on knowledge of Linux kernel config changes to support third party drivers and other kernel-related functionality via plugins.

    @SimonF for refinements to System Devices page and other webGUI improvements.  We intend to merge your mover progress changes during this RC series.

    @thohell for an extra set of eyes looking at md/unraid driver and for work-in-progress of adding changes to support multiple Unraid arrays.

     


     

    Version 6.10.0-rc4 2022-03-19 (vs. 6.10.0-rc3)

    Base distro:

    • docker: version 20.10.13
    • firefox: 98.0.r20220313140707 (AppImage)
    • kbd: version 1.15.3 (to support non-US keyboards)

    Linux kernel:

    • Linux 5.15.30-Unraid
    • oot: md/unraid: version 2.9.22 (revert setting min sector size to 4096)
    • oot: added Intel ixgbe: version 5.14.6

    Management:

    • emhttpd: add 'rootshare' reserved name
    • rc.nginx: prefer IPv4 if both IPv4 and IPv6
    • rc.nginx: ignore case in processing Subject field for custom certificates
    • rc.nginx: remove default server block returning 404 for https if USE_SSL==no and no CA-signed cert
    • webgui: Docker: Add Network / Privacy Category
    • webgui: Revert back to default capitalization of device names
    • webgui: Fix PHP error when calculating balance level
    • webgui: Docker: make popup window fit in browser window
    • webgui: Change parity sync notification from error to notice level
    • webgui: Changed header selection for better support of Android
    • webgui: Let setting "showBannerGradient" default to "yes"
    • webgui: Remove Nchan error detection (Rely on the automatic reconnect of Nchan to re-establish connections when communication is slow)
    • webgui: Fix: Improved DNS Rebinding checks
    • webgui: Revised filedrop.js
    • webgui: Use https for internet connectivity check
    • webgui: Fix regression error for themes auzre & gray
    • webgui: Highlight selected row when hovering over array or shares
    • Like 9
    • Thanks 4



    User Feedback

    Recommended Comments



    6 hours ago, Grobalt said:

    RTL8156B is not working any more with RC4 (it did with RC2)

    Same problem, thread started here

    (It is just me so far)  I really need a long term solution (not just don't update)

    • Like 1
    Link to comment

    Some users mentioned the touch problems to open share/disk content. This is not related to mobile devices I think, it's a general problem. Opening the content of a disk on the first click is a 50:50 chance as the html source code seems to be rebuilded every ~0.2 seconds which avoids clicking the icon:

     

    PS why was the icon changed to an external link icon?! Please use the directory icon again. It makes much more sense.

    • Like 1
    Link to comment

    OK, I think I've found whats causing me grief since my upgrade from 6.9.2 . I use a docker that uses /dev/sr0 to rip blurays and dvd's for me.  Sometimes I put in a disc and that docker hangs and locks up all other dockers, I get zombie processes I cannot SIGKILL, and I'm forced to reboot to clean it up and get the docker working again. What I've noticed is this:

    [  324.178091] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
    [  324.190405] sr 0:0:0:0: [sr0] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s
    [  324.190410] sr 0:0:0:0: [sr0] tag#0 CDB: opcode=0x28 28 00 00 00 04 00 00 00 02 00
    [  324.190412] blk_update_request: I/O error, dev sr0, sector 4096 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
    [  354.383938] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
    [  473.812944] udevd[1688]: worker [27853] /devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb4/4-1/4-1:1.0/host0/target0:0:0/0:0:0:0/block/sr0 timeout; kill it
    [  473.812954] udevd[1688]: seq 11256 '/devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb4/4-1/4-1:1.0/host0/target0:0:0/0:0:0:0/block/sr0' killed

     

    I've never seen udev do this before in 6.9.2 . Is this due to my new bluray drive, or is this due to 6.10.0-rc4 ? This is entirely new behavior to me. to generate diagnostics, I'm required to power off the bluray drive (/dev/sr0) to continue otherwise it hangs there. Anyone got any ideas?

    oceans-diagnostics-20220408-2342.zip

    Edited by Darksurf
    Link to comment

    Do you have problems with time machine backups? Starting a backup basically makes shares unreachable for a couple of minutes and the backup ends up with error.

    Link to comment
    On 4/8/2022 at 11:47 PM, Darksurf said:

    OK, I think I've found whats causing me grief since my upgrade from 6.9.2 . I use a docker that uses /dev/sr0 to rip blurays and dvd's for me.  Sometimes I put in a disc and that docker hangs and locks up all other dockers, I get zombie processes I cannot SIGKILL, and I'm forced to reboot to clean it up and get the docker working again. What I've noticed is this:

    [  324.178091] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
    [  324.190405] sr 0:0:0:0: [sr0] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s
    [  324.190410] sr 0:0:0:0: [sr0] tag#0 CDB: opcode=0x28 28 00 00 00 04 00 00 00 02 00
    [  324.190412] blk_update_request: I/O error, dev sr0, sector 4096 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
    [  354.383938] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
    [  473.812944] udevd[1688]: worker [27853] /devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb4/4-1/4-1:1.0/host0/target0:0:0/0:0:0:0/block/sr0 timeout; kill it
    [  473.812954] udevd[1688]: seq 11256 '/devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb4/4-1/4-1:1.0/host0/target0:0:0/0:0:0:0/block/sr0' killed

     

    I've never seen udev do this before in 6.9.2 . Is this due to my new bluray drive, or is this due to 6.10.0-rc4 ? This is entirely new behavior to me. to generate diagnostics, I'm required to power off the bluray drive (/dev/sr0) to continue otherwise it hangs there. Anyone got any ideas?

    oceans-diagnostics-20220408-2342.zip

    OK, I've troubleshot this down to being mostly a problem with MakeMKV. Evidently it freaks out on certain discs it cannot read and it can cause MakeMKV to hang and/or become an unkillable ZOMBIE process. I thought being in an Unpriviledged Docker would at least allow me to kill off that docker to remove the process, but it appears that doesn't work.  I do not get udev killing off my /dev/sr0 drive on my Manjaro desktop, but MakeMKV failing on specific unreadable discs still causes it to hang and turn into a zombie process just the same, unkillable by SIGKILL.

    Figured that piece of info could be valuable to devs.
    UPDATE: READ MY POST DOWN BELOW, SOLUTION HAS BEEN FOUND/SOLVED. ITS A UDEV RULE ISSUE!

    Edited by Darksurf
    update to notify issue has been solved. Unraid may need a permanent/upstream fix.
    • Like 1
    Link to comment

    SSH / Terminal is dead

     

    Apr 11 20:49:59 Tower webGUI: Successful login user root from 192.168.178.25
    Apr 11 20:50:11 Tower kernel: Bluetooth: Core ver 2.22
    Apr 11 20:50:11 Tower kernel: NET: Registered PF_BLUETOOTH protocol family
    Apr 11 20:50:11 Tower kernel: Bluetooth: HCI device and connection manager initialized
    Apr 11 20:50:11 Tower kernel: Bluetooth: HCI socket layer initialized
    Apr 11 20:50:11 Tower kernel: Bluetooth: L2CAP socket layer initialized
    Apr 11 20:50:11 Tower kernel: Bluetooth: SCO socket layer initialized
    Apr 11 20:51:04 Tower nginx: 2022/04/11 20:51:04 [crit] 3589#3589: *7931687 connect() to unix:/var/run/ttyd.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.178.25, server: , request: "GET /webterminal/ttyd/ HTTP/1.1", upstream: "http://unix:/var/run/ttyd.sock:/", host: "tower", referrer: "http://tower/Settings/ManagementAccess"
    Apr 11 20:51:07 Tower nginx: 2022/04/11 20:51:07 [crit] 3589#3589: *7931687 connect() to unix:/var/run/ttyd.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.178.25, server: , request: "GET /webterminal/ttyd/ HTTP/1.1", upstream: "http://unix:/var/run/ttyd.sock:/", host: "tower"
    Apr 11 20:51:44 Tower nginx: 2022/04/11 20:51:44 [crit] 3589#3589: *7932666 connect() to unix:/var/run/ttyd.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.178.25, server: , request: "GET /webterminal/ttyd/ HTTP/1.1", upstream: "http://unix:/var/run/ttyd.sock:/", host: "tower", referrer: "http://tower/Tools/Syslog"
    Apr 11 20:51:46 Tower nginx: 2022/04/11 20:51:46 [crit] 3589#3589: *7932666 connect() to unix:/var/run/ttyd.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.178.25, server: , request: "GET /webterminal/ttyd/ HTTP/1.1", upstream: "http://unix:/var/run/ttyd.sock:/", host: "tower"
    Apr 11 20:52:49 Tower nginx: 2022/04/11 20:52:49 [crit] 3589#3589: *7933928 connect() to unix:/var/run/ttyd.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.178.25, server: , request: "GET /webterminal/ttyd/ HTTP/1.1", upstream: "http://unix:/var/run/ttyd.sock:/", host: "tower", referrer: "http://tower/Dashboard"
    Apr 11 20:53:07 Tower nginx: 2022/04/11 20:53:07 [crit] 3589#3589: *7933928 connect() to unix:/var/run/ttyd.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.178.25, server: , request: "GET /webterminal/ttyd/ HTTP/1.1", upstream: "http://unix:/var/run/ttyd.sock:/", host: "tower", referrer: "http://tower/Dashboard"
    Apr 11 20:54:12 Tower emhttpd: shcmd (80479): /usr/local/emhttp/webGui/scripts/update_access
    Apr 11 20:54:12 Tower sshd[3466]: Received signal 15; terminating.
    Apr 11 20:54:13 Tower emhttpd: shcmd (80480): /etc/rc.d/rc.nginx reload
    Apr 11 20:54:13 Tower root: Checking configuration for correct syntax and
    Apr 11 20:54:13 Tower root: then trying to open files referenced in configuration...
    Apr 11 20:54:13 Tower root: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
    Apr 11 20:54:13 Tower root: nginx: configuration file /etc/nginx/nginx.conf test is successful
    Apr 11 20:54:13 Tower root: Reloading Nginx configuration...
    Apr 11 20:54:16 Tower nginx: 2022/04/11 20:54:16 [alert] 3589#3589: *7935181 open socket #4 left in connection 5
    Apr 11 20:54:16 Tower nginx: 2022/04/11 20:54:16 [alert] 3589#3589: *7935187 open socket #16 left in connection 8
    Apr 11 20:54:16 Tower nginx: 2022/04/11 20:54:16 [alert] 3589#3589: aborting
    Apr 11 20:54:28 Tower emhttpd: shcmd (80483): /usr/local/emhttp/webGui/scripts/update_access
    Apr 11 20:55:15 Tower nginx: 2022/04/11 20:55:15 [crit] 30158#30158: *7935815 connect() to unix:/var/run/ttyd.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.178.25, server: , request: "GET /webterminal/ttyd/ HTTP/1.1", upstream: "http://unix:/var/run/ttyd.sock:/", host: "tower", referrer: "http://tower/Settings/ManagementAccess"
    

    I'm not using this server for other things except testing.

    Link to comment

    I'm having lot of issues with my PCI-E add-in 2.5GB network card on RC4. It seems to be far worse once I start a VM (Windows 10). Is this a known issue?

     

    Apr 12 14:15:24 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
    Apr 12 14:15:24 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
    Apr 12 14:15:24 bigbird kernel: device eth0 left promiscuous mode
    Apr 12 14:15:24 bigbird kernel: bond0: now running without any active interface!
    Apr 12 14:15:24 bigbird kernel: br0: port 1(bond0) entered disabled state
    Apr 12 14:15:28 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
    Apr 12 14:15:28 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
    Apr 12 14:15:28 bigbird kernel: bond0: (slave eth0): making interface the new active one
    Apr 12 14:15:28 bigbird kernel: device eth0 entered promiscuous mode
    Apr 12 14:15:28 bigbird kernel: bond0: active interface up!
    Apr 12 14:15:28 bigbird kernel: br0: port 1(bond0) entered blocking state
    Apr 12 14:15:28 bigbird kernel: br0: port 1(bond0) entered forwarding state
    Apr 12 14:15:40 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
    Apr 12 14:15:40 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
    Apr 12 14:15:40 bigbird kernel: device eth0 left promiscuous mode
    Apr 12 14:15:40 bigbird kernel: bond0: now running without any active interface!
    Apr 12 14:15:40 bigbird kernel: br0: port 1(bond0) entered disabled state
    Apr 12 14:15:44 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
    Apr 12 14:15:44 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
    Apr 12 14:15:44 bigbird kernel: bond0: (slave eth0): making interface the new active one
    Apr 12 14:15:44 bigbird kernel: device eth0 entered promiscuous mode
    Apr 12 14:15:44 bigbird kernel: bond0: active interface up!
    Apr 12 14:15:44 bigbird kernel: br0: port 1(bond0) entered blocking state
    Apr 12 14:15:44 bigbird kernel: br0: port 1(bond0) entered forwarding state
    Apr 12 14:15:46 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
    Apr 12 14:15:46 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
    Apr 12 14:15:46 bigbird kernel: device eth0 left promiscuous mode
    Apr 12 14:15:46 bigbird kernel: bond0: now running without any active interface!
    Apr 12 14:15:46 bigbird kernel: br0: port 1(bond0) entered disabled state
    Apr 12 14:15:50 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
    Apr 12 14:15:50 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
    Apr 12 14:15:50 bigbird kernel: bond0: (slave eth0): making interface the new active one
    Apr 12 14:15:50 bigbird kernel: device eth0 entered promiscuous mode
    Apr 12 14:15:50 bigbird kernel: bond0: active interface up!
    Apr 12 14:15:50 bigbird kernel: br0: port 1(bond0) entered blocking state
    Apr 12 14:15:50 bigbird kernel: br0: port 1(bond0) entered forwarding state
    Apr 12 14:15:52 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
    Apr 12 14:15:52 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
    Apr 12 14:15:52 bigbird kernel: device eth0 left promiscuous mode
    Apr 12 14:15:52 bigbird kernel: bond0: now running without any active interface!
    Apr 12 14:15:52 bigbird kernel: br0: port 1(bond0) entered disabled state
    Apr 12 14:15:56 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
    Apr 12 14:15:56 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
    Apr 12 14:15:56 bigbird kernel: bond0: (slave eth0): making interface the new active one
    Apr 12 14:15:56 bigbird kernel: device eth0 entered promiscuous mode
    Apr 12 14:15:56 bigbird kernel: bond0: active interface up!
    Apr 12 14:15:56 bigbird kernel: br0: port 1(bond0) entered blocking state
    Apr 12 14:15:56 bigbird kernel: br0: port 1(bond0) entered forwarding state
    Apr 12 14:15:57 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
    Apr 12 14:15:57 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
    Apr 12 14:15:57 bigbird kernel: device eth0 left promiscuous mode
    Apr 12 14:15:57 bigbird kernel: bond0: now running without any active interface!
    Apr 12 14:15:57 bigbird kernel: br0: port 1(bond0) entered disabled state
    Apr 12 14:16:02 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
    Apr 12 14:16:02 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
    Apr 12 14:16:02 bigbird kernel: bond0: (slave eth0): making interface the new active one
    Apr 12 14:16:02 bigbird kernel: device eth0 entered promiscuous mode
    Apr 12 14:16:02 bigbird kernel: bond0: active interface up!
    Apr 12 14:16:02 bigbird kernel: br0: port 1(bond0) entered blocking state
    Apr 12 14:16:02 bigbird kernel: br0: port 1(bond0) entered forwarding state
    Apr 12 14:16:03 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
    Apr 12 14:16:03 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
    Apr 12 14:16:03 bigbird kernel: device eth0 left promiscuous mode
    Apr 12 14:16:03 bigbird kernel: bond0: now running without any active interface!
    Apr 12 14:16:03 bigbird kernel: br0: port 1(bond0) entered disabled state
    Apr 12 14:16:07 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
    Apr 12 14:16:07 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
    Apr 12 14:16:07 bigbird kernel: bond0: (slave eth0): making interface the new active one
    Apr 12 14:16:07 bigbird kernel: device eth0 entered promiscuous mode
    Apr 12 14:16:07 bigbird kernel: bond0: active interface up!
    Apr 12 14:16:07 bigbird kernel: br0: port 1(bond0) entered blocking state
    Apr 12 14:16:07 bigbird kernel: br0: port 1(bond0) entered forwarding state
    Apr 12 14:16:09 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Down
    Apr 12 14:16:09 bigbird kernel: bond0: (slave eth0): link status definitely down, disabling slave
    Apr 12 14:16:09 bigbird kernel: device eth0 left promiscuous mode
    Apr 12 14:16:09 bigbird kernel: bond0: now running without any active interface!
    Apr 12 14:16:09 bigbird kernel: br0: port 1(bond0) entered disabled state
    Apr 12 14:16:13 bigbird kernel: r8169 0000:28:00.0 eth0: Link is Up - 2.5Gbps/Full - flow control off
    Apr 12 14:16:13 bigbird kernel: bond0: (slave eth0): link status definitely up, 2500 Mbps full duplex
    Apr 12 14:16:13 bigbird kernel: bond0: (slave eth0): making interface the new active one
    Apr 12 14:16:13 bigbird kernel: device eth0 entered promiscuous mode
    Apr 12 14:16:13 bigbird kernel: bond0: active interface up!
    Apr 12 14:16:13 bigbird kernel: br0: port 1(bond0) entered blocking state
    Apr 12 14:16:13 bigbird kernel: br0: port 1(bond0) entered forwarding state

     

    Link to comment
    20 minutes ago, ThatDude said:

    I'm having lot of issues with my PCI-E add-in 2.5GB network card on RC4.

    There are a few of us that have reported 2.5gb network issues with RC4 but as yet no one has acknowledged this.

    So far it seems tied to the RTL8156, is this your chipset?

    Link to comment
    7 minutes ago, mdrodge said:

    There are a few of us that have reported 2.5gb network issues with RC4 but as yet no one has acknowledged this.

    So far it seems tied to the RTL8156, is this your chipset?

     

    Mine is detected as RTL8125

     

    [10ec:8125] 28:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller

     

    Link to comment
    On 4/8/2022 at 11:47 PM, Darksurf said:

    OK, I think I've found whats causing me grief since my upgrade from 6.9.2 . I use a docker that uses /dev/sr0 to rip blurays and dvd's for me.  Sometimes I put in a disc and that docker hangs and locks up all other dockers, I get zombie processes I cannot SIGKILL, and I'm forced to reboot to clean it up and get the docker working again. What I've noticed is this:

    [  324.178091] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
    [  324.190405] sr 0:0:0:0: [sr0] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s
    [  324.190410] sr 0:0:0:0: [sr0] tag#0 CDB: opcode=0x28 28 00 00 00 04 00 00 00 02 00
    [  324.190412] blk_update_request: I/O error, dev sr0, sector 4096 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
    [  354.383938] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd
    [  473.812944] udevd[1688]: worker [27853] /devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb4/4-1/4-1:1.0/host0/target0:0:0/0:0:0:0/block/sr0 timeout; kill it
    [  473.812954] udevd[1688]: seq 11256 '/devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb4/4-1/4-1:1.0/host0/target0:0:0/0:0:0:0/block/sr0' killed

     

    I've never seen udev do this before in 6.9.2 . Is this due to my new bluray drive, or is this due to 6.10.0-rc4 ? This is entirely new behavior to me. to generate diagnostics, I'm required to power off the bluray drive (/dev/sr0) to continue otherwise it hangs there. Anyone got any ideas?

    oceans-diagnostics-20220408-2342.zip

     

    @limetech

    I've found the exact issue! I've been experiencing the exact same issues on my desktop. While researching the issue I found someone else experiencing this in other distros too. In the persistent storage udev rules on how optical drives are handled, I've tweaked the udev rules as recommended here: https://forum.makemkv.com/forum/viewtopic.php?t=25357
     

    My desktop is back to working as it should and no longer freeze/hangs on the external Bluray drives. This should also fix unraid too.

     

    TLDR:

    sr* lines in /lib/udev/60-persistent-storage.rules

    # probe filesystem metadata of optical drives which have a media inserted
    KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="?*", \
      IMPORT{builtin}="blkid --offset=$env{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}"
    # single-session CDs do not have ID_CDROM_MEDIA_SESSION_LAST_OFFSET
    KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="", \
      IMPORT{builtin}="blkid --noraid"

    becomes

    # probe filesystem metadata of optical drives which have a media inserted
    KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="?*", \
      GOTO="persistent_storage_end"
    # single-session CDs do not have ID_CDROM_MEDIA_SESSION_LAST_OFFSET
    KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="", \
      GOTO="persistent_storage_end"
    

     

    My desktop is now able to view/play/rip blurays and dvds again. Evidently the IMPORT lines can cause hanging when certain video discs are placed in the drive. This explains why udevd hangs and begins killing /dev/sr0 when certain discs are inserted.

    Link to comment
    4 hours ago, ThatDude said:

    Mine is detected as RTL8125

     

    So Realtek RTL8156 and RTL8125 based NIC's both broken by rc4

    @limetechUrgent  😃 

    Link to comment
    1 hour ago, mdrodge said:

    So Realtek RTL8156 and RTL8125 based NIC's both broken by rc4

    @limetechUrgent  😃 

     

    I wish to share a bit of ancient history (actually about seven years ago) with those folks who are having problems with RealTek NIC's (as I remember it).  RealTek is the low cost manufacturer of NIC's.  RealTek Linux support of their chip sets has been very spotty at best.  Back in those ancient days, LimeTech attempted to figure out whether the RealTek NIC drivers or the ones from the Linux support team provide the most reliable operation.  This required that LimeTech would have to compile the source code for the RealTek driver if there was a problem with the Linux kernel one.  (For those you may not realize it, Linux source drivers may not compile for every distribution of the kernel and changes to the code are often required to get it to do so!)   In the end, because of resource and time constraints, LimeTech made a decision at that point in time that they would only use the Linux kernel drivers.  (For those folks who had problems they could not live with, they would have to find another NIC solution.**) 

     

    I don't know if LimeTech has changed their position in the past seven years but I would tend to suspect that they have not.  If they have not, you might want to consider taking up the issue with Linux Kernel developers.  (And you may not get a lot of sympathy from those folks either.  RealTek prime support focus is on the Windows universe and Linux is treated as the ugly stepchild...)

     

    ** I was one of those.  I purchased an Intel NIC board to solve my problem!  

    Edited by Frank1940
    Link to comment
    2 hours ago, mdrodge said:

    RTL8125 based NIC's both broken by rc4

    FWIW, my addon 8125 2.5G card works perfectly fine

    [10ec:8125]	07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 04)

     

    Link to comment
    1 hour ago, Squid said:

    FWIW, my addon 8125 2.5G card works perfectly fine

    [10ec:8125]	07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 04)

     

    My one works in Windows and on the Stable but won't show up with RC3 or higher.

    Link to comment
    3 hours ago, Frank1940 said:

     

    I wish to share a bit of ancient history

    Thanks for catching me up.

    I did see that people are reporting this in Linux forums to so hopefully....... ;)

    I was wondered if this was the case.

    Though if nothing else I'd just like the info up here somewhere because once this hits stable there is going to be a few annoyed people wondering what's going on (unless it's been mentioned at least)

     

    Link to comment

    Only a slight annoyance on macOS: 

    Basically, Apple has removed the Xserve glyph in macOS 11. They also haven't brought it back in macOS 12 (released a year later). So it seems to be gone for good now (and it seems like it's rather intentional than being a bug).

    It would be nice if UNRAID could instead use the Mac Pro icon for avahai. (This is also what TrueNAS does)

     

    The current Xserve glyph only shows up as a "file" icon which can be confusing to some users.

     

    "model=Xserve" in "/etc/avahi/services/smb.service" would need to be replaced with: "model=MacPro7,1@ECOLOR=226,226,224"

     

    There's some more information here:

     

    Link to comment
    On 3/20/2022 at 1:16 AM, Gingko_2001 said:

    When upgrade from RC3 to RC4,

     

    Saw this error message,  I manually downloaded the Nvidia driver,  then reboot the system.  System boot up fine.

     

    Just put here,  in case someone see this, you have to manually download the Nvidia driver, otherwise may have problem when system boots up.

     

    error.png.d03abdbd437d6862c54d4194c7460f54.png

    What do you mean by manually downloading?

    do you mean using this app?

    imagen.png.71f18f1954a6e7460aad97e191ac3bcc.png

    Is this app compatible with 6.10?

     

    If the manual method is another one could you please specify how you did it?

    Thanks

    Link to comment
    7 minutes ago, wgstarks said:

    Yes

    So why unraid 6.10 uninstalled this plugin?

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

    So why unraid 6.10 uninstalled this plugin?

    That would probably be a question for the app support thread. I’m using it without any issues in RC4.

    Link to comment

    Interface rules missing until network-rules.cfg has been created manually:

     

     

    Link to comment

    Anybody else suddenly getting PCI Express errors on a NVMe drive since upgrading to RC4?

     

    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Multiple Corrected error received: 0000:00:1b.4
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:   device [8086:a3eb] error status/mask=00000041/00002000
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:    [ 6] BadTLP                
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:   device [8086:a3eb] error status/mask=00000001/00002000
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:03:00.0
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:   device [2646:2263] error status/mask=00000001/0000e000
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:   device [8086:a3eb] error status/mask=00000001/00002000
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:03:00.0
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:   device [2646:2263] error status/mask=00000001/0000e000
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:   device [8086:a3eb] error status/mask=00000001/00002000
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:03:00.0
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:   device [2646:2263] error status/mask=00000001/0000e000
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:   device [8086:a3eb] error status/mask=00000001/00002000
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:03:00.0
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:   device [2646:2263] error status/mask=00000001/0000e000
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:   device [8086:a3eb] error status/mask=00000001/00002000
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:03:00.0
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:   device [2646:2263] error status/mask=00000001/0000e000
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:   device [8086:a3eb] error status/mask=00000001/00002000
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:03:00.0
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:   device [2646:2263] error status/mask=00000001/0000e000
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:   device [8086:a3eb] error status/mask=00000001/00002000
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:03:00.0
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:   device [2646:2263] error status/mask=00000001/0000e000
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:   device [8086:a3eb] error status/mask=00000001/00002000
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:03:00.0
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:   device [2646:2263] error status/mask=00000001/0000e000
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:   device [8086:a3eb] error status/mask=00000001/00002000
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:03:00.0
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:   device [2646:2263] error status/mask=00000001/0000e000
    Apr 18 18:34:03 Tower kernel: nvme 0000:03:00.0:    [ 0] RxErr                 
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
    Apr 18 18:34:03 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)

     

    Sometimes when this happens, the drive somehow "gets dropped" - it's still visible in the drive overview in the UI, yet I can't access it anymore and it's missing in /mnt.

    Link to comment
    On 4/18/2022 at 5:39 PM, Pillendreher said:

    getting PCI Express errors on a NVMe drive

    That looks like a hardware problem to me.

    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.