From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to get raid
Date: Tue, 10 Jan 2012 13:14:26 +0700 [thread overview]
Message-ID: <CAA2qdGUe5ZO9i7gwTkXXY12YWg+SZsoBcPS6_9NC1aGAFrainw@mail.gmail.com> (raw)
In-Reply-To: <1326141951.20929.8.camel@office-desktop.gateway.2wire.net>
[-- Attachment #1: Type: text/plain, Size: 1725 bytes --]
On Jan 10, 2012 8:48 AM, "Jeff Cranmer" <jeff@lotussevencars.com> wrote:
>
>
> > >
> > > Me too.
> > >
> > > mdadm --detail /dev/md0 thinks that /dev/sdc1 is faulty.
> > > I'm not sure whether it's really faulty, or just that my setup for
RAID
> > > is screwed up.
> > >
> > > How do I get rid of an existing /dev/md0?
> >
> > you stop it. Override the superblock with dd.. and lose all data on the
disks.
> >
> >
> > >
> > > I'm thinking that I can try creating a RAID1 array using the two
> > > allegedly good disks and see if I can make that work.
> >
> > yeah
> >
> > >
> > > If that works, I'll get rid of it and try recreating the RAID1 with
one
> > > good disk and the one that mdadm thinks is faulty.
> > >
> >
> > you don't have to. You can migrate a 2 disk raid1 to a 3 disk raid5.
Howtos
> > are availble via google.
> >
> >
> > just saying - box in suspend to ram. I change the cable (and connector
on
> > mobo) on a disk with two raid 1 partitions on it.
> >
> > One came back after starting the box.
> >
> > The other? Nothing I tried worked. At the end I dd'ed the partition..
and did
> > a complete 'faulty disk/replacement' resync....
> >
> > argl.
> >
> >
> OK, so lesson learned. Just because it builds correctly in a RAID1
> array, that doesn't mean that the drive isn't toast.
>
> I ran badblocks on the three drive components and, surprise,
> surprise, /dev/sdc came up faulty. I think I'll just build the two
> non-faulty drives as a RAID0 array until the hard drive prices come back
> down to pre-Thailand flood prices and backup regularly.
>
> Thanks for all the help.
>
> Jeff
>
>
>
RAID 0?!?!
Please reconsider.
With RAID 0, *any* single drive failure will result in *total* data loss.
Rgds,
[-- Attachment #2: Type: text/html, Size: 2474 bytes --]
next prev parent reply other threads:[~2012-01-10 6:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 2:57 [gentoo-user] How to get raid Jeff Cranmer
2012-01-04 4:21 ` Paul Hartman
2012-01-05 0:37 ` Jeff Cranmer
2012-01-04 13:35 ` Alexander Puchmayr
2012-01-05 1:14 ` Jeff Cranmer
2012-01-04 13:39 ` Volker Armin Hemmann
2012-01-05 2:28 ` Jeff Cranmer
2012-01-05 3:01 ` Volker Armin Hemmann
2012-01-05 3:45 ` Jeff Cranmer
2012-01-05 8:22 ` Hinnerk van Bruinehsen
2012-01-05 10:22 ` Volker Armin Hemmann
2012-01-06 1:13 ` Jeff Cranmer
2012-01-06 1:41 ` Volker Armin Hemmann
2012-01-06 1:42 ` Volker Armin Hemmann
2012-01-06 4:44 ` Jeff Cranmer
2012-01-06 12:36 ` Volker Armin Hemmann
2012-01-06 23:04 ` Jeff Cranmer
2012-01-07 15:11 ` Jeff Cranmer
2012-01-07 17:20 ` Jeff Cranmer
2012-01-07 17:46 ` Volker Armin Hemmann
2012-01-07 18:27 ` Jeff Cranmer
2012-01-07 18:50 ` Volker Armin Hemmann
2012-01-07 22:43 ` Jeff Cranmer
2012-01-09 20:45 ` Jeff Cranmer
2012-01-10 6:14 ` Pandu Poluan [this message]
2012-01-10 11:56 ` Jeff Cranmer
2012-01-08 18:31 ` Paul Hartman
2012-01-08 20:03 ` Jeff Cranmer
2012-01-08 21:02 ` Jeff Cranmer
2012-01-09 18:58 ` Jeff Cranmer
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=CAA2qdGUe5ZO9i7gwTkXXY12YWg+SZsoBcPS6_9NC1aGAFrainw@mail.gmail.com \
--to=pandu@poluan.info \
--cc=gentoo-user@lists.gentoo.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