8 minutes ago, nraygun said:

I'm a little confused. I went to 7.2.7 because of some CVEs and it seemed that 7.2.7 was newer than 7.3.0.

Is 7.3.1 now the newest with all of the cumulative patches/updates for the flurry of recent CVEs?

Not everyone jumped on 7.3 (some can't due to licensing). So 7.2.x is a maintained version line at least for now - and it got the patches before the 7.3.x version got them. 7.3 is a significant feature addition; 7.3.x is patches - no feature change. So "newer" by release date is not the only thing you need to understand. (Unraid appears to follow semantic versioning if you want to go read more on it)

Updated from 7.2.6 to 7.3.1.

After this update some of my Docker containers couldn't be started or added anymore. Restarting the Docker service didn't help. Syslog showed these messages for 16 of my 23 containers:

Error response from daemon: RWLayer of container daa275f951b3161f2e6983e90bbe1d9142c99f5dc3b8b593c3bbdc389a1c73fb is unexpectedly nil

The workaround was to manually delete all affected containers withdocker rm containerid and then add them again through the ui.

I heard that the migration to a new Docker version in 7.3.0 could have caused this. It would still be a better user experience if Unraid could show these corrupted containers on the Docker page and offer to re-create them or even do this automatically.

Edited May 30May 30 by kennymc.c

23 hours ago, Kilrah said:

7.3.1 is the latest. But along with the new licensing system the "previous" branch i.e. currently 7.2 still gets security updates for those whose updates expired and they can't upgrade to 7.3 without extending.

I have the lifetime license that I bought 6 years ago so I think I'm good license-wise. I'll take it to 7.3.1 soon from 7.2.7.

Can I update from 7.2.3 to 7.3.1 with a Lifetime Plus account? I get this when I rebooted.

Very confused, and very afraid I just lost my data.

3 minutes ago, davidsonserver said:

Can I update from 7.2.3 to 7.3.1 with a Lifetime Plus account? I get this when I rebooted.

Very confused, and very afraid I just lost my data.

I'm pretty sure I saw the same OOBE/setup experience when I updated from 7.2.6 to 7.3 (also Lifetime account).

I basically just skipped it all, was fine.

1 hour ago, davidsonserver said:

Can I update from 7.2.3 to 7.3.1 with a Lifetime Plus account? I get this when I rebooted.

Very confused, and very afraid I just lost my data.

I have the lifetime Pro account, nothing to worry about, this is just the new onboarding screen, just click Get Started, and click all the the defaults presented for you, so next , next, next, complete, that's it all done.

2 minutes ago, dianasta said:

I have the lifetime Pro account, nothing to worry about, this is just the new onboarding screen, just click Get Started, and click all the the defaults presented for you, so next , next, next, complete, that's it all done.

Or even easier click the Skip option.

Updated from 7.3 to 7.3.1 and having one issue. It seems after the update the Unraid Gui version no longer works as expected. On the system it gets stuck at boot process at stage of showing "emhttp: Starting emhttpd...". It never gets past that to load the GUI. However remotely accessing the server to access the GUI works fine. At first I thought something corrupted so tried several times to reimage the flash drive but same issue. Tried previously posted trick of deleting super.dat and Pool config files from config directory but that did not fix it either. Anyone run into this issue?

Edited May 31May 31 by Teknowiz

2 hours ago, itimpi said:

Or even easier click the Skip option.

I ended up selecting Skip, and then selected "Do it later from the dashboard". Thank you all!

11 hours ago, Teknowiz said:

On the system it gets stuck at boot process at stage of showing "emhttp: Starting emhttpd...".

To see if it's a config problem, try booting with a flash drive using a stock 7.3.1 install. If that works or you then need help sorting the config, please create a new thread in the general support forum.

I was terrified when the "Setting up Unraid" screen displayed... I just skipped it after reading the above posts, and a sigh of relief.

Do I always have to look at the "no internal boot setup detected, click here to set up" under my usb flash device?

Is it preferred to boot from an internal disk instead of the usb now?

28 minutes ago, ATEglauer said:

Is it preferred to boot from an internal disk instead of the usb now?

It is a matter of personal preference. I think the notice is there to help those folks who want/need to switch from Flash Drive boot to booting from a more reliable device. I suspect that it launches a wizard to walk them through the process. (Us folks who are fortunate to have a good quality flash drive from the 2010 era or to have a USB SD memory card adapter are in a much better position than those using 2026 era flash drives!!!)

21 hours ago, davidsonserver said:

Can I update from 7.2.3 to 7.3.1 with a Lifetime Plus account? I get this when I rebooted.

Very confused, and very afraid I just lost my data.

21 hours ago, negated said:

I'm pretty sure I saw the same OOBE/setup experience when I updated from 7.2.6 to 7.3 (also Lifetime account).

I basically just skipped it all, was fine.

20 hours ago, dianasta said:

I have the lifetime Pro account, nothing to worry about, this is just the new onboarding screen, just click Get Started, and click all the the defaults presented for you, so next , next, next, complete, that's it all done.

Same. I just closed it. They I manually migrated to boot from SATA and TPM.

2 hours ago, Frank1940 said:

It is a matter of personal preference. I think the notice is there to help those folks who want/need to switch from Flash Drive boot to booting from a more reliable device. I suspect that it launches a wizard to walk them through the process. (Us folks who are fortunate to have a good quality flash drive from the 2010 era or to have a USB SD memory card adapter are in a much better position than those using 2026 era flash drives!!!)

I have a nice flash drive but figured why not migrate to boot from a hard drive? I like it. If you have unRAID already installed you need to free up an internal hard drive or pool, but then you create a boot section that is only 16GB, and can recreate your old pool again as a second data partition. I have two Samsung SATA 850 PRO drives in a ZFS mirror that I used. They only things on them are my boot partition, and my VM and Docker files. Before they were just VM and Docker drives. I really like it!

No more flash drive! Which for my MB is quite nice because only two USB ports are available to unRAID (rest are passed through to VM's); one of the two are used by my UPS so before 7.3 I had BINGO unRAID USB drives available. Now I actually have an open USB port again without using a USB hub. So, for example I can plug a USB hard drive into unRAID and see it in unassigned devices. Couldn't do that since I started using this MB.

Edited June 1Jun 1 by craigr

On 5/29/2026 at 1:39 AM, JorgeB said:

Don't see how that is possible, especially if you opted out of letting Unraid change the boot order.

I still don't understand what happened, but I have it in a decent place as of now. I tried ew-flashing the Supermicro firmware including the manufacturer section (have to move a jumper to allow access to that section of the ROM and enable it in the BIOS) and there was no change. However, I moved a physical jumper that is supposed to allow IPMI to show up on the VGA port, but that isn't what happened. I also disabled legacy on everything in my BIOS. As of now, I get nothing on my monitors from the MB or unRAID at all. But I do get everything through the IPMI remote control including BIOS and full unRAID boot and login. Sometimes with computers you just have to throw your hands up. It all works now and reliably, it's just different.

Edited June 1Jun 1 by craigr

I updated to 7.3.1 and my browser console screen dies every time I move to either VM or Dashboard. My VM no longer works. I keep having to run /etc/rc.d/rc.php-fpm restart to get my console back. I am attaching my diagnostics. Can someone please help. Thanks.

tower2-diagnostics-20260601-1448.zip

7 hours ago, craigr said:

I have a nice flash drive but figured why not migrate to boot from a hard drive? I like it. If you have unRAID already installed you need to free up an internal hard drive or pool, but then you create a boot section that is only 16GB, and can recreate your old pool again as a second data partition. I have two Samsung SATA 850 PRO drives in a ZFS mirror that I used. They only things on them are my boot partition, and my VM and Docker files. Before they were just VM and Docker drives. I really like it!

You forgot one important fact - It counts a a mounted drive. Fine if you are running Pro/Unleashed/Unlimited license. I have 2 servers. One Plus and one Basic. The Plus has 11 of 12 available drives populated, the Basic maxed out at 6. So no NVMe boot for me without spending some money.

I have enough early tech flash drives to last me as long as I live (I'm old). But then, If I lived as long as my stash, I would be immortal as I have yet to have one fail in the 5+ years I've been running Unraid.

2 hours ago, ConnerVT said:

You forgot one important fact - It counts a a mounted drive. Fine if you are running Pro/Unleashed/Unlimited license. I have 2 servers. One Plus and one Basic. The Plus has 11 of 12 available drives populated, the Basic maxed out at 6. So no NVMe boot for me without spending some money.

I have enough early tech flash drives to last me as long as I live (I'm old). But then, If I lived as long as my stash, I would be immortal as I have yet to have one fail in the 5+ years I've been running Unraid.

Use one of your existing SSD drives. That's what I did. I don't have a spare SATA or NVME port just for the unRAID OS regardless of cost.

Move all data off a pool. Stop array. Remove the drives from the pool and delete the pool. Follow the prompts to migrate the OS and choose to use the drives in the pool you just deleted. The OS migrates from the USB to the pool. Assign the same drives to a new data pool with the exact same name you had before. Move data back onto the pool.

11 hours ago, Joe said:

I updated to 7.3.1 and my browser console screen dies every time I move to either VM or Dashboard. My VM no longer works. I keep having to run /etc/rc.d/rc.php-fpm restart to get my console back. I am attaching my diagnostics. Can someone please help. Thanks.

This thread is not the best place for back-and-forth support; please create a new one on the general support forum.

Yesterday I updated my three servers from 7.2.6 to 7.3.1. (Qnap TS-253d, 2700x and 3700x B450)

All have running dockers and VM's. Everything is woking without any problems and like expected!

About internal boot: How do you deal with when you have to rollback a release because of problems and the server wont start or not accessible anymore?

With a pen drive this is easy, but with internal drive?

9 hours ago, craigr said:

Use one of your existing SSD drives. That's what I did. I don't have a spare SATA or NVME port just for the unRAID OS regardless of cost.

I am pretty confident that currently this counts as an additional drive towards the drive limit for Basic, Pro and Starter licenses.

40 minutes ago, ConnerVT said:

I am pretty confident that currently this counts as an additional drive towards the drive limit for Basic, Pro and Starter licenses.

It does not. It's physical drives that count, if you use an existing one for shared duties it's still one drive.

1 minute ago, Kilrah said:

It does not. It's physical drives that count, if you use an existing one for shared duties it's still one drive.

I have been following several threads here for weeks about this. Answers have been very ambiguous about it, leaning toward it does count as additional drive towards the license limit.

Only physical devices count, if you add one or more devices to create a dedicated boot pool, they will count, if you use existing devices to create a split boot pool, it won't increase the count.

I upgraded from 7.3.0 to 7.3.1 and now the disk on the main array don't seems to be spinning down. Anyone seeing the same?

NVM ... it seems like they spun down now ... I will keep on eye, the server was unused over night and they should have been down.

Edited June 2Jun 2 by remblack