Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #265399
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Possibly broken Grub or initrd after updates on Testing |
| Date | 2024-01-01 17:50 +0100 |
| Message-ID | <HRtEd-5kk-1@gated-at.bofh.it> (permalink) |
| References | <HRobv-1YJ-9@gated-at.bofh.it> <HRp7z-2Cx-5@gated-at.bofh.it> <HRtux-5h4-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon 01 Jan 2024 at 17:37:44 (+0100), Richard Rosner wrote:
> So, I found a way to manually mount luks partition in Grub and boot from it.
>
> What I did to get there:
> set root=(hd0,gpt2)
> cryptomount -a
>
> This gave me the unencrypted version of the root partition as (crypto1)
>
> set root=(crypto1)
> linux /vmlinuz root=/dev/mapper/luks-UUID
> initrd /initrd.img
> boot
>
> The problem only is to get the UUID format right. When you're asked to enter the decryption key in a normal boot, it's shown, but without any dashes. But the format must be the same eg Disks shows it. But sure if a Grub tool can show that, but worst case you'll be booted into a initrd BusyBox terminal where you can just look inside /dev/mapper and see the true path that needs to be entered.
>
> Question is, how do I repair the boot process so I don't have to boot by hand every time?
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.
Cheers,
David.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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