linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Wesley W. Terpstra" <wesley@terpstra.ca>
To: Phil Turmel <philip@turmel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: kernel refuses devices mdadm -E accepts
Date: Tue, 20 Jan 2015 19:43:40 +0100	[thread overview]
Message-ID: <CAA-O0XjtzHkm28rmRtH4sFhqD7nKHd6LSFi4+PBquXPTAO8-CQ@mail.gmail.com> (raw)
In-Reply-To: <54BE9F2A.9090102@turmel.org>

An email race condition. ;-)

On Tue, Jan 20, 2015 at 7:32 PM, Phil Turmel <philip@turmel.org> wrote:
> Woops!
> I'd still try a liveCD with 3.18.x or 3.19.

Right. I am considering ordering one of these new 8TB hard disks so I
can raw copy the raid partitions before I try anything drastic.
Unfortunately even 8TB won't fit 4x3TB of data. :-/ I am fairly
certain my data is still good since all disks have a clean bill of
health and other partitions on them worked with bonnie. So, I figure
my biggest risk right now, is doing something else stupid.

The system remains bootable as the uefi+boot+root filesystems were on
RAID1 x4 arrays and not the data RAID5 array. I'm hesitant to take
action until I find away to store the raw partitions, but installing
3.19 and booting that from my existing root partition sounds harmless
enough.

The system does not have a CD-ROM and has insufficient SATA connectors
to attach one. I could try booting via a USB drive, though.

  reply	other threads:[~2015-01-20 18:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 23:01 kernel refuses devices mdadm -E accepts Wesley W. Terpstra
2015-01-19 23:52 ` Roger Heflin
2015-01-20 18:28 ` Phil Turmel
2015-01-20 18:32   ` Phil Turmel
2015-01-20 18:43     ` Wesley W. Terpstra [this message]
     [not found]       ` <FCB084A5-816F-4954-971E-1C69C707F213@blub.net>
2015-01-21 12:37         ` Wesley W. Terpstra
2015-01-20 18:32   ` Wesley W. Terpstra

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=CAA-O0XjtzHkm28rmRtH4sFhqD7nKHd6LSFi4+PBquXPTAO8-CQ@mail.gmail.com \
    --to=wesley@terpstra.ca \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.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;
as well as URLs for NNTP newsgroup(s).