Problems with mkraid on kernel 2.2.19

From: LYNDON PECK (LPECK@email.usps.gov)
Date: Thu Jan 03 2002 - 10:45:49 EST

Next message: Kurt Garloff: "Re: [patch] Re: PYXIS bug detection"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

The general situation-

     I have a Digital PWS500a (not au) - running kernel 2.2.19, raidtools
     0.90, two Adaptec 2940UW's and two Digital Shelf Towers (i forget the
     model number) but the each have 7 - 2 gig drives in them. I'd like to
     create two software raid blocks with these.

Problem -

I set up the raidtab:

     raiddev /dev/md0
             raid-level 5
             nr-raid-disks 7
             nr-spare-disks 0
             persistent-superblock 1
             parity-algorithm left-symmetric
             chunk-size 128
             device /dev/sda1
             raid-disk 0
             device /dev/sdb1
             raid-disk 1
             device /dev/sdc1
             raid-disk 2
             device /dev/sdd1
             raid-disk 3
             device /dev/sde1
             raid-disk 4
             device /dev/sdf1
             raid-disk 5
             device /dev/sdg1
             raid-disk 6

     raiddev /dev/md1
             raid-level 5
             nr-raid-disks 7
             nr-spare-disks 0
             persistent-superblock 1
             parity-algorithm left-symmetric
             chunk-size 128
             device /dev/sdh1
             raid-disk 0
             device /dev/sdi1
             raid-disk 1
             device /dev/sdj1
             raid-disk 2
             device /dev/sdk1
             raid-disk 3
             device /dev/sdl1
             raid-disk 4
             device /dev/sdm1
             raid-disk 5
             device /dev/sdn1
             raid-disk 6

- now when I run 'mkraid /dev/md0' I get this:

     handling MD device /dev/md0
     analyzing super-block
     disk 0: /dev/sda1, 2095662kB, raid superblock at 2095552kB
     disk 1: /dev/sdb1, 2095662kB, raid superblock at 2095552kB
     disk 2: /dev/sdc1, 2095662kB, raid superblock at 2095552kB
     disk 3: /dev/sdd1, 2095662kB, raid superblock at 2095552kB
     disk 4: /dev/sde1, 2095662kB, raid superblock at 2095552kB
     disk 5: /dev/sdf1, 2095662kB, raid superblock at 2095552kB
     disk 6: /dev/sdg1, 2095662kB, raid superblock at 2095552kB
     mkraid: aborted, see the syslog and /proc/mdstat for potential clues.

so I tried 'mkraid /dev/md0 --really-force' then I get pretty much the
same thing:

     DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
     handling MD device /dev/md0
     analyzing super-block
     disk 0: /dev/sda1, 2095662kB, raid superblock at 2095552kB
     disk 1: /dev/sdb1, 2095662kB, raid superblock at 2095552kB
     disk 2: /dev/sdc1, 2095662kB, raid superblock at 2095552kB
     disk 3: /dev/sdd1, 2095662kB, raid superblock at 2095552kB
     disk 4: /dev/sde1, 2095662kB, raid superblock at 2095552kB
     disk 5: /dev/sdf1, 2095662kB, raid superblock at 2095552kB
     disk 6: /dev/sdg1, 2095662kB, raid superblock at 2095552kB
     mkraid: aborted, see the syslog and /proc/mdstat for potential clues.

The syslog has nothing new, and the /proc/mdstat has:

     Personalities :
     read_ahead not set
     md0 : inactive
     md1 : inactive
     md2 : inactive
     md3 : inactive

Would anyone happen to have any ideas? What to check? How to
physically impale this heap of scrap?

Thanks for any input whatsoever in advance-

Lyndon-
To unsubscribe from this list: send the line "unsubscribe linux-alpha" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Next message: Kurt Garloff: "Re: [patch] Re: PYXIS bug detection"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Jan 07 2002 - 21:00:40 EST