I had a power outage. When my system came back up the name had reset to Tower default and my cache and pool devices were not assigned. Before I did any searching I re-assigned my devices and attempted to start the array, when it didn't work I did a reboot.

 

Now, i realize it is probably just my flash drive but my cloud backup has been overwritten with this most current data.

 

Am I screwed? I have a replacement USB drive on the way, will I be able to restore my config?

 

tower-diagnostics-20250225-2257.zip

Your Unraid configuration files are still present in the diagnostics, which is a good sign. Here's what you can do:

 

1.) Backup Your Current USB Drive

-Before doing anything else, copy everything from your existing flash drive to a safe location.

 

2.) Check for Super.dat File

-The super.dat file in config/ stores your drive assignments. If it's intact, your array configuration should be recoverable.

 

3.) Prepare a New Flash Drive

-Install a fresh copy of Unraid on the new USB drive using the Unraid USB Creator.

-Copy the entire /config/ folder from your backup (or extracted diagnostics) to the new flash drive.

-Ensure the super.dat and ident.cfg files are included.

 

4.) Reboot and Check Assignments

-Insert the new USB into your server and boot up.

-Check if your disk assignments and settings are restored.

 

5.) Manually Reassign Drives (If Needed)

-If Unraid doesn't detect your previous assignments, manually assign them without formatting.

-Your parity should remain valid unless you made changes after the outage.

 

Potential Issue with Cloud Backup Overwrite:

If your flash backup on Unraid.net (or MyServers plugin) was overwritten with the post-failure state, you might not be able to restore directly from the cloud. However, since your diagnostics still contain super.dat and ident.cfg, you should be able to manually recover your array.

 

I hope this sheds at least a little light, Lemme know if I can help anymore!

Best & Success,

-DirtyDarrell

4 hours ago, rendermaster said:

when it didn't work I did a reboot.

What didn't work exactly?

@JorgeB most specifically a reboot did not bring my server back to the expected settings. my concern is that a "proper" reboot after an unclean shutdown event may have over-written my settings and configuration

That suggests the flash drive filesystem was damaged/corrupt, do you have a backup?

I shutdown my unraid system and decided to sleep on it.

 

Pulled out the USB drive and I've copied an image to my MacOS laptop.

 

@DirtyDarrell I've located the super.dat file but it's metadata shows it was modified AFTER the bad-recovery situation. I went to the cloud backup first but that had already been overwritten.

 

@JorgeB unfortunately i do not. It appears I had to learn this lesson the hard way.

 

Assuming my data drives are still good, what would be the status of my system config? docker and VMs?

1 hour ago, rendermaster said:

Assuming my data drives are still good, what would be the status of my system config? docker and VMs?

Should all be OK for the VMs, since all data/config is saved on the array/pools, for docker, see if the user-templates folder exists on the flash drive, under \config\plugins\dockerMan\templates-user, if yes all the user templates are there, you can also recover everything.

thanks @JorgeB I see all my various docker apps in the \templates-user folder.

 

when my new usb drive gets here I'll create a new boot drive and follow the instructions from @DirtyDarrell

12 hours ago, rendermaster said:

when my new usb drive gets here I'll create a new boot drive and follow the instructions from @DirtyDarrell

Hopefully, your new USB arrives soon! Wishing you the best of luck with the server rebuild. I don’t think we’ll run into any issues, but if anything comes up or there's any confusion, feel free to reach out. Just a heads-up, sometimes it might be a day or two before I check my notifications on the forums. 💾

Best of luck,

-DirtyDarrell

WHEW!

 

rebuilt the USB, booted up, transferred my license and we're good to go.

 

Much thanks to @DirtyDarrell and @JorgeB