ljm42

Where are you seeing that? in https://forums.unraid.net/bug-reports/stable-releases/612456-major-gui-delays-after-upgrade-specially-dashboard-docker-and-apps-tab-r2660/page/2/?tab=comments#comment-26836 , they say running that command is slow on their 6.12.3 server as well

My interpretation of https://forums.unraid.net/bug-reports/stable-releases/612456-major-gui-delays-after-upgrade-specially-dashboard-docker-and-apps-tab-r2660/page/2/?tab=comments#comment-26836 is that CiscoCoreX has two servers (one on 6.12.3 and one on 6.12.6) that both take about 6 seconds to run this command: time echo 1 > /boot/test.xml Not sure why they are so slow (maybe they are slow flash drives?) but as long as the webgui limits writes to the flash drive it sounds like the slowness doesn't cause noticeable issues. It feels like this is a hardware issue with those specific flash drives and not a kernel issue. In order to prove whether a linux kernel update caused the slowness, we would need to see the results of that command from the same flash drive on the some server under two different versions of Unraid. FWIW, on my 6.12.6 system the results are quite fast: # time echo 1 > /boot/test.xml real 0m0.132s user 0m0.000s sys 0m0.001s

The kernel version is listed in the release notes for each Unraid version: https://docs.unraid.net/unraid-os/release-notes/6.12.6/ But the kernel version is not what fixed the issue when downgrading. It is that the older release didn't have this webgui code:

Those SQUASHFS errors mean the system isn't able to read the bz files on the flash drive. That flash drive is probably bad, but you could try moving it to a different port

Looking at the diags ending in 1149, I see some issues with disks that somebody else might be able to help with: Dec 5 22:21:57 TrueSource kernel: ata6.00: exception Emask 0x0 SAct 0x80ff8001 SErr 0x0 action 0x0 Dec 5 22:21:57 TrueSource kernel: ata6.00: irq_stat 0x40000008 Dec 5 22:21:57 TrueSource kernel: ata6.00: failed command: READ FPDMA QUEUED Dec 5 22:21:57 TrueSource kernel: ata6.00: cmd 60/00:78:c8:4c:23/04:00:cf:01:00/40 tag 15 ncq dma 524288 in Dec 5 22:21:57 TrueSource kernel: res 41/40:00:40:4d:23/00:00:cf:01:00/00 Emask 0x409 (media error) <F> Dec 5 22:21:57 TrueSource kernel: ata6.00: status: { DRDY ERR } Dec 5 22:21:57 TrueSource kernel: ata6.00: error: { UNC } Dec 5 22:21:57 TrueSource kernel: ata6.00: configured for UDMA/133 Dec 5 22:21:57 TrueSource kernel: sd 6:0:0:0: [sds] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s Dec 5 22:21:57 TrueSource kernel: sd 6:0:0:0: [sds] tag#15 Sense Key : 0x3 [current] Dec 5 22:21:57 TrueSource kernel: sd 6:0:0:0: [sds] tag#15 ASC=0x11 ASCQ=0x4 Dec 5 22:21:57 TrueSource kernel: sd 6:0:0:0: [sds] tag#15 CDB: opcode=0x88 88 00 00 00 00 01 cf 23 4c c8 00 00 04 00 00 00 Dec 5 22:21:57 TrueSource kernel: I/O error, dev sds, sector 7770164424 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 2 Dec 5 22:21:57 TrueSource kernel: md: disk7 read error, sector=7770164360 Dec 5 22:21:57 TrueSource kernel: md: disk7 read error, sector=7770164368 Dec 5 22:21:57 TrueSource kernel: md: disk7 read error, sector=7770164376 Dec 5 22:21:57 TrueSource kernel: md: disk7 read error, sector=7770164384 Dec 5 22:21:57 TrueSource kernel: md: disk7 read error, sector=7770164392 ... Dec 6 02:48:39 TrueSource kernel: sd 13:0:1:0: [sdc] tag#1192 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Dec 6 02:48:39 TrueSource kernel: sd 13:0:1:0: [sdc] tag#1192 Sense Key : 0x5 [current] Dec 6 02:48:39 TrueSource kernel: sd 13:0:1:0: [sdc] tag#1192 ASC=0x21 ASCQ=0x0 Dec 6 02:48:39 TrueSource kernel: sd 13:0:1:0: [sdc] tag#1192 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Dec 6 02:48:39 TrueSource kernel: critical target error, dev sdc, sector 1950420992 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2 Dec 6 02:48:39 TrueSource kernel: BTRFS warning (device sdt1): failed to trim 1 device(s), last error -121 Shortly after that there are a bunch of errors from php-fpm and nginx, which led to the error 500's you were seeing. I am not sure if a disk issue can cause these php/nginx errors I do see this system has a Realtek RTL8168h/8111h network card, I'd suggest trying the alternate drivers for that nic: https://forums.unraid.net/topic/141349-plugin-realtek-r8125-r8168-and-r81526-drivers/

