grub-installer has multiple known issues when the target boot-device /rootfs-device class is not the the first one it finds/sorts/uses by default. This is experienced most commonly with scsi/nvme, but also visible with scsi/dasd drives; scsi/mmc drives, etc.
I have not confirmed that the below workarounds work on ppc64el, but in principle they should, as they do work on other platforms: Workaround 1) install the system with just nvme drive present, and thus remove/unplug ansy sda/sdb drives Workaround 2) ensure that sda/sdb drives are formatted clean, and do not have any PReP boot partitions (the logs indicate that PReP partitions on sda/sdb confuse grub-installer) Workaround 3) use the the subiquity installer, as it does not use grub- installer and is not affected by this multiple-classes of drives bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861655 Title: [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861655/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
