pve7.1.2 tries to load Mediatek instead of Intel AX200 wifi drivers

stattik

Member
Feb 28, 2022
5
0
6
56
I'm trying to load the Intel Wi-Fi 6 AX200 wifi drivers in pve7.1.2(uname -r = 5.13.19-2-pve). It appears that the kernal thinks the wifi is Mediatek.

lspci -v output
Code:
03:00.0 Network controller: MEDIATEK Corp. Device 0608
        Subsystem: MEDIATEK Corp. Device 0608
        Flags: fast devsel, IRQ 255, IOMMU group 12
        Memory at e0300000 (64-bit, prefetchable) [disabled] [size=1M]
        Memory at e0400000 (64-bit, prefetchable) [disabled] [size=16K]
        Memory at e0404000 (64-bit, prefetchable) [disabled] [size=4K]
        Capabilities: [80] Express Endpoint, MSI 00
        Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
        Capabilities: [f8] Power Management version 3
        Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
        Capabilities: [108] Latency Tolerance Reporting
        Capabilities: [110] L1 PM Substates
        Capabilities: [200] Advanced Error Reporting

Here are the relevant dmsg entries:
Code:
[    3.428591] bluetooth hci0: Direct firmware load for mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin failed with error -2
[    3.430189] Bluetooth: hci0: Failed to load firmware file (-2)
[   13.673151] Bluetooth: hci0: Execution of wmt command timed out
[   13.673171] Bluetooth: hci0: Failed to send wmt func ctrl (-110)

[    3.061131] usb 5-4: new high-speed USB device number 4 using xhci_hcd
[    3.212947] usb 5-4: New USB device found, idVendor=0e8d, idProduct=0608, bcdDevice= 1.00
[    3.213351] usb 5-4: New USB device strings: Mfr=5, Product=6, SerialNumber=7
[    3.213731] usb 5-4: Product: Wireless_Device
[    3.214099] usb 5-4: Manufacturer: MediaTek Inc.
[    3.214457] usb 5-4: SerialNumber: 000000000
[   15.721253] usb 5-4: Failed to suspend device, error -110

I've followed the instructions from here in an attempt to resolve this:
https://forum.proxmox.com/threads/nuc-drivers-for-intel-ac-9462-wireless.42427/

