Public bug reported: ubuntu-seed / ubuntu-boot partition detection could be improved
Currently in the initrd, snapd-bootstrap searches for ubuntu-boot / ubuntu-seed partition by label or by UEFI variable that was set by sd- boot. sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH, HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to boot. https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h This is nice, but not unique enough. It would be nice if we were able to modify sd-boot stub to export something more specific that ideally maps to a sysfs path. For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH, USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH, UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such. That way initrd would be able to resolve better which block device to key off. Given that EFI device handle is passed to the kernel, doesn't kernel also know where it came from? or not? ** Affects: snapd Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1902748 Title: ubuntu-seed / ubuntu-boot partition detection could be improved Status in snapd: New Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ubuntu-seed / ubuntu-boot partition detection could be improved Currently in the initrd, snapd-bootstrap searches for ubuntu-boot / ubuntu-seed partition by label or by UEFI variable that was set by sd- boot. sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH, HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to boot. https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h This is nice, but not unique enough. It would be nice if we were able to modify sd-boot stub to export something more specific that ideally maps to a sysfs path. For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH, USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH, UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such. That way initrd would be able to resolve better which block device to key off. Given that EFI device handle is passed to the kernel, doesn't kernel also know where it came from? or not? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1902748/+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
