Follow-up Comment #7, bug #26954 (project grub): The "workaround mentality" comes from the fact that there are no clear suggestions for how to resolve the problem. The error message is fairly opaque, even though i think i have a decent grasp of what's going on.
It sounds to me like you're saying that the right solution is to create a new partition table on the device with different (better?) parameters. This would most likely destroy the data currently on the device, right? I ended up taking this route, by creating a new partition table with 63 sectors per trac with a single VFAT partition on it: umount /dev/sdc1 fdisk -S 63 /dev/sdc o n 1 t c w mkfs -t vfat /dev/sdc1 Could you suggest how to make a GPT with BIOS boot partition? Would i use parted for that? Could the grub-setup error message in this case be friendlier? What about something like "You could provide more space for embedding by changing your partitioning scheme, though this may put data on the drive in question at risk (see parted(8), for example)" ? http://en.wikipedia.org/wiki/BIOS_Boot_Partition_%28GPT%29 suggests that you need parted 2.0 in order to make a BIOS Boot Partition, but http://www.gnu.org/software/parted/download.shtml suggests that version 1.9.0 is the latest stable version. I don't see how to make a GPT with a BIOS Boot Partition, i'm afraid. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?26954> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ _______________________________________________ Bug-grub mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-grub
