It sounds like you have a way to boot and look at files and that you have tried just rerunning lilo and that didn't work. I agree, the error message sure seems to imply that the wrong boot info is getting written to disk.
I'm shooting in the dark here. But, if you're using a Debian Rescue disk to boot and you're booting into your "normal" partitions (everything in your normal fstab is mounted), you might first make sure that the dist-upgrade completed: apt-get dist-upgrade I suggest this because, for large upgrades, it's not unusual for apt-get to exit on a package error with a lot of packages yet to be completely processed. With all the messages apt-get generates, I can be looking right at some error text and miss it. If that doesn't do anything, you might then try backing up your /etc/lilo.conf and uninstalling lilo with a purge. Then reinstall lilo: cp -p /etc/lilo.conf ~/lilo.conf.keep apt-get --purge remove lilo apt-get install lilo lilo I don't think the purge will remove /etc/lilo.conf, but, hopefully, you'll end up with the current version of the boot code. I'd assume that the map file is ok. But, you could try uninstalling / reinstalling the kernel, and running lilo again for good measure. This isn't helpful, but I've had really good luck with grub. ;-) On Tuesday 30 July 2002 08:27, Darrin Lajoie wrote: > After a dist-upgrade I've got a little lilo problem. I'm getting an > error: > > Fatal: First boot sector is version 21.5. Expecting version 22.2. > > I think it's either the /boot/map or the /boot/boot.b file that might > be the problem. How can I get lilo to re-generate those files from > scratch so that they work?
