rpc.mountd v4.2 client detached: it’s usually normal, here’s when to worry
rpc.mountd v4.2 client detached shows up on Proxmox NFS mounts all the time. It's usually just a reconnect. Here's how to tell if it's a real problem.
Homelab & Vietnam
184 posts
rpc.mountd v4.2 client detached shows up on Proxmox NFS mounts all the time. It's usually just a reconnect. Here's how to tell if it's a real problem.
Tailscale in an LXC container on Proxmox works, but you need to get the TUN device and capabilities right.
etckeeper on Proxmox works fine if you exclude /etc/pve and hook the right git commands. Here's the setup that doesn't spam cluster commits.
Proxmox backup size vs bootsize: the backup reads allocated blocks on the host, so thin-provisioned disks stay small but a full guest filesystem inflates
Proxmox error (500) adding NFS storage usually means a bad export path, a missing package, or a permissions problem.
New router, PVE host can't connect to network at all? Check the bridge in /etc/network/interfaces, then set a static IP or DHCP.
pve-dbus-vmstate@VMID.service is a generated systemd unit that bridges QEMU VM state changes to D-Bus. Here's when it starts and how to inspect it.
Proxmox snapshots grab every disk in a VM. Here's how to snapshot just one drive using ZFS send, LVM thin snapshots, or backup splitting.
Proxmox HA load balancing isn't dynamic. The CRS places resources but never rebalances them.
Error '0' occured while receiving the doument means the pve user lacks Datastore.Allocate. Assign the role or privilege and the upload works.