Hello,

I need the communities help please. I upgraded to v7.1.4 on August 2nd 2025 from v7.1.2. I had not performed a reboot. I shut down my system today to upgrade to a new Jonsbo N3 case unsuccessfully as my PSU didn't fit.

I put my PSU back in my case and unraid failed to boot with the following

From the above my USB is detected as sda but not loading the EFI folder. Further down neither SATA drives nor IPv4 address is assigned. This is similar to the following pages:

I did log in locally and the lsusb command results are below:

When on v6.1.12 or v7.01 I upgraded my motherboard / CPU / RAM / NVME drives so have been using the current setup for 3-4 upgrades. To diagnose my issue i have performed the following:

1. Tried moving the USB drive to all other USB ports on the motherboard

2. Confirmed in BIOS that no settings changed i.e. fastboot and drive boot sequence with only UEFI / USB as an option. RAM is detected by the MB but I did not perform a RAM test

3. Reverted to old motherboard / CPU / RAM and it booted (minus 1 NVME cache drive as there are not sufficient ports on the old motherboard). This eliminated in my mind corruption of the USB drive or PSU failure

4. Reassembled to the new setup with the same failures

I am unsure what to do next. Some things considered:

1. I have a local flash backup .zip (not in Unraid Connect) of v7.1.2. Should I revert to that? I am also not sure how to do that. Help woudl be appreciated if this is a good idea. Also could I do a file copy of the v7.1.4 file setup and file copy this back later if needed?

2. Buy a new USB drive and create a trial edition to confirm new hardware has somehow not died. If this works swap drives? Should I buy another SANDISK ULTRA or a different brand?

3. Something else?

I am not overly technical or familiar with linux so please keep this in mind when suggesting things to me please.

Edited August 10, 2025Aug 10 by FestivusOz

You can ignore this: Fail to boot with mount: /sys/firmware/efi/efivars: unknown filesystem type 'efivarfs' error, it's normal with 7.1.x and not the issue.

Try recreating the flash drive, 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.

Hello @JorgeB

Thank you for your help. I did not have a Windows or Mac PC handy to use the USB tool. I tried installing the debian tool on my chromebook but it failed. I have no real linux experience but expect the VM has limitations.

I did make a backup of the USB. I then unpacked the v7.1.4.zip and copied the files over the existing to the USB, leaving the folders LOGS, PREVIOUS, BACKUP & PRECLEAR-REPORTS. I assumed i didn't have to run the make bootable script as this was done previously. The drive booted and picked up an IP address and on logging in I got a fresh install screen with Tower and asking me to enter credentials. Though it did create a lot of FSCK0000x.REC files in the root folder of the USB drive

On copying over the my config folder as suggested I get the orginal error of not being able to boot up and not resolving an IPv4 address. I think somehow the config folder has corrupted. Not sure how as i gracefully shutdown my PC the last time.

I have a config folder from v7.1.2 from August 2nd that I am confident is the same / similar to the v7.1.4. Could I try and use that with the v7.1.4 or am I better off getting hold of a Windows PC and creating a v7.1.2 clean disk then restoring the config folder from that?

Again your help would be very much appreciated.

Edited August 12, 2025Aug 12 by FestivusOz

Actually i tried using my config folder from the v7.1.2 backup and received the same outcome. No loading of IPv4 address. i tried renaming of the network.cfg file and I received access. Reverted to v7.1.4 config file and renamed network.cfg. A simple fix in the end.

It took a long time to write / delete files to USB and I got the FSCK000x.REC files. Do you think that the USB could be on its way out?

I am yet to start the array as its well passed midnight.

Thanks for your help @JorgeB .

Edited August 12, 2025Aug 12 by FestivusOz

26 minutes ago, FestivusOz said:

Do you think that the USB could be on its way out?

It's possible if they are appearing right after a new stock install, it may be wroth tryng a new flash drive.

Regarding the no GUI after restoring the config from a backup, you can try to restore just the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.