Comment 8 for bug 14135
Revision history for this message
| Scott Merrilees (scott.merrilees) wrote | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
A slightly different wrinkle. I netbooted my laptop to do a feisty install because there wasn't space on / to do an upgrade. Did an expert install. When I tried to install grub, it failed. Bottom line was that I didn't format /boot, and grub was finding the definition of hd0 in device.map was /dev/hda, however seems like feisty is using the libata version, so hda needed to be sda.
My usual process for debugging grub/lilo install failures on installations goes like this, in case it is useful for someone else:
cd /
/target/bin/mount --bind /dev /target/dev
/target/bin/mount --bind /proc /target/proc
chroot /target /bin/bash
then I can do things like:
# grub-install hd0
/dev/sda3 does not have any corresponding BIOS drive
# # edit /boot/grub/
# grub-install hd0
Installation fnished. No error reported.
...
(hd0) /dev/sda
#
And then I could complete the rebuild. Seems like with a conversion to libata, the grub setup needs to deal with an existing device.map.