Ok, I found the errors in my ways. I misread the howto and had
the failed drives in the raidtab as the first drive in the raid,
there is a three line warning about the failed drive has to be
the last in the configuration.
Next thing I did is mount md0 as /mnt and md1 as /mnt/boot
and proceeded to copy the filesystem to /mnt.
Next I made a bootdisk using:
dd if=vmlinuz-2.2.14-5.0 of=/dev/fd0 bs=2k
rdev /dev/fd0 /dev/md0
rdev -r /dev/fd0 0
rdev -R /dev/fd0 1
Is their any better way to do this in RedHat? mkbootdisk maybe????
Next I changed /mnt/etc/fstab
/dev/md0 / ext2 defaults 1 1
/dev/md1 /boot ext2 defaults 1 2
I then unmounted the raid devices and rebooted with the floppy.
During Boot I get the following errors:
md.c: sizeof(mdp_super_t) = 4096
Partition check:
autodetecting RAID arrays
autorun ...
... autorun DONE.
Bad md_map in ll_rw_block
EXT2-fs: unable to read superblock
isofs_read_super: bread failed, dev=09:00, iso_blknum=16, block=32
Kernel panic: VFS: Unable to mount root fs on 09:00
One thing I also noticed after a reboot, if I re-mount /dev/md0 & md1 to
/mnt and /mnt/boot the file system seems corrupt. If I just mount md0 to
/mnt
then it seems to be ok. What causes this?
Also I'm a little shakey when it comes to making boot disks, I'm
reading up on that now.
Thanks In advance,
Robert Chapman
[EMAIL PROTECTED]
BTW: just wanted to re-itterate my configuration.
Red Hat 6.2 kernel 2.2.14-5.0
/etc/raidtab
# ---------------------------
# Sample raid-5 configuration
raiddev /dev/md0
raid-level 5
nr-raid-disks 3
persistent-superblock 1
chunk-size 32
# Parity placement algorithm
# parity-algorithm left-asymmetric
#
# the best one for maximum performance:
#
# parity-algorithm left-symmetric
# parity-algorithm right-asymmetric
# parity-algorithm right-symmetric
# Spare disks for hot reconstruction
nr-spare-disks 0
device /dev/sdc5
raid-disk 0
device /dev/sdb5
raid-disk 1
device /dev/sda5
failed-disk 2
#---------------------------------
# Sample raid-5 configuration
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
persistent-superblock 1
chunk-size 32
# Parity placement algorithm
# parity-algorithm left-asymmetric
#
# the best one for maximum performance:
#
# parity-algorithm left-symmetric
# parity-algorithm right-asymmetric
# parity-algorithm right-symmetric
# Spare disks for hot reconstruction
nr-spare-disks 0
device /dev/sdb1
raid-disk 0
device /dev/sda1
failed-disk 1
/etc/lilo.conf
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
linear
default=linux
image=/boot/vmlinuz-2.2.14-5.0
label=linux
initrd=/boot/initrd-2.2.14-5.0.img
read-only
root=/dev/sda5
/etc/lilo.conf.sda
# lilo.conf.sda
# GLOBAL SECTION
#device containing /boot directory
disk=/dev/md0
# geometry
bios=0x80
sectors=32
heads=64
cyclinders=17510
#dummy
partition=/dev/md1
# start of device "disk" above
start=32
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=LinuxRaid
image=/boot/vmlinuz-2.2.14-5.0
label=LinuxRaid
initrd=/boot/initrd-2.2.14-5.0.img
read-only
root=/dev/md0
/etc/lilo.conf.sdb
# lilo.conf.sdb
# GLOBAL SECTION
#device containing /boot directory
disk=/dev/md0
# geometry
bios=0x80
sectors=63
heads=255
cyclinders=2232
#dummy
partition=/dev/md1
# start of device "disk" above
start=63
boot=/dev/sdb
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=LinuxRaid
image=/boot/vmlinuz-2.2.14-5.0
label=LinuxRaid
initrd=/boot/initrd-2.2.14-5.0.img
read-only
root=/dev/md0
-----Original Message-----
From: Chapman, Robert
Sent: Tuesday, September 26, 2000 3:51 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Problems with setting up root+boot+raid Help!! :-s
I checked the raidtools and I am running 0.90. As for the
kernel, Im not sure what version is patched in. I did a "dmesg"
to see if I could find out which one, but no luck.
Robert F. Chapman
[EMAIL PROTECTED]
-----Original Message-----
From: Michael [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 26, 2000 4:18 PM
To: Chapman, Robert
Subject: RE: Problems with setting up root+boot+raid Help!! :-s
> I'm using the RH kernel and I haven't patched it at all, which
> raid patches are you referring to?
The RH kernels used to come stock with the 0.42 raid tool set. The
most recent raid tools are version 0.90
You need to look at the kernel startup output to determine what
version of raid it is built with and which raid personalities are
supported i.e. 0,1,4,5
The kernel must match the raid set type you are trying to use.
Michael
>
> Thanks
>
> Robert Chapman
> [EMAIL PROTECTED]
>
>
> -----Original Message-----
> From: Michael [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 26, 2000 2:00 PM
> To: Chapman, Robert
> Subject: RE: Problems with setting up root+boot+raid Help!! :-s
>
>
> > yes, I used "mke2fs /dev/md0" and I didn't receive any errors
> > so I assume it formatted correctly.
>
> Yep format should be OK
> Did you start with a clean kernel from kernel.org or use the RH
> kernel?? The raid patches should be applied to a clean kernel -- ya
> never know what you have with the ones that come with distributions.
>
> this is unrelated, but look at the "stride"
> parameter for mke2fs for faster raid access.
>
> [EMAIL PROTECTED]
>
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
