From: Torsten Neumann <torsten@londo.rhein-main.de>
To: LVM for Linux <linux-lvm@msede.com>
Subject: [linux-lvm] Problems with raid1 and LVM and initrd
Date: Thu, 7 Oct 1999 20:26:54 +0200 (MET DST) [thread overview]
Message-ID: <m11ZIFi-000D4UC@londo.rhein-main.de> (raw)
Hi,
I hope I get the problem description right, the fault machine is miles away.
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.
Disk partitions looks something like
/dev/sda1 /dev/sdb1 256 MB swap area
/dev/sda2 /dev/sdb2 32 MB /boot for vmlinux and initrd
/dev/sda3 /dev/sdb3 2048MB /dev/md0 -> vg00
/dev/sda4 /dev/sdb4 rest vg01
My linuxrc does something like this
mount /proc
insmod raid1
ckraid --fix /etc/raid1.conf
mdadd -ar
insmod lvm
vgscan
vgchange -a y
umount /proc
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)
( By the way does anybody know how to debug initrd ? I wanted to make an
"pvscan -d >foo" but how to I get the output out of ramdisk )
Booting from a third disk and execute the linuxrc script by hand works just
fine, all vg's are seen and useable.
Everythings works, execpt if I start it via initrd.
Any Ideas ?
Regards
Torsten
next reply other threads:[~1999-10-07 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-07 18:26 Torsten Neumann [this message]
1999-10-07 22:38 ` [linux-lvm] Problems with raid1 and LVM and initrd Fernando Dammous
1999-10-08 19:21 ` Torsten Neumann
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:
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=m11ZIFi-000D4UC@londo.rhein-main.de \
--to=torsten@londo.rhein-main.de \
--cc=linux-lvm@msede.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).