| Message ID | 20250415151729.12392-1-badrikesh.prusty@siemens.com |
|---|---|
| State | Accepted, archived |
| Headers | show |
| Series | wic: efi-plus-pcbios: Use --use-uuid for partitions (vs --ondisk sda) | expand |
On 2025-04-15 20:47, 'Badrikesh Prusty' via isar-users wrote: > After installing an image from isar-installer-image for x86-pc to an NVMe > drive, the boot process incorrectly checks /dev/sda1 for the boot partition, > as specified in /etc/fstab. > This is not an issue with devices using SATA drives but causes problems when > NVMe drives or multiple SATA drives are present. > This change checks for partition UUIDs vs /dev/sda device. Applied to next, thanks. With kind regards, Baurzhan
diff --git a/meta-isar/scripts/lib/wic/canned-wks/efi-plus-pcbios.wks b/meta-isar/scripts/lib/wic/canned-wks/efi-plus-pcbios.wks index 03928915..220df99d 100644 --- a/meta-isar/scripts/lib/wic/canned-wks/efi-plus-pcbios.wks +++ b/meta-isar/scripts/lib/wic/canned-wks/efi-plus-pcbios.wks @@ -1,6 +1,6 @@ # Example to show how to create an efi + pcbios image # Note, that the loader argument is mandatory. But systemd-boot also works. -part /boot --source bootimg-biosplusefi-isar --sourceparams="loader=grub-efi" --label boot --active --align 1024 -part / --source rootfs --ondisk sda --fstype=ext4 --mkfs-extraopts "-T default" --label platform --align 1024 --exclude-path=boot +part /boot --source bootimg-biosplusefi-isar --sourceparams="loader=grub-efi" --label boot --active --align 1024 --use-uuid +part / --source rootfs --fstype=ext4 --mkfs-extraopts "-T default" --label platform --align 1024 --use-uuid --exclude-path=boot bootloader --ptable gpt --timeout 3 --append "rootwait console=ttyS0,115200 console=tty0"