From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] moving single LVM disk from one system to another
Date: Mon Aug 19 03:39:02 2002 [thread overview]
Message-ID: <20020819102427.A24314@sistina.com> (raw)
In-Reply-To: <20020817070901.GA5022@linux.interlinx.bc.ca>; from lvm@interlinx.bc.ca on Sat, Aug 17, 2002 at 03:09:02AM -0400
Is that with our without devfs?
Have you checked, that device nodes are in your initrd for vgscan to be able
to access them fine?
Does vgscan fail finding your VG our is it just wrong entries in /etc/fstab
failing your root mount?
On Sat, Aug 17, 2002 at 03:09:02AM -0400, lvm@interlinx.bc.ca wrote:
> My workstation died (the MB, not the disk). :-(
>
> In it I have a single ATA disk with three fdisk type partitions:
>
> hd?1 Linux boot
> hd?2 Windows ~hangs head in shame~ (it's for testing only :-)
> hd?3 LVM
>
> Inside the LVM partition is the root, swap and a couple of other
> filesystems. On the ext3 /boot partition there is an initrd with all
> the magic in it to get LVM and ext3 up and running.
>
> On the dead machine, where the disk was built and last running, the
> disk was device /dev/hde on a Promise ATA100 bus. I want to move it
> to another (working) machine on the primary ATA bus so it will be
> /dev/hda.
>
> When I boot the system, the initrd fires up and runs a vgscan but it
> does not find the rootvol volume group. So I boot on my Linux
> distro's boot CD in rescue mode, install the LVM module, run vgscan
> (the vendor was nice enough to put the lvm tools on the boot/rescue
> cd) and it finds it fine. I run "vgchange -a y" and whammo, the
> volume group is active and I can mount my rootfs. Great. So I chroot
> the HD (LVM) rootfs and mount /boot and run vgscan again so that it
> updates the /etc/lvm* stuff and also build a new initrd, hoping that
> the new configuration information will make it into the initrd.
>
> I reboot again and still vgscan finds no volume groups. What am I
> missing here? Why can the rescue mode of the boot CD find the volume
> group no problem with a vgscan and my initrd's vgscan cannot?
>
> Thanx in advance for any enlightment.
>
> b.
>
> --
> Brian J. Murrell
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
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:[~2002-08-19 3:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-17 2:10 [linux-lvm] moving single LVM disk from one system to another lvm
2002-08-17 5:50 ` Goetz Bock
2002-08-17 9:19 ` lvm
2002-08-19 3:39 ` Heinz J . Mauelshagen [this message]
2002-08-19 4:03 ` lvm
2002-08-19 5:05 ` lvm
2002-08-19 7:24 ` lvm
2002-08-19 7:31 ` Heinz J . Mauelshagen
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=20020819102427.A24314@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.