The 10_lupin script generates menu entries to boot Wubi installs. The following entry has been created:
### BEGIN /etc/grub.d/10_lupin ###
menuentry "Ubuntu, Linux 2.6.38-7-generic" {
insmod ext2
set root='(/dev/loop0)'
search --no-floppy --fs-uuid --set=root 23b0f259-6cdd-4cd2-bc50-8febbcb784b0
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.38-7-generic root=UUID=80E4E195E4E18DAA loop=/ubuntu/disks/root.disk ro quiet splash
initrd /boot/initrd.img-2.6.38-7-generic
}
The UUID 23bf... is the loop device /dev/loop0. The file /ubuntu/disks/root.disk is not on the loop device, it's on the host (UUID=80E4...). So to 1) set root to /dev/loop0 which it should be, override to /dev/loop0 by uuid, and then try to loop mount /ubuntu/disks/root.disk won't work.
On a lucid wubi it looks similar to this:
### BEGIN /etc/grub.d/10_lupin ###
menuentry "Ubuntu, Linux 2.6.32-27-generic" {
insmod ntfs
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 80E4E195E4E18DAA
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.32-27-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro quiet splash
initrd /boot/initrd.img-2.6.32-27-generic
}
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.
The 10_lupin script generates menu entries to boot Wubi installs. The following entry has been created: d/10_lupin ### 6cdd-4cd2- bc50-8febbcb784 b0 disks/root. disk 2.6.38- 7-generic root=UUID= 80E4E195E4E18DA A loop=/ubuntu/ disks/root. disk ro quiet splash img-2.6. 38-7-generic
### 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/ disks/root. disk is not on the loop device, it's on the host (UUID=80E4...). So to 1) set root to /dev/loop0 which it should be, override to /dev/loop0 by uuid, and then try to loop mount /ubuntu/ disks/root. disk won't work.
On a lucid wubi it looks similar to this: d/10_lupin ### disks/root. disk 2.6.32- 27-generic root=/dev/sda1 loop=/ubuntu/ disks/root. disk ro quiet splash img-2.6. 32-27-generic
### BEGIN /etc/grub.
menuentry "Ubuntu, Linux 2.6.32-27-generic" {
insmod ntfs
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 80E4E195E4E18DAA
loopback loop0 /ubuntu/
set root=(loop0)
linux /boot/vmlinuz-
initrd /boot/initrd.
}
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.
ProblemType: Bug ature: Ubuntu 2.6.38-7.36-generic 2.6.38
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)