Whilst using qm importdisk you might experience the following problem: root@hv:~# qm importdisk 123 clients-disk.vmdk nas03 importing disk ‘clients-disk.vmdk’ to VM 123 … iscsiadm: No
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
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
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
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,
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
Background When deleting a disk from the Proxmox UI, you are presented with several options. Depending on where you started, you might get this problem:
Yep, this is apparently normal, mostly if you had data on the drive before, see: https://forum.proxmox.com/threads/proxmox-installation-stuck-on-3-creating-lvs-please-help-guys.94650/
Introduction Proxmox VE hypervisors need to be monitored. Some of the key items you could monitor are: Disk I/O Wait time CPU temperature Smart Status
After installing an HTTPS certificate, the following problem started occurring: 2024-05-19T08:41:52.869412+02:00 server pvestatd[1481]: backup-server1.example.com: error fetching datastores – fingerprint ‘X’ not verified, abort! 2024-05-19T08:41:53.063071+02:00 server
Copyright 2024 © All rights Reserved