Grub2 entries to boot Wubi incorrect... "Error: file not found, Press any key to continue" at boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lupin |
Invalid
|
Undecided
|
Unassigned | ||
grub2 (Ubuntu) |
Fix Released
|
High
|
Colin Watson | ||
Natty |
Fix Released
|
High
|
Colin Watson |
Bug Description
The 10_lupin script generates menu entries to boot Wubi installs. The following entry has been created:
### BEGIN /etc/grub.
menuentry "Ubuntu, Linux 2.6.38-7-generic" {
insmod ext2
set root='(/dev/loop0)'
search --no-floppy --fs-uuid --set=root 23b0f259-
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
initrd /boot/initrd.
}
The UUID 23bf... is the loop device /dev/loop0. The file /ubuntu/
I'm not sure exactly what the cause of the message is - but after selecting to boot, the next screen you get a blank screen with:
"Error: file not found.
Press any key to continue"
After pressing a key it then boots normally.
This did not happen on the initial install, so I assume it's changed since running updates.
I also noticed a flashed 'Error: file not found' just before the grub menu displays. This also did not happen on the initial install.
Just for reference here is a copy of a Lucid version of a lupin menuentry for Wubi. Note the differences of insmod ntfs, and setting root to the partition (not loop device).
On a lucid wubi it looks similar to this:
### BEGIN /etc/grub.
menuentry "Ubuntu, Linux 2.6.32-27-generic" {
insmod ntfs
set root='(hd0,2)'
search --no-floppy --fs-uuid --set 80E4E195E4E18DAA
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
initrd /boot/initrd.
}
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: lupin-support 0.33
ProcVersionSign
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Sat Mar 19 10:52:15 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110314)
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: lupin
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
affects: | lupin (Ubuntu) → grub2 (Ubuntu) |
I reinstalled the same version of Wubi and checked grub.cfg. The lupin entry looks like this: d/10_lupin ### /dev/sda, msdos3) ' disks/root. disk 2.6.38- 6-generic root=UUID= 865491525491463 9 loop=/ubuntu/ disks/root. disk ro quiet splash img-2.6. 38-6-generic d/10_lupin ### f6f6-4e88- a1dc-0321acfe29 2f disks/root. disk 2.6.38- 6-generic root=UUID= 865491525491463 9 loop=/ubuntu/ disks/root. disk ro quiet splash img-2.6. 38-6-generic
### BEGIN /etc/grub.
menuentry "Ubuntu, Linux 2.6.38-6-generic" {
insmod part_msdos
insmod ntfs
set root='(
search --no-floppy --fs-uuid --set=root 8654915254914639
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
initrd /boot/initrd.
}
Apart from changing the target partition it shows that the grub.cfg changed after the install - the original entry looks like the traditional wubi entry, but then running "sudo update-grub" changes it to this:
### BEGIN /etc/grub.
menuentry "Ubuntu, Linux 2.6.38-6-generic" {
insmod ext2
set root='(/dev/loop0)'
search --no-floppy --fs-uuid --set=root b4c80465-
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
initrd /boot/initrd.
}
So I don't think this is a lupin script issue, but rather a grub2 issue.