From: NeilBrown <neilb@suse.de>
To: Killian De Volder <killian.de.volder@megasoft.be>
Cc: linux-raid@vger.kernel.org
Subject: Re: Mdadm misuse or bug ? mdadm: Cannot find 8:18: No such file or directory
Date: Sat, 9 Aug 2014 10:49:15 +1000 [thread overview]
Message-ID: <20140809104915.05b8da17@notabene.brown> (raw)
In-Reply-To: <53E54AC5.4010904@megasoft.be>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
On Sat, 09 Aug 2014 00:10:13 +0200 Killian De Volder
<killian.de.volder@megasoft.be> wrote:
> I'm having some trouble with a disk of unknown cause.
> As a result the disk is now "failed"
>
> #dmesg
> [362288.463008] ata3: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
> ...
> [377997.666956] md: super_written gets error=-5, uptodate=0
> [377997.666960] md/raid1:md126: Disk failure on sdb3, disabling device
>
> I replugged the disk, and added it again to the raid (it is now called sdf instead of sdb):
>
> # cat /proc/mdstat:
> md126 : active raid1 sdf2[5] sdd2[0] sde2[3] sdc2[2] sdb2[4](F)
> 102272 blocks super 1.2 [4/4] [UUUU]
>
> So I wanted to remove the failed disk:
>
> # mdadm /dev/md126 -r failed
> mdadm: Cannot find 8:18: No such file or directory
Hmm.. that looks broken.
What version of mdadm is this?
Does
mdadm /dev/md126 -r detached
work?
How about
mdadm /dev/md127 -r sdb2
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-08-09 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 22:10 Mdadm misuse or bug ? mdadm: Cannot find 8:18: No such file or directory Killian De Volder
2014-08-09 0:49 ` NeilBrown [this message]
2014-08-09 7:52 ` Killian De Volder
2014-08-09 8:23 ` NeilBrown
2014-08-09 8:32 ` Killian De Volder
2014-08-11 0:40 ` NeilBrown
2014-08-11 7:05 ` Killian De Volder
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=20140809104915.05b8da17@notabene.brown \
--to=neilb@suse.de \
--cc=killian.de.volder@megasoft.be \
--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 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).