Disk Geometries reported incorrectly on 2.6.0-testX
Andrzej Krzysztofowicz replied to someone:
Quoted 4 lines
Quoted 1 line
The BIOS reads the MBR and jumps to the code loaded from there.
I found some PC BIOS-es refuse to read the MBR if no active partition is found in the partition table...
They read the MBR but refuse the execute the code contained in it. Reading the MBR is the only way that they get to find out that the partition table includes zero or two (or more) active partitions and decide not to boot.
SuSE 8.1 had this problem. If you installed grub to a /boot partition but intended to continue using your existing active partition, the installer activated the /boot partition. On the next boot, the BIOS detected two active partitions and refused to boot from the hard disk.
Booting a floppy still works on most machines. The BIOS still reads the MBR and presents the partition table in a block of information that is visible to the program that gets booted from the floppy disk. In my experience, the only machines that refused to do this (becoming 100% unbootable) were the old NEC 98 architecture.