[Bug 1788775] [NEW] updating grub can end up with loopback devices in grub.cfg
Michael Hudson-Doyle
mwhudsonlp at fastmail.fm
Fri Aug 24 04:10:32 UTC 2018
Public bug reported:
I had (I think, I can't quite remember) the filesystem.squashfs from a
live server ISO mounted when the kernel was updated. A menu entry for
this OS-resembling device is now in my grub.cfg:
menuentry 'Ubuntu 18.04.1 LTS (18.04) (on /dev/loop35p1)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-cf05f674-791e-48eb-9b42-1bb903f4d024' {
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root cf05f674-791e-48eb-9b42-1bb903f4d024
else
search --no-floppy --fs-uuid --set=root cf05f674-791e-48eb-9b42-1bb903f4d024
fi
linux /boot/vmlinuz-4.15.0-29-generic root=UUID=cf05f674-791e-48eb-9b42-1bb903f4d024 ro
initrd /boot/initrd.img-4.15.0-29-generic
}
I didn't select it :)
Something in this setup should be skipping loopback devices, surely?
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1788775
Title:
updating grub can end up with loopback devices in grub.cfg
Status in grub2 package in Ubuntu:
New
Bug description:
I had (I think, I can't quite remember) the filesystem.squashfs from a
live server ISO mounted when the kernel was updated. A menu entry for
this OS-resembling device is now in my grub.cfg:
menuentry 'Ubuntu 18.04.1 LTS (18.04) (on /dev/loop35p1)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-cf05f674-791e-48eb-9b42-1bb903f4d024' {
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root cf05f674-791e-48eb-9b42-1bb903f4d024
else
search --no-floppy --fs-uuid --set=root cf05f674-791e-48eb-9b42-1bb903f4d024
fi
linux /boot/vmlinuz-4.15.0-29-generic root=UUID=cf05f674-791e-48eb-9b42-1bb903f4d024 ro
initrd /boot/initrd.img-4.15.0-29-generic
}
I didn't select it :)
Something in this setup should be skipping loopback devices, surely?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788775/+subscriptions
More information about the foundations-bugs
mailing list