Public bug reported:
Because of https://bugs.launchpad.net/ubuntu/+source/kdump-
tools/+bug/2103470, this bug was obscured to me until I increased my
system's total RAM to 96GB, at which point kdump-tools could finally get
this far.
Ubuntu 24.10
kdump-tools 1:1.10.3ubuntu4
I would expect the kernel crash dump collector to start up, collect a
crash dump, and then either reboot or put up signposting indicating that
it has finished collecting a crash dump and is ready to reboot when I'd
like it to do so.
Instead, however, it starts into a Busybox shell (ash). This is after
decrypting the encrypted root and registering the LVM VG underneath, but
before actually _mounting_ the (ext4) LV. I'm able to mount these on
/root, which silences some of the errors, but the rescue environment
then tells me that it cannot start '' and the crash kernel itself panics
because init has died.
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: kdump-tools 1:1.10.3ubuntu4
ProcVersionSignature: Ubuntu 6.11.0-19.19-generic 6.11.11
Uname: Linux 6.11.0-19-generic x86_64
ApportVersion: 2.30.0-0ubuntu4.2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 17 19:59:45 2025
InstallationDate: Installed on 2025-02-03 (42 days ago)
InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4)
SourcePackage: kdump-tools
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: kdump-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug oracular wayland-session
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kdump-tools in Ubuntu.
Matching subscriptions: Maintainer
https://bugs.launchpad.net/bugs/2103471
Title:
kdump starts into ash instead of collecting a kernel core dump
(encrypted rootfs)
Status in kdump-tools package in Ubuntu:
New
Bug description:
Because of https://bugs.launchpad.net/ubuntu/+source/kdump-
tools/+bug/2103470, this bug was obscured to me until I increased my
system's total RAM to 96GB, at which point kdump-tools could finally
get this far.
Ubuntu 24.10
kdump-tools 1:1.10.3ubuntu4
I would expect the kernel crash dump collector to start up, collect a
crash dump, and then either reboot or put up signposting indicating
that it has finished collecting a crash dump and is ready to reboot
when I'd like it to do so.
Instead, however, it starts into a Busybox shell (ash). This is after
decrypting the encrypted root and registering the LVM VG underneath,
but before actually _mounting_ the (ext4) LV. I'm able to mount these
on /root, which silences some of the errors, but the rescue
environment then tells me that it cannot start '' and the crash kernel
itself panics because init has died.
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: kdump-tools 1:1.10.3ubuntu4
ProcVersionSignature: Ubuntu 6.11.0-19.19-generic 6.11.11
Uname: Linux 6.11.0-19-generic x86_64
ApportVersion: 2.30.0-0ubuntu4.2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 17 19:59:45 2025
InstallationDate: Installed on 2025-02-03 (42 days ago)
InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241009.4)
SourcePackage: kdump-tools
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2103471/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
