From: Bogo Mipps <bogo.mipps@gmail.com>
To: Joe Landman <joe.landman@gmail.com>,
Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: Have I any chance of restoring my Raid6 data?
Date: Wed, 19 Jul 2017 14:01:49 +1200 [thread overview]
Message-ID: <0b776537-739d-eaec-fd22-0b53c0c32159@gmail.com> (raw)
In-Reply-To: <56444baf-d0a9-13ab-6397-b5da7b9ed28a@gmail.com>
On 07/17/2017 10:28 AM, Joe Landman wrote:
> Why did you recreate the RAID (though you used --assume-clean) ? Did you
> try mounting it before that?
Yes, and data appeared to be missing
>> Is there a chance of restoring my data?
>
> Depends ... if you 'fsck -n /dev/md0' does it say there are errors?
Yes. Unsuccessful. Could find no superblocks, hence no ability to check.
>>
>> P.S. This line looks ominous? <md0: detected capacity change from
>> 4000528203776 to 0> !!!
>
> That is because md0 was stopped.
Ah - thanks. Your input appreciated. Not looking good, having now
followed Peter's post.
prev parent reply other threads:[~2017-07-19 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 22:14 Have I any chance of restoring my Raid6 data? Bogo Mipps
2017-07-16 22:28 ` Joe Landman
2017-07-19 2:01 ` Bogo Mipps [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=0b776537-739d-eaec-fd22-0b53c0c32159@gmail.com \
--to=bogo.mipps@gmail.com \
--cc=joe.landman@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox