linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jon Lewis <jlewis@lewis.org>
Cc: NeilBrown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: md: could not bd_claim hde1
Date: Sun, 11 Oct 2009 12:35:52 +0400	[thread overview]
Message-ID: <4AD198E8.2070707@msgid.tls.msk.ru> (raw)
In-Reply-To: <Pine.LNX.4.61.0910110051270.22812@soloth.lewis.org>

Jon Lewis wrote:
> On Sun, 11 Oct 2009, NeilBrown wrote:
> 
>> Either hde1 or hde is definitely in use by something else.
>> Try:
>> cat /proc/mounts
> 
> # cat /proc/mounts
> rootfs / rootfs rw 0 0
> /dev/root / ext3 rw 0 0

That's what you get for using rh and their nash ;)

What IS /dev/root?  How does your root device
is specified in initramfs -- by uuid/label?

I bet it is running off /dev/hde1, not /dev/md0.

But this does not explain why it can't add
/dev/hde3 to md1.

Speaking of "LVM is not in use" -- I understand
it like "you didn't set it up", but are you sure
it does not stay on the way?  Like, the dm modules -
how about rmmod'ing them?

In any way, if nothing obvious comes on, your best
bet is to booting into single-user mode, stopping
all "extra" processes, umounting everyhing that's
possible, and trying mdadm from there.

Or from initramfs itself, if that has any tools in
there.

/mjt

  reply	other threads:[~2009-10-11  8:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-11  3:39 md: could not bd_claim hde1 Jon Lewis
2009-10-11  3:55 ` NeilBrown
2009-10-11  4:58   ` Jon Lewis
2009-10-11  8:35     ` Michael Tokarev [this message]
2009-10-11 12:55       ` Jon Lewis
2009-10-11 19:23       ` Gabor Gombas

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=4AD198E8.2070707@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=jlewis@lewis.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).