May 22, 20251 yr A couple days ago I decided to update to 7.1.2. The WebUI froze during this update, but when I refreshed it told me it was ready to update and needed a restart. I did and the machine was just giving me a black screen. So, I decided to create a new USB, copy the /config/ and restart. Everything worked. Then I did another restart and everything went black. I tried a new USB-device, same thing happened. First startup was fine, but restarting just yielded a black screen. So, I decided to roll back to 7.0.1. Same thing. I am not sure where to continue from here. One thing I noticed after rolling back was that the docker templates were missing. After further inspection they have been moved to another folder:Is there something wrong with my USB backup maybe? Is that something I can fix? Edited May 22, 20251 yr by Nimrad
May 22, 20251 yr Community Expert 13 minutes ago, Nimrad said:but restarting just yielded a black screen.Is this during boot or where exactly does it start showing?
May 22, 20251 yr Author 7 minutes ago, JorgeB said:Is this during boot or where exactly does it start showing?When you normally get the blue box of boot choices it’s just black. I see normal BIOS boot screens, but nothing from unraid.
May 22, 20251 yr Community Expert That suggests the board is not correctly detecting the flash drive, or not trying to boot from it, make sure fast boot or any similar option is disabled in the BIOS.
May 22, 20251 yr Author 26 minutes ago, JorgeB said:That suggests the board is not correctly detecting the flash drive, or not trying to boot from it, make sure fast boot or any similar option is disabled in the BIOS.But, when I use the USB creator tool and restore a backup everything is perfectly fine again? It only happens after I restart, not with a «fresh» USB. I have looked in the BIOS and everything is exactly the same. My process went like this:Update to 7.1.2 and restart the server - black screen.Create new USB from the creator tool and restore /config/ - unraid boots.Restart the server - black screen.Create new USB from the creator tool on a new USB drive and restore /config/ - unraid boots.Restart the server - black screen.Create new USB from the creator tool with version 7.0.2 and restore /config/ - unraid boots.Restart the server - black screen. Edited May 22, 20251 yr by Nimrad
May 22, 20251 yr Community Expert 4 minutes ago, Nimrad said:But, when I use the USB creator tool and restore a backup everything is perfectly fine again?Are you not removing the flash drive to restore the backup? Also, did you boot with a stock flash drive without restoring the backup and then try to restart?
May 22, 20251 yr Author 1 minute ago, JorgeB said:Also, did you boot with a stock flash drive without restoring the backup and then try to restart?Yes, that works fine. I did not start the array though.2 minutes ago, JorgeB said:Are you not removing the flash drive to restore the backup?I am putting it in my Mac to use the USB creator tool and restore /config/ yes. Edited May 22, 20251 yr by Nimrad
May 22, 20251 yr Community Expert This doesn't make much sense, but you can try redoing the flash drive, and this time restore only the bare minimum, recreate it using the USB tool and just restore the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), boot and restart, and 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.
May 22, 20251 yr Author 5 minutes ago, JorgeB said:This doesn't make much sense, but you can try redoing the flash drive, and this time restore only the bare minimum, recreate it using the USB tool and just restore the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), boot and restart, and 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.I can try, is there an overview somewhere what is what in /config/?Also, what is it that makes the USB bootable? Maybe something is off with those files. Last time I had a similar issue I had to remove a «—» from a folder or file name and it worked.
May 23, 20251 yr Author So. I tried again to start with a fresh USB but copy the /config/ to try and investigate. Unraid once again did this to my dockerMan folder and put all the templates in FSCk0000.000:Attached is also the diagnostic file. Any other ideas going from here? tower-diagnostics-20250523-0749.zip
May 23, 20251 yr Community Expert 12 hours ago, Nimrad said:Also, what is it that makes the USB bootable?Nothing in the config folder, if it's UEFI boot it's just the EFI folder, for legacy boot, it's the syslinux related files on root.1 hour ago, Nimrad said:FSCk0000.000:This usually means there's a problem with the flash drive, or with the USB controller.
May 23, 20251 yr Community Expert 1 hour ago, Nimrad said:Unraid once again did this to my dockerMan folder and put all the templates in FSCk0000.000:That means corruption was detected on the flash drive. The FSCK type files are the result of an attempt to repair the flash drive.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.