Hi Anders, thanks for your testing. You can show all the initrd scripts
debug output to console, for that you'd need to add the kernel parameter
"debug=vc" for example. But I don't suggest to do that here, since you
seem not able to capture the full console log in plain/text form.
Pictures/snapshots might help to spot some issue, but they are very
limited.

So, instead of dumping the output to console, I'll suggest you 2 more
tests:

a) Add the following parameter to kernel command-line: "debug" . With
that, boot normally, and collect/save the following file, in order to
attach it here: "/run/initramfs/initramfs.debug" . This is the full
output of initrd scripts executed. After that, try the kdump - you need
to be sure it inherited this "debug" flag (check the kdump command-line
in "kdump-config show" output to validate it's there). Kdump will fail,
and you can try to SSH the file from the (initramfs) failure shell (or
even dump it there using the "cat" command and grab some pictures,
specially from the final portions of it). You may try to disconnect and
reconnect the keyboard, or use another USB port to see if you can get
that working in the failing (initramfs) shell.


b) Please execute the following 2 commands and submit the 2 resulting files 
here:

lsinitramfs /boot/initrd.img-$(uname -r) > regular_initrd.out
lsinitramfs /var/lib/kdump/initrd.img-$(uname -r) > kdump_initrd.out


Thanks in advance!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1913639

Title:
  linux-crashdump is not capable of mounting zfs root pools

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I could not get any crash logs after using this package.

  I tried using it and triggering a crash from a terminal. The alternate
  kernel boots successfully, but the initrd for linux-crashdump is not
  capable of loading my rpool.

  running: linux-crashdump:amd64 5.4.0.64.67

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-crashdump:amd64 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Jan 28 20:15:19 2021
  InstallationDate: Installed on 2019-08-15 (532 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   eno1      no wireless extensions.
   
   lo        no wireless extensions.
  MachineType: MSI MS-7885
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-65-generic 
root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash 
intel_iommu=on iommu=pt vfio-pci.ids=10de:1b81,10de:10f0,1b21:1242 
video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 
rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset 
crashkernel=2096M-:2096M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware                            1.187.8
  RfKill:
   0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-22 (281 days ago)
  dmi.bios.date: 06/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.E0
  dmi.board.asset.tag: Default string
  dmi.board.name: X99A SLI PLUS(MS-7885)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.E0:bd06/15/2018:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7885
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+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

Reply via email to