From: Phil Turmel <philip@turmel.org>
To: Ken <ravenpi@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Dead three-disk RAID-5. Help?
Date: Fri, 19 Oct 2012 23:59:56 -0400 [thread overview]
Message-ID: <508221BC.6080007@turmel.org> (raw)
In-Reply-To: <CAHw0J8hx+_siPsd7ZQN=WKy2yTpiSzyKk1ULUKa+HBbEwsy8pQ@mail.gmail.com>
Hi Ken,
On 10/19/2012 11:19 PM, Ken wrote:
> I'm currently highly suspicious that I executed the wrong command in
> the wrong window -- which would mean that I blew away the partition
> table, and fsck'd the new partitions, on /dev/sda. Which
> theoretically leaves me with /dev/sdb and /dev/sdc, no? Except that
> when I try to access them, it won't allow me to create the array. If
> I try the whole thing, it either tells me there's no partition table
> on /dev/md0, or that it can't find the superblock on /dev/md0.
Pretty thin on information to help us help you.
Please go through your shell command history to show us some of the
things you tried. Also, what distribution & version?
Some commands to run to give us information to start with (attach the
long ones to your e-mail as plain text):
uname -a
mdadm --version
dmesg
cat /proc/partitions
cat /proc/mdstat
mdadm -D /dev/md0
mdadm -E /dev/sd[abc]
{repeat the last two for any other arrays or member devices involved.
Partitions, perhaps?}
> Any pointers on where to go from here would be very much appreciated
> -- as (of course) the irony is that the system I *meant* to be
> fsck'ing was intended to back up the original system.
There are so many possible ways to set things up that we really need
more information.
> Thank you kindly,
You're welcome.
Phil
prev parent reply other threads:[~2012-10-20 3:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 3:19 Dead three-disk RAID-5. Help? Ken
2012-10-20 3:59 ` Phil Turmel [this message]
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=508221BC.6080007@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=ravenpi@gmail.com \
/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.