Passing the ESP device ---------------------- All UEFI firmware already passes the device path of the loaded image in the EFI_LOADED_IMAGE_PROTOCOL installed on the handle passed to the loaded binary (shim, GRUB, Linux, ...). So your requirement is already fulfilled.
We just have to stop using legacy booting mechanisms. UUIDs ----- UUIDs are globally unique IDs. If two partitions with the same UUID exist in the system ,this is a grave user error. We should not try to fix it. Which remaining gap do you see? Or can we close this bug report as invalid? Best regards Heinrich -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923464 Title: ideally should boot rootfs from a matching hard drive Status in cloud-images: New Status in grub2 package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Status in systemd package in Ubuntu: New Status in u-boot package in Ubuntu: New Status in u-boot-menu package in Ubuntu: New Status in grub2 source package in Impish: New Status in initramfs-tools source package in Impish: New Status in systemd source package in Impish: New Status in u-boot source package in Impish: New Status in u-boot-menu source package in Impish: New Bug description: Ideally we should strive to boot rootfs from a matching hard drive. I.e. if we are booting rootfs by UUID, we should try to find the one that came from the same drive as where ESP (UEFI) came from, or u-boot spl / u-boot got loaded from (loader1/loader2). Such that for example, when booted from external usb stick, rootfs from there is mounted. Or when booted from internal drive whilst a dd backup is attached over usb, rootfs is loaded from the internal drive not from the usb attached backup. This would need: * u-boot to export the drive it loaded extlinux.conf / bootscript from, and pass it on kernel command line * grub to export the device UUID it got loaded from (from the BootServices EFI table) and pass it on the kernel command line or via runtime EFI variable * sdboot already does that I believe, but not sure if initramfs-tools consumes the sdboot provided information * initramfs-tools to consume above and sort the discovered devices based on that, when deciding what to mount as rootfs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1923464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
