https://bugzilla.suse.com/show_bug.cgi?id=1231595 https://bugzilla.suse.com/show_bug.cgi?id=1231595#c1 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Bootloader --- Comment #1 from Stefan Hundhammer <shundhammer@suse.com> --- Yes, indeed this is a worst-case scenario, and most users will have to reinstall because of the complexity. But I am not sure if it's realistic to start this from the initrd. Let's ask our bootloader experts. As a side note, I keep the output of 'lsblk' in a file on my other machines:

sudo /usr/bin/lsblk -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINTS,UUID | sed -e 's/^/> /' NAME SIZE FSTYPE LABEL MOUNTPOINTS UUID nvme0n1 953.9G ├─nvme0n1p1 512M vfat efi-boot /boot/efi DCEA-F8DD ├─nvme0n1p2 2G swap swap [SWAP] 1eed3f64-cafc-4977-b8d7-e8ccb6a9857f ├─nvme0n1p3 100G ext4 root-01 / 8f206b58-5422-40cd-b561-d3ee1dd4d110 ├─nvme0n1p4 100G ext4 root-02 /alternate-root 5969e673-2daa-4904-9d62-8f6d475121d7 ├─nvme0n1p5 200G crypto_LUKS 771f09d1-0b53-4537-9e0a-3afb40430e3c └─nvme0n1p6 551.4G ext4 work /work ba3949fe-98db-4d09-926d-c8ed50e07132

This comes very handy in a situation like this. -- You are receiving this mail because: You are on the CC list for the bug.