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
proxmox
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
Adventures in SDN (Software Defined Networking) in Proxmox
Creating VXLANs: Example: https://pve.proxmox.com/pve-docs/chapter-pvesdn.html#pvesdn_setup_example_vlan VXLan Setup Example Create a zone: ID: vxlan1 Peers Address List: 192.168.0.1,192.168.0.2,192.168.0.3 Create a VNet named vxvnet1 using the VXLAN zone myvxlanzone created previously. ID:
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
Proxmox error “Cannot remove image, a guest with VMID ‘XXX’ exists! You can delete the image from the guest’s hardware pane”
At times, after many live migrations between different disk, and whilst using TrueNAS Scale, you’ll encounter the following error: Cannot remove image, a guest with
Resizing TrueNAS Scale Proxmox NAS causes read-only file system
Typically with LVM disks you can just press the resize button in Proxmox and you won’t have any problems. Of course, if you’re using an
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
How to reduce the size of an LVM disk on a Debian system on Proxmox and an underlying EXT4 disk
Background I’ve never reduced the size of a disk. Everywhere you read up about it there are huge disclaimers that it can break your system,
Oversubscribing LVM-Thin on Proxmox – warnings
Background LVM-Thin is great because you don’t use all the disk space and can share between hosts. However, it’s dangerous to oversubscribe if one of