Change Startup Volume Group from "PVE" to custom VG name

[Reginald182]

Hello,

I have a 5 node cluster that we are working on and when installing Proxmox on these machines we had renamed the base volume group on all our machines to ensure uniformity across different disk structures. On some of the machines we installed Proxmox on its own set of RAID1 disks and then had a set of RAID10 disks that we used for VM storage. When those were rebooted they came out without issue since the system can still find the original "pve" VG. However, on two of our servers we just installed Proxmox on a RAID10 set of disks and then renamed the "pve" VG to match our other servers. Because of this we are getting the error "Volume Group PVE Not Found" which makes since with the renamed VG. I found a temporary fix online that explains how to fix this and get access back to your machines, https://www.youtube.com/watch?v=Op0VrMljRsg&ab_channel=BenjaminSnoha. But seeing how if the machines are rebooted again you have to repeat this process that seems like a poor fix.

Is there away to have the system look for the new VG on start up so that you do not have to constantly rename VGs after every reboot? Thanks for any advice and let me know if I can provide anymore information.

 

[ahriman]

I'm working on the same issue. Were you able to solve this?

 

[dgeigerd]

Hi together, its a really easy fix. I explained it in the Reddit Post here: https://www.reddit.com/r/Proxmox/comments/xt7xh4/is_it_possible_to_mount_raid_array_as_locallvm_in/

Short Version is this:

change all /dev/mapper/pve-root to /dev/mapper/pve1-root in /boot/grub/grub.cfg
change /dev/pve/root to /dev/pve1/root in /etc/fstab
change /dev/pve/swap to /dev/pve1/swap in /etc/fstab
dpkg-reconfigure linux-base
update-initramfs -u
vgchange -ay (idk if that is needed)

and reboot to check if it worked. (had to press ctrl+alt+del a few time after the reboot command, maybe my Server is slow)

Hope i could help you!