On Mon, 2021-07-19 at 20:37 +0200, Ben Hutchings wrote: > On Wed, 2021-07-14 at 10:38 +0200, Julian Schreck wrote: > > 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.
To be more specific: I think update-grub does that. So if you change to a different root device you would have to update /etc/fstab and then run update-grub. But, if you've changed to a different root device, all the older kernel versions would also fail to boot if you didn't do that. > > Note: My disk is encrypted. > [...] > > Make sure you still have cryptsetup-initramfs installed. It's more likely that this package (or something else involved in initramfs building) has been uninstalled for some reason. Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer
signature.asc
Description: This is a digitally signed message part
