When you ZFS Pool runs out on Proxmox
Background When your ZFS pool runs out on Proxmox, your entire host and possibly many of the VMs will crash and stop working. You won’t
Virtualization
How to deal with an orphaned disk on a Proxmox VM
Sometimes, when analysing the “VM Disks” on your NAS, you might see a duplicate. For example, you might see this: vm-202-disk-0 vm-202-disk-1 The format might
Could not find lu_name when destroying a VM on a TrueNAS Core Proxmox NAS
Sometimes when you destroy a VM on a iSCSI TrueNAS Core server you might get the following message: TASK ERROR: Could not find lu_name for
Unable to destroy VM: “TASK ERROR: no such logical volume pve/data”
Whilst destroying a VM, you get the following message: “TASK ERROR: no such logical volume pve/data” Here is the before: This is part of a
After a disk resize made by a WHMCS upgrade, Proxmox reports error and old size
Environment: WHMCS Proxmox VE Modules Gardens Proxmox VE Module TrueNAS Scale iSCSI NAS After a client automatically upgraded a service the disk resize command was
TD-compressed data is corrupt – System halted
This happened to me with Proxmox and a Supermicro X11SSL-F. I think the screen is cut off.
Unable to import vmdk into Proxmox because it’s actually a RAW file
Whilst using qm importdisk you may experience the following problem: root@hvX:~# qm importdisk 123 disk.vmdk nasX importing disk ‘disk.vmdk’ to VM 123 … iscsiadm: No
List of useful Proxmox commands
# pvesm list nasX Volid Format Type Size VMID nasX:base-9000-disk-0 raw images 3758096384 9000 nasX:vm-112-disk-0 raw images 214748364800 112 nasX:vm-125-disk-0 raw images 268435456000 125 nasX:vm-137-disk-0
After enlarging disk beyond 4TB boundary, Proxmox reports error: attempt to read or write outside of disk ‘hdo’.
Woke up this morning to this after enlarging a big disk yesterday: The computer then tries to boot but fails with a Kernel panic: Doing
Proxmox VE Cluster Live Restore of Normal Backup Job Across TheGrandWazoo NAS Fails
Whilst trying to restore a normal backup job from one node to another in another part of the cluster, the following is experienced: Warning: volblocksize