Error sync_wait: 34 An error occurred in another process (expected sequence number 7)

[pedro_h_nina]

Hi.
I'm getting the above error when starting a container based on debian 11 standard. I have this built in a RPi 4 with proxmox 8.1.3 on a 128Gb sd card.
Here are some details,

proxmox-ve: 8.1.0 (running kernel: 6.6.20+rpt-rpi-v8)
pve-manager: 8.1.3+pve1 (running version: 8.1.3+pve1/26764642342c55bb)
proxmox-kernel-helper: 8.1.0
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx7
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0-1
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.4
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.2-1
proxmox-backup-file-restore: 3.0.4-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: not correctly installed
pve-firewall: 5.0.3
pve-firmware: 3.8-1
pve-ha-manager: 4.0.3
pve-i18n: 3.1.4
pve-qemu-kvm: 8.1.2-4
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.10+pve1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.0-pve4

This is the error i have in the syslog:

Mar 13 10:25:23 raspberrypi systemd[1]: Started pve-container@100.service - PVE LXC Container: 100.
Mar 13 10:25:25 raspberrypi kernel: loop0: detected capacity change from 0 to 16777216
Mar 13 10:25:25 raspberrypi kernel: EXT4-fs (loop0): mounted filesystem 90b96334-827c-4a12-8888-62bacfb21848 r/w with ordered data mode. Quota mode: none.
Mar 13 10:25:25 raspberrypi NetworkManager[663]: <info> [1710325525.3698] manager: (veth100i0): new Veth device (/org/freedesktop/NetworkManager/Devices/16)
Mar 13 10:25:26 raspberrypi NetworkManager[663]: <info> [1710325526.9235] manager: (fwbr100i0): new Bridge device (/org/freedesktop/NetworkManager/Devices/17)
Mar 13 10:25:26 raspberrypi NetworkManager[663]: <info> [1710325526.9592] manager: (fwpr100p0): new Veth device (/org/freedesktop/NetworkManager/Devices/18)
Mar 13 10:25:26 raspberrypi NetworkManager[663]: <info> [1710325526.9658] manager: (fwln100i0): new Veth device (/org/freedesktop/NetworkManager/Devices/19)
Mar 13 10:25:26 raspberrypi NetworkManager[663]: <info> [1710325526.9903] device (fwpr100p0): carrier: link connected
Mar 13 10:25:26 raspberrypi NetworkManager[663]: <info> [1710325526.9909] device (fwln100i0): carrier: link connected
Mar 13 10:25:27 raspberrypi kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Mar 13 10:25:27 raspberrypi kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Mar 13 10:25:27 raspberrypi kernel: fwpr100p0: entered allmulticast mode
Mar 13 10:25:27 raspberrypi kernel: fwpr100p0: entered promiscuous mode
Mar 13 10:25:27 raspberrypi kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Mar 13 10:25:27 raspberrypi kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <info> [1710325527.0457] device (fwbr100i0): carrier: link connected
Mar 13 10:25:27 raspberrypi kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Mar 13 10:25:27 raspberrypi kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Mar 13 10:25:27 raspberrypi kernel: fwln100i0: entered allmulticast mode
Mar 13 10:25:27 raspberrypi kernel: fwln100i0: entered promiscuous mode
Mar 13 10:25:27 raspberrypi kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Mar 13 10:25:27 raspberrypi kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <warn> [1710325527.0477] device (fwbr100i0): failed to read bridge setting 'vlan_protocol'
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <warn> [1710325527.0480] device (fwbr100i0): failed to read bridge setting 'vlan_stats_enabled'
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <info> [1710325527.0504] device (fwbr100i0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <info> [1710325527.0520] device (fwbr100i0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Mar 13 10:25:27 raspberrypi dbus-daemon[575]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=663 comm="/usr/sbin/NetworkManager --no-daemon")
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <info> [1710325527.0543] device (fwbr100i0): Activation: starting connection 'fwbr100i0' (e69d8841-5b03-43b8-84f8-51673073ced9)
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <info> [1710325527.0546] device (fwbr100i0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <info> [1710325527.0555] device (fwbr100i0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <info> [1710325527.0561] device (fwbr100i0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <info> [1710325527.0567] device (fwbr100i0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Mar 13 10:25:27 raspberrypi kernel: fwbr100i0: port 2(veth100i0) entered blocking state
Mar 13 10:25:27 raspberrypi kernel: fwbr100i0: port 2(veth100i0) entered disabled state
Mar 13 10:25:27 raspberrypi kernel: veth100i0: entered allmulticast mode
Mar 13 10:25:27 raspberrypi kernel: veth100i0: entered promiscuous mode
Mar 13 10:25:27 raspberrypi systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Mar 13 10:25:27 raspberrypi dbus-daemon[575]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mar 13 10:25:27 raspberrypi systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <info> [1710325527.1205] device (fwbr100i0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <info> [1710325527.1211] device (fwbr100i0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <info> [1710325527.1221] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 13 10:25:27 raspberrypi NetworkManager[663]: <info> [1710325527.1230] device (fwbr100i0): Activation: successful, device activated.
Mar 13 10:25:27 raspberrypi kernel: eth0: renamed from vethJQd3x3
Mar 13 10:25:27 raspberrypi systemd[1]: Reloading postfix@-.service - Postfix Mail Transport Agent (instance -)...
Mar 13 10:25:27 raspberrypi postfix/postfix-script[6495]: refreshing the Postfix mail system
Mar 13 10:25:27 raspberrypi postfix/master[1207]: reload -- version 3.7.10, configuration /etc/postfix
Mar 13 10:25:27 raspberrypi systemd[1]: Reloaded postfix@-.service - Postfix Mail Transport Agent (instance -).
Mar 13 10:25:27 raspberrypi systemd[1]: Reloading postfix.service - Postfix Mail Transport Agent...
Mar 13 10:25:27 raspberrypi systemd[1]: Reloaded postfix.service - Postfix Mail Transport Agent.
Mar 13 10:25:27 raspberrypi kernel: fwbr100i0: port 2(veth100i0) entered disabled state
Mar 13 10:25:27 raspberrypi kernel: veth100i0 (unregistering): left allmulticast mode
Mar 13 10:25:27 raspberrypi kernel: veth100i0 (unregistering): left promiscuous mode
Mar 13 10:25:27 raspberrypi kernel: fwbr100i0: port 2(veth100i0) entered disabled state
Mar 13 10:25:27 raspberrypi pvedaemon[6340]: startup for container '100' failed
Mar 13 10:25:27 raspberrypi pvedaemon[2081]: <root@pam> end task UPID:raspberrypi:000018C4:0002A7B0:65F17F13:vzstart:100:root@pam: startup for container '100' failed
Mar 13 10:25:27 raspberrypi pvedaemon[2080]: unable to get PID for CT 100 (not running?)
Mar 13 10:25:27 raspberrypi pvestatd[1214]: unable to get PID for CT 100 (not running?)
Mar 13 10:25:29 raspberrypi kernel: EXT4-fs (loop0): unmounting filesystem 90b96334-827c-4a12-8888-62bacfb21848.
Mar 13 10:25:29 raspberrypi kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Mar 13 10:25:29 raspberrypi kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Mar 13 10:25:29 raspberrypi kernel: fwln100i0 (unregistering): left allmulticast mode
Mar 13 10:25:29 raspberrypi kernel: fwln100i0 (unregistering): left promiscuous mode
Mar 13 10:25:29 raspberrypi kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Mar 13 10:25:29 raspberrypi kernel: fwpr100p0 (unregistering): left allmulticast mode
Mar 13 10:25:29 raspberrypi kernel: fwpr100p0 (unregistering): left promiscuous mode
Mar 13 10:25:29 raspberrypi kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Mar 13 10:25:29 raspberrypi NetworkManager[663]: <info> [1710325529.8171] device (fwbr100i0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed')
Mar 13 10:25:29 raspberrypi NetworkManager[663]: <info> [1710325529.8180] manager: NetworkManager state is now DISCONNECTED
Mar 13 10:25:29 raspberrypi systemd[1]: pve-container@100.service: Main process exited, code=exited, status=1/FAILURE
Mar 13 10:25:29 raspberrypi systemd[1]: pve-container@100.service: Failed with result 'exit-code'.
Mar 13 10:25:29 raspberrypi systemd[1]: pve-container@100.service: Consumed 1.746s CPU time.
Mar 13 10:25:39 raspberrypi systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

I've reviewed some post around this issue but none solved my problem, so any help is much appreciated.

Cheers