• Unraid OS version 6.10.0-rc5 available


    limetech

    Listening to the Community we decided to remove the requirement for all users to register their server with an Unraid.net account.  Making use of the My Servers plugin, providing a growing number of online-enabled features, does still require use of an Unraid.net account.

     

    Upon upgrade to this release, users who currently have the My Servers plugin installed should upgrade the plugin on their server(s). Servers without the plugin will no longer need, or be able to sign in to Unraid.net and as timeouts kick in, they will automatically be removed from the My Servers Dashboard and disassociated with your Unraid.net account. To continue using the My Servers Dashboard please install the My Servers plugin.

     

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

     


    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 better manage their registration keys and install the optional My Servers plugin.

     

    My Servers is what we call our set of cloud-based services and features that integrate with your Unraid server(s).  After installing the My Servers plugin, you will be prompted to sign-in your server with an existing Unraid.net account, or create a new Unraid.net account.  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. 
    • Local Access link - this is a direct link the the server webGUI on your LAN.
    • 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.
    • 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.
    • Posting privilege in a new set of My Servers forum boards.

     

    Signed-in servers maintain a websocket connection to a cloud-based Lime Technology proxy server for the purpose of relaying real-time status.  Refer to the Privacy section for more information.
     

    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.

     

    [rc5] Resident network guru @bonienl has added the capability to bind a Wireguard virtual network interface to a docker container.  One use of this feature is to configure a Wireguard-enabled VPN which may then be exclusively used by that container, while you main server makes use of the normal LAN network interface.  Please refer to this post for additional details.

     

    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). 

     

    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.
    • There is no longer a requirement for the server to actively update a DDNS server.
    • 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 the new the URL.  Alternately, if you have installed the My Servers plugin, a local access link is included for each server on your Dashboard.  If you have not installed My Servers plugin, since there is no DDNS update daemon, we recommend setting up either a static DHCP lease, or assign a static IP address for your server.  Finally, we have set up nginx such that the URL's:

    • http://<server-name>.<local-tld>/

    or

    • https://<server-name>.<local-tld>/

    will redirect to https://[lan-ip].[hash].myunraid.net

     

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

     

    Linux Kernel

    Upgrade to [rc4] Linux 5.15.x 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

    [rc5] Support Realtek RTL8152/RTL8153 Based USB Ethernet Adapters

     

    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", however is disabled by default.  This may be enabled on the Settings/SMB Settings page.  Some users have reported issues with SMB3 multi-channel in conjunction with certain network bond configurations.

     

    [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.
    • 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.  Terminal font size is configurable via Settings/Display Settings page.
    • [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] Enabled NFSv4 support.

    • [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.

    • [rc5] Fixed a bug where replacing a device in a multiple-device btrfs pool would still tag the old device as missing.

    • [rc5] Fixed an issue where hot plugging a device in a server with spun-down SAS drive(s) could cause the SAS drive(s) to appear unassigned.

    • [rc5] Fixed an issue where the server would disappear from Windows Network after docker and/or VM startup.

    • [rc5] Fixed md/unraid driver regression which would confuse XFS, making it think an online shrink had occurred.

    • [rc5] Fixed: Prevent Unraid from hanging when the array is stopped, while VMs are in paused or suspended state.

    • Numerous other small bug fixes and improvements.

     

    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.

    @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-rc5 2022-04-26 (vs. 6.10.0-rc4)

    Base distro:

    • at: version 3.2.3
    • bind: version 9.16.27
    • btrfs-progs: version 5.16
    • ca-certificates: version 20220403
    • ethtool: version 5.16
    • eudev: version 3.2.11
    • git: version 2.35.3-x86_64-1 (CVE-2022-24765)
    • glib2: version 2.70.3
    • glibc-zoneinfo: version 2022a
    • gzip: version 1.12-x86_64-1 (CVE-2022-1271)
    • haveged: [removed]
    • hdparm: version 9.63
    • iproute2: version 5.16.0
    • libarchive: version 3.6.1-x86_64-1
    • libgpg-error: version 1.44
    • libunwind: version 1.6.2
    • libwebp: version 1.2.2
    • libxml2: version 2.9.13
    • libxslt: version 1.1.35
    • openssl: version 1.1.1n
    • openssl-solibs: version 1.1.1n
    • p11-kit: version 0.24.1
    • pango: version 1.48.11
    • sudo: version 1.9.9
    • tdb: version 1.4.6
    • util-linux: version 2.37.4
    • wsdd2: version 20111022 build 2
    • xz: version 5.2.5-x86_64-4 (CVE-2022-1271)
    • zlib: version 1.2.12
    • zstd: version 1.5.2

    Linux kernel:

    • Linux 5.15.35-Unraid
    • added CONFIG_USB_RTL8152: Realtek RTL8152/RTL8153 Based USB Ethernet Adapters

    Management:

    • emhttpd: fix btrfs pool device replace still showing 'missing'
    • rc.docker: fix startup network race condition
    • rc.libvirt: Prevent Unraid from hanging when the array is stopped, while VMs are in paused or suspended state
    • rc.nginx: read IP address from management interfact (eth0) only
    • rc.samba: disable SMB Multi Channel by default; add control to Settings/SMB Settings page
    • ttyd: fix garbled text in local FireFox Termainl windows
    • upc: refactor(upc):base-6.10 remove sign in requirement
    • webgui: improve: Highlight selected row when hovering over array or shares
    • webgui: Right-clicking or long-clicking a menu item should open the selected menu
    • webgui: Make links in help text standout (red)
    • webgui: Update Outlook/Hotmail smtp settings
    • webgui: UpdateDNS to prefer IPv4 first and then IPv6
    • webgui: Allow simultaneous log and console windows for containers
    • webgui: Fixed: missing samesite attribute in cookies
    • webgui: WireGuard: user nginx settings and unraid.net api
    • webgui: Parity: shown duration time excluding idle time
    • webgui: Miscellaneous updates and fixes
    • webgui: fix: password lockouts not being cleared properly
    • webgui: Support future T2FA
    • webgui: Expand file type icon selection
    • webgui: Show IP on VM Manager VM Page
    • webgui: Docker: Silence PHP errors when editing a template if corruption exists
    • webgui: Fixed PHP errors for share and disk calculations
    • webgui: Main page - lower table update frequency for better responsiveness of links
    • webgui: Change page switching to better suit Safari on mobile devices
    • webgui: Set Main page update frequency to 1s for better support of mobile devices
    • webgui: Docker settings: suppress browser presets
    • webgui: Lower update frequency of monitor function to better suit mobile devices
    • webgui: Docker: fixed list display in fixed view mode
    • webgui: Docker: fixed header display causes gap
    • webgui: WireGuard updates:
      1. Make import config file of VPN providers more robust.
      2. Add tunnel routing for docker containers
      3. Automatically make the WG tunnel available to containers (custom network)
    • webgui: WireGuard: Introduce new network modes:
      1. VPN tunneled access for system
      2. VPN tunneled access for docker
    • webgui: WireGuard: Add warning when tunnel deletion fails
    • webgui: WireGuard: use kill switch when tunnel inactive
    • webgui: Docker: add route for remote WireGuard access
      • Containers with network 'br0' can be remotely accessed by WireGuard without the need to configure static routes on the home router (gateway)
      • "Host access to custom networks" must be enabled to allow access
    • webgui: WireGuard: add logic to recreate networks after reboot
    • webgui: Docker: add route for remote WireGuard access
    • webgui: Wireguard: make management interface seletable
      • Defaults to eth0 - future expansion
    • webgui: Docker: add wireguard description in network selection
    • webgui: diagnostics: fix: anonymize myunraid.net urls
    • webgui: BTRFS balance: fix recommendation message when volume is empty
    • webgui: Log docker icon download failures
    • webgui: Docker: add description to all custom networks
    • webgui: Management: fix ports in use check
    • webgui: Fixed: specific disk settings for pool devices only
    • Like 13
    • Thanks 5
    • Upvote 2



    User Feedback

    Recommended Comments



    Upgraded to RC5 but none of my Plex containers would start. After a bit of troubleshooting it seems it wouldn't download the nvidia drivers and since I used that for transcoding the containers wouldn't start.

    I tried mucking around with the plugin a little but after maybe an hour of trying to force a download of the plugin and a few reboots I rolled back to RC4 and my containers started without issue and the Nvidia plugin page listed the device ID and driver version.

    Link to comment
    3 hours ago, omygoodness said:

    Upgraded from RC4 on Alder Lake Platform. Everything works. No problems with Plex transcoding at all.

    Do you pass through the igpu to Plex container and use hardware transcoding?

     

    Link to comment
    13 hours ago, Driconis said:

    Unsuccessfully attempted to upgrade from rc3

     

    6 hours ago, greenflash24 said:

    rollbacked to -rc4

    These posts would have been more useful with diagnostics.

    Link to comment

    I tried upgrading from rc4 to rc5 but it detects one of my array drives, my cache drive and a spare drive as "wrong". When I select them from the list the array drive says it will be re-built. Not sure why this is so I rolled back to rc4 and it all works ok now.

    Link to comment
    3 minutes ago, jimsefton said:

    I tried upgrading from rc4 to rc5 but it detects one of my array drives, my cache drive and a spare drive as "wrong". When I select them from the list the array drive says it will be re-built. Not sure why this is so I rolled back to rc4 and it all works ok now.

    need diagnostics from rc5.

    Link to comment
    21 hours ago, limetech said:

    From your link does not look like kernel issue.  If you are following this, please alert us if they come up with a solution that requires us to change something.  Best way to alert would be to create a separate Bug Report and then update if the situation changes.  thx

    @limetech The Plex devs have come back this morning and said that the fix to the Alder Lake iGPU for Plex transcodes will be part of the 5.18 Kernal release.

    With the 5.18 kernal being released end of May, im hoping that you might be able to include 5.18 as part of your 6.11 RC1 release ;-)

     

    https://forums.plex.tv/t/plex-media-server-on-ubuntu-21-10-with-intel-12th-gen-alder-lake/768123/12

     

    • Like 2
    Link to comment
    1 minute ago, jimsefton said:

    ok, I got them, do I attach the whole zip file or something specific from inside it?

     

    Please open a new topic and attach the complete zip file.

    In addition I like to see a screenshot of your Main page with the device names in question.

     

    Link to comment
    6 minutes ago, bonienl said:

     

    Please open a new topic and attach the complete zip file.

    In addition I like to see a screenshot of your Main page with the device names in question.

     

    Done, thanks

    • Thanks 2
    Link to comment
    13 hours ago, Freender said:

    Upgraded from rc4 to rc5 - a few hours later unraid was not available over ssh. I did hard reset and rollbacked to rc4.

    I managed to pull syslog from the Graylog, see attached (let me know if something needs to be obfuscated)

     

    Might be related to this issue - https://lore.kernel.org/netdev/YfQMQWsFqCIPBBqO@boxer/T/

     

    Docker config:

    Docker custom network type: macvlan

    Host access to custom networks: Enabled

    I also use IPv6 

     

    Network Cards:

    IOMMU group 16:[8086:10fb] 01:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)

    IOMMU group 17:[8086:10fb] 01:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)

    syslog_rc5.csv

     

    Starting in -rc4 we moved from the in-tree ixgbe driver to the Intel ixgbe driver.  May or may not be related to this.

    Please open a separate Bug Report for this.  thx

    Link to comment
    12 hours ago, Arbadacarba said:

    Any Chance for Libvert 8.2.0 anytime soon? I had things working in RC2 that have been broken since.

     

     

     

     

     

    Is this going to require upgrading qemu from 6.2.0 to 7.0.0 as well?

     

    Link to comment
    12 minutes ago, limetech said:

    Is this going to require upgrading qemu from 6.2.0 to 7.0.0 as well?

    No, 6.2.0 will be fine.

    Edited by ghost82
    • Thanks 1
    Link to comment
    8 hours ago, trurl said:

     

    These posts would have been more useful with diagnostics.

    Agreed. I was previously unaware that diagnostics can be run from the command line. I have temporarily reinstalled rc5 and attached the file to my original post.

    Link to comment
    On 4/27/2022 at 10:08 AM, theobserver_ said:

    This is what I thought also. But I tried another USB Drive fresh build, and I got a different error, bzroot checksum error. Back on Stable Build from backup with no issues. 

    Screen Shot 2022-04-27 at 5.58.34 PM.png

    Edited yesterday at 10:10 AM by theobserver_ (see edit history)

     

    Try this, looks like the same issue, and it worked also on a Dell:

     

    https://forums.unraid.net/topic/119502-bzimage-checksum-error/?do=findComment&comment=1120488

     

    • Thanks 2
    • Upvote 1
    Link to comment
    23 minutes ago, Driconis said:

    Agreed. I was previously unaware that diagnostics can be run from the command line. I have temporarily reinstalled rc5 and attached the file to my original post.

    Looks like 

     

    ethernet is not stable flapping suggest raising seperate bug report or adding to of the other ixgbe bugs.

     

    Apr 28 17:15:09 Patchogue kernel: bond0: (slave eth0): making interface the new active one

    Apr 28 17:15:09 Patchogue kernel: device eth0 entered promiscuous mode

    Apr 28 17:15:09 Patchogue kernel: bond0: active interface up!

    Apr 28 17:15:09 Patchogue kernel: br0: port 1(bond0) entered blocking state

    Apr 28 17:15:09 Patchogue kernel: br0: port 1(bond0) entered forwarding state

    Apr 28 17:15:09 Patchogue kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down

    Apr 28 17:15:09 Patchogue kernel: bond0: (slave eth0): link status definitely down, disabling slave

    Apr 28 17:15:09 Patchogue kernel: device eth0 left promiscuous mode

    Apr 28 17:15:09 Patchogue kernel: bond0: now running without any active interface!

    Apr 28 17:15:09 Patchogue kernel: br0: port 1(bond0) entered disabled state

    Apr 28 17:15:13 Patchogue kernel: ixgbe 0000:05:00.0 eth0: The link is down

    Apr 28 17:15:13 Patchogue kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 1 Gbps, Flow

    Edited by SimonF
    Link to comment
    13 minutes ago, SimonF said:

    Looks like 

     

    ethernet is not stable flapping suggest raising seperate bug report or adding to of the other ixgbe bugs.

     

    Apr 28 17:15:09 Patchogue kernel: bond0: (slave eth0): making interface the new active one

    Apr 28 17:15:09 Patchogue kernel: device eth0 entered promiscuous mode

    Apr 28 17:15:09 Patchogue kernel: bond0: active interface up!

    Apr 28 17:15:09 Patchogue kernel: br0: port 1(bond0) entered blocking state

    Apr 28 17:15:09 Patchogue kernel: br0: port 1(bond0) entered forwarding state

    Apr 28 17:15:09 Patchogue kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down

    Apr 28 17:15:09 Patchogue kernel: bond0: (slave eth0): link status definitely down, disabling slave

    Apr 28 17:15:09 Patchogue kernel: device eth0 left promiscuous mode

    Apr 28 17:15:09 Patchogue kernel: bond0: now running without any active interface!

    Apr 28 17:15:09 Patchogue kernel: br0: port 1(bond0) entered disabled state

    Apr 28 17:15:13 Patchogue kernel: ixgbe 0000:05:00.0 eth0: The link is down

    Apr 28 17:15:13 Patchogue kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 1 Gbps, Flow

    Nice catch! I compared this with diagnostics I pulled after restoring rc3 and this definitely is not happening on rc3. It's my understanding that those of us running SuperMicro A2SDi series motherboards were unable to successfully install rc4 due to ethernet issues with the newer kernel. The issues with rc4 were so severe that I was not even able to log in via command line, all I could determine was that the ethernet never connected to the network at all. It would seem that there are still some remaining issues to be worked out with this. I guess I will stand pat for now and hopefully the next release will work out better. Thanks again.

    Link to comment
    5 hours ago, Driconis said:

    Nice catch! I compared this with diagnostics I pulled after restoring rc3 and this definitely is not happening on rc3. It's my understanding that those of us running SuperMicro A2SDi series motherboards were unable to successfully install rc4 due to ethernet issues with the newer kernel. The issues with rc4 were so severe that I was not even able to log in via command line, all I could determine was that the ethernet never connected to the network at all. It would seem that there are still some remaining issues to be worked out with this. I guess I will stand pat for now and hopefully the next release will work out better. Thanks again.

    That is the board I have as well.  Trying to debug over ipmi when not wanting a lot of down time was a mistake on my end.  In watching the boot on mine it felt like I never saw it load the driver on boot.  I never saw it like I do in stable.  But what I did see was that it could not enable/find my vlan on my bond interface.

    Link to comment
    On 4/27/2022 at 2:53 AM, emrepolat7 said:

    I really like this "webgui: Show IP on VM Manager VM Page"

    How to see this page with ip other useful info? I have usually page without ip and others...

    Edited by sersh
    Link to comment
    27 minutes ago, sersh said:

    How to see this page with ip other useful info? I have usually page without ip and others...

    Click on the VM name in VM manager.

     

    image.thumb.png.fe216e9392cbd5a7a2c94ee2f26c149d.png

    Link to comment
    20 hours ago, feraay said:

    Do you pass through the igpu to Plex container and use hardware transcoding?

    @feraay Yep. If you need any help just let me know. 

    Edited by omygoodness
    Link to comment
    24 minutes ago, SimonF said:

    Click on the VM name in VM manager.

    Thanks. :)

    Edited by sersh
    Link to comment
    21 hours ago, Dimtar said:

    Upgraded to RC5 but none of my Plex containers would start. After a bit of troubleshooting it seems it wouldn't download the nvidia drivers and since I used that for transcoding the containers wouldn't start.

    Please create a dedicated post on the Nvidia Driver plugin support thread.

    Link to comment

    I upgraded from stable 6.9.2 and I am experiencing a lot of permission issues with Dockers is this expected?

     

    Few examples 

     

     System.Data.SQLite.SQLiteException (0x80004005): attempt to write a readonly database

     

    NzbDrone.Common.Exceptions.RadarrStartupException: Radarr failed to start: AppFolder /config is not writable

     

     A reinstall of the docker and copying over of the config has worked for the one I tried

    Edited by Tyranian
    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.