From: Wols Lists <antlists@youngman.org.uk>
To: kyle <kyle.upton.is@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: HELP! RAID5 array disappeared after partitions deleted
Date: Thu, 19 Jan 2017 13:52:28 +0000 [thread overview]
Message-ID: <5880C49C.5090508@youngman.org.uk> (raw)
In-Reply-To: <e3f5d5ff-cea5-8cdc-c235-768e73293283@gmail.com>
On 19/01/17 08:57, kyle wrote:
> I have (had) a large RAID5 array (3x8TB) up and running on Ubuntu 16.04
> using the guide on the following page:
>
> https://www.digitalocean.com/community/tutorials/how-to-create-raid-arrays-with-mdadm-on-ubuntu-16-04
>
>
> The array seemed to be running well, and was automatically loaded on
> re-boot etc, all good!
>
> Today however, i was formatting some USB drives in gparted and it popped
> up some error about the partition table for the raid drives appearing
> corrupted, and using the backup. I didn't think much of this at the
> time, but it looks like that deleted the partition tables, and now i
> have no array.
>
I need to write this stuff up - I keep saying this ...
Search for the following thread(s) and read them:
Please help RAID1 complete fail no superblock 22/11/16
RAID10 with 2 drives auto-assembled as RAID1 05/11/16
Dates are DMY European format. You want to hexdump the likely disk
locations and try and find partition superblocks, raid superblocks, etc
etc. If you can find anything like that and post it to the list, then
the experts can chime in and help you get it back.
There's probably a few more threads like that, but those are the ones
I've just found.
Cheers,
Wol
next prev parent reply other threads:[~2017-01-19 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 8:57 HELP! RAID5 array disappeared after partitions deleted kyle
2017-01-19 13:52 ` Wols Lists [this message]
2017-01-19 23:12 ` kyle
2017-01-19 23:13 ` kyle
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=5880C49C.5090508@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=kyle.upton.is@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 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.