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 14:58:04 +0200 [thread overview]
Message-ID: <5443B55C.7000208@stenborg.me> (raw)
In-Reply-To: <alpine.DEB.2.02.1410191253010.30853@uplift.swm.pp.se>
Hi, thanks for your answer. (Tack!)
My debian mdadm is ver v3.1.4 - 31st August 2010
mdadm --assemble --force /dev/md0 /dev/sd[bcde]
outputs
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: /dev/sdb has no superblock - assembly aborted
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
devices are readable, I tried to read data with
dd if=/dev/sdb of=dump bs=1024 count=1024
and it works, so the device is accressible.
dmesg shows nothing
/proc/mdstat
Personalities :
md0 : inactive sdd[2](S) sdb[0](S) sde[4](S) sdc[1](S)
7814054240 blocks super 1.2
uname -a
Linux backuppc 2.6.32-5-686 #1 SMP Sat Jul 12 22:59:16 UTC 2014 i686
GNU/Linux
System is Debian squeeze-lts
Best regards
´
Per-Ola Stenborg
Mikael Abrahamsson skrev 2014-10-19 12:56:
> On Sun, 19 Oct 2014, Per-Ola Stenborg wrote:
>
>> *** PLEASE advice ***
>
> Please post dmesg output from when you do --assemble --force, and also
> please post your mdadm and kernel versions.
>
> As a first step, compile mdadm from source and use that version, it
> often helps as distributions don't generally ship with the latest mdadm.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-10-19 12:58 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 [this message]
[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
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=5443B55C.7000208@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.