Proxmox installation stuck on 3% creating LVs
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/
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/
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
Introduction I hate Proxmox hypervisor reboots. Any hypervisor reboot is a bad thing, because at the end of the day you’ll have VMs on the
A while ago I rebooted a Proxmox server in cluster and got this scary message: DMAR-IR: [Firmware Bug]: ioapic 3 has no mapping iommu, interrupt
Proxmox disks sometimes break. It’s not supposed to, but when it happens it can be devastating. I only use defaults. Nothing fancy. Whatever the operating
On both my PBS servers this morning I’m getting the following. Both PBS server has more than 2 TB drives, which might be of relevant.
Sometimes you want to get rid of a VM template. In doing so, you might encounter the following issue: TASK ERROR: base volume ‘nas02:base-9403-disk-0’ is
Here is an easily reproducible error that happens on Proxmox (perhaps also TrueNAS Core iSCSI NAS) that doesn’t seem solvable. The errors do not stop
Introduction Every disk crash is different. The point being a disk crash should never happen, so when it does, the results and probability of recovery
NAS refuses to start up. Icon has exclamation and triangle. Hover shows I/O error. Examine /var/log/syslog, search “Error IO”. Apr 3 16:21:14 hvX kernel: [4948799.898572]