December 28, 2025Dec 28 My unraid server locked up yesterday. I ended up re-seating the USB Flash drive, and got it to boot. I just left it up and running without starting the array all night. This morning I noticed the upgrade from 7.2.0 to 7.2.3, so I had it do the update and then started the reboot to finish update. It didn't seem to want to come up. That is when I went and saw this:I hit "enter" like it said to reboot the device. When it came back up it didn't find a boot drive, so I re-seated the USB flash drive again. It started up and I downloaded a backup of the flash drive. It then started to not respond again and I saw this:I couldn't reach it remotely so when I was logged in in locally I just shut it downThen looking at the info about replacing your flash drive I saw that I should try and run Mac Disk Utility to check for and repair errors. Here is what that showed. This is where I'm currently at. The machine is off. I have the USB here by my mac, I have ordered a new USB flash drive. Does it seem like the flash drive is really failing? Should I just wait for the new flash drive to show up, and migrate to that? Is there something else I should look at?
December 28, 2025Dec 28 Community Expert Solution It can be worth trying downloading the zip file for the Unraid release and extract all the bz* type files overwriting the ones at the root of the flash drive. It sometimes helps with this sort of issue.
December 28, 2025Dec 28 Author I download it from the link I found here. I have beyond compare are I take it these are the files you are talking about. The binary comparison says they are already the same. Should I just copy over it, and try it out again?
December 28, 2025Dec 28 Author I took one when it came up with the upgrade to 7.2.3 from 7.2.0 (So it may be corrupt). I do have an old one from February 2025, but I'm not sure if that would be up to date enough. I had Backup/Restore Appdata running on it, but I believe those are on the array 😬. I copy the bz* files over and started up the machine. It's running, but I haven't started the array.
December 28, 2025Dec 28 Community Expert The config folder from flash backup is all you need to get your configuration going again on a new install, whether to the same flash or a new one.
December 28, 2025Dec 28 Community Expert 2 hours ago, openam said:Should I just copy over it, and try it out again?Yes. Rewriting the files can mean they now get read without errors.
December 29, 2025Dec 29 Author Thanks for the help. I copied the bz* files back over the ones in the root of the flash drive. It seemed to work, re-ran the parity check (it passed), and everything is back up and running! I'm making a backup of the flash drive now.
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.