specify /boot folder during installation, since / drive is not accessible by BIOSUbuntu 14.04 USB installation drive not recognized during boot(Dell Latitude D630)Ubuntu 15.10 does not boot on Intel NUC6i3 with Samsung 950 Pro PCIe NVME SSDCan I use a bootable USB to boot Ubuntu on a PCIe SSD?Booting a NVMe driveGrub bootloader not showing up and no Ubuntu boot option in BIOS after installation (boot-info from boot-repair tool attached)
How to remind myself to lock my doors
Big Bracket for equations
Slow coworker receiving compliments while I receive complaints
Why is it so hard to land on the Moon?
How can demon technology be prevented from surpassing humans?
Variable fixing based on a good feasible solution
Why are seats at the rear of a plane sometimes unavailable even though many other seats are available in the plane?
Count number of different name in a file
Can the bass be used instead of drums?
Are there any rules around when something can be described as "based on a true story"?
How can my hammerspace safely "decompress"?
Match the blocks
Shortest way to get an EOF Error
First aid scissors confiscated by Dubai airport security
How is the corresponding author on a (math) paper typically chosen?
What does "drop" mean in this context?
SSH from a shared workplace computer
What causes standard door hinges to close up to a certain amount automatically?
Disrespectful employee going above my head and telling me what to do. I am his manager
How much income am I getting by renting my house?
Is it plausible that an interrupted Windows update can cause the motherboard to fail?
Glacial, Magnetic and Mossy Lures; what Pokémon do they attract?
Does Australia produce unique 'specialty steel'?
Did smallpox emerge in 1580?
specify /boot folder during installation, since / drive is not accessible by BIOS
Ubuntu 14.04 USB installation drive not recognized during boot(Dell Latitude D630)Ubuntu 15.10 does not boot on Intel NUC6i3 with Samsung 950 Pro PCIe NVME SSDCan I use a bootable USB to boot Ubuntu on a PCIe SSD?Booting a NVMe driveGrub bootloader not showing up and no Ubuntu boot option in BIOS after installation (boot-info from boot-repair tool attached)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I have a Dell desktop at work with a 3.5" spinning HDD with Windows installed on it, and a NVMe SSD that I installed in a PCIe x4 adapter, as the motherboard doesn't offer an NVMe slot. Problem is, the BIOS doesn't recognize the NVMe drive, and it's only after the kernel is loaded that it is. This becomes problematic when installing Ubuntu using the standard installation process, as it obviously has no way of knowing that the drive I'm installing it to (the NVMe) is not recognized by the BIOS. So it ends up installing the /boot folder to that NVMe, which causes Grub to fallback to the rescue prompt when booting up the system.
One solution would be to simply create a boot partition on the 3.5" drive that's recognized by the BIOS, with the root filesystem on the NVMe. But in the interest of tidiness, I'd like to have it create the /boot folder in the ESP partition which already contains the Windows Boot Manager. How can I install the bootloader files to a /boot directory contained on that EFI partition, while installing the root filesystem to the NVMe SSD? I have tried boot-rescue and manually re-installing grub, but that doesn't work as it simply installs grub to the EFI partition with the /boot files still located on the NVMe, as it again is unaware that this won't work since the NVMe isn't recognizable by the BIOS.
boot dual-boot grub2 partitioning uefi
asked Apr 25 at 20:43
onlinespendingonlinespending
1162 bronze badges
add a comment
|
I have a Dell desktop at work with a 3.5" spinning HDD with Windows installed on it, and a NVMe SSD that I installed in a PCIe x4 adapter, as the motherboard doesn't offer an NVMe slot. Problem is, the BIOS doesn't recognize the NVMe drive, and it's only after the kernel is loaded that it is. This becomes problematic when installing Ubuntu using the standard installation process, as it obviously has no way of knowing that the drive I'm installing it to (the NVMe) is not recognized by the BIOS. So it ends up installing the /boot folder to that NVMe, which causes Grub to fallback to the rescue prompt when booting up the system.
One solution would be to simply create a boot partition on the 3.5" drive that's recognized by the BIOS, with the root filesystem on the NVMe. But in the interest of tidiness, I'd like to have it create the /boot folder in the ESP partition which already contains the Windows Boot Manager. How can I install the bootloader files to a /boot directory contained on that EFI partition, while installing the root filesystem to the NVMe SSD? I have tried boot-rescue and manually re-installing grub, but that doesn't work as it simply installs grub to the EFI partition with the /boot files still located on the NVMe, as it again is unaware that this won't work since the NVMe isn't recognizable by the BIOS.
boot dual-boot grub2 partitioning uefi
asked Apr 25 at 20:43
onlinespendingonlinespending
1162 bronze badges
1
Do not confuse the ESP - efi system partition with a /boot partition. You just need to add a ext4 partition as /boot on HDD and installer will put kernel & rest of grub into that partition. Initial UEFI grub boot files are still in ESP. There is something new where you can put kernels into ESP, but that then does not use grub and is not a standard configuration. If an advanced user you can look up gummiboot which is now part of systemD and how to configure that. see also:NVME Samsung 970 Evo Plus drive using a PCIe card ubuntuforums.org/showthread.php?t=2415658
– oldfred
Apr 25 at 21:11
right. I'm not confusing the two. Just was hoping to place the /boot kernel files within the EFI partition as well, but may just go with obvious solution I mentioned of simply creating a /boot partition on the bootable, BIOS-recognized HDD and placing the root filesystem on the NVMe which the BIOS does not recognize
– onlinespending
Apr 25 at 21:31
1
I went ahead and did that and it works quite well. I'm satisfied with that as a workable solution.
– onlinespending
Apr 25 at 21:40
You can now post what you did as an answer.
– GabrielaGarcia
Apr 26 at 20:22
add a comment
|
I have a Dell desktop at work with a 3.5" spinning HDD with Windows installed on it, and a NVMe SSD that I installed in a PCIe x4 adapter, as the motherboard doesn't offer an NVMe slot. Problem is, the BIOS doesn't recognize the NVMe drive, and it's only after the kernel is loaded that it is. This becomes problematic when installing Ubuntu using the standard installation process, as it obviously has no way of knowing that the drive I'm installing it to (the NVMe) is not recognized by the BIOS. So it ends up installing the /boot folder to that NVMe, which causes Grub to fallback to the rescue prompt when booting up the system.
One solution would be to simply create a boot partition on the 3.5" drive that's recognized by the BIOS, with the root filesystem on the NVMe. But in the interest of tidiness, I'd like to have it create the /boot folder in the ESP partition which already contains the Windows Boot Manager. How can I install the bootloader files to a /boot directory contained on that EFI partition, while installing the root filesystem to the NVMe SSD? I have tried boot-rescue and manually re-installing grub, but that doesn't work as it simply installs grub to the EFI partition with the /boot files still located on the NVMe, as it again is unaware that this won't work since the NVMe isn't recognizable by the BIOS.
boot dual-boot grub2 partitioning uefi
asked Apr 25 at 20:43
onlinespendingonlinespending
1162 bronze badges
I have a Dell desktop at work with a 3.5" spinning HDD with Windows installed on it, and a NVMe SSD that I installed in a PCIe x4 adapter, as the motherboard doesn't offer an NVMe slot. Problem is, the BIOS doesn't recognize the NVMe drive, and it's only after the kernel is loaded that it is. This becomes problematic when installing Ubuntu using the standard installation process, as it obviously has no way of knowing that the drive I'm installing it to (the NVMe) is not recognized by the BIOS. So it ends up installing the /boot folder to that NVMe, which causes Grub to fallback to the rescue prompt when booting up the system.
One solution would be to simply create a boot partition on the 3.5" drive that's recognized by the BIOS, with the root filesystem on the NVMe. But in the interest of tidiness, I'd like to have it create the /boot folder in the ESP partition which already contains the Windows Boot Manager. How can I install the bootloader files to a /boot directory contained on that EFI partition, while installing the root filesystem to the NVMe SSD? I have tried boot-rescue and manually re-installing grub, but that doesn't work as it simply installs grub to the EFI partition with the /boot files still located on the NVMe, as it again is unaware that this won't work since the NVMe isn't recognizable by the BIOS.
boot dual-boot grub2 partitioning uefi
boot dual-boot grub2 partitioning uefi
asked Apr 25 at 20:43
onlinespendingonlinespending
1162 bronze badges
asked Apr 25 at 20:43
onlinespendingonlinespending
1162 bronze badges
asked Apr 25 at 20:43
onlinespendingonlinespending
1162 bronze badges
asked Apr 25 at 20:43
onlinespendingonlinespending
1162 bronze badges
asked Apr 25 at 20:43
onlinespendingonlinespending
1162 bronze badges
1162 bronze badges
1
Do not confuse the ESP - efi system partition with a /boot partition. You just need to add a ext4 partition as /boot on HDD and installer will put kernel & rest of grub into that partition. Initial UEFI grub boot files are still in ESP. There is something new where you can put kernels into ESP, but that then does not use grub and is not a standard configuration. If an advanced user you can look up gummiboot which is now part of systemD and how to configure that. see also:NVME Samsung 970 Evo Plus drive using a PCIe card ubuntuforums.org/showthread.php?t=2415658
– oldfred
Apr 25 at 21:11
right. I'm not confusing the two. Just was hoping to place the /boot kernel files within the EFI partition as well, but may just go with obvious solution I mentioned of simply creating a /boot partition on the bootable, BIOS-recognized HDD and placing the root filesystem on the NVMe which the BIOS does not recognize
– onlinespending
Apr 25 at 21:31
1
I went ahead and did that and it works quite well. I'm satisfied with that as a workable solution.
– onlinespending
Apr 25 at 21:40
You can now post what you did as an answer.
– GabrielaGarcia
Apr 26 at 20:22
add a comment
|
1
Do not confuse the ESP - efi system partition with a /boot partition. You just need to add a ext4 partition as /boot on HDD and installer will put kernel & rest of grub into that partition. Initial UEFI grub boot files are still in ESP. There is something new where you can put kernels into ESP, but that then does not use grub and is not a standard configuration. If an advanced user you can look up gummiboot which is now part of systemD and how to configure that. see also:NVME Samsung 970 Evo Plus drive using a PCIe card ubuntuforums.org/showthread.php?t=2415658
– oldfred
Apr 25 at 21:11
right. I'm not confusing the two. Just was hoping to place the /boot kernel files within the EFI partition as well, but may just go with obvious solution I mentioned of simply creating a /boot partition on the bootable, BIOS-recognized HDD and placing the root filesystem on the NVMe which the BIOS does not recognize
– onlinespending
Apr 25 at 21:31
1
I went ahead and did that and it works quite well. I'm satisfied with that as a workable solution.
– onlinespending
Apr 25 at 21:40
You can now post what you did as an answer.
– GabrielaGarcia
Apr 26 at 20:22
1
1
Do not confuse the ESP - efi system partition with a /boot partition. You just need to add a ext4 partition as /boot on HDD and installer will put kernel & rest of grub into that partition. Initial UEFI grub boot files are still in ESP. There is something new where you can put kernels into ESP, but that then does not use grub and is not a standard configuration. If an advanced user you can look up gummiboot which is now part of systemD and how to configure that. see also:NVME Samsung 970 Evo Plus drive using a PCIe card ubuntuforums.org/showthread.php?t=2415658
– oldfred
Apr 25 at 21:11
Do not confuse the ESP - efi system partition with a /boot partition. You just need to add a ext4 partition as /boot on HDD and installer will put kernel & rest of grub into that partition. Initial UEFI grub boot files are still in ESP. There is something new where you can put kernels into ESP, but that then does not use grub and is not a standard configuration. If an advanced user you can look up gummiboot which is now part of systemD and how to configure that. see also:NVME Samsung 970 Evo Plus drive using a PCIe card ubuntuforums.org/showthread.php?t=2415658
– oldfred
Apr 25 at 21:11
right. I'm not confusing the two. Just was hoping to place the /boot kernel files within the EFI partition as well, but may just go with obvious solution I mentioned of simply creating a /boot partition on the bootable, BIOS-recognized HDD and placing the root filesystem on the NVMe which the BIOS does not recognize
– onlinespending
Apr 25 at 21:31
right. I'm not confusing the two. Just was hoping to place the /boot kernel files within the EFI partition as well, but may just go with obvious solution I mentioned of simply creating a /boot partition on the bootable, BIOS-recognized HDD and placing the root filesystem on the NVMe which the BIOS does not recognize
– onlinespending
Apr 25 at 21:31
1
1
I went ahead and did that and it works quite well. I'm satisfied with that as a workable solution.
– onlinespending
Apr 25 at 21:40
I went ahead and did that and it works quite well. I'm satisfied with that as a workable solution.
– onlinespending
Apr 25 at 21:40
You can now post what you did as an answer.
– GabrielaGarcia
Apr 26 at 20:22
You can now post what you did as an answer.
– GabrielaGarcia
Apr 26 at 20:22
add a comment
|
1 Answer
1
active
oldest
votes
Went ahead with solution I mentioned of simply creating a /boot partition on the bootable, BIOS-recognized HDD and placing the root filesystem on the NVMe which the BIOS does not recognize. Grub was properly installed to the /EFI partition (shared with the Windows Boot Manger), the kernel boot files to the /boot partition, and the root file system to the NVMe. Works as expected and well enough for my needs.
answered Apr 26 at 20:26
onlinespendingonlinespending
1162 bronze badges
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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/4.0/"u003ecc by-sa 4.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%2faskubuntu.com%2fquestions%2f1138182%2fspecify-boot-folder-during-installation-since-drive-is-not-accessible-by-bio%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
Went ahead with solution I mentioned of simply creating a /boot partition on the bootable, BIOS-recognized HDD and placing the root filesystem on the NVMe which the BIOS does not recognize. Grub was properly installed to the /EFI partition (shared with the Windows Boot Manger), the kernel boot files to the /boot partition, and the root file system to the NVMe. Works as expected and well enough for my needs.
answered Apr 26 at 20:26
onlinespendingonlinespending
1162 bronze badges
add a comment
|
Went ahead with solution I mentioned of simply creating a /boot partition on the bootable, BIOS-recognized HDD and placing the root filesystem on the NVMe which the BIOS does not recognize. Grub was properly installed to the /EFI partition (shared with the Windows Boot Manger), the kernel boot files to the /boot partition, and the root file system to the NVMe. Works as expected and well enough for my needs.
answered Apr 26 at 20:26
onlinespendingonlinespending
1162 bronze badges
add a comment
|
Went ahead with solution I mentioned of simply creating a /boot partition on the bootable, BIOS-recognized HDD and placing the root filesystem on the NVMe which the BIOS does not recognize. Grub was properly installed to the /EFI partition (shared with the Windows Boot Manger), the kernel boot files to the /boot partition, and the root file system to the NVMe. Works as expected and well enough for my needs.
answered Apr 26 at 20:26
onlinespendingonlinespending
1162 bronze badges
Went ahead with solution I mentioned of simply creating a /boot partition on the bootable, BIOS-recognized HDD and placing the root filesystem on the NVMe which the BIOS does not recognize. Grub was properly installed to the /EFI partition (shared with the Windows Boot Manger), the kernel boot files to the /boot partition, and the root file system to the NVMe. Works as expected and well enough for my needs.
answered Apr 26 at 20:26
onlinespendingonlinespending
1162 bronze badges
answered Apr 26 at 20:26
onlinespendingonlinespending
1162 bronze badges
answered Apr 26 at 20:26
onlinespendingonlinespending
1162 bronze badges
answered Apr 26 at 20:26
onlinespendingonlinespending
1162 bronze badges
1162 bronze badges
add a comment
|
add a comment
|
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1138182%2fspecify-boot-folder-during-installation-since-drive-is-not-accessible-by-bio%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
1
Do not confuse the ESP - efi system partition with a /boot partition. You just need to add a ext4 partition as /boot on HDD and installer will put kernel & rest of grub into that partition. Initial UEFI grub boot files are still in ESP. There is something new where you can put kernels into ESP, but that then does not use grub and is not a standard configuration. If an advanced user you can look up gummiboot which is now part of systemD and how to configure that. see also:NVME Samsung 970 Evo Plus drive using a PCIe card ubuntuforums.org/showthread.php?t=2415658
– oldfred
Apr 25 at 21:11
right. I'm not confusing the two. Just was hoping to place the /boot kernel files within the EFI partition as well, but may just go with obvious solution I mentioned of simply creating a /boot partition on the bootable, BIOS-recognized HDD and placing the root filesystem on the NVMe which the BIOS does not recognize
– onlinespending
Apr 25 at 21:31
1
I went ahead and did that and it works quite well. I'm satisfied with that as a workable solution.
– onlinespending
Apr 25 at 21:40
You can now post what you did as an answer.
– GabrielaGarcia
Apr 26 at 20:22