Proxmox Server hat nach Neustart keine Verbindung mehr zum Netzwerk

Allgemein & News
1

Hallo,
mein Proxmox-Server lief mit einer HA VM monatelang auf einem alten Thinkpad T450 wunderbar. Vor ein paar Tagen haben dann alle Zigbee-Geräte nicht mehr funktioniert. Ich konnte den Fehler nicht finden und habe den Proxmox-Server neugestartet. Leider war dies ein Fehler, denn ich komme nicht mehr auf die Prooxmox-GUI. Auf dem Proxmox-Server führt ping zu Host unreachable.

Ich habe im Internet dazu rechierchiert und bereits gelesen, dass dies schonmal vorkommt. Leider brauche ich bei der Fehlerbehebung weitere Unterstützung. Ich habe zwar sporadisch Befehle aus meiner „Literaturrecherche“ ausprobiert, aber ich kenne mich nicht gut genug damit aus, um es wieder zum Laufen zu bringen. Einige Befehle werden bei mir auch gar nicht gefunden.

Ich wäre sehr dankbar, wenn mir jemand den ersten Schritt, den ich gehen sollte erklären könnte. Ich stelle die Terminalausgaben dann hier ein.

Vielen Dank!

2

IP-Adresse passt noch? Schau mal in deinen Router ob der Proxmox noch unter der gewohnten IP da ist?
Oder am Proxmox auf der konsole ip a + Enter!

4

Hallo ihr beiden,
danke schonmal für die Antworten.
Mittlerweile komme ich wieder aufs Webinterface, aber ich habe keine Ahnung wieso.
Ich habe meinen Proxmox-Stick in den Server gesteckt und hochgefahren. Eigentlich wollte ich nur die Terminalausgabe der von euch vorgeschlagenen Befehle auf Stick kopieren, damit ich sie euch zeigen kann.
Es wurde dann vom Stick gebootet und ich habe die Installationsanweisungen durchgeklickt, bis zu dem Zeitpunkt wo die Netzwerkeinstellungen angezeigt wurde. Es erschien hier ein grüner Punkt, also war die Netzwerkverbindung shcenbar ok. Ich habe neugestartet und hatte wieder Zugriff auf das GUI.

Mir ist das Ganze aber noch nicht geheuer. Lasst uns bitte schauen, wo das Problem lag, damit es nicht nochmals auftritt.

Die IP hatte ich statisch vergeben. In den Routereinstellungen wurde noch die ritige IP angezeigt.

@anon70541084
ob sie plötzlich oder noch nie funktioniert haben weiß ich nicht. sudo funktioniert zb nicht. syslog auch nicht. Es handelt sich bereits um eine Austauschfestplatte, nicht mehr um das Original.

ip a
Linux pve 6.8.12-4-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-4 (2024-11-06T15:04Z) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Sep  8 09:52:39 CEST 2025 on tty1
root@pve:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 50:7b:9d:5d:3d:e5 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether dc:53:60:6c:9a:d5 brd ff:ff:ff:ff:ff:ff
4: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN group default qlen 500
    link/none 
    inet 100.89.167.11/32 scope global tailscale0
       valid_lft forever preferred_lft forever
    inet6 fd7a:115c:a1e0::6501:a70b/128 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::9297:a273:56a3:8e9e/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 50:7b:9d:5d:3d:e5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.88/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::527b:9dff:fe5d:3de5/64 scope link 
       valid_lft forever preferred_lft forever
6: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether c6:29:4b:e5:3f:e6 brd ff:ff:ff:ff:ff:ff

Bei dmesg ist alles gelb außer diese beiden Zeilen (rot). Brauchst du den gesamten Output?

dmseg

5.929257] spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash
[    7.872372] nouveau 0000:04:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ]

journalctl

