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.
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).
For me it looks like the grub.cfg has everything it needs to work.
On 01.01.24 18:13, David Wright wrote:
On Mon 01 Jan 2024 at 17:55:29 (+0100), Richard Rosner wrote:
On January 1, 2024 5:43:12 PM GMT+01:00, David Wright
<deb...@lionunicorn.co.uk> wrote:
Like this?
└─sda6 8:6 0 406.2G 0 part
└─luks-f3fbb9ba-a556-406c-b276-555e3e8577bc 254:1 0 406.2G 0 crypt /home
That's groups of 8 4 4 4 12.
Yes, exactly. Is there a way to show that from inside Grub? Lsblk and blkid
aren't available there?
I thought you could boot by hand. Then all the UUIDs are available
to you in lsblk, the /dev/disk/ symlinks, etc. I would then transcribe
them into a 40_custom paragraph in grub.cfg so you can boot easily.
Then I would work on getting Grub to write its grub.cfg correctly.
In the meantime, 40_custom would stay put.
Cheers,
David.
