GrimD

Im getting the samething. Clicking backup now on the new version does nothing.

Changed Status to Solved

@limetech I have converted my USB stick back to GPT and everything seems to be running as expected on 6.10.1 now, thank you.

Currently running 6.10 with MBR fine but will look to convert the USB back to GPT and test with 6.10.1 ASAP.

@dumurluk I would assume yours is MBR, I belive most USB drives are still MBR by default when shipped. I tend to convert mine to GPT as its newer amd most things support it now. The issue seems to be that as soon as you convert a drive to GPT in windows it creats a hidden efi system partition at the beginning of the drive. ONce I put the drive back to MBR. I had just had to do a normal format in wimdows and it worked fine as there is no extra hidden system partition created with MBR.

@agh1701 That looks like a very different issue, you should start a separate thread

@limetech I know but MBR is old and GPT is new Everything else seems to be working as expected on 6.10 now I'm on it so thats good so far

@limetech Thank you for the explanation that, makes total sense now. I have just tried using an MBR partition as suggested by a few people and that does work. I would prefer to use GPT though. I'm sure it makes little difference but its one of those GPT is the new hotness type of things, if that makes sense . Would defiantly be good if you can add that in the next release, I kind of thought that was the whole point of having to label it UNRAID so you could search for and find the correct volume :D.

@limetech I can't use your USB flash creator, it fails with an error that it can't find the device\disk. The USB in question works fine with the same partition layout with 6.9.2 so is this a change in 6.10? Can 6.10 not work the same way as 6.9.2? The USB is an old 16GB SanDisk Corp. Cruzer Fit I'm not opposed to getting a new one if that might solve the issue. Is there a recommended one, preferably one that barley sticks out like the Fit?

@itimpi ya hopefully they will have some thing to add. Appreciate the suggestion but as I said spent too much tome playing with this issue yesterday so going to take a break from it for now unless some thing is specifically needed for troubleshooting.

@itimpi it shows as one partition in every windows tool I have so quite sure it is only one. Spent alot of time on this all ready and happy to stick woth 6.9.2 untill a official solution can be found. If @limetech need any thing to help troubleshoot I'll look to get it to them ASAP.

@JorgeB One of the few things I haven't tried but but the same drive with no changes (other then coping the install files across) works fine with 6.9.2 so why would\should it be an issue for 6.10?

@itimpi but the same drive with no changes (other then coping the install files across) works fine with 6.9.2 so the partition structure is obviously not an issue for 6.9.2.

@limetech Here you go. Seems to be showing the device with the correct Label. Have to say I do really appreciate how easy it is to just copy the files to\from the USB key to switch versions. As a Tech I don't think I've ever worked on an OS that's so easy\quick upgrade and to roll back

I can't even complete the boot process on 6.10 and went back too. Reading all these other issues I don't think I will look to move to 6.10 for a while even if my boot issue is fixed.

@Taddeusz I'm sure it does, Linux doesn't have the same limitation Windows does. Ideally you are supposed to use a GPT partition with UEFI though which is why Microsoft don't support it. Mine works fine with GPT in 6.9.2 and I'm not the only one reporting this issue so hopefully it will get resolved in 6.10.

@Taddeusz I suppose. That is one thing I didn't try, MBR with UEFI. I'm used to Windows which wont boot with a MBR partition with out CSM. Over all the GPT partition with full UEFI mode works fine with 6.9.2. If take the USB that has 6.10 on it and just copy the 6.9.2 install files on to it with no changes (not even running the make boot batch) then it boots right up with no issues. There is nothing in 6.9.2 that's not working for me so far so quite happy to stay on it until the issue is resolved.

Nothing really made a difference except using a MBR partitioned USB with legacy boot (CSM) turned on in the boot options. GPT partitioned drive I can not get it to work no matter what I put. It either did the exact same thing or I stopped form booting at all which was basically tuning on CSM and setting it Legacy only which I would expect as its GPT and legacy boot doesn't usually work with GPT. I have nothing except for the USB boot drive and an ether net cable connected to it usually. Connected a keyboard and VGA monitor to trouble shoot the booting issue that's it. 6.9.2 works with no changes so some thing has changed in 6.10

I have tried both it makes no difference.

16GB, GPT Partition formatted as FAT32

My full diagnostic file is attached in the original post: ASUSTeK COMPUTER INC. - PRIME H410I-PLUS BIOS Information Vendor: American Megatrends Inc. Version: 1601 Release Date: 02/11/2022 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 16.1 I tried changing pretty much every USB and Boot related option. As dumurluk said the USB is seen after the boot, the screen shot shows that is is detected just before the error message. It is what ever process is supposed to detect the UNRAID label on the volume that's not succeeding. Also if I unplug the USB at the error message the Linux system shows it being disconnected and if I plug it back in it shows it being detected again.

So I'm playing about with the currently and have managed to get 6.10 to boot. If I initialise the USB as MBR and then turn on all the boot compatibility options (CSM) in my BIOS\UEFI setup it will boot. Initialising the USB as GPT and using UEFI boots to the USB key but then fails at the "waiting up to 30 sec for device with label UNRAID to come online" with the Unraid boot device not found error. This must be some sort of bug in the code as 6.9.2 works with no issues formatted as GPT with CSM completely disabled. Going to try one final thing which is I have found an other 8GB USB key so going to try that out. Edit: Well the other USB is supper old and crappy and I can't even get the mobo to recognise it as a boot device.

Tried that but still the same Also tried every USB port on the PC and went in to the BIOS and tried every possible option related to USB. The result of changing the BIOS was either it made it not boot from the USB key at all or the issue was the same. I've attached a Photo of the issue. Looking through it, it does show the USB key being detected as a USB Mass storage device before erroring that it can't find a device with label UNRAID Also tried using the clean command in disk part to wipe all the config of the USB drive, reinitialise it as GPT and manually install 6.10 on it again.

I've created a bug report for this issue if any one else wants to add their diagnostic reports too it. Might help locate if its due to a particular bit of hardware etc.

Seems like quite a few people are getting this, I submitted a bug report previously here