------- Comment From [email protected] 2020-10-01 09:43 EDT-------
Took me a bit longer than expected, as I ran into some other unrelated issue. 
Unfortunately I was not successful. What I did on a pristine Ubuntu 20.04.1 
install with a luks-encrypted setup was:

$ add-apt-repository ppa:cascardo/kdump2
$ apt update
$ apt install kexec-tools
$ apt install kdump-tools

The initrd was rebuild and the zipl was run, however zipl.conf wasn't
updated with a new crashkernel value and after rebooting it was still
the old value of 196 in the kernel command line.

Here's the output of dpkg -l for kexec-tools and kdump-tools

ii  kexec-tools    1:2.0.18-1ubuntu1 s390x        tools to support fast kexec r
ii  kdump-tools    1:1.6.7-4ubuntu1+cascardo2 s390x        scripts and tools fo

Here's my cryptab content:
vda6_crypt UUID=3b1c23fa-0cc4-4ba1-b47e-974f79db1b5c none luks,discard

fstab:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/vgubuntu-root /               ext4    errors=remount-ro 0       1
# /boot was on /dev/vda5 during installation
UUID=44950dee-686a-4946-b64e-8b54976d254a /boot           ext4    defaults      
  0       2
/dev/mapper/vgubuntu-swap_1 none            swap    sw              0       0

lsblk output:
NAME                  MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
vda                   252:0    0    6G  0 disk
??vda1                252:1    0  512M  0 part
??vda2                252:2    0    1K  0 part
??vda5                252:5    0  731M  0 part  /boot
??vda6                252:6    0  4.8G  0 part
??vda6_crypt        253:0    0  4.8G  0 crypt
??vgubuntu-root   253:1    0  3.8G  0 lvm   /
??vgubuntu-swap_1 253:2    0  976M  0 lvm   [SWAP]

Maybe I did something wrong. Let me know.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877533

Title:
  [20.10 FEAT] Increase the crashkernel setting if the root volume is
  luks2-encrypted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to