[SOLVED] Storage type & snapshot

Y

yoannyop

New Member
Jul 11, 2024
3
1
3
Hello everyone.
I have an HP server with 2 storage volumes.
On the first one, I installed Proxmox VE and I use the second one for storage.
For this second volume, I followed a procedure to create a :
- new GPT table
- create primary partition in ext4 (parted)
- create volume group (vgcreate)
- create logical volume (lvcreate)
- format in ext4 (mkfs.ext4)
- mount volume
So far, so good, but I can't create snapshots. I have the message "The current guest configuration does not support taking new snapshots"
How do I proceed?
Thanks in advance and have a nice day!
 
yoannyop said:
For this second volume, I followed a procedure to create a :
Click to expand...
You're confusing a few things. With your workflow (point 2 is not needed) and snapshots would only work for manual created LV's.

Please have a look at the storage matrix: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_storage_types

If you have a fresh new storage (your second storage), it is very easy to use it to create an LVM thin volume. Go to the WebUI directly to the Server Node: Disks -> LVM-Thin -> Create Thinpool. Select your virtual raid drive and create your new pool.
 
OP, seems to be using Directory storage, which is fine for use with snapshots if QCOW disk image is used.
However, it is possible that OP has a VM with a TPM disk that is RAW, which prevents the snapshots from being taken.

While Thin LVM is preferred option in OP's situation, using Directory storage is ok. What we would need is:
a) cat /etc/pve/storage.cfg
b) pvesm status
c) qm config [vmid]

Best

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
bbgeek17 said:
OP, seems to be using Directory storage, which is fine for use with snapshots if QCOW disk image is used.
However, it is possible that OP has a VM with a TPM disk that is RAW, which prevents the snapshots from being taken.

While Thin LVM is preferred option in OP's situation, using Directory storage is ok. What we would need is:
a) cat /etc/pve/storage.cfg
b) pvesm status
c) qm config [vmid]

Best

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

root@SV-VN-Hyperviseur-04:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content snippets,iso,vztmpl,backup
shared 0

dir: data
path /mnt/data
content snippets,rootdir,images
prune-backups keep-all=1
shared 0

root@SV-VN-Hyperviseur-04:~# pvesm status
Name Type Status Total Used Available %
data dir active 2302881204 182254816 2097202432 7.91%
local dir active 278462932 198957416 67316388 71.45%

root@SV-VN-Hyperviseur-04:~# qm config 101
agent: 1
bios: ovmf
boot: order=sata0;ide0;ide2;net0
cores: 2
cpu: x86-64-v2-AES
efidisk0: data:101/vm-101-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
ide0: local:iso/virtio-win.iso,media=cdrom,size=708140K
ide2: none,media=cdrom
machine: pc-q35-9.0
memory: 4096
meta: creation-qemu=9.0.2,ctime=1723549871
name: SV-VN-Cert-01
net0: virtio=BC:24:11:94:0D:11,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
sata0: data:101/abaca-cert-px.qcow2,cache=writethrough,size=180G
scsihw: virtio-scsi-single
smbios1: uuid=6d1e81e3-f415-4b80-aa1c-8f37036d873c
sockets: 1
tpmstate0: data:101/vm-101-disk-2.raw,size=4M,version=v2.0
vmgenid: ba3ee98c-6f72-4eb5-a9ce-520de6640ccf


Thank you for your answers.
I can reset my volume 2 if necessary, but my skills aren't up to scratch.
Thanks you for your help
 
Thank you for your answers.
I destroyed my volume 2 and recreated a LVM-THIN using the DISK menu.
Thanks again.
 
  • Like
Reactions: fireon
You must log in or register to reply here.
Top Bottom