Grub is preventing me from booting from usb to install Debian
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I had Linux Mint on dualboot, but I was having problems with the audio, so I deleted the partition using disk manager on windows 10, and was going to install Debian, but when I try to boot Debian from the usb, it goes to GRUB and I am unable to get past this. I tried many solutions on various forums and none of them have removed this obstacle. Anyone got any ideas?
linux debian grub2 grub
asked Jan 3 at 22:22
Daniel Horn
11
 |Â
show 3 more comments
up vote
0
down vote
favorite
I had Linux Mint on dualboot, but I was having problems with the audio, so I deleted the partition using disk manager on windows 10, and was going to install Debian, but when I try to boot Debian from the usb, it goes to GRUB and I am unable to get past this. I tried many solutions on various forums and none of them have removed this obstacle. Anyone got any ideas?
linux debian grub2 grub
asked Jan 3 at 22:22
Daniel Horn
11
You mean the bios doesn't let you interrupt boot to access boot media priority menu ? Or you can boot but on disk instead of USB ? (then your usb stick is not bootable so it ignore it & go back to normal boot on disk))
– francois P
Jan 3 at 22:27
I am able to get into the bios, and even the boot media priority. When I change the boot order to load from a device, it goes to a grub screen.
– Daniel Horn
Jan 3 at 22:28
so I think your usb stick is not bootable did you build it from a gerrator-tool or by yourself just copying iso on it ? a method to build USB bootable stick is doing a dd if=debianxx.iso of=/dev/somedevicename bs=4M && sync did you remember having done something similar ?
– francois P
Jan 3 at 22:30
I used unetbootin to build it.
– Daniel Horn
Jan 3 at 22:31
[link]imgur.com/gallery/fuTYt
– Daniel Horn
Jan 3 at 22:34
 |Â
show 3 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I had Linux Mint on dualboot, but I was having problems with the audio, so I deleted the partition using disk manager on windows 10, and was going to install Debian, but when I try to boot Debian from the usb, it goes to GRUB and I am unable to get past this. I tried many solutions on various forums and none of them have removed this obstacle. Anyone got any ideas?
linux debian grub2 grub
asked Jan 3 at 22:22
Daniel Horn
11
I had Linux Mint on dualboot, but I was having problems with the audio, so I deleted the partition using disk manager on windows 10, and was going to install Debian, but when I try to boot Debian from the usb, it goes to GRUB and I am unable to get past this. I tried many solutions on various forums and none of them have removed this obstacle. Anyone got any ideas?
linux debian grub2 grub
asked Jan 3 at 22:22
Daniel Horn
11
asked Jan 3 at 22:22
Daniel Horn
11
asked Jan 3 at 22:22
Daniel Horn
11
asked Jan 3 at 22:22
Daniel Horn
11
11
You mean the bios doesn't let you interrupt boot to access boot media priority menu ? Or you can boot but on disk instead of USB ? (then your usb stick is not bootable so it ignore it & go back to normal boot on disk))
– francois P
Jan 3 at 22:27
I am able to get into the bios, and even the boot media priority. When I change the boot order to load from a device, it goes to a grub screen.
– Daniel Horn
Jan 3 at 22:28
so I think your usb stick is not bootable did you build it from a gerrator-tool or by yourself just copying iso on it ? a method to build USB bootable stick is doing a dd if=debianxx.iso of=/dev/somedevicename bs=4M && sync did you remember having done something similar ?
– francois P
Jan 3 at 22:30
I used unetbootin to build it.
– Daniel Horn
Jan 3 at 22:31
[link]imgur.com/gallery/fuTYt
– Daniel Horn
Jan 3 at 22:34
 |Â
