After Andreas and I compared side by side the 2 "set -x" outputs, we discovered what is happening.
https://pastebin.ubuntu.com/p/WyvnChrqBQ/ And "/dev/vda1" is being caught instead of "/dev/vda", as it happens to "/dev/sda" (instead of getting "/dev/sda1"). This logic comes a bit above that execution output: https://pastebin.ubuntu.com/p/ZRNHfnmJ4P/ And this is why andreas talks about "grub-mkdevicemap" here, and he is triggered by the "head -n1" usage: 17:10 <rafaeldtinoco> instead of /dev/vda 17:10 <andreas> cyphermox: I wonder about this head -n1 17:10 <andreas> default_bootdev_os="$($chroot $ROOT grub-mkdevicemap --no-floppy -m - | head -n1 | cut -f2)" 17:10 <andreas> if it's making an assumption 17:10 <cyphermox> well, usually hd0 is really what you want 17:10 <cyphermox> and it works for sda 17:10 <cyphermox> I mean, what is so different about virtio? 17:10 <andreas> yeah, I don't have the raw output in the sda case We then tested both, virtio and non-virtio installations and saw that, for the SCSI case: bash-5.0# grub-mkdevicemap --no-floppy -m - (hd0) /dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK_drive-scsi0-0-0 (hd1) /dev/disk/by-id/lvm-pv-uuid-oKqHJy-nRnC-nLm3-AuxT-FmpR-CCox-ltoWeB the disk is listed first (as hd0) in grub-mkdevicemap, while in the VIRTIO case, it is listed as SECOND (explaining why /dev/mapper was generated in subsequent wrong logic bellow). https://pastebin.ubuntu.com/p/hCNPH8GjgS/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838525 Title: LVM setup fails to install grub on virtio storage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1838525/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
