Unable to boot unRAID 6.10.0-rc1 system cannot find a "device with label UNRAID"

As I mentioned in the message I sent you, this seems more like a problem with your setup than an actual bug and probably belongs in General Support. Maybe I will copy it there later and close this.

 

Put your flash drive in your PC and let it checkdisk. While there make a backup. The config folder is all you need to get your configuration going again with a new install if necessary.

 

Make sure your flash drive is named UNRAID, all caps.

 

If booting UEFI, there is a folder on flash that must be named EFI

If booting legacy, that same folder must be named EFI-

 

Boot from a USB2 port.

Odd. Would you mind uploading diagnostics from 6.9.2? (see Tools -> Diagnostics). It may give someone some ideas. 

Since you say 6.9.2 boots OK, you should post your diagnostics so we have a better idea about your hardware and configuration.

I have the same issue, i attempted to update to 6.10 rc-1 and received the identical error. I had to manually rollback to 6.9.2 from a backup.

I can confirm:

1. USB named UNRAID

2.Booting from USB2 port

3. Booting from legacy and there is a folder called EFI-

 

Diagnostics attached

 

 

tower-diagnostics-20210916-1711.zip

9 hours ago, trurl said:

As I mentioned in the message I sent you, this seems more like a problem with your setup than an actual bug and probably belongs in General Support. Maybe I will copy it there later and close this.

 

Put your flash drive in your PC and let it checkdisk. While there make a backup. The config folder is all you need to get your configuration going again with a new install if necessary.

 

Make sure your flash drive is named UNRAID, all caps.

 

If booting UEFI, there is a folder on flash that must be named EFI

If booting legacy, that same folder must be named EFI-

 

Boot from a USB2 port.

I know it seems like a setup issue, also its not booting I can obviously not provide diagnostics to provide more info in 6.10.0-rc1, but will get the 6.9.2 log up as requested. I'm just comparing the logs myself and will post shortly.

 

I've run unraid for many years and have upgraded and tested rc's before and not seen this. This is 100% related to 6.10.0-rc1 either requiring a different configuration than was allowed in prior versions or a bug in code that changes the requirements on the boot device. I

 

It's not an issue of running chkdsk in windows I've definitely named it correctly and tried different usb ports. Its specifically the install files for 6.10.0-rc1 that are causing this, as I have validated this by replacing those files on the usb and only the rc1 version files bring up these log messages. Please leave it where it is there's something here that is worthwhile finding out as it might limit compatability of systems to use this new version.

 

My feeling is perhaps the new version might make certain usb devices incompatible, and I'll test this today by using a different usb device. I've seen threads on opensuse with similar message logs indicating certain usb devices are responsible.

Edited September 16, 2021 by sand

This is my USB device, from memory i think it was on Unraid 5s recommended list and thats why i bought it.

 

https://store.sony.com.au/archived-usb-drives/USM4GN.html#start=1&sz=24

46 minutes ago, sand said:

My feeling is perhaps the new version might make certain usb devices incompatible, and I'll test this today by using a different usb device. I've seen threads on opensuse with similar message logs indicating certain usb devices are responsible.

Could be and you use a age mobo X99, pls try does BIOS XHCI / EHCI handoff setting could be help.

 

1 hour ago, sand said:

I've run unraid for many years

Since this was your first post I assumed you were a new user. New users often post a bug report when they just need some help with their particular setup.

Can either of you upgrade by simply copying the bz* files to the root of your flash drive from the 6.10rc1 zip download?

 

33 minutes ago, Vr2Io said:

Could be and you use a age mobo X99, pls try does BIOS XHCI / EHCI handoff setting could be help.

 

This is a good tip. I tried this earlier, and even in EHCI only mode I wasn't able to boot 6.10.0-rc1.

 

Update: I used the website to get 6.10.0-rc1 files rather than the gui update method, and have been able to boot into rc1 with both a fresh install and also with my customisations added back to the usb. I'm isolating what files differ and will confirm what I find.

Edited September 16, 2021 by sand

Perhaps something incomplete when downloading or extracting if updating from the webUI. How large is your flash drive and RAM?

Ok I've tested all the differences; the issue was/is that in the gui update even though the log lists all the files as copied across to boot at least 2 of the files were not copied sucessfully. I can see for certain that at least the \boot\syslinux\syslinux.cfg- didn't go to the destination (I found it in the root of the usb but I cannot say if this was it's location in a prior version or that the copy failed and sent it there). This file itself doesn't stop 6.10.0-rc1 from booting so there must have been issues with the other files failing to copy across. This process failed twice for me as I tried this twice yesterday and at least one other person so it's likely others may see it too.

 

Both I and Bolagnaise updated using the update to "next" in 6.9.2 so it may be specific to the code deployed there. To update.

 

6 minutes ago, sand said:

using the update to "next" in 6.9.2

So did I and I suspect most others, and it worked for us.

 

4 hours ago, trurl said:

How large is your flash drive and RAM?

 

The reason I also asked about RAM size is because some people with little RAM have had problems with upgrading in the webUI. I think the zip is extracted into RAM before being written to flash.

2 minutes ago, trurl said:

So did I and I suspect most others, and it worked for us.

 

 

16GB only around ~500MB used and RAM is 128GB. It could really be a number of things at either end (networking/availability/etc). I've got a work around so I'm ok if happens again. Thanks.

I had this same error 2 days ago. I solved it by downloading Unraid again on my USB and then restoring a backup that I had of the old USB files. I thought that a few Unraid boot files must have been corrupted. 

 

I got that error after having my system run a memtest overnight and assumed that maybe I shutdown something improperly and broke it that way.