I am having trouble getting the raid devices to come up at reboot.  I am running
kernel 2.2.6 w/ the raid0145-19990421-2.2.6 patches applied w/ autodetection of
raid devices and raid-1 support in the kernel, also i am using
raidtools-19990421-0.90 to mkraid.

I followed the instructions w/ the included Software-Raid Howto and set the
partition type to fd using fdisk, here is my raidtab:

raiddev /dev/md0
        raid-level      1
        nr-raid-disks   2
        nr-spare-disks  0
        persistent-superblock   1
        chunk-size      4
        device          /dev/hda7
        raid-disk       0
        device          /dev/hdc7
        raid-disk       1
raiddev /dev/md1
        raid-level      1
        nr-raid-disks   2
        nr-spare-disks  0
        persistent-superblock   1
        chunk-size      4
        device          /dev/hda8
        raid-disk       0
        device          /dev/hdc8
        raid-disk       1
raiddev /dev/md2
        raid-level      1
        nr-raid-disks   2
        nr-spare-disks  0
        persistent-superblock   1
        chunk-size      4
        device          /dev/hda5
        raid-disk       0
        device          /dev/hdc5
        raid-disk       1
raiddev /dev/md3
        raid-level      1
        nr-raid-disks   2
        nr-spare-disks  0
        persistent-superblock   1
        chunk-size      4
        device          /dev/hda9
        raid-disk       0
        device          /dev/hdc9
        raid-disk       1


after i do mkraid i can cat /proc/mdstat and see the progress of the syncing of
the disks ... once synced i can stop and start the md device w/ no problems,
the trouble is on reboot, at that time the kernel doesnt see /dev/hdc? as
operational and continues in degraded mode the actual syslog message is:

May  5 13:30:02 firebird kernel: autorun ...
May  5 13:30:02 firebird kernel: considering hda9 ...
May  5 13:30:02 firebird kernel:   adding hda9 ...
May  5 13:30:02 firebird kernel: created md3
May  5 13:30:02 firebird kernel: bind<hda9,1>
May  5 13:30:02 firebird kernel: running: <hda9>
May  5 13:30:02 firebird kernel: now!
May  5 13:30:02 firebird kernel: hda9's event counter: 00000004
May  5 13:30:02 firebird kernel: md3: former device hdc9 is unavailable, removin
g from array!
May  5 13:30:02 firebird kernel: md3: max total readahead window set to 128k
May  5 13:30:02 firebird kernel: md3: 1 data-disks, max readahead per data-disk:
 128k
May  5 13:30:02 firebird kernel: raid1: device hda9 operational as mirror 0
May  5 13:30:02 firebird kernel: raid1: md3, not all disks are operational -- tr
ying to recover array
May  5 13:30:02 firebird kernel: raid1: raid set md3 active with 1 out of 2 mirr
ors
May  5 13:30:02 firebird kernel: md: updating md3 RAID superblock on device
May  5 13:30:02 firebird kernel: hda9 [events: 00000005](write) hda9's sb offset
: 205504
May  5 13:30:02 firebird kernel: md: recovery thread got woken up ...
May  5 13:30:02 firebird kernel: md3: no spare disk to reconstruct array! -- con
tinuing in degraded mode
May  5 13:30:02 firebird kernel: md: recovery thread finished ...

it does that for each /dev/md? ... any help is appreciated

trey 

Reply via email to