All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Christian Deufel <christian.deufel@inview.de>,
	linux-raid <linux-raid@vger.kernel.org>,
	Wols Lists <antlists@youngman.org.uk>
Subject: Re: Reassembling Raid5 in degraded state
Date: Tue, 14 Jan 2020 11:40:20 -0500	[thread overview]
Message-ID: <a34d1a67-1d10-60fe-5922-42d27ce8dc6c@turmel.org> (raw)
In-Reply-To: <13b11d17-a23a-3063-70cb-de63d9fa7d09@inview.de>

On 1/14/20 6:28 AM, Christian Deufel wrote:
> Hey Wol
> 
>  > My plan now would be to run mdadm --assemble --force /dev/md3 with 3
>  > disk, to get the Raid going in a degraded state.
> 
>  >Yup, this would almost certainly work. I would recommend overlays and
>  >running a fsck just to check it's all okay before actually doing it on
>  >the actual disks. The event counts say to me that you'll probably lose
>  >little to nothing.
> 
> So as I was trying to reassemble my Raid it crashed again. But this time 
> sdc vanished.

I've experienced the problem of various disks disappearing when you 
attempt to use them.  It has always been some kind of power supply 
problem in my cases.

Consider relocating these drives to another box to continue your 
recovery efforts.

Phil

  reply	other threads:[~2020-01-14 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 11:28 Reassembling Raid5 in degraded state Christian Deufel
2020-01-14 16:40 ` Phil Turmel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-01-13  9:41 Christian Deufel
2020-01-13 15:04 ` Wols Lists
2020-01-13 17:31   ` Song Liu
2020-01-13 18:46     ` Wol

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=a34d1a67-1d10-60fe-5922-42d27ce8dc6c@turmel.org \
    --to=philip@turmel.org \
    --cc=antlists@youngman.org.uk \
    --cc=christian.deufel@inview.de \
    --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.