We both agree the second grub file will boot linux. I doubt it will boot windows, but don't care. Look at the LINUX line from first grub.cfg file from a 4G stick install, four lines cut out below:
set root='(hd2,msdos1)' search --no-floppy --fs-uuid --set 0ddfb60a-4791-45c9-85ec-c13c42c459af echo 'Loading Linux 2.6.35-22-generic ...' linux /boot/vmlinuz-2.6.35-22-generic root=/dev/sdc1 ro single It's the root=/dev/sdc1 part which makes boot fail, EVERY TIME. Surely you will admit that this overrides the search UUID business? I do nothing to cause the device to be used instead of the UUID. Installs to 4G sticks seem to get the device and will not boot without editing the grub commands. Installs to a USB hard disk seem to get the UUID and will work for the first linux boot. After so many bad installs to non-booting sticks, I tend to edit the grub commands at first boot and fix the obvious wrong items, and not to even try to see if the boot works. In addressing this bug, it is of interest that the problem is not consistently a problem with USB installs, since the USB hard disks will actually boot. -- Grub Installer gets devices wrong when running from live USB https://bugs.launchpad.net/bugs/384633 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
