Boot issues with a bootable USB under Linux
Solved
farragut
-
farragut -
farragut -
Hello,
I would like to ask for your help because I am starting to feel overwhelmed. I bought a new laptop and installed the old hard drives from my previous PC, which had a dual boot of Windows 10 Pro / Ubuntu. Before the installation, I cleared my Windows hard drive by uninstalling most of the games and software that were on it, and I also completely formatted my hard drive that was running Ubuntu (which also contained the grub for the dual boot). I then installed the two drives and rebooted.
My new laptop contained an M.2 hard drive that had Windows 10 on it. When I put in my old hard drive, I booted from it and formatted that drive. I then reinstalled Windows to avoid compatibility issues with the drivers and was able to boot from a USB stick to reinstall Windows.
This is where things get strange. When I created my bootable USB stick under Ubuntu using Rufus and rebooted, the BIOS did not detect the bootable USB stick. So, I went into the BIOS to check the settings. I verified that secure boot was indeed disabled (it is) and that legacy mode was enabled (it is). I also played with the boot parameters in the BIOS to prioritize USB devices and ensured that Windows was bootable afterward. I wondered if it was due to the Windows Boot Manager, so I disabled it using the command line “bcdedit -set {bootmgr} timeout 0”, but nothing worked; the BIOS still refuses to boot from the Ubuntu stick.
I checked that the issue wasn't with the ports and tested all of them; that was not the case. I also tried with a Fedora bootable stick, but the BIOS did not boot from it. When I tried to start with the Windows repair tool by selecting "boot from a USB device" and the PC rebooted, I got the nice error message “System doesn't have any USB boot option. Please select another boot option in Boot Manager Menu.” I thought this was strange, so I tried a bootable USB created using the Windows creation tool, and surprisingly! The BIOS detected the stick and booted from it! I confess that I am stuck on how to get my BIOS to boot from my USB stick.
I also tried using another stick to verify that it wasn't an issue with my USB, but it made no difference, and I also recreated the bootable stick to make sure the installation wasn't problematic.
Regarding my PC specifications, if it helps:
Windows 10 Professional
Intel Core i7 9750H
GTX 1660TI
16GB Corsair RAM 2666 MHz
1st hard drive containing Windows 10: Samsung 860 Evo 1TB SATA SSD
2nd hard drive that is supposed to contain Ubuntu: Samsung 970 Evo 250GB M.2 SSD
3rd hard drive for data: ADATA 128GB
Regarding the BIOS:
Name: Quanta
BIOS version: QP161
KBC version: P16100
PCH version: B0 Stepping
ME FW version: 12.0.31.1416
I am open to any help and suggestions. If you need more details, don’t hesitate to ask, and I will provide them to you.
I would like to ask for your help because I am starting to feel overwhelmed. I bought a new laptop and installed the old hard drives from my previous PC, which had a dual boot of Windows 10 Pro / Ubuntu. Before the installation, I cleared my Windows hard drive by uninstalling most of the games and software that were on it, and I also completely formatted my hard drive that was running Ubuntu (which also contained the grub for the dual boot). I then installed the two drives and rebooted.
My new laptop contained an M.2 hard drive that had Windows 10 on it. When I put in my old hard drive, I booted from it and formatted that drive. I then reinstalled Windows to avoid compatibility issues with the drivers and was able to boot from a USB stick to reinstall Windows.
This is where things get strange. When I created my bootable USB stick under Ubuntu using Rufus and rebooted, the BIOS did not detect the bootable USB stick. So, I went into the BIOS to check the settings. I verified that secure boot was indeed disabled (it is) and that legacy mode was enabled (it is). I also played with the boot parameters in the BIOS to prioritize USB devices and ensured that Windows was bootable afterward. I wondered if it was due to the Windows Boot Manager, so I disabled it using the command line “bcdedit -set {bootmgr} timeout 0”, but nothing worked; the BIOS still refuses to boot from the Ubuntu stick.
I checked that the issue wasn't with the ports and tested all of them; that was not the case. I also tried with a Fedora bootable stick, but the BIOS did not boot from it. When I tried to start with the Windows repair tool by selecting "boot from a USB device" and the PC rebooted, I got the nice error message “System doesn't have any USB boot option. Please select another boot option in Boot Manager Menu.” I thought this was strange, so I tried a bootable USB created using the Windows creation tool, and surprisingly! The BIOS detected the stick and booted from it! I confess that I am stuck on how to get my BIOS to boot from my USB stick.
I also tried using another stick to verify that it wasn't an issue with my USB, but it made no difference, and I also recreated the bootable stick to make sure the installation wasn't problematic.
Regarding my PC specifications, if it helps:
Windows 10 Professional
Intel Core i7 9750H
GTX 1660TI
16GB Corsair RAM 2666 MHz
1st hard drive containing Windows 10: Samsung 860 Evo 1TB SATA SSD
2nd hard drive that is supposed to contain Ubuntu: Samsung 970 Evo 250GB M.2 SSD
3rd hard drive for data: ADATA 128GB
Regarding the BIOS:
Name: Quanta
BIOS version: QP161
KBC version: P16100
PCH version: B0 Stepping
ME FW version: 12.0.31.1416
I am open to any help and suggestions. If you need more details, don’t hesitate to ask, and I will provide them to you.
11 answers
jeannets
Posted messages
28363
Registration date
Status
Contributor
Last intervention
Ambassadeur
6 597
I can't find this Insyde BIOS model QP161... I would like to find the manual with the menus for this BIOS... Because on this PC, there is certainly a "thing"...??
QUANTA motherboards are manufactured in large quantities for several PC manufacturers... Let's say that with FOXCOM they produce 90% of the motherboards across various models...
Adding an INSYDE BIOS, with its options, further multiplies the possibilities, even with an identical motherboard... In short, it's not easy to navigate through it all..
Your motherboard may be NL5A and not NLCA..??
Would you know what this motherboard was originally for... Computer brand and model...?? And its age..??
Could you also upload a photo of the BIOS welcome screen, where everything is clearly visible, on the website cjoint.com and share the link here?
https://cjoint.com/
QUANTA motherboards are manufactured in large quantities for several PC manufacturers... Let's say that with FOXCOM they produce 90% of the motherboards across various models...
Adding an INSYDE BIOS, with its options, further multiplies the possibilities, even with an identical motherboard... In short, it's not easy to navigate through it all..
Your motherboard may be NL5A and not NLCA..??
Would you know what this motherboard was originally for... Computer brand and model...?? And its age..??
Could you also upload a photo of the BIOS welcome screen, where everything is clearly visible, on the website cjoint.com and share the link here?
https://cjoint.com/
quentin2121
Posted messages
9063
Registration date
Status
Member
Last intervention
Ambassadeur
1 312
Hello,
To create a bootable USB key for the Ubuntu ISO, use "unetbootin"!
--
“Take your chance, embrace your happiness, and face your risk. When they see you, they will get used to it.” René Char
To create a bootable USB key for the Ubuntu ISO, use "unetbootin"!
--
“Take your chance, embrace your happiness, and face your risk. When they see you, they will get used to it.” René Char
jeannets
Posted messages
28363
Registration date
Status
Contributor
Last intervention
Ambassadeur
6 597
Hello,
Your thing seems quite long and convoluted to me.
1° bcdedit -set {bootmgr} timeout 0 does not disable the Boot manager; it only removes the wait time... So that means ... immediate boot.
Personally, I advise you to leave Windows on disk 1 untouched.
2° Install Ubuntu on your disk 2, after removing your disk 1, let it do its Grub on disk 2, so in case of failure, you could boot Linux from this disk.
And be sure to note all the boot files and the disk identity.
3° Reinsert disk 1, boot into Windows, and modify BCDedit to give it the second boot which is Linux... the best thing is to use EasyBCD, which is graphic.
But you have to feel your way; it's not all that easy.
Your thing seems quite long and convoluted to me.
1° bcdedit -set {bootmgr} timeout 0 does not disable the Boot manager; it only removes the wait time... So that means ... immediate boot.
Personally, I advise you to leave Windows on disk 1 untouched.
2° Install Ubuntu on your disk 2, after removing your disk 1, let it do its Grub on disk 2, so in case of failure, you could boot Linux from this disk.
And be sure to note all the boot files and the disk identity.
3° Reinsert disk 1, boot into Windows, and modify BCDedit to give it the second boot which is Linux... the best thing is to use EasyBCD, which is graphic.
But you have to feel your way; it's not all that easy.
Hi,
First of all, it is necessary to verify the integrity of your downloads by systematically checking the MD5SUM or SHASUM of each ISO image.
Test the USB stick on another PC.
Try using another USB stick.
--
_______________________________ ☯ Zen my nuggets ☮ _____________________________
Make a gesture for the environment, close your windows and adopt a penguin… ????
First of all, it is necessary to verify the integrity of your downloads by systematically checking the MD5SUM or SHASUM of each ISO image.
Test the USB stick on another PC.
Try using another USB stick.
--
_______________________________ ☯ Zen my nuggets ☮ _____________________________
Make a gesture for the environment, close your windows and adopt a penguin… ????
jeannets
Posted messages
28363
Registration date
Status
Contributor
Last intervention
Ambassadeur
6 597
Your key doesn't boot for a reason related to the construction of your USB key... either its formatting (I don't think so) or the file you put in it, it's not meant for UEFI or it doesn't match your PC model (its motherboard) etc... or the USB keys are not "Enabled". You can try placing any USB key to see if it's recognized as a disk..
-- And under Windows, does it recognize the USB keys..? as a disk..
If you formatted your key on Windows, it's in exFAT32 and not in FAT32, but normally reformatted by "Rufus" .. it should be fine, otherwise you can use "SDformatter" which formats in true FAT32...
Otherwise, you can also burn a CD or DVD with the Ubuntu ISO file to do your installation... Initially, it was like that, the USB is a workaround.
-- And under Windows, does it recognize the USB keys..? as a disk..
If you formatted your key on Windows, it's in exFAT32 and not in FAT32, but normally reformatted by "Rufus" .. it should be fine, otherwise you can use "SDformatter" which formats in true FAT32...
Otherwise, you can also burn a CD or DVD with the Ubuntu ISO file to do your installation... Initially, it was like that, the USB is a workaround.
On Windows, the drives are recognized, I tried formatting the same drive under Windows and Ubuntu, the BIOS detects it when it's under Windows but not when it's under Ubuntu. I've reformatted it to FAT32 with each formatting, so that's not the issue either. The problem is that I don't have a CD or DVD burner. In the BIOS, the USB drives are enabled; I checked the configuration.
After doing some research, I noticed that my PC boots in EFI mode and that EasyBCD can't create Linux or other entries. I think that's where the problem lies. Additionally, I installed Grub2 on a USB drive and I can boot into Grub from this drive; I will try to add an entry in Grub to boot from the second USB drive which also contains a burned Ubuntu.
After doing some research, I noticed that my PC boots in EFI mode and that EasyBCD can't create Linux or other entries. I think that's where the problem lies. Additionally, I installed Grub2 on a USB drive and I can boot into Grub from this drive; I will try to add an entry in Grub to boot from the second USB drive which also contains a burned Ubuntu.
jeannets
Posted messages
28363
Registration date
Status
Contributor
Last intervention
Ambassadeur
6 597
In Easy BCD, you can use "NeoGrub" to create a second boot option... It's not always easy... for my part, I have never managed to get its Linux index working.. We would need a relevant course on the subject... the web explanations don’t really explain anything (I haven’t found any).
However, with this NeoGrub https://neosmart.net/EasyBCD/ under Win 10, it allows UEFI and creates an NST directory on your disk... In this folder, you can put the "menus.lst" of GRUB4DOS
It's a solution, it offers you two lines at boot... ** Windows and** Linux
In this menu, you can even have several Linux... that's the idea.
But I don't understand why your USB drive won't boot at all... Where did you get your ISO file..??
Because normally (even without a hard drive) your ISO should boot the PC and show you Ubuntu to try it out and see what it is before installing... So you can't even do that..??
I have the impression that your Linux is strange..
a little reading http://doc.ubuntu-fr.org/uefi
However, with this NeoGrub https://neosmart.net/EasyBCD/ under Win 10, it allows UEFI and creates an NST directory on your disk... In this folder, you can put the "menus.lst" of GRUB4DOS
It's a solution, it offers you two lines at boot... ** Windows and** Linux
In this menu, you can even have several Linux... that's the idea.
But I don't understand why your USB drive won't boot at all... Where did you get your ISO file..??
Because normally (even without a hard drive) your ISO should boot the PC and show you Ubuntu to try it out and see what it is before installing... So you can't even do that..??
I have the impression that your Linux is strange..
a little reading http://doc.ubuntu-fr.org/uefi
After I launch easyBCD, I get an error message saying that Windows is booting in EFI mode and that some parameters are disabled by default. Therefore, I cannot add Linux entries. The problem is that I don't know how to change this so that Windows boots normally and the USB drive can boot into Ubuntu.
The latest version of EasyBCD 2.3 (I think) allows that..
You should have a function key like F12 or F9 etc.. that allows you to choose the Boot device..?? What does it say if you choose USB..?? Otherwise, what does it offer..??
I must say that I find your "Qanta" BIOS a bit curious, the references do not exist at Qanta... and these BIOS seem to contain a Wim file which is a packed piece of Windows.. and the motherboard could be for a server... There are too many unknowns regarding the motherboard... It might be possible that this function is disabled for security reasons.. for example.
You should have a function key like F12 or F9 etc.. that allows you to choose the Boot device..?? What does it say if you choose USB..?? Otherwise, what does it offer..??
I must say that I find your "Qanta" BIOS a bit curious, the references do not exist at Qanta... and these BIOS seem to contain a Wim file which is a packed piece of Windows.. and the motherboard could be for a server... There are too many unknowns regarding the motherboard... It might be possible that this function is disabled for security reasons.. for example.
After checking, I was mistaken; the name of the motherboard seems to be Quanta. Then, when I plug in a USB key and press F12 to access the boot menu, it doesn't offer me anything. When I choose to boot using WinPE, the BIOS tells me it didn't find a bootable USB key.
jeannets
Posted messages
28363
Registration date
Status
Contributor
Last intervention
Ambassadeur
6 597
So..?? what's written on your motherboard..?? Otherwise, use a software like SIW for example to get the references of this motherboard and its BIOS...
Don't you have a manual for this motherboard..?? that also talks about the BIOS settings...?? Otherwise, download it from the manufacturer's website... Generally in English, it is more complete.
Don't you have a manual for this motherboard..?? that also talks about the BIOS settings...?? Otherwise, download it from the manufacturer's website... Generally in English, it is more complete.
It's certainly that your ISO file was not made for your PC... As mentioned in the response from: https://answers.microsoft.com/fr-fr/windows/forum, on the same subject..!
It’s true that your colleague had an easier time than us; he could see the machine's reactions in real-time...
See you later!
See you later!