VM ID changed, now OS won't boot

E

eiger3970

Well-Known Member
Sep 9, 2012
276
3
58
I changed the VM ID and now the 2 VM's OS Console shows error:
Volume group "VolGroup00" not found
The other VM is trying to run a new install.

I followed this process to rename the VM IDs. Funnily enough, there were no files in /var/lib/vz/images.

Stop VM > Yes > SSH into Proxmox < $ cd /var/lib/vz/images > $ mv xyz abc > $ cd abc > $ mv vm-xyz-disk-1.qcow2 vm-abc-disk-1.qcow2 (or .raw) > $ cd /etc/pve/nodes/proxmox/qemu-server > $ mv xyz.conf abc.conf > $ vim abc.conf > change line local:xyz/vm-xyz-disk-1.raw,format=raw,size=30G to local:abc/vm-abc-disk-1.raw,format=raw,size=30G > Save > view Proxmox with new VMID.
 
hi,

probably you assigned the disks wrongly.

eiger3970 said:
Funnily enough, there were no files in /var/lib/vz/images.
Click to expand...
what did you mv then if there were no disks?

official way to change VMID is through cloning or backup&restore
 
  • Like
Reactions: eiger3970
I simply moved the VM IDs from 150 149 148 147 146 145 144 143 142 142 to 141 142 143 144 145 146 147 148 149 150.
I'll have to research how to clone or backup&restore after I rescue Proxmox.

I've just noticed the 141.conf - 150.conf files are in two different locations:
/etc/pve/nodes/proxmox/qemu-server (these are the conf files I renamed).
/etc/pve/qemu-server (I didn't touch these conf files).
/var/lib/vz/images (used to be here, but weren't there even before I started the renaming).
 
Last edited:
eiger3970 said:
I simply moved the VM IDs from 150 149 148 147 146 145 144 143 142 142 to 141 142 143 144 145 146 147 148 149 150.
I'll have to research how to clone or backup&restore after I rescue Proxmox.

I've just noticed the 141.conf - 150.conf files are in two different locations:
/etc/pve/nodes/proxmox/qemu-server (these are the conf files I renamed).
/etc/pve/qemu-server (I didn't touch these conf files).
/var/lib/vz/images (used to be here, but weren't there even before I started the renaming).
Click to expand...
So:
141 was renamed 144.
143 was renamed 146.
 
Ran a backup and restore with a new VMID.
Worked on VM 143.
The 2nd backup/restore with a new VM 144 would boot up a wrong OS?
 
Ok, had to Remove newly restored VM 144, then restore again.
Seemed to have removed the previous VM's OS.
 
You must log in or register to reply here.
Top Bottom