archive mirror
 help / color / mirror / Atom feed
From: Torsten Neumann <>
Subject: Re: [linux-lvm] Problems with raid1 and LVM and initrd
Date: 8 Oct 1999 21:21:16 +0200	[thread overview]
Message-ID: <7tlg7c$6fe$> (raw)

I <> wrote:

[ snip ]

> The problem is the vgscan call. It doesn't find vg00, it just finds vg01.
> Inserting some debug code ( pvdisplay, pvscan, bash ) in the above it looks
> to me that /dev/md0 is correctly initialized. But the lvm-commands just
> returns error codes. The result is an error while booting the
> real-root-device, since there are no drivers it couldn't boot. (init not
> found)

Finally I found what was wrong, because it may be of interest for others:

If starting vgscan,pvscan from my ramdisk they "only" look in /dev/md/ for
md block-devices. They didn't use /dev/md0. Creating /dev/md/ and a
symlink /dev/md/md0 -> /dev/md0 solved the problem.

I didn't figured out why vgscan behaves different when starting via initrd
vs. "normal" bootup-sequence. As said before booting from a 3rd drive works
and there was also no /dev/md dir. 


  parent reply	other threads:[~1999-10-08 19:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-07 18:26 [linux-lvm] Problems with raid1 and LVM and initrd Torsten Neumann
1999-10-07 22:38 ` Fernando Dammous
1999-10-08 19:21 ` Torsten Neumann [this message]
2020-11-27 16:16 ` Michael Marxmeier

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='7tlg7c$6fe$' \ \ \

* 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).