From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] can't find volumes
Date: Fri Jun 27 04:44:02 2003 [thread overview]
Message-ID: <20030627112852.B27001@sistina.com> (raw)
In-Reply-To: <200306261012.h5QACOlx015041@ruby.ridersoft.net>; from lvm@ruby.ridersoft.net on Thu, Jun 26, 2003 at 12:12:24PM +0200
Mark,
that's probably the missing /proc in your chroot environment.
On Thu, Jun 26, 2003 at 12:12:24PM +0200, lvm@ruby.ridersoft.net wrote:
> Hi, I come seeking sage advice :)
>
> Anyways, I've been busy installing a new Linux system using Gentoo. I am running this on a spare box, Duron 800 w 300mb, with the harddisk connected to the Promise ATA 100 onboard controller as /dev/hde8.
>
> Al goes well, and I create the following partitions
>
> /dev/hde6 swap
> /dev/hde7 ext3 fs /boot
> /dev/hde8 lvm
>
> I also create the pv on /dev/hde8 and a logical volume at /dev/lv/ide
>
> /dev/lv/ide is my /
>
> >From my running livecd I then chroot'ed into /dev/lv/ide, and then the troubles began. When I run vgscan when chroot'ed it doesn't find any volume groups. When I run vgchange, i claims that the VDGA record doesn't match the kernel, and urges me to run vgscan, running vgscan doesn't solve this problem since it doesn't find the volume groups.
>
> ls -l /dev/lv/ide shows me that my volume group indeed doesn't excist. However, the mount command shows me that /dev/lv/ide is mounted at root. So in summary, I can't find the volumegroup, even tough I am working on/in it.
>
> I decided to go ahead anyways, and created a initrd using lvmcreate_initrd (based on the kernel i made, 2.4.21 ) it does this, and when I boot it loads this initrd as it is supposed to. It neatly finds my /dev/hda and /dev/hdb cdroms, and once insmod'ed it also find /dev/hde, but the it runs vgscan and finds no volumegroups, that causes vgchange to not find anything either. That causes the kernel to panic, since it cannot find root.
>
> Weird thing is, if I boot with any other rescue/livecd, such as SuSE rescue, knoppix or gentoo live cd, I can vgscan and vgchange -ay to find my volume group and logical volume. But once chroot'ed or booting to my new system, I cannot and will not find it.
>
> Does anyone have any suggestions on why vgscan doesn't find anything and how to solve this ?
>
> Many thanx in advance, I have been strugling with this one for almost a week now, and I am out of options. I have been able to install lvm as root on quite a few systems before, including a LFS system, but right now, I am stumped.
>
> best regards
> Mark
>
>
> When I boot from a livecd image, such as
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2003-06-27 4:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 9:30 [linux-lvm] can't find volumes lvm
2003-06-27 4:44 ` Heinz J . Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-27 8:34 Mark
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=20030627112852.B27001@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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