On 01.01.24 20:30, David Wright wrote:
On Mon 01 Jan 2024 at 19:04:20 (+0100), Richard Rosner wrote:
On 01.01.24 18:13, David Wright wrote:
I can boot by hand, but since this is all archived anyways and it's
uneccessarily difficult to find some sort of guide how to even do
this, it might as well be a documentation for users having such
troubles in the future.
Also, besides the way that I have no clue how it would have to look
like to set up a paragraph in the grub.cfg, I simply don't see
anything wrong with it anyways. So I can't even look at the grub
settings files grub.cfg is being generated from to check where the
error lies.
You append the commands that you used to boot manually with into
/etc/grub.d/40_custom, observing the comments there, and also into
grub.cfg itself at the appropriate place (near the bottom). The
former is so that Grub includes it in any new grub.cfg that you
create.
Good to know.
This is the current content of the grub.cfg: https://pastes.io/bwsmqtkxa4
The UUID of the first partition containing the EFI stuff is 3647-0C47,
the root partition has d602e92a-af2b-4c44-86db-4ea155fafd08 (LUKS1
with ext4 as it seems - why does Debian still not default to creating
LUKS2 by default anyways after 5 years?) and the swap partition has
b33971d1-3407-4d81-a9c2-74c69064aebe (also LUKS1).
Because it could lock people out of their preexisting LUKS partitions.
I meant when you use the automated installer and wipe the whole disk
anyways. There wouldn't be any preexisting LUKS partitions left that
could be broken. Or can there not be LUKS1 and LUKS2 at the same time in
the event that e.g. the device with the system on is LUKS2 and another
device just containing data was LUKS1?
For me it looks like the grub.cfg has everything it needs to work.
Why do your linux lines have two root= strings?
No idea. I never really touched anything related to grub, besides the
earlier mentioned tries to get some logs. Also, since it looks like
there is no grub rescue mode installed (at least it's not being entered
when it should) I did remove the comment in front of
GRUB_DISABLE_RECOVER and set it to "false", just in case that for some
reason it would default to true, thus not installing grub rescue.
There's only one root in the /etc/default/grub.
