From: Wols Lists <antlists@youngman.org.uk>
To: Xuesong LU <disluxs@nus.edu.sg>, linux-raid@vger.kernel.org
Subject: Re: Need Help for Raid Recovery
Date: Mon, 25 Sep 2017 18:57:39 +0100 [thread overview]
Message-ID: <59C94393.8010405@youngman.org.uk> (raw)
In-Reply-To: <ccba6492-26b7-c084-aa1e-6d69c7f48785@nus.edu.sg>
On 25/09/17 08:53, Xuesong LU wrote:
> mdadm --examine /dev/sd[g-p] prints raid partition information for
> sd[h,i,j,l,m,n]. No superblock detected on sd[g,k,o,p].
>
> mdadm --examine /dev/sd[g-p]1 prints raid partition information for
> sd[h,i,j,l,m,n]1. The event counts are the same. It also prints 'No
> superblock detected' for sdg1, and 'no such files' for sd[k,o,p]1.
> (Gone? Can still recover?)
>
> I have UUID for md0 in the mdadm.conf file.
>
> Is there still hope to recover my raid? Thank you!
Go to the raid wiki, and post the requested info to the list.
https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn
Make sure you're using the latest mdadm.
This looks a little familiar to me, but so long as nothing has written
to the disk, and/or the only thing that has been damaged is the
superblocks, this looks rather hopeful.
Bear in mind, though, if the superblocks ARE gone, then it's going to be
a hassle to get it back. A fair bit of trial and error is on the cards
(read up on overlays). But as long as nothing has actually stomped on
the data itself, you should be able to get it back.
Do an "fdisk -l" on k, o, p. I remember a problem a while back when
something stamped on the partition table ...
Cheers,
Wol
next prev parent reply other threads:[~2017-09-25 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 7:53 Need Help for Raid Recovery Xuesong LU
2017-09-25 17:57 ` Wols Lists [this message]
2017-09-28 5:31 ` Xuesong LU
2017-09-28 15:08 ` Wols Lists
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=59C94393.8010405@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=disluxs@nus.edu.sg \
--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