No, actually the "File not found" error in this instance is due to the
installer using the wrong device.map parameters. Nothing at run time
could recover from this (I know Grub inside and out), short of redoing
grub-install with a fixed device.map.
The Edgy installer put grub onto the wrong (internal) hard drive, rather
than the correct (USB external) drive.
To do it properly, rather than toasting *both* drives as it did, it
should have (1) asked for permission since it had a choice of drives (no
need to ask if only one drive), and (2) the device.map should have
looked like this:
(hd0) /dev/sda
Instead of what it used:
(hd1) /dev/sda
Or this (internal drive):
(hd0) /dev/hda
This was a very fatal mistake by the installer -- it rendered both disks
completely unbootable, even the internal drive which I had never given
the installer permission to modify at any point. Bad bad BAD.
Cheers
Cheers
--
Edgy: install to USB drive leaves system unbootable
https://launchpad.net/bugs/68070
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
