1 minute ago, JorgeB said:

7.2 will have the same pool errors; it just won't warn you about them.

Oh i see. Thanks for that info. In that case ill upgrade to 7.3 again and make a new post

Pool health is now monitored by Unraid; because of that, users can get a warning that one or more pool devices have issues after upgrading. The upgrade doesn't cause the warnings; they were just not monitored before.

Anyone needing help with that should create a new thread in the general support forum and post the diags.

Hi,
Move boot to internal storage and it created 2 devices when I only have 1 free. Now i cant delete the other and so I can't start the array.

Any help?

Edited May 14May 14 by comedurme

25 minutes ago, comedurme said:

Move boot to internal storage and it created 2 devices when I only have 1 free. Now i cant delete the other and so I can't start the array.

Any help?

Please start a new thread in the general support forum and post the diagnostics.

Hi,

PowerTOP is no longer capable of configuring my SATA controller, despite the fact that it once functioned flawlessly after upgrading to 7.3.0. I get the message "Enable SATA link power management...." Can it be 

The following requirements are not met in one or two cases?

Two prerequisites must be met for automatic activation already during the startup process:

1. The corresponding SATA controller must be declared as board_ahci_low_power^[7] in the Linux source code in the table pci_device_id ahci_pci_tbl.^[8]

2. The SATA Link Power Management Policy must be set to "3 - Medium power with Device Initiated PM enabled".^[9] This is possible in two ways: 

   • Kernel compile-time parameter CONFIG_SATA_MOBILE_LPM_POLICY=3

   • Kernel boot parameter ahci.mobile_lpm_policy=3  

I'm reasonably sure this is a complete coincidence, but documenting here in case it, for some reason, becomes a trend:

Upgraded from 7.2.4 to 7.3.0 and my server never came back online after the reboot. The screenshot (below) says Array Started, so I'm not sure if that means it successfully rebooted and then died, or died prior/during the reboot.

Regardless, the system was stable with an uptime of almost 2 months prior to the upgrade. It now has no video and does not POST. Power Supply tested good. Re-seated all components. Ordered a new motherboard to try tomorrow and determine if that or something else failed.

CPU: AMD Ryzen 5 5600G

MB: MSI B450M PRO-VDH MAX

Edited May 14May 14 by Goatskin

On 5/13/2026 at 2:45 PM, starbetrayer said:

I still see the firefox bug after reboot, you have to restart the session while it works in Edge.

Me too (using Firefox 150.0.3) - sole issue I noticed for upgrade. Are you using Private Windows browsing ?
Using Developer Tools, I can see there is a weird cookie unraid_a97b82555309bfe11e5bcc0da8c7770b with a weird value :
ca_apps_referrer=false; addAlert-text=Attention%20-%20operation%20continues%20in%20background%20%5B00173392%5D%3Ci%20class%3D'fa%20fa-bomb%20fa-fw%20abortOps'%20title%3D%22Abort%20background%20process%22%20onclick%3D'abortOperation(173392)'%3E%3C%2Fi%3E; addAlert-cmd=plugin%20update%20dynamix.unraid.net.plg; addAlert-plg=; addAlert-func=ca_refresh

I hope Firefox 151 will provide a fix.

Upgraded to 7.3.0 - Everything seemed fine, but frigate docker, won't start anymore.
Also, GUI, seems just as sluggish or worse, than before (just feedback)

EDIT:
Turned out, that date and time was somehow reset during the upgrade.
Setting it correctly again, made the frigate docker start without issues.
(/etc/localtime is used by the frigate docker)

Edited May 15May 15 by muggi

4 hours ago, Goatskin said:

AMD Ryzen 5 5600G

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

3 hours ago, ds9 said:

Me too (using Firefox 150.0.3) - sole issue I noticed for upgrade. Are you using Private Windows browsing ?
Using Developer Tools, I can see there is a weird cookie unraid_a97b82555309bfe11e5bcc0da8c7770b with a weird value :
ca_apps_referrer=false; addAlert-text=Attention%20-%20operation%20continues%20in%20background%20%5B00173392%5D%3Ci%20class%3D'fa%20fa-bomb%20fa-fw%20abortOps'%20title%3D%22Abort%20background%20process%22%20onclick%3D'abortOperation(173392)'%3E%3C%2Fi%3E; addAlert-cmd=plugin%20update%20dynamix.unraid.net.plg; addAlert-plg=; addAlert-func=ca_refresh

I hope Firefox 151 will provide a fix.

I am not using Private Browsing

Successfully updated both my servers from 7.2.6 - backup server first just to step through the process.

• just the 7.3 upgrade, made sure everything was working

• Updated to internal boot (dedicated Optane16gb), auto bios update worked and no issues.

