From: David Wuertele <dave-gnus@bfnet.com>
To: linux-raid@vger.kernel.org
Subject: OOPS! Did I screw myself with mdadm --create?
Date: 25 Jun 2005 16:45:03 -0700 [thread overview]
Message-ID: <m364w22e80.fsf@bfnet.com> (raw)
I recently had a raid server hang, and after a reset the 1.5TB raid 5
array no longer mounted. Being hasty, I messed around with mdadm
commands trying to find out what was going wrong, and in the process I
ran "mdadm -C" thinking that it was one of the steps for mounting an
existing array. I suspect that this was a fatal error, because now
fsck.reiserfs can't find the superblock on the array!
I had an /etc/mdadm.conf file lying around, and I happened to compare
the uuid in the /etc/mdadm.conf file and on one of the partitions.
They did not match!!!
Did I forever ruin my raid array? Is there a way to recover my
reiserfs superblock and the original array data?
Thanks,
Dave
next reply other threads:[~2005-06-25 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-25 23:45 David Wuertele [this message]
2005-06-27 18:13 ` Repost --- please help, did "mdadm --create" make my data unrecoverable? David Wuertele
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=m364w22e80.fsf@bfnet.com \
--to=dave-gnus@bfnet.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.