Help needed, pve wont reboot after vgrenamed

windpoint

New Member
Jun 25, 2021
2
0
1
46
I changed vg name from pve to vg1
system wont boot after the change

Code:
# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.4.6-1-pve root=/dev/mapper/pve-root ro quiet

under /dev/mapper/
I see VG1-root instead pve-root

Not sure where I can modify this setting.
 
Hey,

did you change /etc/fstab and /boot/grub/grub.cfg accordingly, for the second file, running grub-mkconfig might work, if not you have to make the changes manually. Why did you want to rename the VG in the first place?
 
  • Like
Reactions: _gabriel
Thank you, Hannes. This works for me.

BTW, the reason I changed it to vg1,vg2, is that pve is so confusing. it can be node or vg . I know it's stupid. But learned a lot...
 
can be useful if PVE don't boot anymore (wrong user modification update ... ) on the only SSD containing the PVE OS and VM disks.
A new PVE system on a dedicated SSD will boot without error about duplicated "pve" VG name.