From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: Joel Walberg <joel.walberg@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: debian9/raid1 assembly/unexpected failure opening device
Date: Thu, 31 Aug 2017 15:22:26 +0200 [thread overview]
Message-ID: <20170831132226.GA6058@metamorpher.de> (raw)
In-Reply-To: <CAGv-CE+UwWraQpVF8hG+OBxj1B7Gwbh7tUcMq7hKz0MQ0NWd-w@mail.gmail.com>
On Thu, Aug 31, 2017 at 06:06:42AM -0600, Joel Walberg wrote:
> ## root@jowahome:~# mdadm -A /dev/md2014 /dev/sdc1 /dev/sdb1
> ## mdadm: unexpected failure opening /dev/md2014
> ## root@jowahome:~# mdadm -A /dev/md/md2014 /dev/sdc1 /dev/sdb1
> ## mdadm: unexpected failure opening /dev/md2014
Could be related to the name. Try assembling it as /dev/md0.
If that works, change the name to something that isn't md<number>.
(--assemble --update=name --name=xyz I guess)
> ## SMART Extended Self-test Log Version: 1 (1 sectors)
> ## Num Test_Description Status Remaining
> LifeTime(hours) LBA_of_first_error
> ## # 1 Short offline Completed without error 00%
> 21086 -
This is a personal preference... but you should run self tests
more regularly (automated, smartd) to detect HDD errors in time.
> ## 5 Reallocated_Sector_Ct PO--CK 097 097 010 - 3344
That's quite a lot of reallocated sectors already.
This is the kind of drive that will make your rebuilds fail.
I would consider replacing such a drive / putting it to some use
where data loss is acceptable.
Regards
Andreas Klauer
next prev parent reply other threads:[~2017-08-31 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 12:06 debian9/raid1 assembly/unexpected failure opening device Joel Walberg
2017-08-31 13:02 ` Jack Wang
2017-08-31 13:12 ` Joel Walberg
2017-08-31 14:32 ` Wols Lists
2017-08-31 13:51 ` Joel Walberg
2017-08-31 17:12 ` Wols Lists
2017-09-12 22:37 ` Nix
2017-09-13 16:15 ` Wols Lists
2017-08-31 13:22 ` Andreas Klauer [this message]
2017-08-31 13:27 ` Joel Walberg
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=20170831132226.GA6058@metamorpher.de \
--to=andreas.klauer@metamorpher.de \
--cc=joel.walberg@gmail.com \
--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).