From: TeusLollo <TeusLollo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: efibootmgr kernel hook does not create entry
Date: Mon, 22 Aug 2022 17:13:01 +0200 [thread overview]
Message-ID: <20220822151301.zvoOqbcIKHIsq2t9i_6Tcv_mBNiuJHpoVXxmDCkOceI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38533@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1932 bytes --]
New comment by TeusLollo on void-packages repository
https://github.com/void-linux/void-packages/issues/38533#issuecomment-1222497682
Comment:
> The last step in `post-install` looks suspicious
>
> ```
> efibootmgr -qo $bootorder
> ```
The step itself looks nominally correct to me, checking the man-page.
Problem is, we got a fairly complex setup at hand, as evidenced by the "manual" command OP reported working:
`doas efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "Void Linux with test kernel" --loader /vmlinuz-5.18.16_1 --unicode 'loglevel=4 rd.luks.name=809df427-d7d5-408c-a195-3be6e8681333=cryptroot root=/dev/mapper/cryptroot rd.luks.options=discard initrd=\initramfs-5.18.16_1.img' --verbose`
This is utilizing `LUKS`-based filesystem encryption, which can sometimes fail to boot due to seemingly-unrelated issues.
It would also be necessary to understand what values are being assigned into the `$bootorder` variable.
1. Are we by chance trying to boot through an `EFISTUB`? Because I don't see any bootloader-specific `.efi` file in the "manual" command the OP has reported to be working. Seemingly, OP is not using `GRUB`, ad example.
For comparison, a `GRUB`-based non-`LUKS` setup would use the following command: `efibootmgr -c -d /dev/sdx -p 1 -L "<label>" -l "/EFI/<label>/grubx64.efi"`.
2. Has the directory `/dev/nvme0n1` (Which I presume being the `EFI` directory) been marked with the proper `esp` flag?
3. This may not be particularly useful, but what's the output of `lsblk`, accounting also for the `LUKS` configuration? And what file systems are being utilized into relevant partitions? `Btrfs` with `LUKS `is known to throw seemingly-random errors for unclear reasons.
It's working when issuing a manual command, OP said.
Why does it not when automated? What's missing, if anything? Is everything that should go into `$bootorder` variable being assigned?
next prev parent reply other threads:[~2022-08-22 15:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 13:06 [ISSUE] " dkwo
2022-08-08 14:09 ` dkwo
2022-08-08 15:24 ` dkwo
2022-08-11 21:58 ` prez
2022-08-11 21:58 ` prez
2022-08-12 16:36 ` TeusLollo
2022-08-12 16:38 ` TeusLollo
2022-08-13 3:07 ` prez
2022-08-13 8:32 ` dkwo
2022-08-22 12:18 ` sgn
2022-08-22 15:12 ` TeusLollo
2022-08-22 15:13 ` TeusLollo [this message]
2022-08-22 15:41 ` Duncaen
2022-08-22 15:58 ` [ISSUE] [CLOSED] " dkwo
2022-08-22 15:58 ` dkwo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220822151301.zvoOqbcIKHIsq2t9i_6Tcv_mBNiuJHpoVXxmDCkOceI@z \
--to=teuslollo@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).