I upgraded from 7.2.7 to 7.3.2 and it failed. I am really worried, what exactly happened?

There's an apparent issue with the flash drive, try recreating it first, 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.

2 hours ago, JorgeB said:

There's an apparent issue with the flash drive, try recreating it first, 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.

I restored to 7.2.7 and re-did the update and it worked. No idea why it didn't work the first time. How do I know that the usb flash is failing?

If you see any more flash drive related errors logged, it may be failing; you can also try recreating it first as mentioned.

2 hours ago, JorgeB said:

If you see any more flash drive related errors logged, it may be failing; you can also try recreating it first as mentioned.

Im curious as im trying to understand the changes regarding to booting 7.3, what are the specifics of the partition detection and why some older installs dont boot when partitioned "incorrectly"?

17 minutes ago, MowMdown said:

Im curious as im trying to understand the changes regarding to booting 7.3, what are the specifics of the partition detection and why some older installs dont boot when partitioned "incorrectly"?

This seems unrelated to that; there are actual flash drive errors showing, when it's a partition provlem, Unraid still boots normally; just the GUI won't work, and there's a specific error logged by emhttp.

On 7/17/2026 at 9:57 AM, mans_ said:

How do I know that the usb flash is failing?

Syslog is the first indicator but only if you have persistent logging configured -- which most users don't.

Honestly though -- it's pretty much impossible to know a boot drive is about to fail while it's still actively serving as one.

By the time symptoms appear you're often already in trouble.

The more practical approach is two-fold.

First, check what you already have -- ChipGenius or Flash Drive Information Extractor will tell you what controller and NAND type is actually inside your current drive without disturbing it.

That tells you a lot about what to expect long term.

SanDisk being the exception since their controllers block identification tools entirely.

If you want to actively test the drive you'd need to run H2testw on it -- full write and verify cycle that surfaces marginal NAND.

Not practical for most people while it's the active boot device.

Not gonna lie, considering you got help on discord and here and then you run to reddit to complain: https://old.reddit.com/r/unRAID/comments/1uypt4x/quality_of_unraid_updates_is_a_joke/

That's pretty crappy behavior. Especially for something that may or may not be unraid's fault.

Edited Monday at 01:30 PM2 days by MowMdown