From: Neil Cavan <nrcavan@engmail.uwaterloo.ca>
To: linux-raid@vger.kernel.org
Subject: RAID5 Recovery
Date: Sat, 21 Oct 2006 21:14:32 -0400 [thread overview]
Message-ID: <BAYC1-PASMTP06741EF4074D618C18E59FE8030@CEZ.ICE> (raw)
Message-ID: <1161479672.14505.10.camel@localhost> (raw)
Hi,
I had a run-in with the Ubuntu Server installer, and in trying to get
the new system to recognize the clean 5-disk raid5 array left behind by
the previous Ubuntu system, I think I inadvertently instructed it to
create a new raid array using those same partitions.
What I know for sure is that now, I get this:
user@host:~$ sudo mdadm --examine /dev/hda1
mdadm: No super block found on /dev/hda1 (Expected magic a92b4efc, got
00000000)
user@host:~$ sudo mdadm --examine /dev/hdc1
mdadm: No super block found on /dev/hdc1 (Expected magic a92b4efc, got
00000000)
user@host:~$ sudo mdadm --examine /dev/hde1
mdadm: No super block found on /dev/hde1 (Expected magic a92b4efc, got
00000000)
user@host:~$ sudo mdadm --examine /dev/hdg1
mdadm: No super block found on /dev/hdg1 (Expected magic a92b4efc, got
00000000)
user@host:~$ sudo mdadm --examine /dev/hdi1
mdadm: No super block found on /dev/hdi1 (Expected magic a92b4efc, got
00000000)
I didn't format the partitions or write any data to the disk, so I think
the array's data should be intact. Is there a way to recreate the
superblocks, or am I hosed?
Thanks,
Neil
next reply other threads:[~2006-10-22 1:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1161479672.14505.10.camel@localhost>
2006-10-22 1:14 ` Neil Cavan [this message]
2006-10-23 1:29 ` RAID5 Recovery Neil Brown
[not found] ` <1161571953.4871.8.camel@localhost>
2006-10-23 2:52 ` Neil Cavan
2006-10-23 4:01 ` Neil Brown
2007-11-14 1:05 Neil Cavan
2007-11-14 10:58 ` David Greaves
-- strict thread matches above, loose matches on Subject: below --
2013-06-05 12:02 RAID5 recovery Philipp Frauenfelder
2013-06-05 13:20 ` Drew
2013-06-05 13:29 ` John Robinson
2013-06-05 15:10 ` Drew
2013-06-05 20:12 ` Philipp Frauenfelder
2013-06-06 12:28 ` Sam Bingner
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=BAYC1-PASMTP06741EF4074D618C18E59FE8030@CEZ.ICE \
--to=nrcavan@engmail.uwaterloo.ca \
--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).