Re: buster: cannot boot into kernel 4.19.0-17
These packages are also ”[residual-config]“. Which of them should also be (fully) installed with cryptsetup-initramfs?
cryptsetup docutils-common golang-github-gotk3-gotk3-dev ipython3-qtconsole libxvmc1 sgml-base tiny-initramfs-core tlp
xml-core
> > > Dear Sir or Madam,
> > > after an update of my packages (in debian stable for amd64 [1]), which included a newer kernel (from 4.19.0-16 to
> > > 4.19.0-17; [2]), I cannot boot with the newest kernel. After its selection and waiting for 35 seconds, a "rescue shell"
> > > (?) comes up [3].
> > > How can I change the UUID "the boot process" searches for? Do you know what went (or could have gone) wrong here?
> >
> > I think that GRUB reads the root device UUID or other identifier from
> > /etc/fstab, but I'm not sure.
> >
> > > Note: My disk is encrypted.
> > [...]
> >
> > Make sure you still have cryptsetup-initramfs installed.
> That was it; cryptsetup-initramfs was ”[residual-config]“:
>
> $ LC_ALL=C apt list cryptsetup-initramfs
> Listing... Done
> cryptsetup-initramfs/stable,now 2:2.1.0-5+deb10u2 all [residual-config]
>
> > Ben.
> Thanks.
Reply to: