Search results

Great to see this!

A few stray checksum errors right after replacing a bad cable can be normal — ZFS is still verifying and repairing blocks that were previously affected. Run another zpool scrub and monitor if the CKSUM count stays stable or resets to zero. If new errors keep appearing after multiple scrubs, it...

Yeah — that behavior pretty much screams Corosync identity or network conflict, not hardware. When two nodes work fine but adding a third (or fourth) causes the whole cluster to fall apart, it’s usually one of these: 1. Duplicate nodeid or ring0_addr entries in /etc/pve/corosync.conf (worth...

@luke94x i think it was due to underpower. After you turned on the power on USB, it worked.

@verishare , you've heard the guys above saying. And I totally agree, just buy enterprise SSD. ;)

Yep, that’s actually normal — it’s how unprivileged LXC containers isolate files. The container’s root is mapped to a high UID range on the host (like 101000+), so files written from inside can look “hidden” or owned by unknown users outside. It’s a security feature, not a bug. Your fix worked...

Looks like the issue is caused by volatile EFI/TPM devices — OVMF loses the TPM state after save, so Secure Boot and attestation can’t complete. Please try recreating both efidisk0 and tpmstate0 on a persistent storage pool (not volatile:). Then enable Secure Boot again in the EFI menu. This...

Hi, glad it’s sorted. The root cause was indeed UID/GID mapping mismatch — when files were written by the host, they got ownerships outside the container’s mapped range, making them effectively invisible from inside unprivileged LXCs. Copying from within the container re-applied correct mapped...

Based on the error, it means enp1s0 is still configured as a normal interface instead of being in manual mode, so it can’t be used as a bridge port. Edit /etc/network/interfaces, remove any IP lines under enp1s0, and make it look like this: auto enp1s0 iface enp1s0 inet manual auto vmbr0 iface...

Hi, it seems like a TPM attestation issue caused by how QEMU emulates TPM 2.0 in Proxmox. Try switching your VM’s TPM device to version=v2.0,model=crb and ensure Secure Boot is enabled with Microsoft keys (not pre-enrolled-keys=1). Also make sure your guest clock syncs early via the QEMU guest...

Hi @maikverheijen , glad that it helped!

Hi, think you need to do some adjustments 1. Change bond-mode from balance-rr to 802.3ad (LACP) so it matches your Cisco trunk. 2. On the switch, make sure VLANs 20, 30, 110 are allowed on that trunk. 3. Keep only vmbr0 and set VLAN tags per VM (remove vmbr0.30 unless the host needs an IP there).

Can you try this? Try installing on your Proxmox node: apt install thermald acpid systemctl enable --now thermald acpid Reboot and check if /sys/class/thermal/ updates dynamically See if it works after.

Here are just some of my own thoughts for your reference. I would, stick with ext4 on the WD Blue HDD — ZFS adds extra RAM and CPU load with little gain on a single disk. Keep SSD for OS and active VMs, and use the HDD for logs, swap, backups, or low-priority containers. Don’t mix SSD + HDD in...

Hi, based on your description, i'm guessing that your PVE01’s SDN state got out of sync with the cluster. In this case, try removing cached configs under /var/lib/pve-sdn and restart pve-sdn to force regeneration. Also verify /etc/network/interfaces wasn’t edited manually — that can block SDN...

The error messages suggest that the guest driver can’t access the GPU’s memory space and is falling back to 0x0. Please check and try... make sure your VM uses machine: q35 with pcie=1, and that “Above 4G Decoding” and “Resizable BAR” are enabled in BIOS. Confirm vfio-pci is bound to...

Hi, this usually happens when Proxmox doesn’t load the right driver for your SFP NICs — common with Broadcom or Intel X710/XL710 adapters. Check lspci -k | grep -A3 Eth to confirm which module is used (e.g., bnx2x, i40e, or ixgbe). If none is loaded, install the latest pve-firmware or Dell’s...

Hi, this seems like a thermal driver issue with the PVE kernel — the fan control logic relies on ACPI/DPTF modules that aren’t loaded by default in Proxmox. Ubuntu and Debian use a generic kernel that includes these power-management hooks, so BIOS fan control still works there. Try booting...

hi, it looks like your SSD is handling both OS and VM I/O, which accelerates wear. Check if TRIM is active (fstrim -v /), and enable discard on LVM/VM disks to free unused blocks. Move logs, swap, and RRD data off the SSD or into tmpfs/ramdisk to cut small writes. If using ZFS, tune sync...

Based on what i see... this should work. Set your main bridge (vmbr0) to VLAN-aware and keep Internet untagged. Then create eth0.46 for your VoIP VLAN and bridge it as vmbr1. Attach your OpenWRT VM NICs to vmbr0 and vmbr1 accordingly — no VLAN setup needed inside OpenWRT. This lets Proxmox...