Help booting renamed LVM Volume Group

[gizmo4321]

I've been helping a friend migrate data from an older F10 installation that was upgraded from F8 to a new freshly installed F10 on another drive. Both systems were set up using LVM, and both systems have VolGroup00. Using vgrename, we renamed the new F10 installation to 'Fedora10-12182008' and left the old one as 'VolGroup00'. We were then able to mount the new drive while booted on the old one, and copied data from the old drive over to the new one. However, now when we try to boot the new drive, we get the following:

"found Volume Group "Fedora10-12182008"
using metadata type LVM2 Volume Group "VolGroup00" not found
unable to access resume service (/dev/VolGroup01) mount error mounting /dev/root as ext3 no such file or directory

Neither grub.conf nor fstab make any references to VolGroup00; everything refers to the UUID for the drive.

I'm guessing we can boot into the Fedora Live CD and rename the new volume group back to VolGroup00 and everything will be fine, but it would be nice if we could convince Fedora to boot with this drive named the way it is, so that we could avoid any future issues related to mounting 'VolGroup00' named volumes on this system.

Can anyone provide any guidance here?

[edit]
Here's the output from vgdisplay:

--- Volume group ---
VG Name Fedora10-12182008
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 297.88 GB
PE Size 32.00 MB
Total PE 9532
Alloc PE / Size 9531 / 297.84 GB
Free PE / Size 1 / 32.00 MB
VG UUID QdvxYr-kpyu-3Bk9-cmyC-HG7O-9Fbc-EEtj1n

--- Volume group ---
VG Name VolGroup00
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 279.34 GB
PE Size 32.00 MB
Total PE 8939
Alloc PE / Size 8938 / 279.31 GB
Free PE / Size 1 / 32.00 MB
VG UUID sHyfbM-muc7-hUU8-IYOf-bvN3-aEEF-jRyREd


and the output from lvdisplay:
LV Name /dev/Fedora10-12182008/LogVol00
VG Name Fedora10-12182008
LV UUID qzP9D6-W8xw-JeXj-ZIRe-9IN5-olUh-dHqJJJ
LV Write Access read/write
LV Status available
# open 0
LV Size 292.03 GB
Current LE 9345
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2

--- Logical volume ---
LV Name /dev/Fedora10-12182008/LogVol01
VG Name Fedora10-12182008
LV UUID 76Obu2-oOP6-5o9u-5ql7-2jMi-QeWl-1h9kBL
LV Write Access read/write
LV Status available
# open 0
LV Size 5.81 GB
Current LE 186
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID B6zjYX-FPFt-6Qeg-SQoI-qPhQ-Phac-pVxqEL
LV Write Access read/write
LV Status available
# open 1
LV Size 277.38 GB
Current LE 8876
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID wlC7Qw-56fG-qC4F-7Uje-auEj-XAN6-3cX7lP
LV Write Access read/write
LV Status available
# open 1
LV Size 1.94 GB
Current LE 62
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1

[/edit]

[gizmo4321]

Nobody? Am I peeing up a rope here?

[brunson]

I'm battling something similar, but not quite the same, right now. When you first boot the kernel mount an initial ram disk (initrd) to find boot scripts, it clearly can't read your /etc/fstab, because it's on your root partition, cart, horse. That initrd probably has a reference to VolGroup00.

I'm about to go digging through the initrd on my system to see what I have to do to get it to activate my second volume group at boot time, so if I can find anything to confirm or deny this, I'll let you know. In the mean time I'd try renaming that volume group to VolGroup00.

Edit:
In the init script in the initrd image there are these command:

ebrunsonlx(~/initrd)$ grep VolGroup00 init
lvm vgchange -ay --ignorelockingfailure VolGroup00
resume /dev/VolGroup00/LogVol01
mkrootdev -t ext3 -o defaults,ro /dev/VolGroup00/LogVol00

You need to name the volume group appropriately.

[gizmo4321]

Yeah, I finally came across some instructions on how to extract the initrd image, and edit the init script to fix the issue, but I had to boot the LiveCD to do it.