Corrupted Container Disk Image

L

LukasAdmin

New Member
Aug 7, 2021
7
0
1
23
I deleted a container with ID 108, but now when I want to create another container with the same ID, it says that it detected a signature. I checked and the VM folder does not exists and the image is not present on any LVM, what can I do?
 
Do you see the 108 ID when you do the pct list command?

also please check for the 108.conf file using find tool for example: find /etc -name 108.conf 2>/dev/null
 
very likely you are affected by an already fixed bug - the new LVM version in Bullseye / PVE 7 is more strict when checking the space where volumes are allocated. please upgrade to the newest available package versions, and if the problem persists, post the output of pveversion -v and the full task output with the error.
 
  • Like
Reactions: Moayad
Moayad said:
Do you see the 108 ID when you do the pct list command?

also please check for the 108.conf file using find tool for example: find /etc -name 108.conf 2>/dev/null
Click to expand...
No I cannot see the 108 ID and the config file does not exist
 
fabian said:
very likely you are affected by an already fixed bug - the new LVM version in Bullseye / PVE 7 is more strict when checking the space where volumes are allocated. please upgrade to the newest available package versions, and if the problem persists, post the output of pveversion -v and the full task output with the error.
Click to expand...
Result of pveversion -v:
Code: 
proxmox-ve: 7.0-2 (running kernel: 5.11.22-1-pve)
pve-manager: 7.0-8 (running version: 7.0-8/b1dbf562)
pve-kernel-5.11: 7.0-3
pve-kernel-helper: 7.0-3
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.0.0-1+pve5
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-4
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-7
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.1-1
proxmox-backup-file-restore: 2.0.1-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.2-4
pve-cluster: 7.0-3
pve-container: 4.0-5
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-7
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.4-pve1

And this is the error that I get:

Code: 
()
WARNING: ext4 signature detected on /dev/DataStore/vm-108-disk-0 at offset 1080. Wipe it? [y/n]: [n]
  Aborted wiping of ext4.
  1 existing signature left on the device.
  Failed to wipe signatures on logical volume DataStore/vm-108-disk-0.
TASK ERROR: unable to create CT 108 - lvcreate 'DataStore/vm-108-disk-0' error:   Aborting. Failed to wipe start of new LV.
 
yes. you need to upgrade - that particular bug is fixed in libpve-storage-perl >= 7.0-8
 
You must log in or register to reply here.
Top Bottom