Something like this happened when I attempted an Alpha 4 install on a 4th hd, sdb which has an NTFS data partition sdb1, on a second primary partition sdb2. Two other drives (one sdc, one hda) have non- functioning XP partitions. I instructed the installer to write grub to the MBR of sdb. When it didn't boot, I tried chainloading from GrubLegacy on sda which has Mepis 6.5, Hardy, and Jaunty on it. If I use the uuid spec instead of root, it informs me that it is booting from (hd3,1) ext4 [correct uuid] and then immediately follows with: Error 13: Invalid or unsupported executable format, making it seem that GrubLegacy not only is confused about the disk designations, but also is not chainloading. All the other partitions are quite accessible from GrubLegacy, and there is no problem with any of the other OSes . Grub has no stanzas for the XP partitions. Using the 'root' spec in the chainloading stanza calls forth Grub error 22: No such partition. After trying nearly every permutation of commands that seems to hold any hope, I will next try removing the unused XP drives, and then, if that brings no help, rearranging the partitions on the sdb drive. I have already tried reinstalling Grub2 from the LiveCD, with no difference to be seen.
Thanks for your efforts, Joe -- [karmic alpha 4] grub re-writes boot sector on wrong drive on mythbuntu install https://bugs.launchpad.net/bugs/414996 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
