Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #72382

buster: cannot boot into kernel 4.19.0-17

From Julian Schreck <julian.schreck@online.de>
Newsgroups linux.debian.kernel
Subject buster: cannot boot into kernel 4.19.0-17
Date 2021-07-14 11:00 +0200
Message-ID <CAIUh-5BB-1@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


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?
Note: My disk is encrypted.

Kind regards,
 Julian Schreck

PS: forums.debian.net can be pinged right now, but my browser can't load the site.
--
[1] : $ uname -a
Linux first 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux

[2] : $ LC_ALL=C apt list -i *4.19*
Listing... Done
linux-headers-4.19.0-14-amd64/stable,stable,now 4.19.171-2 amd64 [installed]
linux-headers-4.19.0-14-common/stable,stable,now 4.19.171-2 all [installed,automatic]
linux-headers-4.19.0-16-amd64/stable,now 4.19.181-1 amd64 [installed]
linux-headers-4.19.0-16-common/stable,now 4.19.181-1 all [installed]
linux-headers-4.19.0-17-amd64/proposed-updates,stable-updates,now 4.19.194-2 amd64 [installed,automatic]
linux-headers-4.19.0-17-common/proposed-updates,stable-updates,now 4.19.194-2 all [installed,automatic]
linux-image-4.19.0-14-amd64/stable,stable,now 4.19.171-2 amd64 [installed]
linux-image-4.19.0-16-amd64/stable,now 4.19.181-1 amd64 [installed,automatic]
linux-image-4.19.0-17-amd64/proposed-updates,stable-updates,now 4.19.194-2 amd64 [installed,automatic]
linux-kbuild-4.19/proposed-updates,stable-updates,now 4.19.194-2 amd64 [installed,automatic]

[3] : Gave up waiting for suspend/resume device
Gave up waiting for root file system device.  Common problems:
– Boot args (cat /proc/cmdline)
  – Check rootdelay= (did the system wait long enough?)
– Missing modules (cat /proc/modules; ls /dev)
ALERT! UUID=[an unknown UUID] does not exist.  Dropping to a shell!


BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

Back to linux.debian.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

buster: cannot boot into kernel 4.19.0-17 Julian Schreck <julian.schreck@online.de> - 2021-07-14 11:00 +0200
  Re: buster: cannot boot into kernel 4.19.0-17 Ben Hutchings <ben@decadent.org.uk> - 2021-07-19 20:40 +0200
    Re: buster: cannot boot into kernel 4.19.0-17 Ben Hutchings <ben@decadent.org.uk> - 2021-07-19 20:50 +0200
    Re: buster: cannot boot into kernel 4.19.0-17 Julian Schreck <julian.schreck@online.de> - 2021-07-20 11:20 +0200
      Re: buster: cannot boot into kernel 4.19.0-17 Julian Schreck <julian.schreck@online.de> - 2021-07-20 11:50 +0200
        Re: buster: cannot boot into kernel 4.19.0-17 Ben Hutchings <ben@decadent.org.uk> - 2021-07-20 14:20 +0200

csiph-web