Pulling my hair out trying to add a disk to VM...

[JohnBee]

I've been at this for a few days now(on/off), and cannot make sense of the issue.

My plan is to commission an SSD drive to a Windows VM - seemed simple enough, though I can't for the likes of me, figure out how to do that, as every option seems to throw back errors, first I tried LVM-Thin, thinking I'd retain snapshot capabilities, but could not figure out a way to do this, and so I decided to go the LVM route - though here again, I can't seem to attach the disk to the VM




That said, does anyone know why this is happening and how to fix it?

 

[bbgeek17]

Note that the allocated capacity is measured in GiB, which is not the same as GB.
Use a web calculator to convert 1900GiB to bytes, you will see that it would be 2040109465600. Which is more than what you have, based on the error message provided.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[JohnBee]

Hi and thanks for the response
Though unfortunately, it doesn't matter what size I enter, it will always return the same error

 

[bbgeek17]

What is the output of:
- lsblk
- pvs
- vgs
- lvs
- cat /etc/pve/storage.cfg
- pvesm status
- pvesm list myvg

Please use text output encoded with CODE tags

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[alexskysilk]

That said, does anyone know why this is happening and how to fix it?

your disk(s) associated with myvg is full. either add more disks to the volume group or delete or move stuff.

 

[justinclift]

My plan is to commission an SSD drive to a Windows VM

Ahhh. Are you wanting to just pass the entire disk directly to a VM as a raw device, so it can manage the whole thing without using LVM/ZFS/etc in between?

I'm pretty sure there's a way to do that from the command line. Can go locate the info if that's what you're trying to do.