October 26Oct 26 6 minutes ago, FlamongOle said:Upgraded to 7.3.4 from 7.3.3, server starts but I can't access webgui anymore, and logs are filled up with:Please start a thread in the general support forum; and if you cannot get the diagnostics, see if you can get the syslog:cp /var/log/syslog /boot/syslog.txt
October 26Oct 26 5 hours ago, Mainfrezzer said:Eli stole the header fade once again.I noticed the same
October 27Oct 27 19 hours ago, Mainfrezzer said:Eli stole the header fade once again.Yes he did. I didn't notice, but just checked. I had not noticed, as I had the banner image turned off on my backup/test server when it was broken last time.
October 27Oct 27 i cant seem to update from 7.3.2 i keep getting across all my unraids something went wrongand since the release page doesnt seem to work for me where i can manually download teh zip file i stuck.. as also my scripts to upgrade from 1 location and update all the unraids at once doesnt 100% always work
October 30Oct 30 11 hours ago, Zonediver said:...and again... no icons...Maybe you can print out some stickers, and stick them on your monitor...🫣
November 1Nov 1 don't know if it is related to this release, just observed a questionable behavior.in "main" tab of the GUI. when i click at symbol for "disk log information".on all hard disks I get the info when calling 192.168.1.20/logterminal/sdb/ --> sh: line 1: ata2[.:]: command not foundon all nvme I get the normal disk info log like usual.is this known? only me having something configured wrong or beeing blind? or could this be a specific bug and needs to be reported? Edited November 1Nov 1 by NoRaid99
November 1Nov 1 Upgraded from 7.3.3. Usually I see the message “safe to reboot” in notification, but I didn’t see any notification message this time. Not even a “do not reboot yet” message. I felt weird about it so waited extra time just to make sure. After reboot, some hardware drivers were missing. Nividia and Nuvoton.After installing the Nvidia plugin, the default recommended production branch is 580.x for some reason. It used to recommend 595.x for my RTX2000 ada.
November 1Nov 1 7 hours ago, NoRaid99 said:in "main" tab of the GUI. when i click at symbol for "disk log information".on all hard disks I get the info when calling 192.168.1.20/logterminal/sdb/ --> sh: line 1: ata2[.:]: command not foundYep, seeing the same thing. With both spinning HDD (spun up) and SATA SSD. No NVMe in this server to try.
November 2Nov 2 18 hours ago, NoRaid99 said:in "main" tab of the GUI. when i click at symbol for "disk log information".This is a known issue, tracked here: https://product.unraid.net/p/error-when-clicking-on-drive-icon-on-main-page-to-display-disk-log-information-release-7-3-3
November 3Nov 3 I upgraded three servers to v7.3.4: two from v7.3.3 and one from v7.3.2. The two coming from v7.3.3 were fine. The server coming from v7.3.2 had one issue: its 10GbE QLogic card (cLOM8214, rev 54, an NC523SFP-style 2-port adapter) is no longer detected. I had a similar problem on my previous upgrade. The NVIDIA driver updated from v580.173.20 to v580.196.07 and worked without problems. The array, docker containers and everything else appear to be working.SymptomsMany PCIe bus errors scroll by during boot, before Unraid finishes starting.In Tools > System Devices, the 10GbE card shows as “Device change action / removed.”What I triedShut down, removed the card, and powered on.Went to Tools > System Devices and clicked “Acknowledge all PCI changes.”Shut down, reinstalled the card, and powered on.Went back to System Devices and clicked “Acknowledge all PCI changes” again.Rebooted.Result: The card no longer shows up at all.What the diagnostics logs show (captured after the first reboot on v7.3.4)The card is not enumerated at all. system/lspci.txt has no 01:00.x or QLogic entries, and logs/syslog.txt has no 0000:01:00 or qlcnic lines. system/lsmod.txt shows qlcnic is not loaded. config/pci_diffs.json lists both functions (01:00.0 and 01:00.1, 1077:8020) as “removed.”It worked on v7.3.2. logs/syslog-previous.txt (the Oct 11 boot, kernel 6.18.38) shows the card binding to qlcnic at 01:00.0 with driver v5.3.66 and firmware v4.20.1, identified as an NC523SFP 10Gb 2-port adapter, chip rev 0x54. The v7.3.4 kernel is 6.18.58 (system/ethtool.txt).Root port 00:01.0 (Intel Xeon E5 v3), which the card sits behind, is flooding fatal errors. logs/syslog.txt has 3,108 “Uncorrectable (Fatal), Data Link Layer” events with status SDES (surprise link down). Each is followed by “Root Port link has been reset” and “device recovery successful.”The link was already marginal on v7.3.2. logs/syslog-previous.txt shows it trained at 2.5 GT/s x8, although the card is capable of 5.0 GT/s.The syslog is truncated. logs/syslog.txt is capped at 2 MB and the error flood fills it, so the early boot lines are cut off. The first retained line is already mid-flood.NVIDIA is fine. system/nvidia-smi.txt shows driver 580.196.07 and a normal GPU listing (GTX 960 and GTX 1060).End Result: Removed the card from the server. server-diagnostics-20261102-1201.zip
November 3Nov 3 1 hour ago, chris1259 said:The server coming from v7.3.2 had one issue: its 10GbE QLogic card (cLOM8214, rev 54, an NC523SFP-style 2-port adapter) is no longer detected.The thread is not the right place for troubleshooting that requires back and forth, please start a new thread in the general support forum and repost the diagnostics there.
November 4Nov 4 I don't understand, unraid says an update to 7.2.4 is available?Why don't i see this 7.3.4? (I'm currently on 7.0.1)
November 4Nov 4 1 hour ago, jowi said:Why don't i see this 7.3.4What licence do you have, and are you still within the support period you paid for?
November 4Nov 4 As far as i know i have an unlimited license? But if i go to the update section i get redirected to https://account.unraid.net/serverand there i can select 7.3.4... weird.
November 4Nov 4 3 minutes ago, jowi said:and there i can select 7.3.4... weird.The upgrade wizard/workflow changed and you're so far back that your current version doesn't know about that, so it showed you the last of the old workflow it knows of.
November 4Nov 4 On 11/3/2026 at 9:27 AM, JorgeB said:The thread is not the right place for troubleshooting that requires back and forth, please start a new thread in the general support forum and repost the diagnostics there.Sorry for the confusion. This was a warning, not a request for support :-)
November 4Nov 4 17 minutes ago, chris1259 said:This was a warning, not a request for support :-)Roger that, but if the card stopped being detected by lspci, this is not a software issue, most likely it happened due to the reboot, but if you want to discuss it further, please create a new topic.
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.