I can't find what's wrong with my lilo.conf

From: Jeff (jeff_at_rt.com)
Date: 05/26/04

  • Next message: David: "Re: I can't find what's wrong with my lilo.conf" 
    Date: 25 May 2004 20:44:28 -0700

    Hi, I am managing a remote system. I have a new drive mounted as a
    slave that I'm migrating everything over to, and when I'm done, the
    first drive will be taken out. When I try booting with the following
    lilo.conf, the system doesn't come up, and some one on site has to go
    and manually boot it into the kernel labeled "linux". I am not sure
    what is going wrong. At one point a couple of days ago someone on the
    site was able to get it into the RHELsmp kernel and the filesystem on
    hdc3 was mounted on root like I wanted, but now I can't repeat that on
    my own.

    I have already tried using linear instead of lba32, and I get the same
    result.

    [root@anuurn root]# cat /etc/lilo.conf
    prompt
    timeout=50
    default=RHELsmp
    boot=/dev/hda
    map=/boot/map
    install=/boot/boot.b
    message=/boot/message
    lba32

    image=/boot/vmlinuz-2.4.7-10
            label=linux.bak
            initrd=/boot/initrd-2.4.7-10.img
            read-only
            root=/dev/hda2

    image=/boot/vmlinuz-2.4.18-27.7.x
            label=linux
            root=/dev/hda2
            read-only
            initrd=/boot/initrd-2.4.18-27.7.x.img
            append="ide0=ata66 ide1=ata66 ide0=autotune ide1=autotune
    hda=autotune hdb=autotune hdc=autotune"

    image=/boot/vmlinuz-2.4.21-4.0.1.ELsmp
            label=RHELsmp
            initrd=/boot/initrd-2.4.21-4.0.1.ELsmp.img
            read-only
            append="root=/dev/hdc3"

    image=/boot/vmlinuz-2.4.21-4.0.1.EL
            label=RHEL
            initrd=/boot/initrd-2.4.21-4.0.1.EL.img
            read-only
            append="root=/dev/hdc3"

  • Next message: David: "Re: I can't find what's wrong with my lilo.conf"