errors after editing lilo..conf

Gerald Penyweit — Fri, 15 Feb 2002 23:51:13 GMT

Can someone tell me what the
below error messages mean from running "lilo" after making
modifications to the /etc/lilo.conf file? I have included the entries made to /etc/lilo.conf here. I made each entry singularly, then
ran /sbin/lilo on each line.
I have installed RH Linux 7.0, and RH Linux 7.2 on the respective partitions listed in /etc/lilo.conf and
can boot from both partitions
using its bootable floppy disks created after installing
Os'es. Here's the lilo.conf file here:

prompt
timeout=50
default=linux7_2
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.7-10
label=linux7_2
initrd=/boot/initrd-2.4.7-10.img
read-only
root=/dev/hda7

#First entry made, then lilo is run. 1st entry was
#commented out before second entry is made and lilo
#ran.
#Fatal: First sector of /dev/hda1 doesn't have a valid boot signature

#other=/dev/hda1
#label=linux7_0

#Second entry made.

#Fatal: open /boot/vmlinuz-2.2.16-22: No such file or directory

#image=/boot/vmlinuz-2.2.16-22
#label=linux7_0
#initrd=/boot/initrd-2.2.16-22.img
#read-only
#root=/dev/hda1

Re: errors after editing lilo..conf

Kodjo Agbenu — Sun, 17 Feb 2002 22:20:50 GMT

Hello,

The problem here is very simple : let's suppose you are currently running RedHat 7.2. Of course, your /boot is available for lilo to find the kernel, the initrd, the map file, and other information needed to build a boot sector.

However, the /boot you are using does not contain anything related to RedHat 7.0, because as you may have noticed, the partitions are not the same.

Now, let's find a way to solve this problem.

1. The bad way

Manually mount the /boot from RedHat 7.0, then copy the files needed by lilo to take the kernel 2.2.16 into account.

Why is it bad ? When booted on RedHat 7.0, imagine that you have to change something in the kernel or lilo configuration : you will have to do the same thing (mount the /boot from RedHat 7.2, etc...).

2. The good way

Boot on RedHat 7.0 and upgrade LILO program (from RedHat 7.2 cdroms) to make sure you have the same version of lilo on both versions.

Manually mount the /boot partition from RedHat 7.2, then copy the kernel and System.map-2.2.16... from 7.0 to 7.2's /boot directory.

Edit your /etc/fstab to make the /boot partition from 7.2 being your /boot on 7.0.

Move /etc/lilo.conf into the newly mounted boot, and create a symbolic link from /etc/lilo.conf to /boot/lilo.conf.

Edit your /boot/lilo.conf and make it boot both 7.0 and 7.2.
Use /sbin/lilo to refresh bootable sectors on the disk.

Reboot in 7.2, remove /etc/lilo.conf and make /etc/lilo.conf being a symlink to /boot/lilo.conf.

Good luck.

Kodjo

topic errors after editing lilo..conf in Operating System - Linux

errors after editing lilo..conf

Re: errors after editing lilo..conf