VM Status Unknown Grey Question Mark: Fix it in Proxmox
VM status unknown grey question mark usually means missing storage, a stale lock, or an orphaned config. Here's the step-by-step fix for Proxmox.
Homelab & Vietnam
39 posts
VM status unknown grey question mark usually means missing storage, a stale lock, or an orphaned config. Here's the step-by-step fix for Proxmox.
870 EVO 1TB internal SSD not reading in Proxmox? Check the SATA link, kernel logs, and smartctl before blaming the drive. Here's the fix.
When Proxmox backup to NFS seems to work but actually doesn't, the GUI hides the useful error. Check the task log and journalctl for the real NFS failure.
Corrupted data on a raidz1 pool with all disks healthy? Check the scrub output, then try a zpool clear and a targeted resilver before you rebuild.
Proxmox has no native LVM-thin over iSCSI plugin, but you can set it up manually with a TrueNAS target. Here are the exact commands.
Proxmox VE ZFS benchmark with NVMe drives: a practical workflow that tests ashift, recordsize, and sync side-by-side on real hardware.
Clonezilla changes disk UUIDs, breaking Proxmox storage references. Here's the fix: update /etc/pve/storage.cfg and VM configs to match the new UUIDs.
rsync --sparse doesn't understand qcow2's internal sparse blocks, so it writes zeros as real data.
Clustered iSCSI as LVM on LVM-thin SAN works if you skip the cluster filesystem and use LVM on top. Here's the setup with TrueNAS and the gotchas.
Freezing Linux VMs and sporadic node connection issues usually come down to IOMMU grouping, ZFS ARC pressure, or a flaky NIC driver.