Recent content by garethw

Makes sense. I figured out why the last VM wasn't booting, my predecessor had created it using OVMF (UEFI) instead of SeaBIOS. God knows why...

Thanks, I tried recreating the VM using virtio and swapping in the disk image but it won't boot. Would it depend on how the VM was originally set up? Strange because all the VMs on the other node are set up using virtio. Tried SCSI as well same issue.

OK I think I solved my own problem ;) I added a new VM with the ID 201 on the vm-data1 volume and once it was added I logged into the console and edited the 201.conf and changed the ID/size of the IDE0 device to match the old vm-101-disk0 VM is now booting.

OK I figured out how to add the LVM storage and can now see the vm-101-disk0 etc I can see the volume as an option when I go to Create a VM but I can't see what I select to use an existing VM disk?

Thanks for the response. I don't believe replication / backup was enabled to the other node so I've got nothing but the RAID-5 volume. So I'm in the Proxmox web interface, how do I add an LVM storage exactly? I went to the 'Storage View' and clicked on 'LVM' under Disks on the tree to the...

Here is the output of lvs / vgs / pvs it appears there are some LVM filesystems, just not sure how to mount them I don't really understand LVM root@server2:/mnt# lvs /dev/sdc: open failed: No medium found LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync...

My predecessor installed Proxmox on an SD memory card (apparently he didn't read that this isn't recommended!) and of course the SD card has failed. The VMs were stored on a 16TB RAID-5 volume which is intact. I installed the most recent version of Proxmox VE on a new hard drive hoping to...