Booting FreeBSD using grub2 on uefi machine
I just installed FreeBSD 10.3 on an HP 450-a114. The install went smoothly with no issues. The machine has Windows 10, Linux Mint, and an LFS distro. In the past (on the older BIOS-only machines), all I have had to do is add a menu entry to a grub file, run update-grub, and then FreeBSD would boot Using grub2. The machine I am on now is uefi, and I cannot get FreeBSD to boot. Windows and Linux boot fine though. Everything is on a single drive. Here are my partitions:
/dev/sda1 -> Some uefi partition (label: /boot/efi)
/dev/sda2 -> Some Windows partition
/dev/sda3 -> Windows 10
/dev/sda7 -> My LFS distro
/dev/sda6 -> Linux Mint
/dev/sda8 -> Some efi partition installed by FreeBSD (label: EFI)
/dev/sda9 -> FreeBSD
/dev/sda10 -> FreeBSD swap
/dev/sda4 -> Windows recovery image
/dev/sda5 -> Windows recovery image.
If anyone needs any type of command line output, I will be happy to post it.
grub2 dual-boot uefi
edited Jun 18 '16 at 0:13
Jeff Schaller
42.9k1159136
asked Jun 17 '16 at 23:54
PatrickPatrick
1234
bumped to the homepage by Community♦ 58 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I just installed FreeBSD 10.3 on an HP 450-a114. The install went smoothly with no issues. The machine has Windows 10, Linux Mint, and an LFS distro. In the past (on the older BIOS-only machines), all I have had to do is add a menu entry to a grub file, run update-grub, and then FreeBSD would boot Using grub2. The machine I am on now is uefi, and I cannot get FreeBSD to boot. Windows and Linux boot fine though. Everything is on a single drive. Here are my partitions:
/dev/sda1 -> Some uefi partition (label: /boot/efi)
/dev/sda2 -> Some Windows partition
/dev/sda3 -> Windows 10
/dev/sda7 -> My LFS distro
/dev/sda6 -> Linux Mint
/dev/sda8 -> Some efi partition installed by FreeBSD (label: EFI)
/dev/sda9 -> FreeBSD
/dev/sda10 -> FreeBSD swap
/dev/sda4 -> Windows recovery image
/dev/sda5 -> Windows recovery image.
If anyone needs any type of command line output, I will be happy to post it.
grub2 dual-boot uefi
edited Jun 18 '16 at 0:13
Jeff Schaller
42.9k1159136
asked Jun 17 '16 at 23:54
PatrickPatrick
1234
bumped to the homepage by Community♦ 58 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Have you tried chainloading sda8? Archwiki on grub
– cylgalad
Jun 18 '16 at 7:27
add a comment |
I just installed FreeBSD 10.3 on an HP 450-a114. The install went smoothly with no issues. The machine has Windows 10, Linux Mint, and an LFS distro. In the past (on the older BIOS-only machines), all I have had to do is add a menu entry to a grub file, run update-grub, and then FreeBSD would boot Using grub2. The machine I am on now is uefi, and I cannot get FreeBSD to boot. Windows and Linux boot fine though. Everything is on a single drive. Here are my partitions:
/dev/sda1 -> Some uefi partition (label: /boot/efi)
/dev/sda2 -> Some Windows partition
/dev/sda3 -> Windows 10
/dev/sda7 -> My LFS distro
/dev/sda6 -> Linux Mint
/dev/sda8 -> Some efi partition installed by FreeBSD (label: EFI)
/dev/sda9 -> FreeBSD
/dev/sda10 -> FreeBSD swap
/dev/sda4 -> Windows recovery image
/dev/sda5 -> Windows recovery image.
If anyone needs any type of command line output, I will be happy to post it.
grub2 dual-boot uefi
edited Jun 18 '16 at 0:13
Jeff Schaller
42.9k1159136
asked Jun 17 '16 at 23:54
PatrickPatrick
1234
I just installed FreeBSD 10.3 on an HP 450-a114. The install went smoothly with no issues. The machine has Windows 10, Linux Mint, and an LFS distro. In the past (on the older BIOS-only machines), all I have had to do is add a menu entry to a grub file, run update-grub, and then FreeBSD would boot Using grub2. The machine I am on now is uefi, and I cannot get FreeBSD to boot. Windows and Linux boot fine though. Everything is on a single drive. Here are my partitions:
/dev/sda1 -> Some uefi partition (label: /boot/efi)
/dev/sda2 -> Some Windows partition
/dev/sda3 -> Windows 10
/dev/sda7 -> My LFS distro
/dev/sda6 -> Linux Mint
/dev/sda8 -> Some efi partition installed by FreeBSD (label: EFI)
/dev/sda9 -> FreeBSD
/dev/sda10 -> FreeBSD swap
/dev/sda4 -> Windows recovery image
/dev/sda5 -> Windows recovery image.
If anyone needs any type of command line output, I will be happy to post it.
grub2 dual-boot uefi
grub2 dual-boot uefi
edited Jun 18 '16 at 0:13
Jeff Schaller
42.9k1159136
asked Jun 17 '16 at 23:54
PatrickPatrick
1234
edited Jun 18 '16 at 0:13
Jeff Schaller
42.9k1159136
asked Jun 17 '16 at 23:54
PatrickPatrick
1234
edited Jun 18 '16 at 0:13
Jeff Schaller
42.9k1159136
edited Jun 18 '16 at 0:13
Jeff Schaller
42.9k1159136
edited Jun 18 '16 at 0:13
Jeff Schaller
42.9k1159136
42.9k1159136
asked Jun 17 '16 at 23:54
PatrickPatrick
1234
asked Jun 17 '16 at 23:54
PatrickPatrick
1234
asked Jun 17 '16 at 23:54
PatrickPatrick
1234
1234
bumped to the homepage by Community♦ 58 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 58 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Have you tried chainloading sda8? Archwiki on grub
– cylgalad
Jun 18 '16 at 7:27
add a comment |
Have you tried chainloading sda8? Archwiki on grub
– cylgalad
Jun 18 '16 at 7:27
Have you tried chainloading sda8? Archwiki on grub
– cylgalad
Jun 18 '16 at 7:27
Have you tried chainloading sda8? Archwiki on grub
– cylgalad
Jun 18 '16 at 7:27
add a comment |
1 Answer
1
active
oldest
votes
So /dev/sda1 is probably the EFI system partition used by Windows, LFS and Mint. You can boot into them because the relevant files for these operating systems are inside /dev/sda1 and so is GRUB. Therefore, GRUB can detect them.
However, the FreeBSD installation has created it's own EFI system partition in /dev/sda8 and this is the reason why update-grub doesn't work because the GRUB in /dev/sda1 isn't able to find the relevant EFI files in /dev/sda1.
You can try moving the relevant EFI files in /dev/sda8 created by FreeBSD to /dev/sda1, edit them to reflect the changes, and try running update-grub again.
On another note, why install so many operating systems on so many partitions? Using a virtualization solution like qemu or VirtualBox might be a better option.
answered Jun 18 '16 at 3:33
Libre ArchLibre Arch
1587
I will try that. I am very familiar with virtual machines, but my computer is not the highest quality, so I can only run 32-bit virtual machines, and even these are SO slow.
– Patrick
Jun 18 '16 at 12:13
So, I just went into the machines boot device options as I was booting, I found a weird efi entry, hit, and it booted (I had not moved any files like you suggested). Is there are way to get grub to do the same thing?
– Patrick
Jun 18 '16 at 12:35
@pdf4664 Yes, you can use your UEFI boot menu to boot into either of the operating systems. You can try to move your FreeBSD EFI files in/dev/sda8to/dev/sda1and runupdate-grubin either Mint or LFS. I think that should work.
– Libre Arch
Jun 18 '16 at 14:10
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%2f290508%2fbooting-freebsd-using-grub2-on-uefi-machine%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
So /dev/sda1 is probably the EFI system partition used by Windows, LFS and Mint. You can boot into them because the relevant files for these operating systems are inside /dev/sda1 and so is GRUB. Therefore, GRUB can detect them.
However, the FreeBSD installation has created it's own EFI system partition in /dev/sda8 and this is the reason why update-grub doesn't work because the GRUB in /dev/sda1 isn't able to find the relevant EFI files in /dev/sda1.
You can try moving the relevant EFI files in /dev/sda8 created by FreeBSD to /dev/sda1, edit them to reflect the changes, and try running update-grub again.
On another note, why install so many operating systems on so many partitions? Using a virtualization solution like qemu or VirtualBox might be a better option.
answered Jun 18 '16 at 3:33
Libre ArchLibre Arch
1587
I will try that. I am very familiar with virtual machines, but my computer is not the highest quality, so I can only run 32-bit virtual machines, and even these are SO slow.
– Patrick
Jun 18 '16 at 12:13
So, I just went into the machines boot device options as I was booting, I found a weird efi entry, hit, and it booted (I had not moved any files like you suggested). Is there are way to get grub to do the same thing?
– Patrick
Jun 18 '16 at 12:35
@pdf4664 Yes, you can use your UEFI boot menu to boot into either of the operating systems. You can try to move your FreeBSD EFI files in/dev/sda8to/dev/sda1and runupdate-grubin either Mint or LFS. I think that should work.
– Libre Arch
Jun 18 '16 at 14:10
add a comment |
So /dev/sda1 is probably the EFI system partition used by Windows, LFS and Mint. You can boot into them because the relevant files for these operating systems are inside /dev/sda1 and so is GRUB. Therefore, GRUB can detect them.
However, the FreeBSD installation has created it's own EFI system partition in /dev/sda8 and this is the reason why update-grub doesn't work because the GRUB in /dev/sda1 isn't able to find the relevant EFI files in /dev/sda1.
You can try moving the relevant EFI files in /dev/sda8 created by FreeBSD to /dev/sda1, edit them to reflect the changes, and try running update-grub again.
On another note, why install so many operating systems on so many partitions? Using a virtualization solution like qemu or VirtualBox might be a better option.
answered Jun 18 '16 at 3:33
Libre ArchLibre Arch
1587
I will try that. I am very familiar with virtual machines, but my computer is not the highest quality, so I can only run 32-bit virtual machines, and even these are SO slow.
– Patrick
Jun 18 '16 at 12:13
So, I just went into the machines boot device options as I was booting, I found a weird efi entry, hit, and it booted (I had not moved any files like you suggested). Is there are way to get grub to do the same thing?
– Patrick
Jun 18 '16 at 12:35
@pdf4664 Yes, you can use your UEFI boot menu to boot into either of the operating systems. You can try to move your FreeBSD EFI files in/dev/sda8to/dev/sda1and runupdate-grubin either Mint or LFS. I think that should work.
– Libre Arch
Jun 18 '16 at 14:10
add a comment |
So /dev/sda1 is probably the EFI system partition used by Windows, LFS and Mint. You can boot into them because the relevant files for these operating systems are inside /dev/sda1 and so is GRUB. Therefore, GRUB can detect them.
However, the FreeBSD installation has created it's own EFI system partition in /dev/sda8 and this is the reason why update-grub doesn't work because the GRUB in /dev/sda1 isn't able to find the relevant EFI files in /dev/sda1.
You can try moving the relevant EFI files in /dev/sda8 created by FreeBSD to /dev/sda1, edit them to reflect the changes, and try running update-grub again.
On another note, why install so many operating systems on so many partitions? Using a virtualization solution like qemu or VirtualBox might be a better option.
answered Jun 18 '16 at 3:33
Libre ArchLibre Arch
1587
So /dev/sda1 is probably the EFI system partition used by Windows, LFS and Mint. You can boot into them because the relevant files for these operating systems are inside /dev/sda1 and so is GRUB. Therefore, GRUB can detect them.
However, the FreeBSD installation has created it's own EFI system partition in /dev/sda8 and this is the reason why update-grub doesn't work because the GRUB in /dev/sda1 isn't able to find the relevant EFI files in /dev/sda1.
You can try moving the relevant EFI files in /dev/sda8 created by FreeBSD to /dev/sda1, edit them to reflect the changes, and try running update-grub again.
On another note, why install so many operating systems on so many partitions? Using a virtualization solution like qemu or VirtualBox might be a better option.
answered Jun 18 '16 at 3:33
Libre ArchLibre Arch
1587
answered Jun 18 '16 at 3:33
Libre ArchLibre Arch
1587
answered Jun 18 '16 at 3:33
Libre ArchLibre Arch
1587
answered Jun 18 '16 at 3:33
Libre ArchLibre Arch
1587
1587
I will try that. I am very familiar with virtual machines, but my computer is not the highest quality, so I can only run 32-bit virtual machines, and even these are SO slow.
– Patrick
Jun 18 '16 at 12:13
So, I just went into the machines boot device options as I was booting, I found a weird efi entry, hit, and it booted (I had not moved any files like you suggested). Is there are way to get grub to do the same thing?
– Patrick
Jun 18 '16 at 12:35
@pdf4664 Yes, you can use your UEFI boot menu to boot into either of the operating systems. You can try to move your FreeBSD EFI files in/dev/sda8to/dev/sda1and runupdate-grubin either Mint or LFS. I think that should work.
– Libre Arch
Jun 18 '16 at 14:10
add a comment |
I will try that. I am very familiar with virtual machines, but my computer is not the highest quality, so I can only run 32-bit virtual machines, and even these are SO slow.
– Patrick
Jun 18 '16 at 12:13
So, I just went into the machines boot device options as I was booting, I found a weird efi entry, hit, and it booted (I had not moved any files like you suggested). Is there are way to get grub to do the same thing?
– Patrick
Jun 18 '16 at 12:35
@pdf4664 Yes, you can use your UEFI boot menu to boot into either of the operating systems. You can try to move your FreeBSD EFI files in/dev/sda8to/dev/sda1and runupdate-grubin either Mint or LFS. I think that should work.
– Libre Arch
Jun 18 '16 at 14:10
I will try that. I am very familiar with virtual machines, but my computer is not the highest quality, so I can only run 32-bit virtual machines, and even these are SO slow.
– Patrick
Jun 18 '16 at 12:13
I will try that. I am very familiar with virtual machines, but my computer is not the highest quality, so I can only run 32-bit virtual machines, and even these are SO slow.
– Patrick
Jun 18 '16 at 12:13
So, I just went into the machines boot device options as I was booting, I found a weird efi entry, hit, and it booted (I had not moved any files like you suggested). Is there are way to get grub to do the same thing?
– Patrick
Jun 18 '16 at 12:35
So, I just went into the machines boot device options as I was booting, I found a weird efi entry, hit, and it booted (I had not moved any files like you suggested). Is there are way to get grub to do the same thing?
– Patrick
Jun 18 '16 at 12:35
@pdf4664 Yes, you can use your UEFI boot menu to boot into either of the operating systems. You can try to move your FreeBSD EFI files in
/dev/sda8 to /dev/sda1 and run update-grub in either Mint or LFS. I think that should work.– Libre Arch
Jun 18 '16 at 14:10
@pdf4664 Yes, you can use your UEFI boot menu to boot into either of the operating systems. You can try to move your FreeBSD EFI files in
/dev/sda8 to /dev/sda1 and run update-grub in either Mint or LFS. I think that should work.– Libre Arch
Jun 18 '16 at 14:10
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.
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%2f290508%2fbooting-freebsd-using-grub2-on-uefi-machine%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
Have you tried chainloading sda8? Archwiki on grub
– cylgalad
Jun 18 '16 at 7:27