show 3 more comments
You mean the bios doesn't let you interrupt boot to access boot media priority menu ? Or you can boot but on disk instead of USB ? (then your usb stick is not bootable so it ignore it & go back to normal boot on disk))
– francois P
Jan 3 at 22:27
I am able to get into the bios, and even the boot media priority. When I change the boot order to load from a device, it goes to a grub screen.
– Daniel Horn
Jan 3 at 22:28
so I think your usb stick is not bootable did you build it from a gerrator-tool or by yourself just copying iso on it ? a method to build USB bootable stick is doing a dd if=debianxx.iso of=/dev/somedevicename bs=4M && sync did you remember having done something similar ?
– francois P
Jan 3 at 22:30
I used unetbootin to build it.
– Daniel Horn
Jan 3 at 22:31
[link]imgur.com/gallery/fuTYt
– Daniel Horn
Jan 3 at 22:34
You mean the bios doesn't let you interrupt boot to access boot media priority menu ? Or you can boot but on disk instead of USB ? (then your usb stick is not bootable so it ignore it & go back to normal boot on disk))
– francois P
Jan 3 at 22:27
You mean the bios doesn't let you interrupt boot to access boot media priority menu ? Or you can boot but on disk instead of USB ? (then your usb stick is not bootable so it ignore it & go back to normal boot on disk))
– francois P
Jan 3 at 22:27
I am able to get into the bios, and even the boot media priority. When I change the boot order to load from a device, it goes to a grub screen.
– Daniel Horn
Jan 3 at 22:28
I am able to get into the bios, and even the boot media priority. When I change the boot order to load from a device, it goes to a grub screen.
– Daniel Horn
Jan 3 at 22:28
so I think your usb stick is not bootable did you build it from a gerrator-tool or by yourself just copying iso on it ? a method to build USB bootable stick is doing a dd if=debianxx.iso of=/dev/somedevicename bs=4M && sync did you remember having done something similar ?
– francois P
Jan 3 at 22:30
so I think your usb stick is not bootable did you build it from a gerrator-tool or by yourself just copying iso on it ? a method to build USB bootable stick is doing a dd if=debianxx.iso of=/dev/somedevicename bs=4M && sync did you remember having done something similar ?
– francois P
Jan 3 at 22:30
I used unetbootin to build it.
– Daniel Horn
Jan 3 at 22:31
I used unetbootin to build it.
– Daniel Horn
Jan 3 at 22:31
[link]imgur.com/gallery/fuTYt
– Daniel Horn
Jan 3 at 22:34
[link]imgur.com/gallery/fuTYt
– Daniel Horn
Jan 3 at 22:34
 |Â