root@pve:~# journalctl -p err -p warning --since 2025-09-05 --until 2025-09-07 |cat
Sep 05 09:00:29 pve pvestatd[1052]: could not populate metric data cache: mkstemp "/run/pve/metrics.tmp_XXXXXX" failed: ENOENT: No such file or directory
Sep 05 09:00:30 pve systemd[1]: lxcfs.service: Failed with result 'exit-code'.
Sep 05 09:00:32 pve pveproxy[2758777]: got inotify poll request in wrong process - disabling inotify
Sep 05 09:00:45 pve systemd[1]: pve-cluster.service: State 'stop-sigterm' timed out. Killing.
Sep 05 09:00:45 pve systemd[1]: pve-cluster.service: Main process exited, code=killed, status=9/KILL
Sep 05 09:00:45 pve systemd[1]: pve-cluster.service: Failed with result 'timeout'.
-- Boot f420154a0cf34f29b3927958102e9f4b --
Sep 05 09:04:28 pve kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Sep 05 09:04:28 pve kernel: pnp 00:00: disabling [mem 0x000c0000-0x000c3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 09:04:28 pve kernel: pnp 00:00: disabling [mem 0x000c4000-0x000c7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 09:04:28 pve kernel: pnp 00:00: disabling [mem 0x000c8000-0x000cbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 09:04:28 pve kernel: pnp 00:00: disabling [mem 0x000cc000-0x000cffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 09:04:28 pve kernel: pnp 00:00: disabling [mem 0x000d0000-0x000d3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 09:04:28 pve kernel: pnp 00:00: disabling [mem 0x000d4000-0x000d7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 09:04:28 pve kernel: pnp 00:00: disabling [mem 0x000d8000-0x000dbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 09:04:28 pve kernel: pnp 00:00: disabling [mem 0x000dc000-0x000dffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 09:04:28 pve kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
Sep 05 09:04:28 pve kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Sep 05 09:04:28 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Sep 05 09:04:28 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Sep 05 09:04:28 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Sep 05 09:04:28 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Sep 05 09:04:28 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Sep 05 09:04:28 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Sep 05 09:04:28 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Sep 05 09:04:28 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Sep 05 09:04:28 pve kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 05 09:04:28 pve kernel: ata1.00: supports DRM functions and may not be fully accessible
Sep 05 09:04:28 pve kernel: ata1.00: supports DRM functions and may not be fully accessible
Sep 05 09:04:28 pve kernel: spl: loading out-of-tree module taints kernel.
Sep 05 09:04:28 pve kernel: zfs: module license 'CDDL' taints kernel.
Sep 05 09:04:28 pve kernel: Disabling lock debugging due to kernel taint
Sep 05 09:04:28 pve kernel: zfs: module license taints kernel.
Sep 05 09:04:29 pve lvm[433]: PV /dev/sda3 online, VG pve is complete.
Sep 05 09:04:29 pve lvm[433]: VG pve finished
Sep 05 09:04:29 pve lvm[485]: PV /dev/sdb3 not used.
Sep 05 09:04:29 pve kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash
Sep 05 09:04:29 pve kernel: spi-nor: probe of spi0.0 failed with error -22
Sep 05 09:04:29 pve kernel: at24 0-0050: supply vcc not found, using dummy regulator
Sep 05 09:04:30 pve kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Sep 05 09:04:30 pve kernel: at24 0-0051: supply vcc not found, using dummy regulator
Sep 05 09:04:30 pve kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Sep 05 09:04:31 pve kernel: ACPI Warning: \_SB.PCI0.PEG.VID._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20230628/nsarguments-61)
Sep 05 09:04:32 pve kernel: bluetooth hci0: Direct firmware load for intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq failed with error -2
Sep 05 09:04:32 pve kernel: Bluetooth: hci0: failed to open Intel firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq (-2)
Sep 05 09:04:32 pve kernel: bluetooth hci0: Direct firmware load for intel/ibt-hw-37.8.bseq failed with error -2
Sep 05 09:04:32 pve kernel: Bluetooth: hci0: failed to open default fw file: intel/ibt-hw-37.8.bseq
Sep 05 09:04:32 pve kernel: nouveau 0000:04:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ]
Sep 05 09:04:32 pve kernel: nouveau 0000:04:00.0: [drm] No compatible format found
Sep 05 09:04:43 pve kernel: kvm_intel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
Sep 05 12:36:27 pve systemd[1]: lxcfs.service: Failed with result 'exit-code'.
-- Boot 34cae6b5fdd7455581ae776c212954db --
Sep 05 12:38:51 pve kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Sep 05 12:38:51 pve kernel: pnp 00:00: disabling [mem 0x000c0000-0x000c3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 12:38:51 pve kernel: pnp 00:00: disabling [mem 0x000c4000-0x000c7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 12:38:51 pve kernel: pnp 00:00: disabling [mem 0x000c8000-0x000cbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 12:38:51 pve kernel: pnp 00:00: disabling [mem 0x000cc000-0x000cffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 12:38:51 pve kernel: pnp 00:00: disabling [mem 0x000d0000-0x000d3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 12:38:51 pve kernel: pnp 00:00: disabling [mem 0x000d4000-0x000d7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 12:38:51 pve kernel: pnp 00:00: disabling [mem 0x000d8000-0x000dbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 12:38:51 pve kernel: pnp 00:00: disabling [mem 0x000dc000-0x000dffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 12:38:51 pve kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
Sep 05 12:38:51 pve kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Sep 05 12:38:51 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Sep 05 12:38:51 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Sep 05 12:38:51 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Sep 05 12:38:51 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Sep 05 12:38:51 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Sep 05 12:38:51 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Sep 05 12:38:51 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Sep 05 12:38:51 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Sep 05 12:38:51 pve kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 05 12:38:51 pve kernel: ata1.00: supports DRM functions and may not be fully accessible
Sep 05 12:38:51 pve kernel: ata1.00: supports DRM functions and may not be fully accessible
Sep 05 12:38:51 pve kernel: spl: loading out-of-tree module taints kernel.
Sep 05 12:38:51 pve kernel: zfs: module license 'CDDL' taints kernel.
Sep 05 12:38:51 pve kernel: Disabling lock debugging due to kernel taint
Sep 05 12:38:51 pve kernel: zfs: module license taints kernel.
Sep 05 12:38:52 pve lvm[441]: PV /dev/sda3 online, VG pve is complete.
Sep 05 12:38:52 pve lvm[441]: VG pve finished
Sep 05 12:38:52 pve lvm[486]: PV /dev/sdb3 not used.
Sep 05 12:38:52 pve kernel: at24 0-0050: supply vcc not found, using dummy regulator
Sep 05 12:38:52 pve kernel: at24 0-0051: supply vcc not found, using dummy regulator
Sep 05 12:38:52 pve kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Sep 05 12:38:53 pve kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash
Sep 05 12:38:53 pve kernel: spi-nor: probe of spi0.0 failed with error -22
Sep 05 12:38:53 pve kernel: bluetooth hci0: Direct firmware load for intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq failed with error -2
Sep 05 12:38:53 pve kernel: Bluetooth: hci0: failed to open Intel firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq (-2)
Sep 05 12:38:53 pve kernel: bluetooth hci0: Direct firmware load for intel/ibt-hw-37.8.bseq failed with error -2
Sep 05 12:38:53 pve kernel: Bluetooth: hci0: failed to open default fw file: intel/ibt-hw-37.8.bseq
Sep 05 12:38:54 pve kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Sep 05 12:38:54 pve kernel: ACPI Warning: \_SB.PCI0.PEG.VID._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20230628/nsarguments-61)
Sep 05 12:38:55 pve kernel: nouveau 0000:04:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ]
Sep 05 12:38:55 pve kernel: nouveau 0000:04:00.0: [drm] No compatible format found
Sep 05 12:39:06 pve kernel: kvm_intel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
Sep 05 12:39:54 pve kernel: e1000e 0000:00:19.0 enp0s25: NETDEV WATCHDOG: CPU: 1: transmit queue 0 timed out 7699 ms
Sep 05 12:39:54 pve kernel: e1000e 0000:00:19.0 enp0s25: Reset adapter unexpectedly
Sep 05 12:41:27 pve kernel: e1000e 0000:00:19.0 enp0s25: NETDEV WATCHDOG: CPU: 2: transmit queue 0 timed out 5136 ms
Sep 05 12:41:27 pve kernel: e1000e 0000:00:19.0 enp0s25: Reset adapter unexpectedly
Sep 05 13:08:07 pve systemd[1]: lxcfs.service: Failed with result 'exit-code'.
Sep 05 13:08:21 pve systemd[1]: pve-cluster.service: State 'stop-sigterm' timed out. Killing.
Sep 05 13:08:21 pve systemd[1]: pve-cluster.service: Main process exited, code=killed, status=9/KILL
Sep 05 13:08:21 pve systemd[1]: pve-cluster.service: Failed with result 'timeout'.
Sep 05 13:08:22 pve kernel: watchdog: watchdog0: watchdog did not stop!
-- Boot 73972865620c46f0a570e95784a2e31c --
Sep 05 13:08:52 pve kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Sep 05 13:08:52 pve kernel: pnp 00:00: disabling [mem 0x000c0000-0x000c3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 13:08:52 pve kernel: pnp 00:00: disabling [mem 0x000c4000-0x000c7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 13:08:52 pve kernel: pnp 00:00: disabling [mem 0x000c8000-0x000cbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 13:08:52 pve kernel: pnp 00:00: disabling [mem 0x000cc000-0x000cffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 13:08:52 pve kernel: pnp 00:00: disabling [mem 0x000d0000-0x000d3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 13:08:52 pve kernel: pnp 00:00: disabling [mem 0x000d4000-0x000d7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 13:08:52 pve kernel: pnp 00:00: disabling [mem 0x000d8000-0x000dbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 13:08:52 pve kernel: pnp 00:00: disabling [mem 0x000dc000-0x000dffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 05 13:08:52 pve kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
Sep 05 13:08:52 pve kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Sep 05 13:08:52 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Sep 05 13:08:52 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Sep 05 13:08:52 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Sep 05 13:08:52 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Sep 05 13:08:52 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Sep 05 13:08:52 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Sep 05 13:08:52 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Sep 05 13:08:52 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Sep 05 13:08:52 pve kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 05 13:08:52 pve kernel: ata1.00: supports DRM functions and may not be fully accessible
Sep 05 13:08:52 pve kernel: ata1.00: supports DRM functions and may not be fully accessible
Sep 05 13:08:52 pve kernel: spl: loading out-of-tree module taints kernel.
Sep 05 13:08:52 pve kernel: zfs: module license 'CDDL' taints kernel.
Sep 05 13:08:52 pve kernel: Disabling lock debugging due to kernel taint
Sep 05 13:08:52 pve kernel: zfs: module license taints kernel.
Sep 05 13:08:53 pve lvm[440]: PV /dev/sda3 online, VG pve is complete.
Sep 05 13:08:53 pve lvm[440]: VG pve finished
Sep 05 13:08:53 pve kernel: at24 0-0050: supply vcc not found, using dummy regulator
Sep 05 13:08:53 pve kernel: at24 0-0051: supply vcc not found, using dummy regulator
Sep 05 13:08:53 pve lvm[486]: PV /dev/sdb3 not used.
Sep 05 13:08:54 pve kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash
Sep 05 13:08:54 pve kernel: spi-nor: probe of spi0.0 failed with error -22
Sep 05 13:08:54 pve kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Sep 05 13:08:55 pve kernel: ACPI Warning: \_SB.PCI0.PEG.VID._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20230628/nsarguments-61)
Sep 05 13:08:56 pve kernel: nouveau 0000:04:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ]
Sep 05 13:08:56 pve kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Sep 05 13:08:56 pve kernel: nouveau 0000:04:00.0: [drm] No compatible format found
Sep 05 13:09:07 pve kernel: kvm_intel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
Sep 05 13:39:12 pve pvestatd[1026]: auth key pair too old, rotating..
Sep 05 14:09:18 pve systemd[1]: run-u7.service: Failed with result 'exit-code'.
Sep 05 15:09:18 pve systemd[1]: run-u8.service: Failed with result 'exit-code'.
Sep 05 16:09:18 pve systemd[1]: run-u9.service: Failed with result 'exit-code'.
Sep 05 17:09:18 pve systemd[1]: run-u10.service: Failed with result 'exit-code'.
Sep 05 18:09:18 pve systemd[1]: run-u11.service: Failed with result 'exit-code'.
Sep 05 19:09:18 pve systemd[1]: run-u12.service: Failed with result 'exit-code'.
Sep 05 20:09:18 pve systemd[1]: run-u13.service: Failed with result 'exit-code'.
Sep 05 21:09:18 pve systemd[1]: run-u14.service: Failed with result 'exit-code'.
Sep 05 22:09:18 pve systemd[1]: run-u15.service: Failed with result 'exit-code'.
Sep 05 23:09:18 pve systemd[1]: run-u16.service: Failed with result 'exit-code'.
Sep 06 00:09:18 pve systemd[1]: run-u17.service: Failed with result 'exit-code'.
Sep 06 01:09:18 pve systemd[1]: run-u18.service: Failed with result 'exit-code'.
Sep 06 02:09:18 pve systemd[1]: run-u19.service: Failed with result 'exit-code'.
Sep 06 03:09:18 pve systemd[1]: run-u20.service: Failed with result 'exit-code'.
Sep 06 04:09:18 pve systemd[1]: run-u21.service: Failed with result 'exit-code'.
Sep 06 05:09:18 pve systemd[1]: run-u22.service: Failed with result 'exit-code'.
Sep 06 06:09:18 pve systemd[1]: run-u23.service: Failed with result 'exit-code'.
Sep 06 07:09:18 pve systemd[1]: run-u24.service: Failed with result 'exit-code'.
Sep 06 08:09:18 pve systemd[1]: run-u25.service: Failed with result 'exit-code'.
Sep 06 09:09:18 pve systemd[1]: run-u26.service: Failed with result 'exit-code'.
Sep 06 10:09:18 pve systemd[1]: run-u27.service: Failed with result 'exit-code'.
Sep 06 11:09:18 pve systemd[1]: run-u28.service: Failed with result 'exit-code'.
Sep 06 12:09:18 pve systemd[1]: run-u29.service: Failed with result 'exit-code'.
Sep 06 13:09:18 pve systemd[1]: run-u30.service: Failed with result 'exit-code'.
Sep 06 13:39:16 pve pvestatd[1026]: auth key pair too old, rotating..
Sep 06 14:09:18 pve systemd[1]: run-u31.service: Failed with result 'exit-code'.
Sep 06 15:09:18 pve systemd[1]: run-u32.service: Failed with result 'exit-code'.
Sep 06 16:09:18 pve systemd[1]: run-u33.service: Failed with result 'exit-code'.
Sep 06 17:09:18 pve systemd[1]: run-u34.service: Failed with result 'exit-code'.
Sep 06 18:09:18 pve systemd[1]: run-u35.service: Failed with result 'exit-code'.
Sep 06 19:09:18 pve systemd[1]: run-u36.service: Failed with result 'exit-code'.
Sep 06 20:09:18 pve systemd[1]: run-u37.service: Failed with result 'exit-code'.
Sep 06 21:09:18 pve systemd[1]: run-u38.service: Failed with result 'exit-code'.
Sep 06 22:09:18 pve systemd[1]: run-u39.service: Failed with result 'exit-code'.
Sep 06 23:09:18 pve systemd[1]: run-u40.service: Failed with result 'exit-code'.
5 
e1000e ... NETDEV WATCHDOG: transmit queue 0 timed out
e1000e ... Reset adapter unexpectedly

e1000e Error und Proxmox,
hier hat sich dein netzwerkadapter weggehangen und wurde von Treiber resettet!
Das könnte die Ursache sein!?

Ich hatte ein ähnliches Problem mit einem NUC welcher auch unter Proxmox lief, Lösungsansatz → Fix Intel Network Adapter (E1000) hanging/errors in Proxmox - Balaji's Tech Notes
bzw.mal Google bemühen mit „Proxmox+e1000e“ da gibt es jede Menge zu!

7

Ich kann da ausser dem E1000e nichts kritisches sehen! Haben wir das selbe Log?

9

Hast du ein neues device angeschlossen?

Pcie device names sind ja leider auf consumer hardware nicht persistent.
Heißt, wenn du ne zusätzliche Platte, GPU, etc einbaust, passen die device Namen nicht mehr.

11

PCIe device naming ist leider so gut wie nie stabil.
Ich hab das die nerven verloren, als ich ne Zeit lang meine Grafikkarte staendig Ein- und Ausgebaut habe und Proxmox meine NVMe SSDs nicht mehr gefunden hab.

Super nervig.

Hab vergessen, ob Proxmox/Debian auch netplan nutzt. Da kann man dann mal schauen, ob das ethernet device noch den gleichen namen hat, wie das bei ip a.

13

ihr habt mich verwirrt :ghost: :grimacing:

Die Originalfestplatte war kaputt, deshalb habe ich Eratz eingebaut. Vielleicht liegt es daran?
Update habe ich nicht gemacht.

Den Ubuntu-Bootstick und Sachen im Bios deaktivieren probiere ich aus. Ich befürchte aber, dass ich heute nicht mehr dazu komme.
Unter /usr/bin/ gibts kein sudo ?!

15

da habe ich ja ordentlich Eindruch hinterlassen ^^

öhm, sie war neuer als die alte :flushed:

17

ich bin vor Ort schon übefordert :laughing:
Aber die Bewunderung für Leute, die sowas können ist groß

ich habe im Bios gefühlt alles deaktiviert und die Befehle nochmals ausgeführt

 journalctl -p err -p warning --since 2025-09-10
Sep 10 13:39:39 pve pvestatd[1030]: auth key pair too old, rotating..
Sep 10 18:09:15 pve kernel: sd 3:0:0:0: [sdc] No Caching mode page found
Sep 10 18:09:15 pve kernel: sd 3:0:0:0: [sdc] Assuming drive cache: write through
Sep 10 18:19:28 pve kernel: sd 3:0:0:0: [sdc] No Caching mode page found
Sep 10 18:19:28 pve kernel: sd 3:0:0:0: [sdc] Assuming drive cache: write through
Sep 10 18:30:19 pve systemd[1]: lxcfs.service: Failed with result 'exit-code'.
Sep 10 18:30:25 pve kernel: watchdog: watchdog0: watchdog did not stop!
-- Boot d1b4f6e7d00f446fb3df7ae65a4cd4a0 --
Sep 10 18:43:15 pve kernel: pnp 00:00: disabling [mem 0x000c0000-0x000c3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 10 18:43:15 pve kernel: pnp 00:00: disabling [mem 0x000c4000-0x000c7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 10 18:43:15 pve kernel: pnp 00:00: disabling [mem 0x000c8000-0x000cbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 10 18:43:15 pve kernel: pnp 00:00: disabling [mem 0x000cc000-0x000cffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 10 18:43:15 pve kernel: pnp 00:00: disabling [mem 0x000d0000-0x000d3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 10 18:43:15 pve kernel: pnp 00:00: disabling [mem 0x000d4000-0x000d7fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 10 18:43:15 pve kernel: pnp 00:00: disabling [mem 0x000d8000-0x000dbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 10 18:43:15 pve kernel: pnp 00:00: disabling [mem 0x000dc000-0x000dffff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
Sep 10 18:43:15 pve kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
Sep 10 18:43:15 pve kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Sep 10 18:43:15 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Sep 10 18:43:15 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Sep 10 18:43:15 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Sep 10 18:43:15 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Sep 10 18:43:15 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Sep 10 18:43:15 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Sep 10 18:43:15 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Sep 10 18:43:15 pve kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Sep 10 18:43:15 pve kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 10 18:43:15 pve kernel: ata1.00: supports DRM functions and may not be fully accessible
Sep 10 18:43:15 pve kernel: ata1.00: supports DRM functions and may not be fully accessible
Sep 10 18:43:15 pve kernel: spl: loading out-of-tree module taints kernel.
Sep 10 18:43:15 pve kernel: zfs: module license 'CDDL' taints kernel.
Sep 10 18:43:15 pve kernel: Disabling lock debugging due to kernel taint
Sep 10 18:43:15 pve kernel: zfs: module license taints kernel.
Sep 10 18:43:16 pve lvm[420]: PV /dev/sda3 online, VG pve is complete.
Sep 10 18:43:16 pve lvm[420]: VG pve finished
Sep 10 18:43:16 pve kernel: at24 0-0050: supply vcc not found, using dummy regulator
Sep 10 18:43:16 pve kernel: at24 0-0051: supply vcc not found, using dummy regulator
Sep 10 18:43:16 pve lvm[460]: PV /dev/sdb3 not used.
Sep 10 18:43:16 pve kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash
Sep 10 18:43:16 pve kernel: spi-nor: probe of spi0.0 failed with error -22
Sep 10 18:43:17 pve kernel: ACPI Warning: \_SB.PCI0.PEG.VID._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20230628/nsarguments-61)
Sep 10 18:43:18 pve kernel: nouveau 0000:03:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ]
Sep 10 18:43:18 pve kernel: nouveau 0000:03:00.0: [drm] No compatible format found

dmesg
Wed Sep 10 18:43:15 2025] spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash
[Wed Sep 10 18:43:17 2025] nouveau 0000:03:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ]

journalctl ist deutlich kürzer. Woran lag die fehlende Netzwerkverbindung? :flushed:

19

super, danke nochmals für die Hilfe! Sie ist wirklich Gold wert.
Dann kann ich mich jetzt also darum kümmern, weshalb ich den Proxmox-Server ursprünglich neugestartet hatte (Zigbee Devices funktionieren nicht)… und danach sind die übergroßen Backups dran; es gibt immer etwas zu tun :laughing:

bzgl sudo:

root@pve:/# find . -name sudo |grep -i bin
# kein output
root@pve:/# find . -name sudo 
./usr/share/bash-completion/completions/sudo
lroot@pve:/# ls -l ./usr/share/bash-completion/completions/sudo
-rw-r--r-- 1 root root 1504 Apr  3  2022 ./usr/share/bash-completion/completions/sudo
root@pve:/# ./usr/share/bash-completion/completions/sudo
-bash: ./usr/share/bash-completion/completions/sudo: Permission denied
20

sinnvoller Weise würde ich mit folgenden „Zeilen“ nach eventuell installierten Programmen suchen

which sudo
command -v sudo
dpkg -l | grep sudo

Es wäre mir neu das bei Proxmox „Sudo“ von Haus aus installiert wird!?

23

sudo ist in der Priorität nach hinten gerutscht :sob:
Das Netzwerk ist wieder nicht erreichbar. Neustart hat nicht geholfen. Wenn ich den Router anpinge komt „Destination host unreachable“. Also sind wir wieder am Anfang.
Es wäre ja auch zu schön gewesen. Soll ich nochmal journalctl ausführen?
Wie bekomme ich den output davon dann hier in Forum eingefügt ohne Netzwerk: Handyfotos oder geht es besser?

25

Bin nach wie vor der Meinung das deine „e1000“ das Problem ist. Falls du die Kiste wieder online bekommst kannst Du gern mal folgenden Link testen → Proxmox VE Helper-Scripts
Was es ist und macht wird dir sicher Stevie gern erklären wollen!

Hast du einen „USB-Netzwerkadapter“ dann nimm doch den mal zum testen!?