Snapshot error lvcreate snapshot 'pve/snap_vm-100-disk-1_test' error: Run `lvcreate --help' for mor

Derek DiCamillo

New Member
Feb 19, 2019
16
0
1
40
I am getting an error when trying to do a snapshot.


lvcreate snapshot 'pve/snap_vm-100-disk-1_test' error: Run `lvcreate --help' for more information.

I am not sure how to trouble shoot this.
 
I am getting an error when trying to do a snapshot.


lvcreate snapshot 'pve/snap_vm-100-disk-1_test' error: Run `lvcreate --help' for more information.

I am not sure how to trouble shoot this.


What in particular did you do and how does the related configuration (storage, vm, ...) look like?
 
I am receiving this error message when trying to create a snapshot:


Logical volume "vm-101-state-Test" created.
saving VM state and RAM using storage 'local-lvm'
1.51 MiB in 0s
completed saving the VM state in 1s, saved 1020.68 MiB
snapshotting 'drive-scsi0' (local-lvm:vm-101-disk-0)
modprobe: FATAL: Module dm-snapshot not found in directory /lib/modules/5.13.19-2-pve
/sbin/modprobe failed: 1
snapshot: Required device-mapper target(s) not detected in your kernel.
snapshot create failed: starting cleanup
Logical volume "vm-101-state-Test" successfully removed.
TASK ERROR: lvcreate snapshot 'pve/snap_vm-101-disk-0_Test' error: Run `lvcreate --help' for more information.
 
Hi,
I am receiving this error message when trying to create a snapshot:


Logical volume "vm-101-state-Test" created.
saving VM state and RAM using storage 'local-lvm'
1.51 MiB in 0s
completed saving the VM state in 1s, saved 1020.68 MiB
snapshotting 'drive-scsi0' (local-lvm:vm-101-disk-0)
modprobe: FATAL: Module dm-snapshot not found in directory /lib/modules/5.13.19-2-pve
/sbin/modprobe failed: 1
snapshot: Required device-mapper target(s) not detected in your kernel.
snapshot create failed: starting cleanup
Logical volume "vm-101-state-Test" successfully removed.
TASK ERROR: lvcreate snapshot 'pve/snap_vm-101-disk-0_Test' error: Run `lvcreate --help' for more information.
did you recently install a newer kernel and not yet reboot? In any case, kernel 5.13 is about a year old, please upgrade to a current version and try again.
P.S. Proxmox VE 7 will be end-of-life in 2 weeks, so please consider upgrading to version 8 too: https://pve.proxmox.com/wiki/Upgrade_from_7_to_8