From: David Greaves <david@dgreaves.com>
To: Guy <bugzilla@watkins-home.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 - 2nd drive died whilst waiting for RMA
Date: Fri, 12 Nov 2004 18:13:31 +0000 [thread overview]
Message-ID: <4194FD4B.60306@dgreaves.com> (raw)
In-Reply-To: <200411121749.iACHnKN01022@www.watkins-home.com>
Thanks Guy :)
Nothing at all.
I haven't rebooted; I haven't attempted any dd's
The only think I've done is stop the monitor:
/etc/init.d/mdadm stop
and see what's up
cat /proc/mdstat
and run
mdadm --display /dev/md0
I'm preparing linux-2.6.9 (currently running 2.6.6).
I've ordered another 250Gb disk and a basic Sil-Img 2xSATA controller
that should be here in the morning so I'm not planning on doing anything
until then.
I've been reading up on dd_rescue and dd_rhelp too.
They're now installed and waiting.
David
Guy wrote:
>Let me know what you have done so far.
>
>Guy
>
>-----Original Message-----
>From: linux-raid-owner@vger.kernel.org
>[mailto:linux-raid-owner@vger.kernel.org] On Behalf Of David Greaves
>Sent: Friday, November 12, 2004 12:32 PM
>To: Dick Streefland
>Cc: linux-raid@vger.kernel.org
>Subject: Re: RAID5 - 2nd drive died whilst waiting for RMA
>
>Dick Streefland wrote:
>
>
>
>>David Greaves <david@dgreaves.com> wrote:
>>| so, the plan in order to try and extract data:
>>| * insert new drive as /dev/sdd1
>>| * dd if=/dev/sda1 of=/dev/sdd1
>>| * mdadm /dev/md0 --remove /dev/sda1
>>| * physically swap /dev/sda and /dev/sdd so /dev/sdd
>>| * mdadm /dev/md0 --add /dev/sda1
>>| * fsck filesystem and expect to lose files where there were bad blocks
>>| * wait for new drive (special delivery - tomorrow morning)
>>| * insert new drive as /dev/sdd
>>| * mdadm /dev/md0 --add /dev/sdd1
>>
>>You might want to check out "ddrescue", which is a version of "dd"
>>that is designed to read from a disk with bad sectors.
>>
>>
>>
>>
>That was it - thanks :)
>
>I was googling 'dd recover' and various 'badblocks' etc... not 'dd rescue'
>
>Also found dd_rhelp which looks sensible.
>
>fingers crossed that it works...
>
>David
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
next prev parent reply other threads:[~2004-11-12 18:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 10:07 RAID5 - 2nd drive died whilst waiting for RMA David Greaves
2004-11-12 12:17 ` David Greaves
2004-11-12 16:22 ` Dick Streefland
2004-11-12 17:31 ` David Greaves
2004-11-12 17:49 ` Guy
2004-11-12 18:13 ` David Greaves [this message]
2004-11-12 17:48 ` Guy
2004-11-12 18:09 ` Guy
2004-11-12 18:30 ` David Greaves
2004-11-12 18:47 ` Guy
2004-11-13 19:48 ` David Greaves
2004-11-13 20:01 ` Måns Rullgård
2004-11-13 20:28 ` David Greaves
2004-11-13 20:32 ` Måns Rullgård
2004-11-13 20:39 ` Guy
2004-11-13 21:54 ` David Greaves
2004-11-15 16:55 ` David Greaves
2004-11-16 6:13 ` Brad Campbell
2004-11-17 11:21 ` David Greaves
2004-11-17 11:24 ` Måns Rullgård
2004-11-17 11:44 ` Brad Campbell
2004-11-17 12:04 ` David Greaves
2004-11-15 20:56 ` Robin Bowes
2004-11-15 21:24 ` Guy
2004-11-15 21:30 ` Robin Bowes
2004-11-15 21:39 ` Gordon Henderson
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=4194FD4B.60306@dgreaves.com \
--to=david@dgreaves.com \
--cc=bugzilla@watkins-home.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 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.