archive mirror
 help / color / mirror / Atom feed
From: Michael Marxmeier <>
Subject: Re: [linux-lvm] Problems with raid1 and LVM and initrd
Date: Thu, 7 Oct 99 21:02:02 MESZ	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>; from "Torsten Neumann" at Oct 7, 99 8:26 pm

> I'm trying to setup LVM on top of a md-raid1 device, and then put my root
> filesystem on it. Setting up raid1 was no problem, setting up LVM on top of
> it - no problem. Setting up a second VG on other partitions - no problem.
> 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)

This could be related to a consistency problem with the dynamically
assigned LVM minors. vgscan creates a /etc/lvmtab and /etc/lvmtab.d
(and the correcsponding dev files -- can't remember of head) on your
_ramdisk_. Later LVM tries to access the possibly inconsistent data
(and dev files) on your hard disk.

Please have a look at

Please try the following:

I assume the vgscan on the ram disk completes w/o problem.
Could you transfer the /etc/lvmtab, /etc/lvmtab.d/*
to your hard disk and make sure the LVM dev files are the same?

You should be able to simply call an interactive shell in the

Hope this helps

Michael Marxmeier           Marxmeier Software AG
E-Mail:      Besenbruchstrasse 9
Phone : +49 202 2431440     42285 Wuppertal, Germany
Fax   : +49 202 2431420

      parent reply	other threads:[~2020-11-27 16:16 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
2020-11-27 16:16 ` Michael Marxmeier [this message]

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 \ \ \ \ \

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