From: Wols Lists <antlists@youngman.org.uk>
To: George Rapp <george.rapp@gmail.com>,
"theelectricengineer@gmail.com" <theelectricengineer@gmail.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Please help RAID1 complete fail no superblock
Date: Tue, 22 Nov 2016 15:05:02 +0000 [thread overview]
Message-ID: <58345E9E.1080102@youngman.org.uk> (raw)
In-Reply-To: <CAF-KpgbDRbUZeKd+fL8qSGXa-2=QEZqVeAQsQk5U7YqJrcyL3A@mail.gmail.com>
On 22/11/16 14:49, George Rapp wrote:
> On Tue, Nov 22, 2016 at 9:31 AM, theelectricengineer@gmail.com
> <theelectricengineer@gmail.com> wrote:
>> Hello good people of the linux-raid group,
>>
>> I really need your help with my RAID1 that has completely failed, on which I have photos of my beloved deceased grandparents.
>>
>> I had the RAID1 array for about 3 years, and I had replaced one of the drives when it failed about one year ago. All worked fine.
>>
>> A few weeks ago, I bought a new computer and wanted to move the array to the new computer.
>> I read several guides, and thought that all I had to do was turn both computers off, move the drives, and in the new computer execute: mdadm --assemble --scan
>> which I did.
>>
>> The output was: mdadm: /dev/sdb has no superblock - assembly aborted
>>
>> I panicked, moved the drives back, but the old RAID wouldn't start!
>> The old computer too says that one of the drives has no superblock
>> and, even worse, that the other is UNALLOCATED SPACE!!!
>>
>> I don't understand why the partition on the second drive disappeared, and I'm so worried.
>>
>> PLEASE, PLEASE help me...
>>
>> I read the wiki pages (raid wiki kernel), but I'm afraid to run any commands that might make things worse.
>>
>> I would be very happy if I could restore the data from either one of the drives,
>> and copy it to the new drives in my new computer (as I should have done before moving the drives).
>>
>
> Yadiv -
>
> One more piece of information that would be helpful is the partition
> tables for each drive:
>
> # fdisk -l /dev/sdb /dev/sdc
>
And search the archive for the following thread - "RAID10 with 2 drives
auto-assembled as RAID1". It's pretty recent.
You've got a mirror, which means both of your drives should have a valid
filesystem on them, so things look optimistic. It's just a case of
finding it - that thread should help you look. The experts will chime
in, but if you can find the string sequences they're looking for, it'll
help you recover the partition(s). What filesystem were you using?
Cheers,
Wol
next prev parent reply other threads:[~2016-11-22 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 14:31 Please help RAID1 complete fail no superblock theelectricengineer
2016-11-22 14:49 ` George Rapp
2016-11-22 15:05 ` Wols Lists [this message]
[not found] ` <CAOLyU3WMJc+En=DbOW-n2uAXe7b1Gvo6jGCr0zLv5LumrxKJNQ@mail.gmail.com>
2016-11-23 20:25 ` Wols Lists
2016-11-23 21:47 ` YK
-- strict thread matches above, loose matches on Subject: below --
2016-11-22 16:24 theelectricengineer
2016-11-22 18:05 ` Please " Phil Turmel
2016-11-22 20:38 theelectricengineer
2016-11-22 22:01 ` Please " Phil Turmel
2016-11-22 23:04 ` YK
2016-11-22 23:08 ` YK
2016-11-26 17:45 ` YK
2016-11-26 19:58 ` Phil Turmel
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=58345E9E.1080102@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=george.rapp@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=theelectricengineer@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.