> using 2.5.29 (vanilla or BK-curr) i cannot use /sbin/lilo anymore
> to update the partition table.
> if i do it then the partition table gets corrupted and the system
> does not boot - it stops at 'LI'.
The standard explanation is that LILO cannot find the second stage
loader, like you say, and that happens because it looks in the wrong
place. For example, because it stores CHS coordinates in the wrong
geometry. (But it can also happen because something changed in the
disk numbering.)
"Corruption" of the partition table is to be expected only if you
ask LILO to rewrite the (CHS part of) the partition table.
The funny thing is, I removed some stuff here in 2.5.30,
so I would understand things immediately if you reported this
about 2.5.30. But for 2.5.29 I do not immediately see why
you would see any changes.
Did you in the meantime find out what was wrong?
Are things OK in 2.5.28 and wrong in vanilla 2.5.29
with the same version of LILO? (which version?)
Do you use the linear or lba32 options? The fix-table option?
What corruption do you see in the partition table?
Do you use LVM?
What happens under 2.5.30?
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/