This system has a RTL8125B nic, I'd suggest trying the alternate drivers for that nic: https://forums.unraid.net/topic/141349-plugin-realtek-r8125-r8168-and-r81526-drivers/

Most likely the system is having issues with macvlan. Navigate to Settings > Docker, switch to advanced view, and change the "Docker custom network type" from macvlan to ipvlan. This is the default configuration that Unraid has shipped with since version 6.11.5 and should work for most systems. For more details see https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces

Delete config/wireguard/wg1.* from the flash drive and then refresh the page

You are having issues with SSL and DNS. After disabling SSL like JorgeB recommended you should be able to access the server via: http://10.10.10.10 (note: http not https) Then follow the instructions here: https://docs.unraid.net/unraid-os/manual/security/secure-webgui-ssl/ to enable SSL with a custom certificate. Note that servername + localTLD has to be listed in the custom SSL cert. And the network has to provide a DNS entry that resolves to the server's IP.

This feels like something specific to your environment that may not be automatically solved by a new release. It is up to you, but if you'd like to keep going here's what I'd recommend... Setup a new flash drive with 6.12.6 and boot into a default config. Navigate around the webgui and see how it responds. If this all works fine, then that points to a configuration issue with your server that we can work to isolate. If it is still slow, I would start by focusing on your client. Try accessing the server from private/incognito mode, or a different browser or even a different computer. The webgui did change, so it is possible that browser extensions or security software on the client could be causing issues with the updated webgui. Either way, be sure to grab diagnostics while in this state.

Please note there is nothing anybody can recommend without seeing diagnostics that show the problem

It looks like you've been with us for a while so I'd recommend navigating to Settings > Docker, switching to advanced view, and changing the "Docker custom network type" from macvlan to ipvlan. This is the default setting that Unraid 6.11 ships with. This will prevent crashes related to macvlan call traces, I'm not sure if the slowdowns you are seeing are possibly related to macvlan issues. If that doesn't help, since htop is pointing at the unraid-api I'd suggest uninstalling the Connect plugin to see if that helps. It may be a symptom of the problem and not the cause, but might as well rule it out.

The OpenZFS team has published a true fix (rather than just a mitigation) for the ZFS data corruption issue, so we are publishing Unraid 6.12.6 with that fix. This also includes an IPv6 bug fix. All users are encouraged to read the release notes and upgrade. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.4, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (issues related to Docker not stopping should be resolved in this release) Go to Tools -> Update OS. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip. Release Notes

Are you using a statically assigned IPv6 address? We just tracked down an issue related to that, although DHCP and SLAAC should work fine. This will be fixed in the next release: https://forums.unraid.net/bug-reports/prereleases/bugs-with-ipv6-in-6125-rc1-r2742/?tab=comments#comment-26714 If you don't have a statically assigned IPv6 address, please start a new thread in general support and include your diagnostics along with a description of the problem. This release thread is not meant for support.

Sorry, I originally replied based on your post in this thread as it had no hints about the other communication. I just commented on your thread, this issue will be resolved in the next release https://forums.unraid.net/topic/145859-after-upgrade-troubles-with-ipv6/#comment-1332834

Ah, looks like you have a statically assigned IPv6 address. We just tracked down an issue with that, it will be fixed in the next release: https://forums.unraid.net/bug-reports/prereleases/bugs-with-ipv6-in-6125-rc1-r2742/?tab=comments#comment-26714

Thanks for the diagnostics, they allowed us to track this down. DHCP and SLAAC work fine for IPv6 but there is an issue with statically assigned IPv6 addresses that will be fixed in the next release.

Jumbo frames (especially on eth0) can cause many issues, reverting the MTU to 1500 is likely what solved the problem. BTW, the Fix Common Problems plugin is great for detecting configuration issues like this, it would have sent you here: https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/#comment-1167702

Not much to go on there, we really need your diagnostics. The next time you upgrade, be sure to grab diagnostics and then start a new topic in general support where you detail the issue. It is very difficult to do back and forth support in this release thread.

This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip.

You can just uninstall/reinstall the nvidia plugin

If a different system is managing everything, generate the config in that system and then click the "Import Tunnel" button in the upper right corner of the Settings -> VPN Manager page.

We are watching it. As we are unsure when a new version of ZFS will be available we have published Unraid 6.12.5 with a mitigation in place (details in the release notes)

The Unraid 6.12.5 release includes a mitigation for a ZFS data corruption issue, along with other bug fixes and security updates. All users are encouraged to read the release notes and upgrade. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.4, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (issues related to Docker not stopping should be resolved in this release) Go to Tools -> Update OS. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip. Release Notes

Please see my comment earlier in this thread