mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Stephen Mueller <stephen@mueller.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RAID array is gone, please help
Date: Thu, 23 Mar 2017 17:09:08 -0400	[thread overview]
Message-ID: <20170323210908.GQ14186@csclub.uwaterloo.ca> (raw)
In-Reply-To: <28c5f9ba-c312-0439-9d8a-78e06c3f00f0@mueller.org>

On Thu, Mar 23, 2017 at 10:02:23PM +0100, Stephen Mueller wrote:
> Looks like it worked! Thanks!

Well at least you could backup the data, just in case.

> I used:
> 
> sudo mdadm --create /dev/md0 --assume-clean --verbose --level-10
> --raid-devices=4 /dev/sdc /dev/sdd /dev/sde /dev/sdf

I wonder about the assume-clean, but I would think any data you wrote
will have been duplicated at the time you wrote it, and only unused
space might not have been synced yet.

Maybe running a forced resync would be worthwhile.

> And I got my instructions for creating the array here, and they
> also don't use partitions...
> 
> https://www.digitalocean.com/community/tutorials/how-to-create-raid-arrays-with-mdadm-on-ubuntu-16-04

Well it works, as long as you don't leave anything around to confuse it,
in this case a GPT partition table that somehow came back to bite you.

I wonder if mdadm could perhaps warn about the existing partition table
when being asked to create a new device.

Does it survive reboots now?

-- 
Len Sorensen

  reply	other threads:[~2017-03-23 21:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 16:49 raid
2017-03-23 17:37 ` Lennart Sorensen
2017-03-23 18:09   ` raid
2017-03-23 19:27     ` Lennart Sorensen
2017-03-23 19:38       ` Stephen Mueller
2017-03-23 19:59         ` Lennart Sorensen
2017-03-23 20:09           ` Stephen Mueller
2017-03-23 21:01             ` Lennart Sorensen
2017-03-23 21:02             ` Stephen Mueller
2017-03-23 21:09               ` Lennart Sorensen [this message]
2017-03-23 21:11                 ` Stephen Mueller

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=20170323210908.GQ14186@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stephen@mueller.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

all inboxes | Powered by JetHome®