Search results

Thank you very much Dominik, The rename inside the guest worked like a charm... I will also add the ssd vg from the host lvm scan list as you indicated.

I have this: root@pve01:~# pvs PV VG Fmt Attr PSize PFree /dev/sda3 pve lvm2 a-- 930.75g 16.00g /dev/sdb ssd lvm2 a-- 893.25g 401.25g /dev/ssd/vm-106-disk-2 PGData lvm2 a-- 32.00g 0 /dev/ssd/vm-107-disk-2 PGData...

Ok... Now I searched for that issue and got this thread: https://forum.proxmox.com/threads/lvm-volume-groups-with-same-name.45658/ The issue probably arose because we copied a qemu backup image from an older proxmox (3) and did an image qemu restore on this new proxmox v5... and on 2 VM's...

Hi, first thanks for your help. vgs: root@pve01:~# time vgs VG #PV #LV #SN Attr VSize VFree PGData 1 1 0 wz--n- 200.00g 0 PGData 1 1 0 wz--n- 32.00g 0 pve 1 3 0 wz--n- 930.75g 16.00g ssd 1 11 0 wz--n- 893.25g 401.25g real...

Hello, I had a single proxmox 5.2 node and all was fine... I created some machines... perfect... Then I added a second node, enabled cluster mode, and all seems fine also... Both nodes seem available on the web interface, and I created more machines on node 2... Now I was going to create a...