Sorry, I forgot to add that I ran mkraid, as instructed in the HOWTO:

  [root@beethoven /root]# mkraid -f --only-superblock -c /etc/raidtab
/dev/md0
  mkraid is only relevant for RAID 1, 4, and 5 devices
  mkraid: aborted

thornton

Thornton Prime wrote:
> 
> After running several ckdisk/raidrun cycles, I finally got it to
> successfully run raidrun, but now mounting the disk reports:
> 
>   [root@beethoven /root]# mount /dev/md0 /home/stoli
>   mount: wrong fs type, bad option, bad superblock on /dev/md0,
>        or too many mounted file systems
> 
> Any recommendations?
> 
> thornton
> 
> Thornton Prime wrote:
> >
> > I got a few helpful responses from some folks on the mailing list, but
> > would like to throw things back out ...
> >
> > I can successfully run raidadd and ckraid, but raidrun always fails with
> > the message:
> >
> >    md: 09:00: raid array is not clean -- run ckraid
> >
> > ckraid always appears to complete without errors. I have run ckraid with
> > --fix, --force-continue, --suggest-failed-disk-mask 0x01,
> > --suggest-fix-parity, --force-check and a few combinations therein.
> >
> > Here is my /etc/raidtab
> >
> >   raiddev /dev/md0
> >
> >     raid-level                5
> >     nr-raid-disks             5
> >     nr-spare-disks            0
> >     chunk-size                16
> >     parity-algorithm          left-asymmetric
> >
> >     device                    /dev/sdd1
> >     raid-disk                 0
> >     device                    /dev/sde1
> >     raid-disk                 1
> >     device                    /dev/sdf1
> >     raid-disk                 2
> >     device                    /dev/sdg1
> >     raid-disk                 3
> >     device                    /dev/sdh1
> >     raid-disk                 4
> >
> > Here is /proc/mdstat after I run raidadd /dev/md0
> >
> >   Personalities : [4 raid5]
> >   read_ahead not set
> >   md0 : inactive sdd1 sde1 sdf1 sdg1 sdh1 44419200 blocks
> >   md1 : inactive
> >   md2 : inactive
> >   md3 : inactive
> >
> > The only message that shows up in the log is
> >
> >   md: 09:00: raid array is not clean -- run ckraid
> >
> > Just a re-cap. I am running RedHat 5.2, unpatched kernel 2.2.3, md is
> > compiled as kernel modules, but loads fine using insmod before I attempt
> > raidadd or anything else. (I also tried a 2.2.6 kernel with the raid
> > driver compiled in, and got the same results).
> >
> > Everything was all working grand before a power outage last night.
> >
> > Any help would be appreciated. As I mentioned before, if you need, I can
> > pay someone for time if they want to call (phone number below).
> >
> > thornton
> >
> > Thornton Prime wrote:
> > >
> > > I installed software RAID on a RedHat 5.2 machine last week. I had
> > > previously upgraded the kernel to 2.2.3. Everything went well.
> > >
> > > It is RAID5 on 5 Seagate SCSI drives on a BusLogic board, totalling
> > > around 35G of available disk space.
> > >
> > > Last night we had a power outage. The system restarted without problems
> > > except for the RAID. The was successfully recognized by the raidadd
> > > command, but it failed to start with the raidrun command. I ran ckraid
> > > with a number of different options, all ran successfully, but raidrun
> > > still failed.
> > >
> > > I downloaded, compiled and installed the latest RAID tools from RedHat.
> > > Supposedly all I need is raidstart, but this simply fails with an
> > > 'invalid argument'.
> > >
> > > I need to mount this drive. Bummer.
> > >
> > > This is urgent, so if someone felt so inclined, to call me at (310)
> > > 689-3170, call collect, ask for Thornton, and if you can fix the problem
> > > over the phone we will pay a fair value for your time.
> > >
> > > Of course, I gladly invite any suggestions via this list also.
> > >
> > > thornton

Reply via email to