Public bug reported:
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
** Affects: cloud-images
Importance: Undecided
Status: New
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Affects: u-boot (Ubuntu)
Importance: Undecided
Status: New
** Affects: u-boot-menu (Ubuntu)
Importance: Undecided
Status: New
** Tags: rls-ii-incoming
** Description changed:
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
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: u-boot (Ubuntu)
Importance: Undecided
Status: New
** Also affects: u-boot-menu (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-images
Importance: Undecided
Status: New
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923464
Title:
ideally should boot rootfs from a matching hard drive
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1923464/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
