This morning I decided to upgrade my UnRAID OS version to 7.3.2 (or whatever the latest is). After updating all plugins, I updated the OS, and it seemed to go fine. A reboot was necessary to install the update, and here is where it all went sideways. The initial reboot attempts got stalled in some kind of endless boot loop. I stopped the server, replaced the flash drive files with the 'previous' folder full of files and rebooted. It appeared to start up fine but now I am not able to connect to the server in any way. I pinged the IP and there seems to be something responding. I can navigate the UnRAID file system from a monitor attached to the server, but that is the only sign of life.

Can anyone offer some advice as to how to get access to it again? I was able run diagnostics which I have attached here.

tower-diagnostics-20260803-0639.zip

Edited 8 hours ago8 hr by ratmice
grammar

I also noticed it does not see any shares at all, /mnt is empty. This seems bad.

The content of the ‘config’ folder in the diagnostics looks incomplete. It as if something went wrong during the boot sequence and the contents of the ‘config’ folder were not correctly read from the flash drive.

It could be worth backing up the flash drive; recreate it using the USB Creator tool; and then copy the ‘config’ folder from the backup to the flash drive overwriting the config folder already there.

Fixed this error

Edited 5 hours ago5 hr by ratmice
incorrect info

Try recreating the flash drive or using a different one, and make sure it's selected as the boot device in the BIOS.

I was able to get the server to start and access the GUI. But, it appears that the upgrade from earlier has borked all my config files so disk assignments are gone, shares are gone, dockers gone, plugins gone, etc... I know everything was working fine this am, is there a safe way to reassign disks, etc... without screwing up data on the drives? I have a screenshot of the drive assignments, so I think they can be put back as they were. If I tell it that parity is already valid, I assume it will forego the parity check. is there any danger (data loss) if I have any of the disk assignments wrong besides not being parity protected?

sorry for the basic questions, but this is slightly out of my league.

Additionally, I have checked the "parity is already valid', but it still says that 'All existing data on this device will be OVERWRITTEN when array is Started' at the top of the main page (corresponding to the 2 parity disks). I just want to be sure that the checkbox will be respected and no parity rebuild will occur. I plan to immediately start a non-correcting parity check to ensure that I have all disks assigned correctly.

Edited 4 hours ago4 hr by ratmice