From: David Greaves <david@dgreaves.com>
To: Cry <cry_regarder@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Two Drive Failure on RAID-5
Date: Thu, 22 May 2008 09:38:40 +0100 [thread overview]
Message-ID: <48353110.8060602@dgreaves.com> (raw)
In-Reply-To: <loom.20080521T210407-628@post.gmane.org>
Cry wrote:
> Janos Haar <janos.haar <at> netcenter.hu> writes:
>>> No. /dev/sdg1 is a *partition* on your old drive.
>
> Nope. /dev/sda is my old drive. It has NO partitions because I was
> retarded 1 year ago:
>
> Folks, I made a mistake when I created my original raid array
> (there is a note about it in the archives of this group) that
> I built the array on the raw drives, not on partitions.
That is not a 'problem' although it is not regarded as best practice.
> /dev/sda IS the drive. There is no /dev/sda1. However, the
> replacement drive is a 750Gig (not 500 like the originals) so
> I built a partition on the drive of the correct size: /dev/sdg1.
And you didn't think to mention this?
Maybe you thought it would be in the support file I keep for you?
When people offer suggestions they (or at least I) will probably form a picture
of what's going on - if you are going to throw tweaks into the mix then they may
throw us off. Mention them.
You have failed to answer some potentially relevant questions and, before you
get this array rebuilt you wandered off (on the same thread) into discussions
about what disk drives you might like to buy, the best type of external
enclosure and various other oddments. This is not helpful.
>The correct information should already be in /dev/sdg1 since I copied the entire
>/dev/sda there (probably overwrote stuff in /dev/sdg2 since /dev/sda was 160K
>bigger than /dev/sdg1).
Err, no. Linux doesn't randomly overwrite other partitions...
You're on 0.9 superblocks which are located at the end of the disk.
I *think* your assemble problem is that /dev/sdg1 was an old component (slot 6);
it had a superblock near the end of the partition which you didn't zero. You
copied most of /dev/sda into it but you made /dev/sdg1 too small by a few k. The
copy finished before it copied the /dev/sda superblock (I don't know why it
didn't overwrite the old superblock??). Also, at some point, md will try and
seek past the end of /dev/sdg1 and will die.
You have now dug a maze of twisty passages...
I think at this point you should enlarge /dev/sdg1, recopy /dev/sda to /dev/sdg1
and try again. That will probably work.
David
next prev parent reply other threads:[~2008-05-22 8:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 22:49 Two Drive Failure on RAID-5 Cry
2008-05-20 7:37 ` David Greaves
2008-05-20 15:32 ` Cry
2008-05-20 17:18 ` David Lethe
2008-05-20 19:01 ` Cry
2008-05-20 20:09 ` David Lethe
2008-05-20 23:11 ` Keith Roberts
2008-05-20 19:40 ` Janos Haar
2008-05-20 17:27 ` David Lethe
2008-05-20 19:28 ` Brad Campbell
2008-05-20 9:14 ` David Greaves
2008-05-20 12:17 ` Janos Haar
2008-05-21 14:14 ` Cry
2008-05-21 20:15 ` David Greaves
2008-05-21 20:47 ` Janos Haar
2008-05-21 21:21 ` Cry
2008-05-22 8:38 ` David Greaves [this message]
2008-05-31 9:27 ` Cry
2008-05-22 0:05 ` Cry
-- strict thread matches above, loose matches on Subject: below --
2008-05-21 0:24 Re: " David Lethe
2008-05-22 14:42 ` Ric Wheeler
2008-05-22 16:16 ` David Lethe
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=48353110.8060602@dgreaves.com \
--to=david@dgreaves.com \
--cc=cry_regarder@yahoo.com \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).