Public bug reported:
I'm trying to create a bootable disk image using an image file mounted
as a loop device with partx.
While the grub-install succeeds, when I attempt to boot in KVM or
VMware, it fails with the following error:
""""
error: no such device: 92136917-76ff-4115-9eed-9caa20529682.
Entering rescue mode...
grub rescue> _
""""
The grub boot configuration entry my process creates is pretty simple:
"""
menuentry 'Ubuntu LTS (v16.04)' {
search --set=root --no-floppy --fs-uuid 92136917-76ff-4115-9eed-9caa20529682
loopback loop /images/16.04.img
linux (loop)/vmlinuz root=UUID=92136917-76ff-4115-9eed-9caa20529682
rootdelay=120 rw quiet panic=5 vga=791 consoleblank=0 max_loop=256 splash
loop=/images/16.04.img net.ifnames=0 nomdmonisw nomdmonddf bootdegraded=true
audit=1
initrd (loop)/initrd.img
}
"""
I think it's because this commit is missing from Ubuntu 16.04's grub2
package:
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=35f2d96c0d68772c831952b2ee4eba6519d6ea1b
Could this get fixed in some way?
I'm using Ubuntu 16.04.6. The current grub2 package version is
"2.02~beta2-36ubuntu3.21".
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824245
Title:
Can't create a bootable disk by doing image creation on a loop device
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824245/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