- I downloaded the firmware-iwlwifi package from buster-backports(bullseye-backports didn't have it) and copied the files to the proper directories.
- I ran 'update-initramfs -k all -u' and rebooted but the kernal still tries the load the Mediatek driver.

Any help would be greatly appreciated.
 
Thanks for the quick reply. No, it's a Minisforum HM80. Your post got me thinking. I booted a Debian live CD and it showed the same behavior. I then installed Debian 11.2 and maunally installed the Intel firmware but there was no change. I installed Windows 10 and the wifi and bt adapters were the only items that had no drivers. I installed the provided Intel drivers but it didn't help. Then I dug a little deeper and discovered that Minisforum released the H80 with the Intel card but sometime after, switched to the Mediatek RZ608 card and never told anyone. Their support page still only shows the Intel drivers.

So I found this page: https://askubuntu.com/questions/1380400/no-wifi-adapter-found-on-ubuntu-20-04-3-lts

It's very similar to yours. It provides workaround to load the module but it's for Ubuntu and Proxmox doesn't have the /bus/pci/drivers/mt7921e directory.

Since the drivers aren't in the kernel yet, I've been trying to stop the drivers from loading. I've updated /etc/modprobe.d/pve-blacklist.conf

Code:
blacklist m7921e
blacklist mt76
blacklist mt7601u   
blacklist mt7922

.. and while the drivers aren't showing up in lsmod, I get the same errors as before in "lspci -v" and dmesg. I also get the same startup delay and shutdown/reboot hangs. Any idea how to stop that module from loading?
 
I also get the same startup delay and shutdown/reboot hangs
you didn't mention any startup delays/hangs before, can you post the logs from that?

Any idea how to stop that module from loading?
can you maybe disable the device in the bios completely?
my guess is that the driver is only for the wifi part and the errors are for the bluetooth module (via usb) that is using a different driver?
 
Sorry about that. It was one of the first things I looked at but forgot to mention.


Here the full dmesg. The delay happens after the 15 second mark.

https://pastebin.com/DDWg8269


This is the partial shutdown log. The full log is also available at the same pastebin link.
Code:
Mar 01 12:58:23 pve02 systemd[1]: Stopping D-Bus System Message Bus...
Mar 01 12:58:23 pve02 systemd[1]: Stopping Permit User Sessions...
Mar 01 12:58:23 pve02 systemd[1]: systemd-user-sessions.service: Succeeded.
Mar 01 12:58:23 pve02 systemd[1]: Stopped Permit User Sessions.
Mar 01 12:58:23 pve02 systemd[1]: dbus.service: Succeeded.
Mar 01 12:58:23 pve02 systemd[1]: Stopped D-Bus System Message Bus.
Mar 01 12:58:23 pve02 systemd[1]: systemd-logind.service: Succeeded.
Mar 01 12:58:23 pve02 systemd[1]: Stopped User Login Management.
Mar 01 12:58:24 pve02 systemd[1]: pve-guests.service: Succeeded.
Mar 01 12:58:24 pve02 systemd[1]: Stopped PVE guests.
Mar 01 12:58:24 pve02 systemd[1]: Stopping Proxmox VE firewall...
Mar 01 12:58:24 pve02 systemd[1]: Stopping PVE Local HA Resource Manager Daemon...
Mar 01 12:58:24 pve02 systemd[1]: Stopping Proxmox VE LXC Syscall Daemon...
Mar 01 12:58:24 pve02 systemd[1]: Stopping PVE Status Daemon...
Mar 01 12:58:24 pve02 systemd[1]: Stopping PVE SPICE Proxy Server...
Mar 01 12:58:24 pve02 systemd[1]: pve-lxc-syscalld.service: Succeeded.
Mar 01 12:58:24 pve02 systemd[1]: Stopped Proxmox VE LXC Syscall Daemon.
Mar 01 12:58:24 pve02 systemd[1]: pvescheduler.service: Succeeded.
Mar 01 12:58:24 pve02 systemd[1]: Stopped Proxmox VE scheduler.
Mar 01 12:58:24 pve02 systemd[1]: pvescheduler.service: Consumed 13.582s CPU time.
Mar 01 12:58:25 pve02 systemd[1]: spiceproxy.service: Succeeded.
Mar 01 12:58:25 pve02 systemd[1]: Stopped PVE SPICE Proxy Server.
Mar 01 12:58:25 pve02 systemd[1]: spiceproxy.service: Consumed 4.793s CPU time.
Mar 01 12:58:25 pve02 systemd[1]: pvestatd.service: Succeeded.
Mar 01 12:58:25 pve02 systemd[1]: Stopped PVE Status Daemon.
Mar 01 12:58:25 pve02 systemd[1]: pvestatd.service: Consumed 4min 50.964s CPU time.
Mar 01 12:58:25 pve02 systemd[1]: pve-firewall.service: Succeeded.
Mar 01 12:58:25 pve02 systemd[1]: Stopped Proxmox VE firewall.
Mar 01 12:58:25 pve02 systemd[1]: pve-firewall.service: Consumed 5min 19.160s CPU time.
Mar 01 12:58:25 pve02 systemd[1]: Stopping Proxmox VE firewall logger...
Mar 01 12:58:25 pve02 systemd[1]: pve-ha-lrm.service: Succeeded.
Mar 01 12:58:25 pve02 systemd[1]: Stopped PVE Local HA Resource Manager Daemon.
Mar 01 12:58:25 pve02 systemd[1]: pve-ha-lrm.service: Consumed 18.015s CPU time.
Mar 01 12:58:25 pve02 systemd[1]: Stopping LXC Container Initialization and Autoboot Code...
Mar 01 12:58:25 pve02 systemd[1]: Stopping PVE Cluster HA Resource Manager Daemon...
Mar 01 12:58:25 pve02 systemd[1]: Stopping PVE API Proxy Server...
Mar 01 12:58:25 pve02 systemd[1]: Stopping PVE Qemu Event Daemon...
Mar 01 12:58:25 pve02 systemd[1]: qmeventd.service: Succeeded.
Mar 01 12:58:25 pve02 systemd[1]: Stopped PVE Qemu Event Daemon.
Mar 01 12:58:25 pve02 systemd[1]: qmeventd.service: Consumed 1.759s CPU time.
Mar 01 12:58:25 pve02 systemd[1]: lxc.service: Control process exited, code=exited, status=1/FAILURE
Mar 01 12:58:25 pve02 systemd[1]: lxc.service: Failed with result 'exit-code'.
Mar 01 12:58:25 pve02 systemd[1]: Stopped LXC Container Initialization and Autoboot Code.
Mar 01 12:58:25 pve02 systemd[1]: Stopping LXC network bridge setup...
Mar 01 12:58:25 pve02 systemd[1]: Stopping FUSE filesystem for LXC...
Mar 01 12:58:25 pve02 systemd[1]: var-lib-lxcfs.mount: Succeeded.
Mar 01 12:58:25 pve02 systemd[1]: Unmounted /var/lib/lxcfs.
Mar 01 12:58:25 pve02 systemd[1]: lxcfs.service: Succeeded.
Mar 01 12:58:25 pve02 systemd[1]: Stopped FUSE filesystem for LXC.
Mar 01 12:58:25 pve02 systemd[1]: lxc-net.service: Succeeded.
Mar 01 12:58:25 pve02 systemd[1]: Stopped LXC network bridge setup.
Mar 01 12:58:26 pve02 systemd[1]: pvefw-logger.service: Succeeded.
Mar 01 12:58:26 pve02 systemd[1]: Stopped Proxmox VE firewall logger.
Mar 01 12:58:26 pve02 systemd[1]: pvefw-logger.service: Consumed 12.215s CPU time.
Mar 01 12:58:27 pve02 systemd[1]: pve-ha-crm.service: Succeeded.
Mar 01 12:58:27 pve02 systemd[1]: Stopped PVE Cluster HA Resource Manager Daemon.
Mar 01 12:58:27 pve02 systemd[1]: pve-ha-crm.service: Consumed 10.627s CPU time.
Mar 01 12:58:27 pve02 systemd[1]: Stopping System Logging Service...
Mar 01 12:58:27 pve02 systemd[1]: Stopping Proxmox VE watchdog multiplexer...
Mar 01 12:58:27 pve02 systemd[1]: watchdog-mux.service: Succeeded.
Mar 01 12:58:27 pve02 systemd[1]: Stopped Proxmox VE watchdog multiplexer.
Mar 01 12:58:27 pve02 systemd[1]: watchdog-mux.service: Consumed 3.255s CPU time.
Mar 01 12:58:27 pve02 systemd[1]: rsyslog.service: Succeeded.
Mar 01 12:58:27 pve02 systemd[1]: Stopped System Logging Service.
Mar 01 12:58:27 pve02 systemd[1]: pveproxy.service: Succeeded.
Mar 01 12:58:27 pve02 systemd[1]: Stopped PVE API Proxy Server.
Mar 01 12:58:27 pve02 systemd[1]: pveproxy.service: Consumed 3min 55.050s CPU time.
Mar 01 12:58:27 pve02 systemd[1]: Stopped target PVE Storage Target.
Mar 01 12:58:27 pve02 systemd[1]: Stopped target ceph target allowing to start/stop all ceph*@.service instances at once.
Mar 01 12:58:27 pve02 systemd[1]: Stopped target ceph target allowing to start/stop all ceph-fuse@.service instances at once.
Mar 01 12:58:27 pve02 systemd[1]: Stopping PVE API Daemon...
Mar 01 12:58:27 pve02 systemd[1]: Stopping OpenBSD Secure Shell server...
Mar 01 12:58:27 pve02 systemd[1]: ssh.service: Succeeded.
Mar 01 12:58:27 pve02 systemd[1]: Stopped OpenBSD Secure Shell server.
Mar 01 12:58:29 pve02 systemd[1]: pvedaemon.service: Succeeded.
Mar 01 12:58:29 pve02 systemd[1]: Stopped PVE API Daemon.
Mar 01 12:58:29 pve02 systemd[1]: pvedaemon.service: Consumed 3min 54.550s CPU time.
Mar 01 12:58:29 pve02 systemd[1]: Stopping The Proxmox VE cluster filesystem...
Mar 01 12:58:29 pve02 systemd[1]: etc-pve.mount: Succeeded.
Mar 01 12:58:29 pve02 systemd[1]: Unmounted /etc/pve.
Mar 01 12:58:30 pve02 systemd[1]: pve-cluster.service: Succeeded.
Mar 01 12:58:30 pve02 systemd[1]: Stopped The Proxmox VE cluster filesystem.
Mar 01 12:58:30 pve02 systemd[1]: pve-cluster.service: Consumed 1min 42.140s CPU time.
Mar 01 12:58:30 pve02 systemd[1]: Stopping LSB: start or stop rrdcached...
Mar 01 12:58:31 pve02 systemd[1]: rrdcached.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped LSB: start or stop rrdcached.
Mar 01 12:58:31 pve02 systemd[1]: rrdcached.service: Consumed 26.788s CPU time.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target Remote File Systems.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target System Time Synchronized.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target System Time Set.
Mar 01 12:58:31 pve02 systemd[1]: Unmounting /mnt/media...
Mar 01 12:58:31 pve02 systemd[1]: Unmounting /mnt/pve/vm_backup...
Mar 01 12:58:31 pve02 systemd[1]: Stopping chrony, an NTP client/server...
Mar 01 12:58:31 pve02 systemd[1]: chrony.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped chrony, an NTP client/server.
Mar 01 12:58:31 pve02 systemd[1]: mnt-media.mount: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Unmounted /mnt/media.
Mar 01 12:58:31 pve02 systemd[1]: mnt-pve-vm_backup.mount: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Unmounted /mnt/pve/vm_backup.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target Basic System.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target Paths.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target Remote File Systems (Pre).
Mar 01 12:58:31 pve02 systemd[1]: Stopped target NFS client services.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target Slices.
Mar 01 12:58:31 pve02 systemd[1]: Removed slice User and Session Slice.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target Sockets.
Mar 01 12:58:31 pve02 systemd[1]: dbus.socket: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Closed D-Bus System Message Bus Socket.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target System Initialization.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target Local Encrypted Volumes.
Mar 01 12:58:31 pve02 systemd[1]: systemd-ask-password-console.path: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
Mar 01 12:58:31 pve02 systemd[1]: systemd-ask-password-wall.path: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target Swap.
Mar 01 12:58:31 pve02 systemd[1]: syslog.socket: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Closed Syslog Socket.
Mar 01 12:58:31 pve02 systemd[1]: Stopping Login to default iSCSI targets...
Mar 01 12:58:31 pve02 systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:acpi_video0...
Mar 01 12:58:31 pve02 systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
Mar 01 12:58:31 pve02 systemd[1]: systemd-backlight@backlight:acpi_video0.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Mar 01 12:58:31 pve02 systemd[1]: Removed slice system-systemd\x2dbacklight.slice.
Mar 01 12:58:31 pve02 systemd[1]: systemd-update-utmp.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Mar 01 12:58:31 pve02 systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Create Volatile Files and Directories.
Mar 01 12:58:31 pve02 systemd[1]: open-iscsi.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Login to default iSCSI targets.
Mar 01 12:58:31 pve02 systemd[1]: Stopping iSCSI initiator daemon (iscsid)...
Mar 01 12:58:31 pve02 systemd[1]: iscsid.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped iSCSI initiator daemon (iscsid).
Mar 01 12:58:31 pve02 systemd[1]: iscsid.service: Consumed 2.446s CPU time.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target Network is Online.
Mar 01 12:58:31 pve02 systemd[1]: Stopping Network initialization...
Mar 01 12:58:31 pve02 systemd[1]: networking.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Network initialization.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target Local File Systems.
Mar 01 12:58:31 pve02 systemd[1]: Unmounting /boot/efi...
Mar 01 12:58:31 pve02 systemd[1]: systemd-sysctl.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Apply Kernel Variables.
Mar 01 12:58:31 pve02 systemd[1]: systemd-modules-load.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Load Kernel Modules.
Mar 01 12:58:31 pve02 systemd[1]: boot-efi.mount: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Unmounted /boot/efi.
Mar 01 12:58:31 pve02 systemd[1]: Reached target Unmount All Filesystems.
Mar 01 12:58:31 pve02 systemd[1]: systemd-fsck@dev-disk-by\x2duuid-AA2B\x2d4681.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped File System Check on /dev/disk/by-uuid/AA2B-4681.
Mar 01 12:58:31 pve02 systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Mar 01 12:58:31 pve02 systemd[1]: Stopped target Local File Systems (Pre).
Mar 01 12:58:31 pve02 systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Mar 01 12:58:31 pve02 systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Create Static Device Nodes in /dev.
Mar 01 12:58:31 pve02 systemd[1]: systemd-sysusers.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Create System Users.
Mar 01 12:58:31 pve02 systemd[1]: systemd-remount-fs.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Remount Root and Kernel File Systems.
Mar 01 12:58:31 pve02 systemd[1]: lvm2-monitor.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Mar 01 12:58:31 pve02 systemd[1]: Reached target Shutdown.
Mar 01 12:58:31 pve02 systemd[1]: Reached target Final Step.
Mar 01 12:58:31 pve02 systemd[1]: systemd-reboot.service: Succeeded.
Mar 01 12:58:31 pve02 systemd[1]: Finished Reboot.
Mar 01 12:58:31 pve02 systemd[1]: Reached target Reboot.
Mar 01 12:58:31 pve02 systemd[1]: Shutting down.
Mar 01 12:58:31 pve02 systemd[1]: Using hardware watchdog 'Software Watchdog', version 0, device /dev/watchdog
Mar 01 12:58:31 pve02 systemd[1]: Set hardware watchdog to 10min.
Mar 01 12:58:31 pve02 systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 01 12:58:31 pve02 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Mar 01 12:58:31 pve02 systemd-journald[415]: Journal stopped

This is what show up on the console during a reboot.
Code:
[60871.406864] watchdog: watchdog0: watchdog did not stop!
[60871.460121] systemd-shutdown[1]: Syncing filesystems and block devices.
[60871.460792] systemd-shutdown[1]: Sending SIGTERM from PID1 (system-shutdow).
[60871.480993] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[60871.483342] systemd-shutdown[1]: Using hardware watchdog 'Software Watchdog', version 0, device /dev/watchdog
[60871.484049] systemd-shutdown[1]: Unmounting file systems.
[60871.485225] [143443] "Remounting '/' read-only in with options 'ssd, space_cache, ubvolid=5,subvol=/'.
[60871.489502] BTRFS info (device nvme0n1p3): disk space caching is enabled
[60871.448137] systemd-shutdown[1]: All filesystems unmounted.
[60871.498183] systemd-shutdown[1]: Deactivating swaps.
[60871.498263] systemd-shutdown[1]: All swaps deactivated.
[60871.498291] systemd-shutdown[1]: Detaching loop devices.
[60871.499115] systemd-shutdown[1]: All loop devices detached.
[60871.499149] systemd-shutdown[1]: Stopping MD devices.
[60871.499282] systemd-shutdown[1]: All MD devices stopped.
[60871.499321] systemd-shutdown[1]: Detaching all DM devices.
[60871.499437] systemd-shutdown[1]: All DM devices detached.
[60871.499477] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices, ND devices and DM devices detached.
[60871.500341] systemd-shutdown[1]: Syncing filsystems and block devices.
[60871.500507] systemd-shutdown[1]: Rebooting
[60871.500537] kvm: exiting hardware virtualization
_

Let me know if you need other logs.

I don't see anything in the BIOS that would disable that device. Assuming it's not baked into the motherboard, I may be able to take the device apart and remove it.

Thanks again.
 
Last edited:
thanks, but i don't see anything out of the ordinary aside from that one line in the boot....
I don't see anything in the BIOS that would disable that device. Assuming it's not baked into the motherboard, I may be able to take the device apart and remove it.
in that case, removing it (if possible) is probably the best course of action
note that the system otherwise seems to work, only the boot/shutdown is delayed. but that should make no further problem.
 
Removing the card doesn't stop the delays or hanging on restarts but I noticed this in the journal around the time of the delay:

Code:
Mar 02 18:32:19 pve02 systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0...
Mar 02 18:32:19 pve02 systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Mar 02 18:32:48 pve02 systemd[1]: systemd-fsckd.service: Succeeded.
Mar 02 18:33:18 pve02 systemd-udevd[438]: 0000:05:00.7: Worker [467] processing SEQNUM=3580 is taking a long time
Mar 02 18:34:18 pve02 systemd[1]: systemd-udev-settle.service: Main process exited, code=exited, status=1/FAILURE
Mar 02 18:34:18 pve02 systemd[1]: systemd-udev-settle.service: Failed with result 'exit-code'.
Mar 02 18:34:18 pve02 systemd[1]: Failed to start Wait for udev To Complete Device Initialization.
Mar 02 18:34:18 pve02 systemd[1]: Dependency failed for Import ZFS pools by cache file.
Mar 02 18:34:18 pve02 systemd[1]: zfs-import-cache.service: Job zfs-import-cache.service/start failed with result 'dependency'.
Mar 02 18:34:18 pve02 systemd[1]: Dependency failed for Import ZFS pools by device scanning.
Mar 02 18:34:18 pve02 systemd[1]: zfs-import-scan.service: Job zfs-import-scan.service/start failed with result 'dependency'.
Mar 02 18:34:18 pve02 systemd[1]: systemd-udev-settle.service: Consumed 2.858s CPU time.
Mar 02 18:34:18 pve02 systemd[1]: Reached target ZFS pool import target.
Mar 02 18:34:18 pve02 systemd[1]: Starting Mount ZFS filesystems...
Mar 02 18:34:18 pve02 systemd[1]: Starting Wait for ZFS Volume (zvol) links in /dev...
Mar 02 18:34:18 pve02 systemd[1]: Finished Mount ZFS filesystems.
Mar 02 18:34:18 pve02 systemd[1]: Reached target Local File Systems.
Mar 02 18:34:18 pve02 zvol_wait[606]: No zvols found, nothing to do.
Mar 02 18:34:18 pve02 systemd[1]: Starting Load AppArmor profiles...
Mar 02 18:34:18 pve02 systemd[1]: Starting Set console font and keymap...

I included the complete journal in the patebin address.
https://pastebin.com/DDWg8269
 
ok i found the bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956519
which seemed to be fixed with ubuntus kernel 5.13.0-28.31 which corresponds with our kernel version 5.13.19-8.
you have 5.13.19-2 AFAICS so an upgrade would be good (i think those versions (or newer) are only available on pve-no-subscription and pve-test, not on enterprise yet)
 
pve-no-subscription is 5.13.19-4 and pvetest is 5.13.19-5. Both fixed the startup delay and reboot/shutdown freezes. Thanks alot for all your time and assistance!
 
pve-no-subscription is 5.13.19-4 and pvetest is 5.13.19-5. Both fixed the startup delay and reboot/shutdown freezes. Thanks alot for all your time and assistance!
ah yes, i confused the package version (5.13.19-4 on no subscription) with the kernel version (which is 5.13.19-9)
great that it fixed the issue :)