From: "Brian J. Murrell" <lvm@interlinx.bc.ca>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Migrating to an LVM system (boot/root) disk
Date: Sat, 2 Jun 2001 19:16:24 -0700 [thread overview]
Message-ID: <20010602191624.E21442@linux.interlinx.bc.ca> (raw)
I would like to migrate my system disk to using LVM, completely --
boot and root filesystems (as well as others). I have 0.9.1beta7 as
well as the lilo patch posted previous to this list.
Fortunately I have a new ide disk that is larger than my system disk
currently so I can migrate to it. My current system disk is on
/dev/hda and the new disk is on /dev/hdc. I have created one large
/dev/hdc1 partition on the new disk.
I have also created a PV, a VG and two LVs -- root and boot. I have
mounted the lvs and copied my boot and root filesytems to the PVs. I
also create the lvm initrd. So far so good.
I edited my /etc/lilo.conf on the new root filesystem to change the
following:
...
-boot=/dev/hda
+boot=/dev/hdc
...
image=/boot/vmlinuz
label=linux
- root=/dev/hda5
+ root=/dev/system/boot
+ initrd=/boot/initrd-lvm-2.4.5-1.1mdk.gz
read-only
However when I chroot to the root filesystem on the new disk and run
the lilo command I get the following:
# lilo
Warning: /dev/hdc is not on the first disk
Fatal: This version of LVM does not support boot LVs
The warning I understand but it would seem there is some problem with
what I have cobbled together here as my lilo does not like my LVM for
booting.
One other thing that has occurred to me is that the PV that underlies
the VG was named as /dev/hdc1. I have a suspicion that I will not be
able to simply move that drive from the secondary IDE bus to the
primary IDE bus as it will then be known as /dev/sda1. Is this
correct?
Is there a better way to do this migration if my desire is really to
have one large parition/PV for my VG rather than using a bunch of
partitions/PV's?
Any comments most welcome.
Thanx much, in advance,
b.
P.S. I also have horrible nightsweats of trying to boot an LVM box from
"emergency" boot media (diskettes, CDROM, etc.). :-)
--
Brian J. Murrell
next reply other threads:[~2001-06-03 2:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-03 2:16 Brian J. Murrell [this message]
2001-06-03 5:02 ` [linux-lvm] Migrating to an LVM system (boot/root) disk Steve Wray
2001-06-03 10:22 ` Brian J. Murrell
2001-06-03 10:59 ` Steve Wray
2001-06-03 18:27 ` Michael Tokarev
2001-06-03 21:12 ` Steve Wray
2001-06-03 23:11 ` Michael Tokarev
2001-06-04 17:34 ` Andreas Dilger
2001-06-04 18:59 ` Michael Tokarev
2001-06-04 21:03 ` Steve Wray
2001-06-04 22:15 ` AJ Lewis
2001-06-04 23:15 ` Michael Tokarev
2001-06-04 23:28 ` Luca Berra
2001-06-05 16:57 ` AJ Lewis
2001-06-05 17:55 ` Andreas Dilger
2001-06-05 18:08 ` Luca Berra
2001-06-04 3:40 ` Andreas Dilger
2001-06-04 6:04 ` Brian J. Murrell
2001-06-04 17:37 ` Andreas Dilger
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=20010602191624.E21442@linux.interlinx.bc.ca \
--to=lvm@interlinx.bc.ca \
--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.