hi
> - Make one copy of /etc/lilo.conf for each disk, i.e., lilo-sda.conf,
> lilo-sdb.conf, etc.
raid is supposed to be be hardware dependent... you should NOT
have to make 2 copies of lilo.conf
you need to make sure your kernel supports the scsi controller...
( ie... dont use the generic kernel ...
you need to fix initrd to spport your kernel...
or might be easier to do a partition test ( as shown below ) before
mucking with initrd issues
> > I read about setting a default value solving the "LI" problem, but it
> > didn't work for me.
lilo is NOT able to find the disks...
in your lilo.conf, all the chsp info is NOT needed ...
(cylinder,hed,sector,partition)
i claim that your partitions should look like
/ 64Mb or there abouts
/tmp 128Mb
/var 512mb
/usr 4Gb
/opt rest of disk - less swap
fix your /etc/raidtab to be something like
/ /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/md0
/tmp /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde2 /dev/md1
/var /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 /dev/sde3 /dev/md2
/usr /dev/sda5 /dev/sdb5 /dev/sdc5 /dev/sdd5 /dev/sde5 /dev/md3
/opt /dev/sda6 /dev/sdb6 /dev/sdc6 /dev/sdd6 /dev/sde6 /dev/md4
swap /dev/sda7 /dev/sdb7 /dev/sdc7 /dev/sdd7 /dev/sde7 /dev/md5
pull out any disks... and the system will still boot !!!
c ya
alvin
> > --- lilo.conf.sda: ---
> > disk=/dev/md0
> > bios=0x80
> > sectors=63
> > heads=255
> > cylinders=254
> > partition=/dev/md4
> > start=63
> > boot=/dev/sda
> > lba32
> > map=/boot/map
> > install=/boot/boot.b
> > timeout=50
> > message=/boot/message
> > delay=30
> > default=linux
> >
> > image=/boot/vmlinuz-2.2.16-22enterprise
> > label=linux
> > initrd=/boot/initrd-2.2.16-22enterprise.img
> > read-only
> > root=/dev/md0
> >
> > --- lilo.conf.sdb: ---
> > disk=/dev/md0
> > bios=0x80 (should this be 0x81 for modern hardware, less than 1 yr old?)
> > sectors=63
> > heads=255
> > cylinders=254
> > partition=/dev/md4
> > start=63
> > boot=/dev/sdb
> > lba32
> > map=/boot/map
> > install=/boot/boot.b
> > prompt
> > timeout=50
> > message=/boot/message
> > delay=30
> > default=linux
> >
> > image=/boot/vmlinuz-2.2.16-22enterprise
> > label=linux
> > initrd=/boot/initrd-2.2.16-22enterprise.img
> > read-only
> > root=/dev/md0
> >
> > Both lilo's were properly committed using 'lilo -C lilo.conf.sd[a,b]'
> >
> > --- cat /proc/mdstat ---
> > Personalities : [raid1]
> > read_ahead 1024 sectors
> > md0 : active raid1 sdb1[0] sda1[1] 2048192 blocks [2/2] [UU]
> > md2 : active raid1 sdb5[1] sda5[0] 4787264 blocks [2/2] [UU]
> > md1 : active raid1 sdd1[1] sdc1[0] 17775808 blocks [2/2] [UU]
> > unused devices: <none>
> >
> > --- fstab (truncated) ---
> > /dev/md0 / ext2 defaults 1 1
> > /dev/md1 /home ext2 defaults 1 2
> > /dev/md2 /var ext2 defaults 1 2
> >
> > Based on the above, what do I need to change in order to gracefully
> > recover from a disk failure?
> >
> > Any assistance would be greatly appreciated.
> >
> > Thanks,
> >
> > Dale
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > the body of a message to [EMAIL PROTECTED]
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
