since upgrading to Kernel 5.15.35 I have following warning (and a second similar one) during boot:
May 15 17:04:57 pve-2 kernel: WARNING: CPU: 0 PID: 1228 at include/net/netfilter/nf_conntrack.h:175 __ovs_ct_lookup+0x907/0xa40 [openvswitch]
May 15 17:04:57 pve-2 kernel: Modules linked...
After upgrading to ifupdown to ifupdown2 (as part of PVE7), I have a problem to configure NetFlow with ovs_extra in /etc/network/interfaces. Following statement worked in ifupdown:
ovs_extra --id=@nf create NetFlow targets=\"10.0.20.20:9995\" active_timeout=60 -- set Bridge vmbr0 netflow=@nf
I did a fresh reinstall of PVE on a separate disk and migrated the VMs. I kept the former zfs-pool as storage.
With respect to your question see post #2 of this threat: https://forum.proxmox.com/threads/cant-boot-after-upgrade.32655/#post-160924
One more question. I have recognized that several ZFS packages have been updated (see history.log attached above; e.g. libzfs2:amd64 (0.6.5.8-pve13~bpo80, 0.6.5.8-pve14~bpo80) and then the problems started. But Grub is still from November 30, 2016. Might this be the reason for Grub not...
After "insmod normal" I get the "error: unknown filesystem" again.
I still do not understand why I can't access the zfs filesystem from Grub - even Grub from Proxmox Install CD doesn't work. I assume wiping the MTB wouldn't help. Two possibilities:
a) install Grub on MicroSD and load...
There is no result, however if you convert 1d540bdfe4ab7feb (hex) to 2113327181385662443 (dec):
root@pve:~# blkid -U 1d540bdfe4ab7feb
root@pve:~# blkid -U 2113327181385662443
root@pve:~# lsblk -o NAME,FSTYPE,LABEL,UUID /dev/sda3 /dev/sdb3
NAME FSTYPE LABEL UUID
"update-grub" and "grub-install /dev/sda" (see attachment) went fine. Key question is still why:
a) Grub bootloader on /dev/sda can't load subsequent modules from /dev/sda3
b) Grub on Proxmox 4.4 install disk can't access kernel/initrd from zfs pool on /dev/sda3.
Thanks for your support!