May 14, 20251 yr I've been running unraid for over a year, decided to update today from 7.0.1 to 7.1.2, surprised it didn't come back online. So I plugged an HDMI cable to check what was up and noticed it was booting straight into the bios, I changed the USB drive to another port, force reboot and it started booting but to this error. Apologies for being a photo, as I have the server in my living room, never plugged to a monitor. Any idea on what to do here? Never encountered this before and all updates prior were a breeze. Until today...
May 14, 20251 yr Community Expert is this samsung disc your cache SSD? It looks like it died and keeps unraid from starting. Plug it off completly and see if rebooting works again. Edited May 14, 20251 yr by MAM59
May 14, 20251 yr Author 41 minutes ago, MAM59 said: is this samsung disc your cache SSD? It looks like it died and keeps unraid from starting. Plug it off completly and see if rebooting works again. Samsung Flash Drive FIT 1100 is the flash drive I use. Cache SSDs are both a Sabrent and a Crucial. As can be seen in my signature. How would it die with an update though? When it's been rock solid oO I just plugged the flash drive on my mac and it looks fine. Edited May 14, 20251 yr by Sptz87
May 14, 20251 yr Community Expert You could try downloading the zip file for the release and extracting all the bz* type files overwriting the ones on the flash drive. An update is one time a lot is written to the flash drive so it can sometimes cause errors accessing it that would not otherwise be seen.
May 14, 20251 yr Author 53 minutes ago, itimpi said: You could try downloading the zip file for the release and extracting all the bz* type files overwriting the ones on the flash drive. An update is one time a lot is written to the flash drive so it can sometimes cause errors accessing it that would not otherwise be seen. Yep, that worked. Wow lol. That simple. Just replaced the bz* files and instantly booted perfectly.
May 14, 20251 yr Author 1 hour ago, itimpi said: You could try downloading the zip file for the release and extracting all the bz* type files overwriting the ones on the flash drive. An update is one time a lot is written to the flash drive so it can sometimes cause errors accessing it that would not otherwise be seen. Think I spoke to soon. To test I just restarted the server and same thing happened again. Copied the files yet again, and now it just doesn't boot with the same issue...
May 14, 20251 yr Community Expert Does it still boot with the previous release? If yes, get the output from lsusb -vt
June 19, 20251 yr Author On 5/14/2025 at 6:06 PM, JorgeB said:Does it still boot with the previous release? If yes, get the output fromlsusb -vt So I forgot to update this thread. Basically it fails to boot all the time. I have to change USB ports for it to work. I just tried to upgrade now to 7.1.4 and lo and behold. Not booting. :[
June 19, 20251 yr Community Expert 1 minute ago, Sptz87 said:I have to change USB ports for it to work.I think this could be a hardware problem. Spend ~20$ and buy a "Raspberry-Pi-USB-Hub" (you will need a power supply too).This will cut off the stick's power from the motherboard and feed it by itself.There MAY BE some spikes coming back from somewhere that kick the "overpower" feature of your MoBo's USB port. Then this port will be shut off until the next reset (of this port, not of the computer).That forces you to do "port hopping" all the time.(But then it is just a GUESS, cheap enough to try it out. The hub already cured some problems with selfpowered devices, but even a non-powered device like a stick can produce problems if the cables are long enough and there are some electrical machines working nearby)
June 19, 20251 yr Author Just now, MAM59 said:I think this could be a hardware problem. Spend ~20$ and buy a "Raspberry-Pi-USB-Hub" (you will need a power supply too).This will cut off the stick's power from the motherboard and feed it by itself.There MAY BE some spikes coming back from somewhere that kick the "overpower" feature of your MoBo's USB port. Then this port will be shut off until the next reset (of this port, not of the computer).That forces you to do "port hopping" all the time.(But then it is just a GUESS, cheap enough to try it out. The hub already cured some problems with selfpowered devices, but even a non-powered device like a stick can produce problems if the cables are long enough and there are some electrical machines working nearby)That's interesting and a possibility! But this never happened before though, only after going to 7.1.2. Even going from 6 to 7 which was a big jump was absolutely fine. I could reliably reboot the server remotely etc all the time. No issues!
June 19, 20251 yr Community Expert 1 minute ago, Sptz87 said:only after going to 7.1.2. Even going from 6 to 7 which was a big jump was absolutely fine.yeah, I said its only a guess.But it may be a combination of both. The spikes were there all the time but the 7.x driver was the first to activate the protection mechanism of the ports.
June 19, 20251 yr Author 5 minutes ago, MAM59 said:yeah, I said its only a guess.But it may be a combination of both. The spikes were there all the time but the 7.x driver was the first to activate the protection mechanism of the ports.So what just happened right now. Upgraded to 7.1.4 = no bootChanged USB port = no bootDownloaded a copy of 7.1.4 and replaced manually on my laptop every single file and folder except for config and syslinuxPlugged to the original usb port = booted
June 19, 20251 yr Community Expert 2 hours ago, Sptz87 said:Plugged to the original usb port = bootedBut this might be accidentally again too...Try to reboot now and let us see what happens...
March 7Mar 7 Author On 6/19/2025 at 1:48 PM, MAM59 said:But this might be accidentally again too...Try to reboot now and let us see what happens...Little bit late reply. Life got in the way. Everytime I reboot it happens. Just yesterday I updated from 7.1.4 to 7.2.4 and it doesn't boot. Have to turn off the server, grab the usb drive, replace the BZ* files and it then boots fine
March 7Mar 7 Community Expert yeah, looks like your flash drive does not like to be (over)written by linux.Never heard about this before, but of course "s@it can happen everywhere"...Either try a different flash, or wait for 7.3. There they say you can install UNRAID on an normal internal drive and do not need an USB stick anymore. But so far no time for release or betas are known yet...
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.