Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: "lrhorer@satx.rr.com" <lrhorer@satx.rr.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Help - Urgent!!!
Date: Fri, 13 Nov 2009 16:11:07 +1100	[thread overview]
Message-ID: <19196.60011.858158.550391@notabene.brown> (raw)
In-Reply-To: message from lrhorer@satx.rr.com on Thursday November 12

On Thursday November 12, lrhorer@satx.rr.com wrote:
> Damn!!!
> 
>         I was doing some testing at the behest of Doug, when I made a
> critical error which locked up the system and now the main array won't
> assemble, at all.  I issued the command
> 
> `mdadm -G /dev/md0 -b internal --bitmap-chunk=65535`
> 
>         And the system complained it was an invalid chunk-size, so I
> tried:
> 
> `mdadm -G /dev/md0 -b internal --bitmap-chunk=65536`
> 
>         This time there was no error, but the command line just hung
> solid.  I tired everything I could to recover, but the system just went
> downhill more and more.  Finally I tried a shutdown, but even that would
> not work.  I had to hit the big red switch, and now when I rebooted the
> system, mdadm will not assemble the array no matter what I try.  I tried
> 
> 
> `mdadm --assemble /dev/md0 -f`
> 
> `mdadm --assemble /dev/md0 -u xxxxxxxx:xxxxxxxxx:xxxxxx:xxxxxx`
> 
>         etc.  It just keeps saying, "No devices found for md0".  When I
> issue the --examine switch, the information all looks good for all the
> drives, just no RAID.  What do I do, now?


1/ show us what the result of --examine was.
2/ add -vvv to the --assemble and report the result of that.

NeilBrown

  reply	other threads:[~2009-11-13  5:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  4:53 Help - Urgent!!! lrhorer
2009-11-13  5:11 ` Neil Brown [this message]
2009-11-13  5:12   ` Neil Brown
2009-11-13  5:14     ` lrhorer
2009-11-13  6:08       ` Neil Brown
2009-11-13  6:22         ` lrhorer
2009-11-13  7:03           ` Neil Brown
2009-11-13 15:09             ` lrhorer
2009-11-14 21:45             ` Leslie Rhorer
2009-11-15  0:05               ` Majed B.
2009-11-15  1:05                 ` Leslie Rhorer
2009-11-13  9:06         ` Janek Kozicki
2009-11-13  9:44           ` Sujit K M
2009-11-13  5:16     ` lrhorer
     [not found] ` <200911130913.48292.lrhorer@satx.rr.com>
     [not found]   ` <19197.55846.756558.21650@notabene.brown>
2009-11-14  0:30     ` lrhorer
2009-11-14  0:34       ` Majed B.
  -- strict thread matches above, loose matches on Subject: below --
2009-11-13  4:34 Help - Urgent! Rhorer, Leslie

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=19196.60011.858158.550391@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=lrhorer@satx.rr.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox