From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: David Mitchell <mr.david.mitchell@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Superblock Missing
Date: Sat, 2 Sep 2017 03:43:33 +0200 [thread overview]
Message-ID: <20170902014333.GA26507@metamorpher.de> (raw)
In-Reply-To: <CAANkkp+3WwZvKu60LkU_0VpxZvZuNrrE=qDt=4DPc80AO+sgEg@mail.gmail.com>
On Fri, Sep 01, 2017 at 08:52:23PM -0400, David Mitchell wrote:
> # mdadm --examine /dev/md0
> mdadm: No md superblock detected on /dev/md0.
Everyone will assume user error at this point.
/dev/md0 is not supposed to have a mdadm superblock to examine.
It has a filesystem or LUKS or LVM header or whatever it is you do.
For --examine you have to provide one or more member devices.
You can do mdadm --detail /dev/md* or mdadm --examine /dev/sd*.
> Requested from "When Things Go Wrong"
>
> -------------------------------------
> # mdadm --examine /dev/sd[cde]1
> /dev/sdc1:
> Magic : a92b4efc
> Version : 1.2
Oh look. There it is. Your superblock...
Other than that I see no problems. Your Load Cycle Counts are high
and for WD there are tools to finetune that behaviour but it's
unclear whether that's actually a real problem.
> 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% 0 -
Consider running smart tests more regularly.
Regards
Andreas Klauer
next prev parent reply other threads:[~2017-09-02 1:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-02 0:52 Superblock Missing David Mitchell
2017-09-02 1:43 ` Andreas Klauer [this message]
2017-09-02 15:43 ` David Mitchell
2017-09-02 16:49 ` Andreas Klauer
2017-09-04 3:35 ` David Mitchell
2017-09-04 15:02 ` Wols Lists
2017-09-04 15:49 ` Andreas Klauer
2017-09-04 17:56 ` David Mitchell
2017-09-06 3:07 ` David Mitchell
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=20170902014333.GA26507@metamorpher.de \
--to=andreas.klauer@metamorpher.de \
--cc=linux-raid@vger.kernel.org \
--cc=mr.david.mitchell@gmail.com \
/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