From: David Greaves <david@dgreaves.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 - 2nd drive died whilst waiting for RMA
Date: Fri, 12 Nov 2004 12:17:45 +0000 [thread overview]
Message-ID: <4194A9E9.70003@dgreaves.com> (raw)
In-Reply-To: <41948B65.3090504@dgreaves.com>
David Greaves wrote:
> So my RAID5 has 2 dead drives and is toasted :(
> I had a few smaller disks on another machine which I lvm'ed together
> to do a backup - but I could only fit about a quarter of my data
> there. I'd *really* like not to have lost all this stuff.
>
> However I do now have a 'good' drive.
> Can I dd the newly dead drive (bear in mind it probably only has a bad
> block or two) onto the new drive and come back up in degraded mode?
>
I've had a think and this is my plan.... comments appreciated.
Currently:
/dev/md0:
Version : 00.90.01
Creation Time : Sat Jun 5 18:13:04 2004
Raid Level : raid5
Array Size : 980446208 (935.03 GiB 1003.98 GB)
Device Size : 245111552 (233.76 GiB 250.99 GB)
Raid Devices : 5
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Fri Nov 12 09:46:53 2004
State : clean, degraded
Active Devices : 3
Working Devices : 3
Failed Devices : 1
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 128K
Number Major Minor RaidDevice State
0 0 0 -1 removed
1 8 33 1 active sync /dev/sdc1
2 8 17 2 active sync /dev/sdb1
3 0 0 -1 removed
4 3 65 4 active sync /dev/hdb1
5 8 1 -1 faulty /dev/sda1
UUID : 19779db7:1b41c34b:f70aa853:062c9fe5
Events : 0.4443578
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
or am I wasting my time?
David
next prev parent reply other threads:[~2004-11-12 12:17 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 [this message]
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
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=4194A9E9.70003@dgreaves.com \
--to=david@dgreaves.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).