Re: RAID superblock confusion

[Mike Fedyk <mfedyk@matchmail.com>]

On Wed, Apr 10, 2002 at 02:37:48PM -0600, Richard Gooch wrote:
> Andreas Dilger writes:
> > On Apr 10, 2002  13:24 -0600, Richard Gooch wrote:
> > > Andreas Dilger writes:
> > > > On Apr 10, 2002  09:33 -0600, Richard Gooch wrote:
> > > > > Even though I'm using persistent superblockss, which is supposed to
> > > > > allow one to move devices from one controller to another, I can't
> > > > > use my RAID) set in this configuration. Looks like a bug.
> > > > > 
> > > > > md0: former device scsi/host2/bus0/target1/lun0/part2 is unavailable,
> > > > >      removing from array!
> > > > > md: md0, array needs 6 disks, has 5, aborting.
> > > > 
> > > > Note that this appears to be your real problem.
> > > 
> > > No. I tested all 6 partitions used in the RAID set. They are all
> > > available.
> > 
> > Well, MD seems to think it is unavailable...  I would check the
> > codepath that generates this message and see why it is happening.
> > Maybe it is a timing issue or something, that MD autostart is
> > starting before this device is set up or something?  I don't know.
> 
> The device is set up (i.e. SCSI host driver is loaded) long before I
> do raidstart /dev/md/0

But kernel auto-detection doesn't depend on the raidstart command.  If
things are setup correctly, you can remove that from your init scripts.