• only surprise was that somewhere in all my hardware jumping I'd left the fTPM disabled; Have not switched to TPM key yet, may stick with usb, but no issues enabling that and booting still.

Main server I was a little more nervous about given the vague comments about VLAN issues and docker issues; The above steps were in part to give me confidence I could roll back in a hurry. Regardless, stepped through one at a time and everything went smoothly. All dockers still working properly, including those on VLANs. No issues with powertop, the same blockers for high c-states still there but still hit c3 as before. Both servers offer the option of switching to TPM for the licensing key. Neither having issues with the dedicated boot.

Oh, and no issues accessing the GUI with Firefox 150.0.2/linux - I am using self-signed certs and local dns though, so maybe not quite what others are having issues with. I did verify IP and <servername>.local both work.

I did do a bunch of work ahead of the 7.2.5 update due to a history of odd issues - I think the key changes there were disabling "Host access to custom networks" and finding an alternative solution for the ONE docker which I had requiring it, and possibly dropping the custom MTU on my internal 10g lan port to 1500. The latter speed caps at ~8gb/s vs 9.8gb/s with jumbo packets, but ssd speed is the actual bottleneck anyway so I haven't looked back. I do use macvlan as well for dockers, and had to do a bunch of of manual MAC transcribing. Need to add custom MACs to the ones where it matters less, 'cause it royally screws with the network topology mapping and monitoring.

16 hours ago, JorgeB said:

Pool health is now monitored by Unraid; because of that, users can get a warning that one or more pool devices have issues after upgrading. The upgrade doesn't cause the warnings; they were just not monitored before.

That's nice.

Does this mean that the monitoring scripts mentioned here can be disabled ?

9 minutes ago, ChatNoir said:

That's nice.

Does this mean that the monitoring scripts mentioned here can be disabled

Yep, those are no longer needed with 7.3

23 hours ago, jademonkee said:

Upgraded to 7.3.0 without issue.

It seems to me that my power consumption has dropped? I think my CPU is falling into low-power states more easily/often now.

Thanks for all the hard work ✌️

A day later, and yes: it seems that my UPS is reporting that my machine (of course, this includes the other peripherals attached to the UPS) is sitting around 90-100w when 'idle' (IE, no VM running, but all my usual Dockers running), whereas it used to idle around 120w-140w.
Looks like the newer kernel is properly using amd-pstate rather than acpi-cpufreq.

The min freq of the CPU has also changed from 545.0000 MHz to 429.5810 MHz.

Great stuff!

I've gone to do my upgrade. 7.2.6 -> 7.3.0
On system reboot im greeted withn a "failed to allocate initramfs memory" on each unraid option

Anyone got any suggestions?

Edited May 15May 15 by Joeh

5 minutes ago, Joeh said:

On system reboot im greeted withn a "failed to allocate initramfs memory" on each unraid option

Anyone got any suggestions?

Try recreating the flash drive, first backup the current one, then recreate it using the USB tool, confirm the flash drive boots with the stock install, and if yes, restore only the /config folder from the backup overwriting any existing files.

If that doesn't work or you need more help, please start a new thread in the general support forum.

Updated and switched to internal boot and TPM registration without issue. I used an old 250gb sata Samsung 850.

I was not signed in to the portal when I clicked the “move to tpm” button and the portal complained it couldn’t find an account associated with my license and that I should create a ticket to resolve. I almost created a ticket until I decided to check to see if it was missing some sort of login. Maybe the wording for that error can be changed.

Edited May 15May 15 by spencers

22 hours ago, starbetrayer said:

I am not using Private Browsing

Thanks, so the issue is not limited to Private Browsing.
I guess that when using Firefox when the Web service is not fully started and we try to access the web interface, we have a cookie created that prevents access.
The weird cookie value I'm seeing is created by code in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout/HeadInlineJS.php

For a sucessful sesssion, the cookie has a different value format - such as 55b41aba704666854bd545ecf3791689

...i am confused...

Edited May 15May 15 by Zonediver

Can someone explain, what this means?

Edited May 15May 15 by Zonediver

31 minutes ago, Zonediver said:

Can someone explain, what this means?

Don't take my word for it, but I think it just means that you haven't linked your key to your account yet. You can link your key(s) to your unraid account so that if you ever need to retrieve them, you can just download them. E.g, If your local/backup key gets lost.

But then again, the wording and the big read banner suggest it's mandatory for some operations now?

Edit: Sorry, I didn't see your previous post with the errors.

Edited May 15May 15 by strike

Login to unraid.net and try again.

2 minutes ago, trurl said:

Login to unraid.net and try again.

Well...

I tried it several times and got this...

Edited May 15May 15 by Zonediver

Here a screenshot from https://account.unraid.net/server/link-key

Edited May 15May 15 by Zonediver

Is your Unraid Connect plugin up-to-date?