mwf369

I had notes on where the drives were assigned within Unraid, but was hoping to validate this from the config before recreating these assignments. Any time the old super.dat was included on the USB, the webgui wouldn'y load, so this was the best option. And it worked! Thanks for your help. Mark

So, with a lot of trial-and-error, and I've found that if I create a stock install and copy everything from the backup config folder to the new install EXCEPT the super.dat the system boots, and the webgui comes up! However, all my disks are listed as unassigned. What's the best course of action at this point? If I reassign all of the disks to their original spot in the array, should everything come up as expected? Is there a log file (perhaps in the diagnostic zip?) that I could use to correlate the drives (by serial #) to their assigned location in the array? Thanks, Mark

No. Should I? What should be added/removed? There's not much there.

Well, that's the issue. The GUI won't load.

How do you do this from the CLI??

After the upgrading from 6.12.13 to 6.12.14, my Unraid system would not respond, except to ping. Webgui wouldn't load, array and docker didn't appear to be online. Restarted a couple of times, logged in to the console and confirmed that the network was up, but webgui and array would not come up. So I logged into Unraid Connect, downloaded the most recent backup zip file, created a new USB key with USB Creator and tried to restore the system. For some reason, the system ignored the network IP config entered in the USB Creator (and presumably present in the backup?), and resulted in the same condition: the restored system won't load the Webgui or start the array. I tried 3 times with the same outcome. Interestingly, the "restored" config is also 6.12.14. Finally, I created a USB Key with 6.12.14 without the backup file, and the system booted right up and loaded the Webgui. BUT, my config is completely gone. It seems that there must be some driver or configuration in my system that is not compatible with 6.12.14. Can this be identified and eliminated from the USB Key created from the restore, so I can recover my system? Thanks in advance. tower-diagnostics-20250104-2040.zip

It is unfortunate that the Unraid team has abandoned this key feature. Considering the thousands of views over the last 18 months on your post (and several others on similar SMB/AD/Permission issues) you would think it would gather some attention. It's likely most users have moved on to other solutions, unfortunately.

Anyone have a solution for this? Or a doc or guide to point to? I've been struggling with this same issue since moving off 6.9 last year.