show 3 more comments
3 Answers
3
active
oldest
votes
up vote
0
down vote
If your computer supports UEFI boot, you should be able to boot directly from the flash drive (reference your motherboard's keyboard shortcuts for the exact boot key). Otherwise, you'll need a direct-write utility to write the ISO to the flash drive. Unetbootin is old software and not necessary when you have a bootable ISO (most are these days).
answered Jan 4 at 2:40
Free Bullets
37526
UNetbootin is updated regularly.
– jdwolf
Jan 4 at 2:41
Thanks for the correction. To clarify, unetbootin was conceived before Linux ISOs were created with USB boot in mind. From what I hear, it tends to modify the image which can cause booting issues. I'd recommend using a different program to wrote the image.
– Free Bullets
Jan 4 at 6:33
add a comment |Â
up vote
0
down vote
As @jdwolf already commented...
You may actually be booting from USB after all. If the system is booting in UEFI mode, there should be an UEFI bootloader at EFIbootbootx64.efi on the USB stick. On Linux installation media, this UEFI bootloader is often an UEFI version of GRUB.
If unetbootin changed the layout of the boot files without also adjusting the configuration of the UEFI bootloader (which might be found at EFIbootbootx64.cfg or EFIbootgrub.cfg), then your boot attempt from the USB media might end up with an UEFI GRUB with no valid configuration.
It is also possible that your UEFI implementation may be buggy. Some UEFI versions of GRUB were quite sensitive to UEFI implementation details - I think this has been improving lately, as the GRUB developers receive bug reports and other experience on various UEFI implementations.
With modern distributions, unetbootin and similar tools could be unnecessary for preparing an installation USB media: many installation ISOs come now prepared with isohybrid (see here) or similar tools so that you can simply write the ISO to the USB media using dd or a similar tool and have it just work. This way both the legacy BIOS and UEFI bootloaders on the installation media should be using the configuration that the distribution maintainers have actually tested, rather than a configuration built by unetbootin using heuristics.
answered Jan 4 at 5:18
telcoM
10.8k11232
add a comment |Â
up vote
0
down vote
As a last resort you can try to enable "legacy boot" option if supported by you BIOS.
In my previous experience (hp envy 15 amd apu), the bootable flash drive (gentoo x86_64) required this option in order to be detected by the bios.
answered Jan 9 at 15:01
gat1
467
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
If your computer supports UEFI boot, you should be able to boot directly from the flash drive (reference your motherboard's keyboard shortcuts for the exact boot key). Otherwise, you'll need a direct-write utility to write the ISO to the flash drive. Unetbootin is old software and not necessary when you have a bootable ISO (most are these days).
answered Jan 4 at 2:40
Free Bullets
37526
UNetbootin is updated regularly.
– jdwolf
Jan 4 at 2:41
Thanks for the correction. To clarify, unetbootin was conceived before Linux ISOs were created with USB boot in mind. From what I hear, it tends to modify the image which can cause booting issues. I'd recommend using a different program to wrote the image.
– Free Bullets
Jan 4 at 6:33
add a comment |Â
up vote
0
down vote
If your computer supports UEFI boot, you should be able to boot directly from the flash drive (reference your motherboard's keyboard shortcuts for the exact boot key). Otherwise, you'll need a direct-write utility to write the ISO to the flash drive. Unetbootin is old software and not necessary when you have a bootable ISO (most are these days).
answered Jan 4 at 2:40
Free Bullets
37526
UNetbootin is updated regularly.
– jdwolf
Jan 4 at 2:41
Thanks for the correction. To clarify, unetbootin was conceived before Linux ISOs were created with USB boot in mind. From what I hear, it tends to modify the image which can cause booting issues. I'd recommend using a different program to wrote the image.
– Free Bullets
Jan 4 at 6:33
add a comment |Â
up vote
0
down vote
up vote
0
down vote
If your computer supports UEFI boot, you should be able to boot directly from the flash drive (reference your motherboard's keyboard shortcuts for the exact boot key). Otherwise, you'll need a direct-write utility to write the ISO to the flash drive. Unetbootin is old software and not necessary when you have a bootable ISO (most are these days).
answered Jan 4 at 2:40
Free Bullets
37526
If your computer supports UEFI boot, you should be able to boot directly from the flash drive (reference your motherboard's keyboard shortcuts for the exact boot key). Otherwise, you'll need a direct-write utility to write the ISO to the flash drive. Unetbootin is old software and not necessary when you have a bootable ISO (most are these days).
answered Jan 4 at 2:40
Free Bullets
37526
answered Jan 4 at 2:40
Free Bullets
37526
answered Jan 4 at 2:40
Free Bullets
37526
answered Jan 4 at 2:40
Free Bullets
37526
37526
UNetbootin is updated regularly.
– jdwolf
Jan 4 at 2:41
Thanks for the correction. To clarify, unetbootin was conceived before Linux ISOs were created with USB boot in mind. From what I hear, it tends to modify the image which can cause booting issues. I'd recommend using a different program to wrote the image.
– Free Bullets
Jan 4 at 6:33
add a comment |Â
UNetbootin is updated regularly.
– jdwolf
Jan 4 at 2:41
Thanks for the correction. To clarify, unetbootin was conceived before Linux ISOs were created with USB boot in mind. From what I hear, it tends to modify the image which can cause booting issues. I'd recommend using a different program to wrote the image.
– Free Bullets
Jan 4 at 6:33
UNetbootin is updated regularly.
– jdwolf
Jan 4 at 2:41
UNetbootin is updated regularly.
– jdwolf
Jan 4 at 2:41
Thanks for the correction. To clarify, unetbootin was conceived before Linux ISOs were created with USB boot in mind. From what I hear, it tends to modify the image which can cause booting issues. I'd recommend using a different program to wrote the image.
– Free Bullets
Jan 4 at 6:33
Thanks for the correction. To clarify, unetbootin was conceived before Linux ISOs were created with USB boot in mind. From what I hear, it tends to modify the image which can cause booting issues. I'd recommend using a different program to wrote the image.
– Free Bullets
Jan 4 at 6:33
add a comment |Â
up vote
0
down vote
As @jdwolf already commented...
You may actually be booting from USB after all. If the system is booting in UEFI mode, there should be an UEFI bootloader at EFIbootbootx64.efi on the USB stick. On Linux installation media, this UEFI bootloader is often an UEFI version of GRUB.
If unetbootin changed the layout of the boot files without also adjusting the configuration of the UEFI bootloader (which might be found at EFIbootbootx64.cfg or EFIbootgrub.cfg), then your boot attempt from the USB media might end up with an UEFI GRUB with no valid configuration.
It is also possible that your UEFI implementation may be buggy. Some UEFI versions of GRUB were quite sensitive to UEFI implementation details - I think this has been improving lately, as the GRUB developers receive bug reports and other experience on various UEFI implementations.
With modern distributions, unetbootin and similar tools could be unnecessary for preparing an installation USB media: many installation ISOs come now prepared with isohybrid (see here) or similar tools so that you can simply write the ISO to the USB media using dd or a similar tool and have it just work. This way both the legacy BIOS and UEFI bootloaders on the installation media should be using the configuration that the distribution maintainers have actually tested, rather than a configuration built by unetbootin using heuristics.
answered Jan 4 at 5:18
telcoM
10.8k11232
add a comment |Â
up vote
0
down vote
As @jdwolf already commented...
You may actually be booting from USB after all. If the system is booting in UEFI mode, there should be an UEFI bootloader at EFIbootbootx64.efi on the USB stick. On Linux installation media, this UEFI bootloader is often an UEFI version of GRUB.
If unetbootin changed the layout of the boot files without also adjusting the configuration of the UEFI bootloader (which might be found at EFIbootbootx64.cfg or EFIbootgrub.cfg), then your boot attempt from the USB media might end up with an UEFI GRUB with no valid configuration.
It is also possible that your UEFI implementation may be buggy. Some UEFI versions of GRUB were quite sensitive to UEFI implementation details - I think this has been improving lately, as the GRUB developers receive bug reports and other experience on various UEFI implementations.
With modern distributions, unetbootin and similar tools could be unnecessary for preparing an installation USB media: many installation ISOs come now prepared with isohybrid (see here) or similar tools so that you can simply write the ISO to the USB media using dd or a similar tool and have it just work. This way both the legacy BIOS and UEFI bootloaders on the installation media should be using the configuration that the distribution maintainers have actually tested, rather than a configuration built by unetbootin using heuristics.
answered Jan 4 at 5:18
telcoM
10.8k11232
add a comment |Â
up vote
0
down vote
up vote
0
down vote
As @jdwolf already commented...
You may actually be booting from USB after all. If the system is booting in UEFI mode, there should be an UEFI bootloader at EFIbootbootx64.efi on the USB stick. On Linux installation media, this UEFI bootloader is often an UEFI version of GRUB.
If unetbootin changed the layout of the boot files without also adjusting the configuration of the UEFI bootloader (which might be found at EFIbootbootx64.cfg or EFIbootgrub.cfg), then your boot attempt from the USB media might end up with an UEFI GRUB with no valid configuration.
It is also possible that your UEFI implementation may be buggy. Some UEFI versions of GRUB were quite sensitive to UEFI implementation details - I think this has been improving lately, as the GRUB developers receive bug reports and other experience on various UEFI implementations.
With modern distributions, unetbootin and similar tools could be unnecessary for preparing an installation USB media: many installation ISOs come now prepared with isohybrid (see here) or similar tools so that you can simply write the ISO to the USB media using dd or a similar tool and have it just work. This way both the legacy BIOS and UEFI bootloaders on the installation media should be using the configuration that the distribution maintainers have actually tested, rather than a configuration built by unetbootin using heuristics.
answered Jan 4 at 5:18
telcoM
10.8k11232
As @jdwolf already commented...
You may actually be booting from USB after all. If the system is booting in UEFI mode, there should be an UEFI bootloader at EFIbootbootx64.efi on the USB stick. On Linux installation media, this UEFI bootloader is often an UEFI version of GRUB.
If unetbootin changed the layout of the boot files without also adjusting the configuration of the UEFI bootloader (which might be found at EFIbootbootx64.cfg or EFIbootgrub.cfg), then your boot attempt from the USB media might end up with an UEFI GRUB with no valid configuration.
It is also possible that your UEFI implementation may be buggy. Some UEFI versions of GRUB were quite sensitive to UEFI implementation details - I think this has been improving lately, as the GRUB developers receive bug reports and other experience on various UEFI implementations.
With modern distributions, unetbootin and similar tools could be unnecessary for preparing an installation USB media: many installation ISOs come now prepared with isohybrid (see here) or similar tools so that you can simply write the ISO to the USB media using dd or a similar tool and have it just work. This way both the legacy BIOS and UEFI bootloaders on the installation media should be using the configuration that the distribution maintainers have actually tested, rather than a configuration built by unetbootin using heuristics.
answered Jan 4 at 5:18
telcoM
10.8k11232
answered Jan 4 at 5:18
telcoM
10.8k11232
answered Jan 4 at 5:18
telcoM
10.8k11232
answered Jan 4 at 5:18
telcoM
10.8k11232
10.8k11232
add a comment |Â
add a comment |Â
up vote
0
down vote
As a last resort you can try to enable "legacy boot" option if supported by you BIOS.
In my previous experience (hp envy 15 amd apu), the bootable flash drive (gentoo x86_64) required this option in order to be detected by the bios.
answered Jan 9 at 15:01
gat1
467
add a comment |Â
up vote
0
down vote
As a last resort you can try to enable "legacy boot" option if supported by you BIOS.
In my previous experience (hp envy 15 amd apu), the bootable flash drive (gentoo x86_64) required this option in order to be detected by the bios.
answered Jan 9 at 15:01
gat1
467
add a comment |Â
up vote
0
down vote
up vote
0
down vote
As a last resort you can try to enable "legacy boot" option if supported by you BIOS.
In my previous experience (hp envy 15 amd apu), the bootable flash drive (gentoo x86_64) required this option in order to be detected by the bios.
answered Jan 9 at 15:01
gat1
467
As a last resort you can try to enable "legacy boot" option if supported by you BIOS.
In my previous experience (hp envy 15 amd apu), the bootable flash drive (gentoo x86_64) required this option in order to be detected by the bios.
answered Jan 9 at 15:01
gat1
467
answered Jan 9 at 15:01
gat1
467
answered Jan 9 at 15:01
gat1
467
answered Jan 9 at 15:01
gat1
467
467
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f414654%2fgrub-is-preventing-me-from-booting-from-usb-to-install-debian%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
You mean the bios doesn't let you interrupt boot to access boot media priority menu ? Or you can boot but on disk instead of USB ? (then your usb stick is not bootable so it ignore it & go back to normal boot on disk))
– francois P
Jan 3 at 22:27
I am able to get into the bios, and even the boot media priority. When I change the boot order to load from a device, it goes to a grub screen.
– Daniel Horn
Jan 3 at 22:28
so I think your usb stick is not bootable did you build it from a gerrator-tool or by yourself just copying iso on it ? a method to build USB bootable stick is doing a dd if=debianxx.iso of=/dev/somedevicename bs=4M && sync did you remember having done something similar ?
– francois P
Jan 3 at 22:30
I used unetbootin to build it.
– Daniel Horn
Jan 3 at 22:31
[link]imgur.com/gallery/fuTYt
– Daniel Horn
Jan 3 at 22:34