ubuntu-seed / ubuntu-boot partition detection could be improved
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Confirmed
|
Medium
|
Unassigned | ||
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
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_
https:/
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_
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?
Changed in snapd: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Ian Johnson (anonymouse67) |
tags: | added: uc20 |
Changed in snapd: | |
assignee: | Ian Johnson (anonymouse67) → nobody |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1902748
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.