Create Linux USB that can boot from any computers like the liveusb installer
From my understanding, when installing Linux on a USB, it's only guaranteed to boot on that machine, unlike the liveUSB installer.
So my Dell laptop already has Linux on it's internal hard drive. When I put the installer in I hit F12 before booting and it will give me an option to boot from that installer.
Then, I choose the target to be on an empty usb. After finish installing. I pops out the installer and try to boot with the new USB. The BIOS won't list it when I hit F12.
I tried to install the boot record on both /dev/sdb and /dev/sdb1, still doesn't seem to work.
What makes those live installers special that the BIOS can see it?
linux boot usb grub bootable
asked Dec 12 at 9:19
romerun
101
add a comment |
From my understanding, when installing Linux on a USB, it's only guaranteed to boot on that machine, unlike the liveUSB installer.
So my Dell laptop already has Linux on it's internal hard drive. When I put the installer in I hit F12 before booting and it will give me an option to boot from that installer.
Then, I choose the target to be on an empty usb. After finish installing. I pops out the installer and try to boot with the new USB. The BIOS won't list it when I hit F12.
I tried to install the boot record on both /dev/sdb and /dev/sdb1, still doesn't seem to work.
What makes those live installers special that the BIOS can see it?
linux boot usb grub bootable
asked Dec 12 at 9:19
romerun
101
add a comment |
From my understanding, when installing Linux on a USB, it's only guaranteed to boot on that machine, unlike the liveUSB installer.
So my Dell laptop already has Linux on it's internal hard drive. When I put the installer in I hit F12 before booting and it will give me an option to boot from that installer.
Then, I choose the target to be on an empty usb. After finish installing. I pops out the installer and try to boot with the new USB. The BIOS won't list it when I hit F12.
I tried to install the boot record on both /dev/sdb and /dev/sdb1, still doesn't seem to work.
What makes those live installers special that the BIOS can see it?
linux boot usb grub bootable
asked Dec 12 at 9:19
romerun
101
From my understanding, when installing Linux on a USB, it's only guaranteed to boot on that machine, unlike the liveUSB installer.
So my Dell laptop already has Linux on it's internal hard drive. When I put the installer in I hit F12 before booting and it will give me an option to boot from that installer.
Then, I choose the target to be on an empty usb. After finish installing. I pops out the installer and try to boot with the new USB. The BIOS won't list it when I hit F12.
I tried to install the boot record on both /dev/sdb and /dev/sdb1, still doesn't seem to work.
What makes those live installers special that the BIOS can see it?
linux boot usb grub bootable
linux boot usb grub bootable
asked Dec 12 at 9:19
romerun
101
asked Dec 12 at 9:19
romerun
101
asked Dec 12 at 9:19
romerun
101
asked Dec 12 at 9:19
romerun
101
asked Dec 12 at 9:19
romerun
101
101
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There are several possibilities, and without knowing your laptop model and the name and version of the Linux distribution you're installing, it's hard to say for certain.
The most important piece of information would be whether your system uses traditional BIOS-style boot or UEFI.
When booting UEFI-style from a removable media, the media should have a partition with a filesystem that is understood by your system firmware: FAT32 support is guaranteed by the UEFI specification, ISO9660 might also be supported, and perhaps NTFS, but not much else. If a supported filesystem type is found on a removable media, the firmware looks for a boot file in a standard UEFI fallback boot path: EFIBOOTbootx64.efi on 64-bit x86 hardware. The installer might be designed for HDD/SSD-based installations in mind, and it might not set up the bootloader using this fallback path. That might be easily fixed by accessing the freshly-installed stick in another OS, locating the primary UEFI bootloader file, and copying it to the correct location.
If you are booting traditional BIOS-style, the installer has no way of knowing for certain which order your storage devices were detected by the BIOS; furthermore, it has no way of anticipating how that ordering will change when you remove the installer. As a result, the installer will have to rely on unreliable heuristics, and it might be writing the bootloader to the wrong device.
answered Dec 12 at 10:48
telcoM
15.7k12143
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f487530%2fcreate-linux-usb-that-can-boot-from-any-computers-like-the-liveusb-installer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are several possibilities, and without knowing your laptop model and the name and version of the Linux distribution you're installing, it's hard to say for certain.
The most important piece of information would be whether your system uses traditional BIOS-style boot or UEFI.
When booting UEFI-style from a removable media, the media should have a partition with a filesystem that is understood by your system firmware: FAT32 support is guaranteed by the UEFI specification, ISO9660 might also be supported, and perhaps NTFS, but not much else. If a supported filesystem type is found on a removable media, the firmware looks for a boot file in a standard UEFI fallback boot path: EFIBOOTbootx64.efi on 64-bit x86 hardware. The installer might be designed for HDD/SSD-based installations in mind, and it might not set up the bootloader using this fallback path. That might be easily fixed by accessing the freshly-installed stick in another OS, locating the primary UEFI bootloader file, and copying it to the correct location.
If you are booting traditional BIOS-style, the installer has no way of knowing for certain which order your storage devices were detected by the BIOS; furthermore, it has no way of anticipating how that ordering will change when you remove the installer. As a result, the installer will have to rely on unreliable heuristics, and it might be writing the bootloader to the wrong device.
answered Dec 12 at 10:48
telcoM
15.7k12143
add a comment |
There are several possibilities, and without knowing your laptop model and the name and version of the Linux distribution you're installing, it's hard to say for certain.
The most important piece of information would be whether your system uses traditional BIOS-style boot or UEFI.
When booting UEFI-style from a removable media, the media should have a partition with a filesystem that is understood by your system firmware: FAT32 support is guaranteed by the UEFI specification, ISO9660 might also be supported, and perhaps NTFS, but not much else. If a supported filesystem type is found on a removable media, the firmware looks for a boot file in a standard UEFI fallback boot path: EFIBOOTbootx64.efi on 64-bit x86 hardware. The installer might be designed for HDD/SSD-based installations in mind, and it might not set up the bootloader using this fallback path. That might be easily fixed by accessing the freshly-installed stick in another OS, locating the primary UEFI bootloader file, and copying it to the correct location.
If you are booting traditional BIOS-style, the installer has no way of knowing for certain which order your storage devices were detected by the BIOS; furthermore, it has no way of anticipating how that ordering will change when you remove the installer. As a result, the installer will have to rely on unreliable heuristics, and it might be writing the bootloader to the wrong device.
answered Dec 12 at 10:48
telcoM
15.7k12143
add a comment |
There are several possibilities, and without knowing your laptop model and the name and version of the Linux distribution you're installing, it's hard to say for certain.
The most important piece of information would be whether your system uses traditional BIOS-style boot or UEFI.
When booting UEFI-style from a removable media, the media should have a partition with a filesystem that is understood by your system firmware: FAT32 support is guaranteed by the UEFI specification, ISO9660 might also be supported, and perhaps NTFS, but not much else. If a supported filesystem type is found on a removable media, the firmware looks for a boot file in a standard UEFI fallback boot path: EFIBOOTbootx64.efi on 64-bit x86 hardware. The installer might be designed for HDD/SSD-based installations in mind, and it might not set up the bootloader using this fallback path. That might be easily fixed by accessing the freshly-installed stick in another OS, locating the primary UEFI bootloader file, and copying it to the correct location.
If you are booting traditional BIOS-style, the installer has no way of knowing for certain which order your storage devices were detected by the BIOS; furthermore, it has no way of anticipating how that ordering will change when you remove the installer. As a result, the installer will have to rely on unreliable heuristics, and it might be writing the bootloader to the wrong device.
answered Dec 12 at 10:48
telcoM
15.7k12143
There are several possibilities, and without knowing your laptop model and the name and version of the Linux distribution you're installing, it's hard to say for certain.
The most important piece of information would be whether your system uses traditional BIOS-style boot or UEFI.
When booting UEFI-style from a removable media, the media should have a partition with a filesystem that is understood by your system firmware: FAT32 support is guaranteed by the UEFI specification, ISO9660 might also be supported, and perhaps NTFS, but not much else. If a supported filesystem type is found on a removable media, the firmware looks for a boot file in a standard UEFI fallback boot path: EFIBOOTbootx64.efi on 64-bit x86 hardware. The installer might be designed for HDD/SSD-based installations in mind, and it might not set up the bootloader using this fallback path. That might be easily fixed by accessing the freshly-installed stick in another OS, locating the primary UEFI bootloader file, and copying it to the correct location.
If you are booting traditional BIOS-style, the installer has no way of knowing for certain which order your storage devices were detected by the BIOS; furthermore, it has no way of anticipating how that ordering will change when you remove the installer. As a result, the installer will have to rely on unreliable heuristics, and it might be writing the bootloader to the wrong device.
answered Dec 12 at 10:48
telcoM
15.7k12143
answered Dec 12 at 10:48
telcoM
15.7k12143
answered Dec 12 at 10:48
telcoM
15.7k12143
answered Dec 12 at 10:48
telcoM
15.7k12143
15.7k12143
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f487530%2fcreate-linux-usb-that-can-boot-from-any-computers-like-the-liveusb-installer%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
