All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas J. Baker" <tjb@unh.edu>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Any hope for a 27 disk RAID6+1HS array with four disks   reporting "No md superblock detected"?
Date: Mon, 09 Feb 2009 09:48:18 -0500	[thread overview]
Message-ID: <1234190898.10428.7.camel@localhost.localdomain> (raw)
In-Reply-To: <a12770d97b01cc418aaff84bdd9e9349.squirrel@neil.brown.name>

On Sat, 2009-02-07 at 13:09 +1100, NeilBrown wrote:
> On Sat, February 7, 2009 8:47 am, Thomas J. Baker wrote:
> > On Sat, 2009-02-07 at 08:01 +1100, NeilBrown wrote:
> >> On Sat, February 7, 2009 7:32 am, Thomas J. Baker wrote:
> >>
> >> > Thanks for the info. I think I follow everything. One last question
> >> > before really trying it - is this what is expected when I actually run
> >> > the command - the warnings about previous array, etc?
> >>
> >> Yes, you would expect exactly those messages.
> >>
> >> NeilBrown
> >>
> >
> > OK, first I put the drives back to their original configuration (I had
> > swapped two banks to make them appear physically as the kernel sees them
> > logically to make it easier to track down the possibly faulty disks.)
> > For clarity, I put them back to the original configuration before trying
> > anything.
> >
> > Next I ran
> >
> > mdadm --create /dev/md0 --verbose --level=6 --raid-devices=26  \
> > /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1 missing \
> > /dev/sdi1 missing /dev/sdk1 /dev/sdl1 /dev/sdm1 /dev/sdn1 /dev/sdo1 \
> > /dev/sdp1 /dev/sdq1 /dev/sdr1 /dev/sdt1 /dev/sdu1 /dev/sdv1 \
> > /dev/sdw1 /dev/sdx1 /dev/sdy1 /dev/sdz1 /dev/sdaa1 /dev/sdab1
> 
> 
> You said  "--raid-devices=26".  Why did you do that?
> It should be '27'.
> You need to have 25 real devices and 2 'missing' devices.
> 24 of those real devices you can identify the correct position for
> by looking at the --examine information from before you tried to
> recreate the array.
> The 25th real device you have to guess which is likely to be
> the right one.
> 
> 
> >
> > which completed but when I fsck'd the disk, it wasn't happy, complaining
> > about a missing superblock on /dev/md0. I then stopped the array. I'm
> > not sure what to do next. It seems like the examine information of all
> > the disks has been updated by the last create. I guess I should only go
> > by the previous examine? As for the missing statement, should that only
> > relate to drives with no md superblock?
> 
> Yes, go by the previous examine information.
> 
> The 'missing' can be any two devices.  The important thing is the devices
> that aren't 'missing'.  They need to be devices that you have reason to
> believe belong to that slot in the array.
> 
> NeilBrown
> 

OK, specifying 27 devices worked and I successfully mounted the RAID and
looked around. Thanks again for the guidance! I guess things look OK
(there are directories and files!) 

I was wondering if I should fsck it before adding the other two disks
back in or after? Any other words of experience?

Thanks again,

tjb
-- 
=======================================================================
| Thomas Baker                                  email: tjb@unh.edu    |
| Systems Programmer                                                  |
| Research Computing Center                     voice: (603) 862-4490 |
| University of New Hampshire                     fax: (603) 862-1761 |
| 332 Morse Hall                                                      |
| Durham, NH 03824 USA              http://wintermute.sr.unh.edu/~tjb |
=======================================================================


  reply	other threads:[~2009-02-09 14:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04 19:27 Any hope for a 27 disk RAID6+1HS array with four disks reporting "No md superblock detected"? Thomas J. Baker
2009-02-04 20:50 ` Joe Landman
2009-02-04 21:03   ` Thomas J. Baker
2009-02-04 21:17     ` Thomas J. Baker
2009-02-05 18:49     ` Bill Davidsen
2009-02-05 18:59       ` Thomas J. Baker
2009-02-05 23:57         ` Bill Davidsen
2009-02-06  0:08           ` Thomas Baker
2009-02-06  5:14 ` Neil Brown
2009-02-06 20:32   ` Thomas J. Baker
2009-02-06 21:01     ` NeilBrown
2009-02-06 21:47       ` Thomas J. Baker
2009-02-07  2:09         ` NeilBrown
2009-02-09 14:48           ` Thomas J. Baker [this message]
2009-02-10 16:58             ` Nagilum
2009-02-07  4:05   ` Mr. James W. Laferriere
2009-02-08 22:02     ` Thomas Baker
2009-02-09 11:47       ` Max Waterman
2009-02-10  8:55         ` Luca Berra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1234190898.10428.7.camel@localhost.localdomain \
    --to=tjb@unh.edu \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.