From: Per-Ola Stenborg <per-ola@stenborg.me>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-raid@vger.kernel.org
Subject: Re: Multiple drive failure after stupid mistake. Help needed
Date: Sun, 19 Oct 2014 21:00:52 +0200 [thread overview]
Message-ID: <54440A64.9060909@stenborg.me> (raw)
In-Reply-To: <alpine.DEB.2.02.1410191905190.30853@uplift.swm.pp.se>
Yes! It works! Thanks so much. Lets hope the sdc drive survives the
rebuild this time.
At least I got the opportunity to backup the 24GB important (not backed
up data).
The Linux raid usually works so well that you never have to worry. And
when things go wrong
you therefor never have the experience to help fix the problem.
Thanks again!
Best regards
Per-Ola Stenborg
Mikael Abrahamsson skrev 2014-10-19 19:06:
> On Sun, 19 Oct 2014, Per-Ola Stenborg wrote:
>
>> I compiled the latest mdadm v3.3.2 - 21st August 2014
>> running
>> mdadm --assemble --force /dev/md0 /dev/sd[bcde]
>> outputs
>> mdadm: /dev/sdb is busy - skipping
>> mdadm: /dev/sdc is busy - skipping
>> mdadm: /dev/sdd is busy - skipping
>> mdadm: /dev/sde is busy - skipping
>>
>> Strange. What does this mean? Is it flaged as in use in the kernel? The
>
> Stop the array before you try to start it again.
>
> Also consider upgrading to a newer kernel if there is a backports one
> (there should be for debian squeeze), a lot of things have happened
> since 2.6.32.
>
prev parent reply other threads:[~2014-10-19 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 9:45 Multiple drive failure after stupid mistake. Help needed Per-Ola Stenborg
2014-10-19 10:56 ` Mikael Abrahamsson
2014-10-19 12:58 ` Per-Ola Stenborg
[not found] ` <CAFE24U0GKPhkYe1faCBWohimJYL4O_PBYOJ+aLa_mSMKQCGGhw@mail.gmail.com>
2014-10-19 15:56 ` Per-Ola Stenborg
2014-10-19 17:06 ` Mikael Abrahamsson
2014-10-19 19:00 ` Per-Ola Stenborg [this message]
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=54440A64.9060909@stenborg.me \
--to=per-ola@stenborg.me \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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.