From: Robin Hill <robin@robinhill.me.uk>
To: Matthew Tice <mjtice@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Problems with raid after reboot.
Date: Mon, 25 Jul 2011 22:21:07 +0100 [thread overview]
Message-ID: <20110725212107.GA6422@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <CA+taBv_yfW_njVX4r7fpAT105fvBeVMBLbU4M+6tTDY7R1yndA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
On Mon Jul 25, 2011 at 03:04:34PM -0600, Matthew Tice wrote:
> Well things are a lot different now - I'm unable to start the array
> successfully. I removed an older non-relevant drive that was giving
> me smart errors - when I rebooted the drive assignments shifted (not
> sure this really matters, though).
>
> Now when I try to start the array I get:
>
> # mdadm -A -f /dev/md0
> mdadm: no devices found for /dev/md0
>
> I can nudge it slightly with auto-detect:
>
> # mdadm --auto-detect
>
> Then I try to assemble the array with:
>
> # mdadm -A -f /dev/md0 /dev/sd[bcde]
> mdadm: cannot open device /dev/sde: Device or resource busy
> mdadm: /dev/sde has no superblock - assembly aborted
>
<- SNIP ->
> │ └─sde: [8:64] MD raid5 (none/4) 931.51g md_d0 inactive spare
<- SNIP ->
>
> I've looked but I'm unable to find where the drive is in use.
lsdrv shows that it's in use in array md_d0 - presumably this is a
part-assembled array (possibly auto-assembled by the kernel). Try
stopping that first, then doing the "mdadm -A -f /dev/md0 /dev/sd[bcde]"
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-07-25 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 21:24 Problems with raid after reboot Matthew Tice
2011-07-23 3:12 ` Matthew Tice
2011-07-25 21:04 ` Matthew Tice
2011-07-25 21:21 ` Robin Hill [this message]
2011-07-25 21:30 ` Matthew Tice
2011-07-25 21:33 ` Matthew Tice
2011-07-25 21:42 ` Matthew Tice
2011-07-25 21:55 ` Matthew Tice
2011-07-26 8:37 ` Robin Hill
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=20110725212107.GA6422@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mjtice@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;
as well as URLs for NNTP newsgroup(s).