UEFI Stub booting not working
up vote
0
down vote
favorite
I am trying to boot Arch Linux via an EFI Stub. I created an EFI partition (formatted as FAT32), a swap partition and a main partition on which I installed the Arch Linux core package group. I then used the efibootmgr to configure my motherboard to use the EFI partition to boot using the command as follows:
# efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "mysystem" --loader /vmlinuz-linux --unicode 'root=PARTUUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rw initrd=initramfs-linux.img' --verbose
I know that this worked because the boot option "mysystem" is showing up in my motherboard's BIOS boot options and it lists the SSD involved so I know the PARTUUID I used is correct.
However, when I tell the machine to boot this way it pauses briefly and then fails (either going back to the BIOS setup or giving an error message depending on how it was initiated).
So, either the EFI partition is empty for some reason or the files there are not matching the settings in the efibootmgr instruction. But I do not know how to diagnose this further. How do I even find out the contents of the EFI partition in the first place?
boot uefi
edited Nov 29 at 2:58
jasonwryan
48.7k14134184
asked Nov 29 at 2:51
Tyler Durden
1,52841849
add a comment |
up vote
0
down vote
favorite
I am trying to boot Arch Linux via an EFI Stub. I created an EFI partition (formatted as FAT32), a swap partition and a main partition on which I installed the Arch Linux core package group. I then used the efibootmgr to configure my motherboard to use the EFI partition to boot using the command as follows:
# efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "mysystem" --loader /vmlinuz-linux --unicode 'root=PARTUUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rw initrd=initramfs-linux.img' --verbose
I know that this worked because the boot option "mysystem" is showing up in my motherboard's BIOS boot options and it lists the SSD involved so I know the PARTUUID I used is correct.
However, when I tell the machine to boot this way it pauses briefly and then fails (either going back to the BIOS setup or giving an error message depending on how it was initiated).
So, either the EFI partition is empty for some reason or the files there are not matching the settings in the efibootmgr instruction. But I do not know how to diagnose this further. How do I even find out the contents of the EFI partition in the first place?
boot uefi
edited Nov 29 at 2:58
jasonwryan
48.7k14134184
asked Nov 29 at 2:51
Tyler Durden
1,52841849
Paste the output ofefibootmgrandtree $esp(for your ESP, obviously).
– jasonwryan
Nov 29 at 2:57
@jasonwryan That is not easy to do because the system is not booting, so I do not have web access for it yet. The command "tree $esp" results in the error "zsh: command not found: tree".
– Tyler Durden
Nov 29 at 3:19
You chroot in from the live media and paste from there. Instead of tree you can usels -R.
– jasonwryan
Nov 29 at 4:50
@jasonwryan ls -R $esp results in showing a single file: install.txt which is the file in the root directory of the archiso ramdisk.
– Tyler Durden
Nov 29 at 12:39
You chroot in from the archiso...
– jasonwryan
Nov 29 at 16:39
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am trying to boot Arch Linux via an EFI Stub. I created an EFI partition (formatted as FAT32), a swap partition and a main partition on which I installed the Arch Linux core package group. I then used the efibootmgr to configure my motherboard to use the EFI partition to boot using the command as follows:
# efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "mysystem" --loader /vmlinuz-linux --unicode 'root=PARTUUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rw initrd=initramfs-linux.img' --verbose
I know that this worked because the boot option "mysystem" is showing up in my motherboard's BIOS boot options and it lists the SSD involved so I know the PARTUUID I used is correct.
However, when I tell the machine to boot this way it pauses briefly and then fails (either going back to the BIOS setup or giving an error message depending on how it was initiated).
So, either the EFI partition is empty for some reason or the files there are not matching the settings in the efibootmgr instruction. But I do not know how to diagnose this further. How do I even find out the contents of the EFI partition in the first place?
boot uefi
edited Nov 29 at 2:58
jasonwryan
48.7k14134184
asked Nov 29 at 2:51
Tyler Durden
1,52841849
I am trying to boot Arch Linux via an EFI Stub. I created an EFI partition (formatted as FAT32), a swap partition and a main partition on which I installed the Arch Linux core package group. I then used the efibootmgr to configure my motherboard to use the EFI partition to boot using the command as follows:
# efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "mysystem" --loader /vmlinuz-linux --unicode 'root=PARTUUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rw initrd=initramfs-linux.img' --verbose
I know that this worked because the boot option "mysystem" is showing up in my motherboard's BIOS boot options and it lists the SSD involved so I know the PARTUUID I used is correct.
However, when I tell the machine to boot this way it pauses briefly and then fails (either going back to the BIOS setup or giving an error message depending on how it was initiated).
So, either the EFI partition is empty for some reason or the files there are not matching the settings in the efibootmgr instruction. But I do not know how to diagnose this further. How do I even find out the contents of the EFI partition in the first place?
boot uefi
boot uefi
edited Nov 29 at 2:58
jasonwryan
48.7k14134184
asked Nov 29 at 2:51
Tyler Durden
1,52841849
edited Nov 29 at 2:58
jasonwryan
48.7k14134184
asked Nov 29 at 2:51
Tyler Durden
1,52841849
edited Nov 29 at 2:58
jasonwryan
48.7k14134184
edited Nov 29 at 2:58
jasonwryan
48.7k14134184
edited Nov 29 at 2:58
jasonwryan
48.7k14134184
48.7k14134184
asked Nov 29 at 2:51
Tyler Durden
1,52841849
asked Nov 29 at 2:51
Tyler Durden
1,52841849
asked Nov 29 at 2:51
Tyler Durden
1,52841849
1,52841849
Paste the output ofefibootmgrandtree $esp(for your ESP, obviously).
– jasonwryan
Nov 29 at 2:57
@jasonwryan That is not easy to do because the system is not booting, so I do not have web access for it yet. The command "tree $esp" results in the error "zsh: command not found: tree".
– Tyler Durden
Nov 29 at 3:19
You chroot in from the live media and paste from there. Instead of tree you can usels -R.
– jasonwryan
Nov 29 at 4:50
@jasonwryan ls -R $esp results in showing a single file: install.txt which is the file in the root directory of the archiso ramdisk.
– Tyler Durden
Nov 29 at 12:39
You chroot in from the archiso...
– jasonwryan
Nov 29 at 16:39
add a comment |
Paste the output ofefibootmgrandtree $esp(for your ESP, obviously).
– jasonwryan
Nov 29 at 2:57
@jasonwryan That is not easy to do because the system is not booting, so I do not have web access for it yet. The command "tree $esp" results in the error "zsh: command not found: tree".
– Tyler Durden
Nov 29 at 3:19
You chroot in from the live media and paste from there. Instead of tree you can usels -R.
– jasonwryan
Nov 29 at 4:50
@jasonwryan ls -R $esp results in showing a single file: install.txt which is the file in the root directory of the archiso ramdisk.
– Tyler Durden
Nov 29 at 12:39
You chroot in from the archiso...
– jasonwryan
Nov 29 at 16:39
Paste the output of
efibootmgr and tree $esp (for your ESP, obviously).– jasonwryan
Nov 29 at 2:57
Paste the output of
efibootmgr and tree $esp (for your ESP, obviously).– jasonwryan
Nov 29 at 2:57
@jasonwryan That is not easy to do because the system is not booting, so I do not have web access for it yet. The command "tree $esp" results in the error "zsh: command not found: tree".
– Tyler Durden
Nov 29 at 3:19
@jasonwryan That is not easy to do because the system is not booting, so I do not have web access for it yet. The command "tree $esp" results in the error "zsh: command not found: tree".
– Tyler Durden
Nov 29 at 3:19
You chroot in from the live media and paste from there. Instead of tree you can use
ls -R.– jasonwryan
Nov 29 at 4:50
You chroot in from the live media and paste from there. Instead of tree you can use
ls -R.– jasonwryan
Nov 29 at 4:50
@jasonwryan ls -R $esp results in showing a single file: install.txt which is the file in the root directory of the archiso ramdisk.
– Tyler Durden
Nov 29 at 12:39
@jasonwryan ls -R $esp results in showing a single file: install.txt which is the file in the root directory of the archiso ramdisk.
– Tyler Durden
Nov 29 at 12:39
You chroot in from the archiso...
– jasonwryan
Nov 29 at 16:39
You chroot in from the archiso...
– jasonwryan
Nov 29 at 16:39
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f484813%2fuefi-stub-booting-not-working%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
Paste the output of
efibootmgrandtree $esp(for your ESP, obviously).– jasonwryan
Nov 29 at 2:57
@jasonwryan That is not easy to do because the system is not booting, so I do not have web access for it yet. The command "tree $esp" results in the error "zsh: command not found: tree".
– Tyler Durden
Nov 29 at 3:19
You chroot in from the live media and paste from there. Instead of tree you can use
ls -R.– jasonwryan
Nov 29 at 4:50
@jasonwryan ls -R $esp results in showing a single file: install.txt which is the file in the root directory of the archiso ramdisk.
– Tyler Durden
Nov 29 at 12:39
You chroot in from the archiso...
– jasonwryan
Nov 29 at 16:39