hi everyone.
a few days ago, my partition tables were fine. proof of fact: i
installed the new kernel-image-2.4.3-686 that was uploaded a few days
ago into my boot sector, and lilo did not complain; i am now running
that image. today, i was trying to set up my cd writer, so i added
append="hdd=ide-scsi" to lilo.conf, but now when i run lilo, i got this:
Warning: current root is not on the first disk
Device 0x0340: Invalid partition table, 2nd entry
3D address: 1/0/128 (129024)
Linear address: 1/0/2040 (2056320)
so i ran fdisk on my two drives, and this is what i see:
Disk /dev/hda: 16 heads, 63 sectors, 19590 cylinders
Units = cylinders of 1008 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 4909 2473978+ b Win95 FAT32
Partition 1 does not end on cylinder boundary:
phys=(307, 254, 63) should be (307, 15, 63)
/dev/hda2 4909 19588 7397932+ f Win95 Ext'd (LBA)
Partition 2 does not end on cylinder boundary:
phys=(204, 254, 63) should be (204, 15, 63)
/dev/hda5 4909 19588 7397901 b Win95 FAT32
Disk /dev/hdb: 16 heads, 63 sectors, 39683 cylinders
Units = cylinders of 1008 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 1 2040 1028128+ 82 Linux swap
Partition 1 does not end on cylinder boundary:
phys=(127, 254, 63) should be (127, 15, 63)
/dev/hdb2 2041 2455 208845 83 Linux
Partition 2 does not end on cylinder boundary:
phys=(153, 254, 63) should be (153, 15, 63)
/dev/hdb3 2455 39462 18651465 83 Linux
Partition 3 does not end on cylinder boundary:
phys=(1023, 254, 63) should be (1023, 15, 63)
/dev/hdb4 39462 39669 104422+ 83 Linux
Partition 4 does not end on cylinder boundary:
phys=(1023, 254, 63) should be (1023, 15, 63)
i've done nothing to my partition tables, and like i said, lilo
installed the 2.4.3 kernel image just fine, so this clearly wasn't a
problem a few days ago. this problem just seems to have appeared out of
nowhere. luckily i can still boot, but if my partition table ever gets
overwritten by Windows (i have had experiences with Windows doing that
for no reason), i won't be able to reinstall LILO.
is there a way to get either fdisk or lilo to fix this problem? by fix
i mean correct so that i can still boot and access my files.
/ben
--
|_ |_ | _ _ |_ PGP public key: http://www.wilykit.com/wilykit.key
|_) . |_)|(_|(_ |\ "Never rub another man's rhubarb." -- Joker
Attachment:
pgpWh7ZLooBpS.pgp
Description: PGP signature