All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Waldo <pwaldo@waldoware.com>
To: Dan Williams <dan.j.williams@gmail.com>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: In Trouble--Please Help! (was Re: Can't add disk to failed raid array)
Date: Tue, 25 Jul 2006 10:27:05 -0400	[thread overview]
Message-ID: <44C62A39.2040906@waldoware.com> (raw)
In-Reply-To: <e9c3a7c20607241126n614b7941i4319a7889ac12c5e@mail.gmail.com>

Dan Williams wrote:
> On 7/23/06, Paul Waldo <pwaldo@waldoware.com> wrote:
>> Here is the dmesg output.  No log files are created with the FC5 
>> rescue disk.
>> Thanks!
> I ran into this as well, I believe at this point you want to set:
> 
> md-mod.start_dirty_degraded=1
> 
> as part of your boot options.  Understand you may see some filesystem
> corruption as noted in the documentation.
> 
> See:
> http://www.linux-m32r.org/lxr/http/source/Documentation/md.txt?v=2.6.17#L54
> 
> Regards,
> 
> Dan

Woo Hoo!  I am back in the running!
The md-mod.start_dirty_degraded enabled me to get the array running and 
I can now boot the machine.

Per Neil's comments, I adjusted the partitioning on the new drive 
(/dev/hdd2) to exactly match that of the other partitions in the array. 
  Success!  The array is now rebuilding with the new disk!!

Thanks for everyone's help on this--I'd be dead without it.  In return, 
maybe I can impart a lesson learned.  My big problem was that the new 
replacement disk, even though the same model as the original it was 
replacing, did not have the same geometry as the original.  It was short 
by 2 cylinders, which prevented it from being added to the array.  Next 
time I create an array of "identical" disks, I am going to keep a few 
cylinders on each one unused for just this type of problem.

Again, thanks for all the help!

Paul

  parent reply	other threads:[~2006-07-25 14:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-16  0:56 Can't add disk to failed raid array Paul Waldo
2006-07-16 10:19 ` Neil Brown
2006-07-16 12:24   ` Paul Waldo
2006-07-18  5:36     ` Neil Brown
2006-07-23 11:04       ` In Trouble--Please Help! (was Re: Can't add disk to failed raid array) Paul Waldo
2006-07-23 11:25         ` Neil Brown
2006-07-23 11:50           ` Paul Waldo
2006-07-23 11:53           ` Paul Waldo
2006-07-23 11:59             ` Neil Brown
2006-07-23 12:32               ` Paul Waldo
2006-07-24 18:26                 ` Dan Williams
2006-07-24 18:35                   ` Paul Waldo
2006-07-24 19:06                     ` Dan Williams
2006-07-25 14:27                   ` Paul Waldo [this message]
2006-07-24 23:24                 ` Neil Brown
2006-08-02 19:15                   ` Converting Ext3 to Ext3 under RAID 1 Dan Graham
2006-08-02 19:28                     ` dean gaudet
2006-08-02 19:31                     ` Paul Clements
2006-08-03  7:50                       ` Michael Tokarev
2006-08-02 22:38                     ` Robert Heinzmann
     [not found] ` <200607160913.32005.pwaldo@waldoware.com>
     [not found]   ` <Pine.LNX.4.62.0607161524170.7520@uplift.swm.pp.se>
2006-07-16 14:39     ` Can't add disk to failed raid array Paul Waldo
2006-07-17 18:36 ` Paul Waldo

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=44C62A39.2040906@waldoware.com \
    --to=pwaldo@waldoware.com \
    --cc=dan.j.williams@gmail.com \
    --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.