I was on version 7.2.6 and updated to 7.3.0. Now I cannot start the server. At least I can access the server via SSH, but nothing else. SMB shares are not working, UI shows Internal Server Error 500, and Docker daemon is not started.

I could gather some diagnostics, but I don't know how to get them. The only idea would be to shut down the server and grab the USB stick, which wouldn't be nice at all.

root@UNRAID-Server:/# diagnostics
Starting diagnostics collection... done.
ZIP file '/boot/logs/unraid-server-diagnostics-20260513-0053.zip' created.

No clue what happened... but that is horrible.

Could get the diagnostics via SCP.

So I could restart a few times with the same result. Now I'm stuck in a BIOS screen loop. This is crazy. Probably broke the flash device.

This is my flash drive. No wonder I'm stuck in a BIOS loop. What the hell happened here?

What I tried now is to use a different flash drive and created it with Unraid USB Creator directly for version 7.3.0. Now I see that: waiting up to 30 seconds for device with label UNRAID to come online.

I don't know what to do anymore.

unraid-server-diagnostics-20260513-0053.zip

Edited May 13May 13 by sasbro97

7 hours ago, sasbro97 said:

What I tried now is to use a different flash drive and created it with Unraid USB Creator directly for version 7.3.0. Now I see that: waiting up to 30 seconds for device with label UNRAID to come online.

Does it boot if the new flash drive has a stock 7.2 instead?

@JorgeB I could boot now to with my old flash drive installed with Unraid USB Creator and Unraid 7.3.0. It booted, but the UI is not loading again. But this time, SSH is also not working. I just see the login prompt on my attached screen to the server.

What should I do?

Ok, never mind, it is really like a fresh install. I'm scared to do anything right now. I had switched my WebUI port and now tried the default one and saw this:

But still, the question: what should I do now? I got flash drive backups with 7.2.6.

A comparison of my backups. Left side is my own backup of the whole flash drive and the right side is Unraid Connect backup. Why do they look so different, and can I restore the left side by just copying everything?

Edited May 13May 13 by sasbro97

All those FSCK files suggest the flash drive or its filesystem were having issues, you can try restoring only the config folder from one of the backups, all settings are there, if it doesn't work, try the other one.

All the FSCK files on the left indicate files/folders that have been found to be corrupted when doing a file system check on the flash drive. This suggest to me there could also be corrupt config files on the backup.

You could start by restoring the basic config files in the config folder:

super.dat to get your disk configuration back

your licence .key file (if not already done)

This should be enough to get your drives back. If not then I suggest come back here and ask again.

There is also the .xml files in 'config/plugins/dockerMan/templates-user' that contain the settings used for any docker containers.

All the .cfg files in the 'config' folder should be human readable text files so you could see if any of them do not look sensible by trying to load them into a text editor.

There are also .cfg files in config/shares for each of your user Shares.

I just copied the files of my own backup, including all FSCK files, and could finally boot normally again to 7.2.6.

I'm now scared to update. This flash drive dilemma is the reason why I wanted to update so early to get rid of it.

I still don't know what happened in the last update and why everything broke. So I'm not sure if I should try to normally update from the WebUI again. How should I proceed now?

The problem was likely the reboot, due to the flash drive issues, not the upgrade itself.

Same issue with me, 7.2.6 to 7.3.0, had to roll back

Another try was successful. So I guess it's really flash drive related. I need to really convert to internal boot. But moving my whole cache with all appdata and stuff will need a lot of time...

Same issue, had a heart stopping moment, the upgrade went fine, stable for a few days, but I had to do a reboot (dead network switch) I didn't know was dead until I did the hard reset.

Then, server name changed, still had the same IP, dropped me two nvme appcache drives.

Once I stopped the array and changed the pool back to normal, all was good. But, I have the old GUI, not the fancy 7.3 one.

All my dockers seem to be working, so I don't really care.

@CasaP wait, which fancy new GUI? Did I miss something?

At least you had more luck than me. For me, it seems that it was a really unlucky incident. Unraid was not the reason, very surely.

I agree, just a set of bad coincidences.

I find UnRaid bullet proof, you nearly need to go out of your way to break it.

I do a monthly parity check, when the June one is finished, I'm going to look into the internal boot, these USB sticks are way too fragile.

@CasaP that's what I'm doing right now, if mover finally finishes moving my data back. I will be way happier because my biggest problems and culprits with Unraid were always these goddamn USB sticks.

You might have a look at my experience with switching to internal boot if you want to use an existing ZFS pool. I was so confused with mover as I never use it and didn't know that snapshots are not moved: https://forums.unraid.net/topic/198907-mover-for-switching-to-internal-boot-for-appdata-not-working/

@JorgeB One question regarding the new internal boot. I have it mirrored anyway to my cache SSDs, but let's say we got the worst case and both are broken. I use TPM licensing. Could I have a USB stick ready to boot from again?

Yes, just need to have a copy of the current /config folder.