Re: Possibly broken Grub or initrd after updates on Testing

From	Richard Rosner <richard@rosner-online.de>
Newsgroups	linux.debian.user
Subject	Re: Possibly broken Grub or initrd after updates on Testing
Date	2024-01-01 19:10 +0100
Message-ID	<HRuTD-6gR-3@gated-at.bofh.it> (permalink)
References	(1 earlier) <HRp7z-2Cx-5@gated-at.bofh.it> <HRtux-5h4-1@gated-at.bofh.it> <HRtEd-5kk-1@gated-at.bofh.it> <HRtNT-5nz-7@gated-at.bofh.it> <HRu7f-5Ml-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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 <deblis@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.
>

Thread

Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 11:50 +0100
  Re: Possibly broken Grub or initrd after updates on Testing Michael Kjörling <2695bd53d63c@ewoof.net> - 2024-01-01 12:00 +0100
    Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 13:00 +0100
      Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 17:40 +0100
        Re: Possibly broken Grub or initrd after updates on Testing David Wright <deblis@lionunicorn.co.uk> - 2024-01-01 17:50 +0100
          Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 18:00 +0100
            Re: Possibly broken Grub or initrd after updates on Testing David Wright <deblis@lionunicorn.co.uk> - 2024-01-01 18:20 +0100
              Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 19:10 +0100
                Re: Possibly broken Grub or initrd after updates on Testing David Wright <deblis@lionunicorn.co.uk> - 2024-01-01 20:40 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 21:30 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-01 21:50 +0100
                Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after  updates on Testing] Richard Rosner <richard@rosner-online.de> - 2024-01-03 20:30 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Eddie <eddie.seymour@gmail.com> - 2024-01-03 21:10 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-03 22:10 +0100
                Re: Possibly broken Grub or initrd after updates on Testing David Wright <deblis@lionunicorn.co.uk> - 2024-01-04 19:10 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-04 20:00 +0100
                Re: Possibly broken Grub or initrd after updates on Testing David Wright <deblis@lionunicorn.co.uk> - 2024-01-07 18:10 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-07 19:00 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-07 19:00 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Jeffrey Walton <noloader@gmail.com> - 2024-01-04 02:20 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Richard Rosner <richard@rosner-online.de> - 2024-01-04 08:50 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Pocket <pocket@columbus.rr.com> - 2024-01-04 12:00 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Jeffrey Walton <noloader@gmail.com> - 2024-01-04 12:00 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd after updates on Testing] Richard Rosner <richard@rosner-online.de> - 2024-01-04 13:10 +0100
                Re: Possibly broken Grub or initrd after updates on Testing Richard Rosner <richard@rosner-online.de> - 2024-01-04 08:50 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2024-01-04 08:20 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Joel Roth <joelz@pobox.com> - 2024-01-04 09:40 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Richard Rosner <richard@rosner-online.de> - 2024-01-04 12:00 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Richard Rosner <richard@rosner-online.de> - 2024-01-04 18:20 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Joel Roth <joelz@pobox.com> - 2024-01-04 19:00 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Jeffrey Walton <noloader@gmail.com> - 2024-01-05 00:40 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] songbird <songbird@anthive.com> - 2024-01-07 20:50 +0100
                Re: Replace Grub with rEFInd [WAS Possibly broken Grub or initrd  after updates on Testing] Richard Rosner <richard@rosner-online.de> - 2024-01-07 21:00 +0100

csiph-web