FYI: Thanks for the input. My main issue was that I had to run mkinitrd
to remove the old references to the old vol group name.
For
vgrename old_rootvg new_rootvg
changed the kernel line entries in grub.conf
change the volume mount entries in fstab
vgchange -ay ( I don't think I needed to issue that)
mkinitrd
usage: mkinitrd [--version] [--help] [-v] [-f] [--preload <module>]
[--image-version] [--with=<module>]
<initrd-image> <kernel-version>
(ex: mkinitrd /boot/initramfs-2.6.32-279.19.1.el6.x86_64.img
2.6.32-279.19.1.el6.x86_64)
so then from the example I ran:
mkinitrd /boot/initramfs-2.6.32-279.19.1.el6.x86_64.img
2.6.32-279.19.1.el6.x86_64
On Thu, Feb 14, 2013 at 5:36 PM, Chris Knadle <[email protected]>wrote:
> On Thursday, February 14, 2013 14:28:56, Michael Quick wrote:
> > Booting a Cloned Drive and booting with both drives plugged in.
>
> By default that's an impossible situation.
>
> If you look at the contents of /etc/fstab you're most likely going to find
> that your system is discovering the partitions to mount at boot time by
> using
> their UUIDs. UUID = Universally /Unique/ IDentifier.
>
> https://en.wikipedia.org/wiki/UUID
>
> When you clone the drive, the UUIDs of the clone is identical to the
> original.
> When you boot with both drives connected, you're trying to boot with two
> sets
> of filesystems that have /non-unique/ UUIDs, when each UUID /must/ be
> unique.
>
> Run the 'blkid' command as root to see the UUIDs.
>
> > I have a RHEL6 drive encrypted with LUKS (a rootvg and /boot). I want to
> > clone it so dd seems promising or clonezilla. I dd the entire disk over
> and
> > that drive works great in general. Swap the drive in, and it boots fine.
> >
> > However, another scenario which I would like to account for is the delta
> of
> > data not on the backed up drive. So my thought is to boot them both in
> the
> > same system (say from ultra bay/USB) but it reads the wrong disk etc...
>
> Now you know why.
>
> > So I then go through the effort of trying to rename the LV PV update
> grub
> > and fstab etc. to get it to see two separate drives (and properly see the
> > other partition in Linux) , but I keep getting KPs. Not sure what I'm
> doing
> > wrong.
> >
> > Q: Has anyone done this before?
> > Q: OR Is there a better way?
>
> You have two options as to how to fix this.
>
> A) assign different UUIDs to the clone drive's filesystems ('blkid -U
> <uuid>')
> B) boot by hard-coded device names rather than via UUIDs. Doing this will
> require modification of both grub2 configuration and /etc/fstab.
>
> -- Chris
>
> --
> Chris Knadle
> [email protected]
> _______________________________________________
> Mid-Hudson Valley Linux Users Group http://mhvlug.org
> http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug
>
> Upcoming Meetings (6pm - 8pm) Vassar College
> Feb 6 - Raspberry Pi
> Mar 6 - 10th Anniversary Meeting - Linux where you least expect it
> Apr 3 - Typography: Physical Art to Digital Art
>
_______________________________________________
Mid-Hudson Valley Linux Users Group http://mhvlug.org
http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug
Upcoming Meetings (6pm - 8pm) Vassar College
Feb 6 - Raspberry Pi
Mar 6 - 10th Anniversary Meeting - Linux where you least expect it
Apr 3 - Typography: Physical Art to Digital Art
