I eventually figured it out, it was due to ntopng package and nothing to do with pfSense or Proxmox. I did find out that disabling pcie power saving can help:
add pcie_port_pm=off pcie_aspm.policy=performance to GRUB_CMDLINE_LINUX_DEFAULT in...
No sure how to interpret the first two, but I don't see any obvious errors using dmesg (output too long to post) and it does not seem like packets are going over iptables. Here is the output:
ethtool -g eno4
Ring parameters for eno4:
Pre-set...
Hello,
I recently did an in place upgrade to PVE 9, everything seems to be working fine but now the network card seems to be slow. I run pfSense in a VM with a couple of network interfaces passed through. I have not made any changes to the VM...
I moved a lot of data off the pool and used zfs rewrite to rewrite all the files hoping it would recover the reported capacity but none of it worked. The only interesting thing was that when I copied files to another pool the reported size of...
i have now re-written or moved nearly 100% of the data on pool with the exception of VM disks and so far no difference in reported capacity. Does anyone have any additional ideas? Would exporting and re-importing the pool help?
Here is a listing of all the properties, I had added a quota on a subdirectory but have since removed it to see if it was causing issues:
zpool get all S
zfs get all S
I am incrementally using zfs rewrite to rewrite all the files but I don't see any change so far in the capacity. I even moved some files off the pool but it made no difference to the total reported capacity.
Does anyone have any other suggestions?
I had a zpool with 4x8TB SATA drives in a RAIDz2 with a total capacity of 16TB. I updates to PVE 9 and ZFS to 2.3 and attached 2 additional drives to the zpool using:
zpool upgrade <poolname>
zpool attach <poolname> raidz2-0...
well, proxmox-boot-tool here thinks it's driving systemd-boot, and so does the UEFI setup. You could re-enable it (install the tooling, then make sure it boots the proper kernel). But I'd suggest going back with GRUB if you don't need...
yeah, re-init with grub using proxmox-boot-tool, as I suggested, that should do it. Or switch to UEFI entry 0007 (cue the James Bond theme..), possibly with efibootmgr, but more likely in your UEFI/BIOS setup.
Success! These are the steps:
umount /boot/efi
proxmox-boot-tool init /dev/disk/by-uuid/AED9-4562 grub
proxmox-boot-tool refresh
mount -a
reboot
After that the system rebooted with the updates showing kernel: Linux 6.17.4-2-pve .
Thanks for...
I don't have ZFS on the boot drive.
I cleared all warnings from pve8to9 prior to apt update && apt dist-upgrade .
I don't have bootctl command available.
# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
AED9-4562 is configured with: uefi (versions: 5.15.158-2-pve, 6.8.12-18-pve, grubx64.efi)
Tried the following so far:
proxmox-boot-tool kernel unpin
proxmox-boot-tool refresh
and also:
apt install --reinstall proxmox-kernel-6.17
reboot
made no difference.