Professional Web Applications Themes

lilo + raid1 - Linux Setup, Configuration & Administration

I have several systems with identical hardware that all have software raid1 running on RH9 on hot-swappable serial ata drives. One of our machines has developed a problem recently. Running 'lilo -v' used to write out boot sectors info for both drivers - now it only does one drive. lilo -v LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger 'lba32' extensions Copyright (C) 1999,2000 John Coffman boot = /dev/hda, map = /boot/map.0301 Reading boot sector from /dev/hda Merging with /boot/boot.b Mapping message file /boot/message Boot image: /boot/vmlinuz-2.4.20-20.9smp Mapping RAM disk /boot/initrd-2.4.20-20.9smp.img Added 2.4.20-20.9smp * Boot image: /boot/vmlinuz-2.4.20-20.9 Mapping RAM disk ...

  1. #1

    Default lilo + raid1

    I have several systems with identical hardware that all have software
    raid1 running on RH9 on hot-swappable serial ata drives.

    One of our machines has developed a problem recently. Running 'lilo
    -v' used to write out boot sectors info for both drivers - now it only
    does one drive.

    lilo -v
    LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
    'lba32' extensions Copyright (C) 1999,2000 John Coffman

    boot = /dev/hda, map = /boot/map.0301
    Reading boot sector from /dev/hda
    Merging with /boot/boot.b
    Mapping message file /boot/message
    Boot image: /boot/vmlinuz-2.4.20-20.9smp
    Mapping RAM disk /boot/initrd-2.4.20-20.9smp.img
    Added 2.4.20-20.9smp *
    Boot image: /boot/vmlinuz-2.4.20-20.9
    Mapping RAM disk /boot/initrd-2.4.20-20.9.img
    Added 2.4.20-20.9
    /boot/boot.0300 exists - no backup copy made.
    Writing boot sector.

    On other machines 'lilo -v' writes info to BOTH disks.

    LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
    'lba32' extensions Copyright (C) 1999,2000 John Coffman

    boot = /dev/hda, map = /boot/map.0301
    Reading boot sector from /dev/hda
    Merging with /boot/boot.b
    Mapping message file /boot/message
    Boot image: /boot/vmlinuz-2.4.20-20.9smp
    Mapping RAM disk /boot/initrd-2.4.20-20.9smp.img
    Added 2.4.20-20.9smp *
    Boot image: /boot/vmlinuz-2.4.20-20.9
    Mapping RAM disk /boot/initrd-2.4.20-20.9.img
    Added 2.4.20-20.9
    /boot/boot.0300 exists - no backup copy made.
    Writing boot sector.
    boot = /dev/hdb, map = /boot/map.0341
    Reading boot sector from /dev/hdb
    Merging with /boot/boot.b
    Mapping message file /boot/message
    Boot image: /boot/vmlinuz-2.4.20-20.9smp
    Mapping RAM disk /boot/initrd-2.4.20-20.9smp.img
    Added 2.4.20-20.9smp *
    Boot image: /boot/vmlinuz-2.4.20-20.9
    Mapping RAM disk /boot/initrd-2.4.20-20.9.img
    Added 2.4.20-20.9
    /boot/boot.0340 exists - no backup copy made.
    Writing boot sector.

    Since a number of machines have identical hardware+setup I took the
    lilo.conf file from another system and put it in.

    Still like just runs on on drive..

    Below I have the output of several setup files all take from other
    systems. Keep in mind the systems, partitions /proc/md5stat
    /etc/raidtab are EXACTLY the same. I've double and tripled checked -
    diff to..

    Basically lilo isn't writing its info to /dev/hdb anymore - for what
    reason is beyond me.

    Fdisk on BOTH /dev/hda and /dev/hdb looks as following. Partitions
    are the same size, hdX1 is bootable, with the same types of partitions

    Disk /dev/hda: 120.0 GB, 120034123776 bytes
    255 heads, 63 sectors/track, 14593 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

    Device Boot Start End Blocks Id System
    /dev/hda1 * 1 2677 21502971 fd Linux raid
    autodetect
    /dev/hda2 2678 12355 77738535 fd Linux raid
    autodetect
    /dev/hda3 12356 14331 15872220 fd Linux raid
    autodetect
    /dev/hda4 14332 14593 2104515 f Win95 Ext'd (LBA)
    /dev/hda5 14332 14592 2096451 fd Linux raid
    autodetect


    /proc/mdstat
    Personalities : [raid1]
    read_ahead 1024 sectors
    md5 : active raid1 hda5[0] hdb5[1]
    2096384 blocks [2/2] [UU]

    md3 : active raid1 hda3[0] hdb3[1]
    15872128 blocks [2/2] [UU]

    md2 : active raid1 hda2[0] hdb2[1]
    77738432 blocks [2/2] [UU]

    md1 : active raid1 hda1[0] hdb1[1]
    21502848 blocks [2/2] [UU]

    unused devices: <none>

    /etc/lilo.conf
    prompt
    timeout=50
    default=2.4.20-20.9smp
    boot=/dev/md1
    map=/boot/map
    install=/boot/boot.b
    message=/boot/message
    #linear
    lba32

    image=/boot/vmlinuz-2.4.20-20.9smp
    label=2.4.20-20.9smp
    initrd=/boot/initrd-2.4.20-20.9smp.img
    read-only
    root=/dev/md1

    image=/boot/vmlinuz-2.4.20-20.9
    label=2.4.20-20.9
    initrd=/boot/initrd-2.4.20-20.9.img
    read-only
    root=/dev/md1

    /etc/raidtab
    raiddev /dev/md1
    raid-level 1
    nr-raid-disks 2
    chunk-size 64k
    persistent-superblock 1
    nr-spare-disks 0
    device /dev/hda1
    raid-disk 0
    device /dev/hdb1
    raid-disk 1
    raiddev /dev/md2
    raid-level 1
    nr-raid-disks 2
    chunk-size 64k
    persistent-superblock 1
    nr-spare-disks 0
    device /dev/hda2
    raid-disk 0
    device /dev/hdb2
    raid-disk 1
    raiddev /dev/md3
    raid-level 1
    nr-raid-disks 2
    chunk-size 64k
    persistent-superblock 1
    nr-spare-disks 0
    device /dev/hda3
    raid-disk 0
    device /dev/hdb3
    raid-disk 1
    raiddev /dev/md5
    raid-level 1
    nr-raid-disks 2
    chunk-size 64k
    persistent-superblock 1
    nr-spare-disks 0
    device /dev/hda5
    raid-disk 0
    device /dev/hdb5
    raid-disk 1
    Roger Guest

  2. #2

    Default Re: lilo + raid1


    On 29 Sep 2003 19:57:49 -0700, net (Roger) wrote:
     

    You have not done a raid1 install for LILO, but rather a single-disk install.
    A raid1 installation is initiated by specifying the boot record on /dev/mdX:
    viz.,

    boot = /dev/md1

    NOTE: The RH version of LILO is 3 years out of date, and is not compatible
    with the present version 22 raid1 implementation. The version 22
    implementation writes the boot record to the partition, not the MBR, unless
    you request it to do so. Also, it uses a single map file, not one for each
    disk. (The raid1 codes transparently write the map file to all disks in the
    raid set.)

    see: http://freshmeat.net -- search for project: LILO

    --John



     

    JohnInSD Guest

  3. #3

    Default Re: lilo + raid1

    JohnInSD At san DOT rr dot COM <com> wrote in message news:<com>... 
    >
    > You have not done a raid1 install for LILO, but rather a single-disk install.
    > A raid1 installation is initiated by specifying the boot record on /dev/mdX:
    > viz.,
    >
    > boot = /dev/md1[/ref]

    Jon - thanks for the reply - BUT as listed in the lilo.conf file I
    posted above the boot=/dev/md1

    /etc/lilo.conf
    prompt
    timeout=50
    default=2.4.20-20.9smp
    boot=/dev/md1
    map=/boot/map
    install=/boot/boot.b
    message=/boot/message
    #linear
    lba32

    image=/boot/vmlinuz-2.4.20-20.9smp
    label=2.4.20-20.9smp
    initrd=/boot/initrd-2.4.20-20.9smp.img
    read-only
    root=/dev/md1

    image=/boot/vmlinuz-2.4.20-20.9
    label=2.4.20-20.9
    initrd=/boot/initrd-2.4.20-20.9.img
    read-only
    root=/dev/md1
     

    Others have suggested I put variations of the following in my
    lilo.conf

    raid-extra-boot="/dev/hda,/dev/hdc"
    disk=/dev/md1
    root=/dev/md1
    bios=0x80
    ectors=63
    heads=255
    cylinders=14593
    partition=/dev/md1
    start=63

    BUT all those result in syntax errors. Looking in the lilo.conf man
    page those options are not doented BUT that doesn't mean they does
    exists.

    Keeping in mind your comment that yes Lilo was depreciated in 7.3 or
    8.0 - I looked andt found the above commands were only implemented in
    lilo ~v22.1 or later - can't exactly remember.

    The point it unless I install a non-stock RH verison of lilo -
    something I've done before back in the 6.1 days - I'm stuck.

    Basically I installed grub and did some testing - booting the system
    with one or the other drives out and things worked out just fine. I
    just didn't want to make the jump to grub because I've just heard bad
    things about grub and raid. Grub w/o a system running raid I've ran
    since it became the default RH boot loader - but NOT in raid
    environments.

    Thanks for the suggestion of a newer lilo version. I would of gone
    that way but grub looks like its the safe bet for RH systems w/ raid
    over the long haul. I don't expect RH to invest any effort into newer
    lilo versions hence I'll switch boot loaders.

    Thanks!
    Roger Guest

  4. #4

    Default Re: lilo + raid1

    The "raid-extra-boot=" did not appear until LILO version 22. RedHat has not
    updated LILO in over 3 years. They are back on version 21, and not even the
    last of the version 21 series (LILO 21.7).

    Current version is available through http://freshmeat.net/projects/lilo.
    "make install" will install the update docs; but you may have to delete the
    version 21 Redhat man pages, since they are in a different location.

    --John


    On 1 Oct 2003 11:53:03 -0700, net (Roger) wrote:
     
    >>
    >> You have not done a raid1 install for LILO, but rather a single-disk install.
    >> A raid1 installation is initiated by specifying the boot record on /dev/mdX:
    >> viz.,
    >>
    >> boot = /dev/md1[/ref]
    >
    >Jon - thanks for the reply - BUT as listed in the lilo.conf file I
    >posted above the boot=/dev/md1
    >
    >/etc/lilo.conf
    >prompt
    >timeout=50
    >default=2.4.20-20.9smp
    >boot=/dev/md1
    >map=/boot/map
    >install=/boot/boot.b
    >message=/boot/message
    >#linear
    >lba32
    >
    >image=/boot/vmlinuz-2.4.20-20.9smp
    > label=2.4.20-20.9smp
    > initrd=/boot/initrd-2.4.20-20.9smp.img
    > read-only
    > root=/dev/md1
    >
    >image=/boot/vmlinuz-2.4.20-20.9
    > label=2.4.20-20.9
    > initrd=/boot/initrd-2.4.20-20.9.img
    > read-only
    > root=/dev/md1

    >
    >Others have suggested I put variations of the following in my
    >lilo.conf
    >
    >raid-extra-boot="/dev/hda,/dev/hdc"
    >disk=/dev/md1
    >root=/dev/md1
    >bios=0x80
    >ectors=63
    >heads=255
    >cylinders=14593
    >partition=/dev/md1
    >start=63
    >
    >BUT all those result in syntax errors. Looking in the lilo.conf man
    >page those options are not doented BUT that doesn't mean they does
    >exists.
    >
    >Keeping in mind your comment that yes Lilo was depreciated in 7.3 or
    >8.0 - I looked andt found the above commands were only implemented in
    >lilo ~v22.1 or later - can't exactly remember.
    >
    >The point it unless I install a non-stock RH verison of lilo -
    >something I've done before back in the 6.1 days - I'm stuck.
    >
    >Basically I installed grub and did some testing - booting the system
    >with one or the other drives out and things worked out just fine. I
    >just didn't want to make the jump to grub because I've just heard bad
    >things about grub and raid. Grub w/o a system running raid I've ran
    >since it became the default RH boot loader - but NOT in raid
    >environments.
    >
    >Thanks for the suggestion of a newer lilo version. I would of gone
    >that way but grub looks like its the safe bet for RH systems w/ raid
    >over the long haul. I don't expect RH to invest any effort into newer
    >lilo versions hence I'll switch boot loaders.
    >
    >Thanks![/ref]

    JohnInSD Guest

Similar Threads

  1. Promise 20276 FastTrak IDE RAID1 Hot Swap
    By Bernard in forum Linux Setup, Configuration & Administration
    Replies: 2
    Last Post: August 21st, 11:53 PM
  2. Booting 2nd HDD from Lilo
    By Darsin in forum Linux Setup, Configuration & Administration
    Replies: 5
    Last Post: August 15th, 07:33 AM
  3. Lilo Problems
    By Jefferson Cowart in forum Debian
    Replies: 7
    Last Post: August 12th, 05:10 AM
  4. OS X 10.2.6: Installing Classic on a RAID1 volume?
    By Bev A. Kupf in forum Mac Applications & Software
    Replies: 0
    Last Post: July 23rd, 02:38 AM
  5. Adding a second HD and using RAID1 (mirroring)?
    By Bev A. Kupf in forum Mac Applications & Software
    Replies: 1
    Last Post: July 3rd, 01:20 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139