Ungeklärter Reboot

david83 · May 24, 2020

Hallo zusammen,

Ich nutze Proxmox 6.2 und mein System rebooted sich von Zeit zu Zeit. Ich Ich kann mir das nicht erklären und bin auf Ursachenforschung gegangen. Leider komme ich nicht weiter. Ich wäre wirklich dankbar für jede Hilfe.

Die Logs:

Code:

root@pve:~# last -x | head | tac
root     pts/1        192.168.178.202  Wed May 13 13:34 - 13:34  (00:00)
root     pts/1        192.168.178.35   Mon May 18 17:18 - down   (00:03)
shutdown system down  5.3.18-3-pve     Mon May 18 17:21 - 17:23  (00:01)
reboot   system boot  5.3.18-3-pve     Mon May 18 17:23   still running
runlevel (to lvl 5)   5.3.18-3-pve     Mon May 18 17:24 - 01:18 (5+07:54)
reboot   system boot  5.3.18-3-pve     Sun May 24 01:16   still running
runlevel (to lvl 5)   5.3.18-3-pve     Sun May 24 01:18   still running
root     pts/1        192.168.178.33   Sun May 24 08:34 - 08:35  (00:01)
root     pts/1        192.168.178.33   Sun May 24 08:43 - 09:52  (01:09)
root     pts/1        192.168.178.33   Sun May 24 10:13   still logged in
root@pve:~#

Code:

/log/messages:May 24 01:17:02 pve kernel: [    0.380340] ACPI: Power Resource [DRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.380930] ACPI: Power Resource [DRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.381526] ACPI: Power Resource [DRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.382122] ACPI: Power Resource [DRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.382786] ACPI: Power Resource [DRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.383505] ACPI: Power Resource [WRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.392989] ACPI: Power Resource [FN00] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    4.521780] raid6: using ssse3x2 recovery algorithm
/var/log/messages:May 24 01:18:12 pve kernel: [   91.374240] EXT4-fs (dm-6): recovery complete
/var/log/syslog:May 24 00:00:00 pve rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="1233" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
/var/log/syslog:May 24 00:00:01 pve rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="1233" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
/var/log/syslog:May 24 01:17:02 pve systemd[1]: Started Update UTMP about System Boot/Shutdown.
/var/log/syslog:May 24 01:17:02 pve rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.1901.0]
/var/log/syslog:May 24 01:17:02 pve rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="1337" x-info="https://www.rsyslog.com"] start
/var/log/syslog:May 24 01:17:02 pve kernel: [    0.379748] ACPI: Power Resource [DRST] (on)
/var/log/syslog:May 24 01:17:02 pve kernel: [    0.380340] ACPI: Power Resource [DRST] (on)
/var/log/syslog:May 24 01:17:02 pve kernel: [    0.380930] ACPI: Power Resource [DRST] (on)
/var/log/syslog:May 24 01:17:02 pve kernel: [    0.381526] ACPI: Power Resource [DRST] (on)
/var/log/syslog:May 24 01:17:02 pve kernel: [    0.382122] ACPI: Power Resource [DRST] (on)
/var/log/syslog:May 24 01:17:02 pve kernel: [    0.382786] ACPI: Power Resource [DRST] (on)
/var/log/syslog:May 24 01:17:02 pve kernel: [    0.383505] ACPI: Power Resource [WRST] (on)
/var/log/syslog:May 24 01:17:02 pve kernel: [    0.392989] ACPI: Power Resource [FN00] (on)

jan-t · May 24, 2020

Hallo david83, bist Du dir sicher, dass Du Proxmox 6.2 verwendest?

5.3.18-3-pve, das sieht doch nach Proxmox 5.3 aus.

Hast Du evtl. etwas verbastelt, hingebastelt?

Wie hast Du Proxmox 6.2 installiert?

VG
jan-t

david83 · May 24, 2020

Hallo,
Da hab ich mich wohl vertan.

Pve Manager 6.1.8
Kernel: 5.3.18-3-pve

jan-t · May 24, 2020

Oder ich habe mich zu weit aus dem Fenster gelehnt.

Das proxmox-ve_6.2-1.iso, beihaltet den Proxmox pve-manager: 6.2-4 und den Kernel 5.3.18-3-pve.
https://forum.proxmox.com/threads/a...ronment-6-2-4-mit-proxmox-ve_6-2-1-iso.69711/

So wird das richtig sein.

Wie hast Du dein System installiert?

tom · May 24, 2020

jan-t said:
Das proxmox-ve_6.2-1.iso, beihaltet den Proxmox pve-manager: 6.2-4 und den Kernel 5.3.18-3-pve.

Nein, das 6.2 ISO enthält einen 5.4 Kernel, siehe auch:

https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_6.2

david83 · May 24, 2020

Also ich habe das Installationsmedium herunterladen und per USB Stick installiert.

Es geht hier um den Reboot um 01:17

jan-t · May 24, 2020

proxmox-ve_6.2-1.iso,
mit Kernel 5.4 LTS

Hoffentlich dieses, ich vermute eher Du hast ein anderes Iso gewählt.

david83 · May 24, 2020

Also es war von dieser Seite: https://www.proxmox.com/en/downloads/category/iso-images-pve

Die Frage ist hierbei ob das was damit zu tun hat. Ich weiß halt gar nicht ob es Softwareseitig oder Hardwareseitig ein Problem ist, da ich keinen Fehler finde.

jan-t · May 24, 2020

Also es war von dieser Seite: https://www.proxmox.com/en/downloads/category/iso-images-pve

Das ist ja nun keine präzise Antwort.

Ich weiß halt gar nicht ob es Softwareseitig oder Hardwareseitig ein Problem ist, da ich keinen Fehler finde.

Woher sollen das jemand anderes wissen, wenn deine Informationen nicht genau sind?

david83 · May 24, 2020

Also ich werde morgen genau alle Daten und Logs Posten. Danke erstmal für die Beteiligung.

jan-t · May 25, 2020

Hallo david83,

bisher hast Du nicht geklärt, welches Iso Du für die Installation genutzt hast.

Hallo zusammen,

Ich nutze Proxmox 6.2 u

Da bin ich mir gar nicht so sicher,
proxmox-ve_6.2-1.iso,
ist mit Kernel 5.4 LTS

Deine verwendete Hardware ist auch nicht bekannt.

VG
jan-t

david83 · May 25, 2020

Guten Morgen,

hier meine Daten. Bitte sagt bescheid wenn etwas fehlt.

Installiertes Image: proxmox-ve_6.1-2.iso
Server laüft seit 1,5 Monaten
Seitdem 6 ungeklärte reboots.
Es sind 2 vm und ein Lxc am laufen.
Es handelt sich um einen Server der bei mir zu Hause steht.

Hardware:
Mainboard Asrock j5005 itx mit Intel Gemini Lake
Ram Crucial 2x8 GB DDR4 PC2400
Netzteil Ituner Picu Psu80 80Watt
Hauptfestplatte für Proxmox SSD 128GB
Datenplatte 500 GB Sata HDD

Software:
pve-manager/6.1-8/806edfe1 (running kernel: 5.3.18-3-pve)

Letzter ungewollter Reboot 24.05. 01:16

Logs:

Code:

root@pve:~# last -x | head | tac
root     pts/1        192.168.178.202  Wed May 13 13:34 - 13:34  (00:00)
root     pts/1        192.168.178.35   Mon May 18 17:18 - down   (00:03)
shutdown system down  5.3.18-3-pve     Mon May 18 17:21 - 17:23  (00:01)
reboot   system boot  5.3.18-3-pve     Mon May 18 17:23   still running
runlevel (to lvl 5)   5.3.18-3-pve     Mon May 18 17:24 - 01:18 (5+07:54)
reboot   system boot  5.3.18-3-pve     Sun May 24 01:16   still running
runlevel (to lvl 5)   5.3.18-3-pve     Sun May 24 01:18   still running
root     pts/1        192.168.178.33   Sun May 24 08:34 - 08:35  (00:01)
root     pts/1        192.168.178.33   Sun May 24 08:43 - 09:52  (01:09)

last -x | less

Code:

root     pts/1        192.168.178.35   Mon May 25 07:48   still logged in
root     pts/1        192.168.178.33   Sun May 24 10:26 - 10:29  (00:02)
root     pts/1        192.168.178.33   Sun May 24 10:26 - 10:26  (00:00)
root     pts/1        192.168.178.33   Sun May 24 10:25 - 10:25  (00:00)
root     pts/1        192.168.178.33   Sun May 24 10:24 - 10:24  (00:00)
root     pts/1        192.168.178.33   Sun May 24 10:13 - 10:16  (00:03)
root     pts/1        192.168.178.33   Sun May 24 08:43 - 09:52  (01:09)
root     pts/1        192.168.178.33   Sun May 24 08:34 - 08:35  (00:01)
runlevel (to lvl 5)   5.3.18-3-pve     Sun May 24 01:18   still running
reboot   system boot  5.3.18-3-pve     Sun May 24 01:16   still running
runlevel (to lvl 5)   5.3.18-3-pve     Mon May 18 17:24 - 01:18 (5+07:54)
reboot   system boot  5.3.18-3-pve     Mon May 18 17:23   still running
shutdown system down  5.3.18-3-pve     Mon May 18 17:21 - 17:23  (00:01)
root     pts/1        192.168.178.35   Mon May 18 17:18 - down   (00:03)
root     pts/1        192.168.178.202  Wed May 13 13:34 - 13:34  (00:00)
root     pts/1        192.168.178.202  Wed May 13 13:27 - 13:27  (00:00)
runlevel (to lvl 5)   5.3.18-3-pve     Fri May  8 20:32 - 17:21 (9+20:48)
reboot   system boot  5.3.18-3-pve     Fri May  8 20:31 - 17:21 (9+20:50)
root     pts/1        192.168.178.202  Fri May  8 14:49 - 14:50  (00:00)
root     pts/1        192.168.178.33   Wed May  6 10:09 - 10:13  (00:03)
root     pts/1        192.168.178.33   Wed May  6 09:54 - 10:04  (00:09)
root     pts/1        192.168.178.33   Sun May  3 21:03 - 21:10  (00:07)
root     pts/1        192.168.178.35   Sun May  3 20:45 - 20:59  (00:13)
runlevel (to lvl 5)   5.3.18-3-pve     Sun May  3 20:44 - 20:32 (4+23:48)
reboot   system boot  5.3.18-3-pve     Sun May  3 20:43 - 17:21 (14+20:38)
root     pts/0        192.168.178.35   Sun May  3 20:42 - crash  (00:00)
root     pts/0        192.168.178.35   Sun May  3 20:40 - 20:42  (00:01)
runlevel (to lvl 5)   5.3.18-3-pve     Sun May  3 20:37 - 20:44  (00:07)
root     pts/0        192.168.178.35   Sun May  3 20:36 - 20:40  (00:03)
reboot   system boot  5.3.18-3-pve     Sun May  3 20:36 - 17:21 (14+20:45)
shutdown system down  5.3.18-3-pve     Sun May  3 20:35 - 20:36  (00:00)
root     pts/0        192.168.178.35   Sun May  3 20:27 - down   (00:08)
root     pts/0        192.168.178.33   Sat May  2 22:36 - 22:37  (00:01)
runlevel (to lvl 5)   5.3.18-3-pve     Sat May  2 22:31 - 20:35  (22:04)
root     pts/0        192.168.178.33   Sat May  2 22:30 - 22:33  (00:02)
reboot   system boot  5.3.18-3-pve     Sat May  2 22:30 - 20:35  (22:04)
shutdown system down  5.3.18-3-pve     Sat May  2 22:30 - 22:30  (00:00)
root     pts/1        192.168.178.33   Sat May  2 22:29 - down   (00:01)
runlevel (to lvl 5)   5.3.18-3-pve     Sat May  2 22:27 - 22:30  (00:02)

Code:

/var/log/messages:May 24 00:00:01 pve rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="1233" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
/var/log/messages:May 24 01:17:02 pve rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.1901.0]
/var/log/messages:May 24 01:17:02 pve rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="1337" x-info="https://www.rsyslog.com"] start
/var/log/messages:May 24 01:17:02 pve kernel: [    0.379748] ACPI: Power Resource [DRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.380340] ACPI: Power Resource [DRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.380930] ACPI: Power Resource [DRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.381526] ACPI: Power Resource [DRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.382122] ACPI: Power Resource [DRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.382786] ACPI: Power Resource [DRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.383505] ACPI: Power Resource [WRST] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    0.392989] ACPI: Power Resource [FN00] (on)
/var/log/messages:May 24 01:17:02 pve kernel: [    4.521780] raid6: using ssse3x2 recovery algorithm
/var/log/messages:May 24 01:18:12 pve kernel: [   91.374240] EXT4-fs (dm-6): recovery complete
/var/log/messages:May 25 00:00:03 pve rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="1337" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
/var/log/syslog:May 25 00:00:03 pve rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="1337" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
grep: /var/log/apcupsd*: No such file or directory

jan-t · May 25, 2020

https://forum.proxmox.com/threads/ungeklärter-reboot.70271/#post-315379

Nein, das 6.2 ISO enthält einen 5.4 Kernel, siehe auch:

https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_6.2

Wie kommst Du zu dem Kernel "kernel: 5.3.18-3-pve"?

Das stimmt auch meiner Sicht irgendwas nicht, entweder verbastelt, falsches Iso oder besondere älteren Kernel installiert.

proxmox-ve_6.1-2.iso -- Released 12. May 2020

david83 · May 25, 2020

Teil 2

Ausgabe der /var/log/debug

Code:

May 24 01:17:02 pve kernel: [    0.000031] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
May 24 01:17:02 pve kernel: [    0.000034] e820: remove [mem 0x000a0000-0x000fffff] usable
May 24 01:17:02 pve kernel: [    0.000054] MTRR default type: uncachable
May 24 01:17:02 pve kernel: [    0.000056] MTRR fixed ranges enabled:
May 24 01:17:02 pve kernel: [    0.000058]   00000-9FFFF write-back
May 24 01:17:02 pve kernel: [    0.000060]   A0000-BFFFF uncachable
May 24 01:17:02 pve kernel: [    0.000061]   C0000-FFFFF write-protect
May 24 01:17:02 pve kernel: [    0.000063] MTRR variable ranges enabled:
May 24 01:17:02 pve kernel: [    0.000065]   0 base 00FF000000 mask 7FFF000000 write-combining
May 24 01:17:02 pve kernel: [    0.000068]   1 base 0000000000 mask 7F80000000 write-back
May 24 01:17:02 pve kernel: [    0.000069]   2 base 006F000000 mask 7FFF000000 uncachable
May 24 01:17:02 pve kernel: [    0.000071]   3 base 0070000000 mask 7FF0000000 uncachable
May 24 01:17:02 pve kernel: [    0.000073]   4 base 0100000000 mask 7F00000000 write-back
May 24 01:17:02 pve kernel: [    0.000075]   5 base 0200000000 mask 7E00000000 write-back
May 24 01:17:02 pve kernel: [    0.000077]   6 base 0400000000 mask 7F80000000 write-back
May 24 01:17:02 pve kernel: [    0.000078]   7 base 0090000000 mask 7FF0000000 write-combining
May 24 01:17:02 pve kernel: [    0.000080]   8 disabled
May 24 01:17:02 pve kernel: [    0.000081]   9 disabled
May 24 01:17:02 pve kernel: [    0.007701] e820: update [mem 0x69ce6000-0x69ce6fff] usable ==> reserved
May 24 01:17:02 pve kernel: [    0.007741] BRK [0x42b001000, 0x42b001fff] PGTABLE
May 24 01:17:02 pve kernel: [    0.007745] BRK [0x42b002000, 0x42b002fff] PGTABLE
May 24 01:17:02 pve kernel: [    0.007747] BRK [0x42b003000, 0x42b003fff] PGTABLE
May 24 01:17:02 pve kernel: [    0.007892] BRK [0x42b004000, 0x42b004fff] PGTABLE
May 24 01:17:02 pve kernel: [    0.008334] BRK [0x42b005000, 0x42b005fff] PGTABLE
May 24 01:17:02 pve kernel: [    0.008461] BRK [0x42b006000, 0x42b006fff] PGTABLE
May 24 01:17:02 pve kernel: [    0.008600] BRK [0x42b007000, 0x42b007fff] PGTABLE
May 24 01:17:02 pve kernel: [    0.008758] BRK [0x42b008000, 0x42b008fff] PGTABLE
May 24 01:17:02 pve kernel: [    0.008955] BRK [0x42b009000, 0x42b009fff] PGTABLE
May 24 01:17:02 pve kernel: [    0.009194] BRK [0x42b00a000, 0x42b00afff] PGTABLE
May 24 01:17:02 pve kernel: [    0.009896] ACPI: Local APIC address 0xfee00000
May 24 01:17:02 pve kernel: [    0.011167] On node 0 totalpages: 4103374
May 24 01:17:02 pve kernel: [    0.011169]   DMA zone: 64 pages used for memmap
May 24 01:17:02 pve kernel: [    0.011171]   DMA zone: 23 pages reserved
May 24 01:17:02 pve kernel: [    0.011173]   DMA zone: 3995 pages, LIFO batch:0
May 24 01:17:02 pve kernel: [    0.011277]   DMA32 zone: 6709 pages used for memmap
May 24 01:17:02 pve kernel: [    0.011279]   DMA32 zone: 429363 pages, LIFO batch:63
May 24 01:17:02 pve kernel: [    0.028366]   Normal zone: 57344 pages used for memmap
May 24 01:17:02 pve kernel: [    0.028367]   Normal zone: 3670016 pages, LIFO batch:63
May 24 01:17:02 pve kernel: [    0.118362] ACPI: Local APIC address 0xfee00000
May 24 01:17:02 pve kernel: [    0.118426] ACPI: IRQ0 used by override.
May 24 01:17:02 pve kernel: [    0.118428] ACPI: IRQ9 used by override.
May 24 01:17:02 pve kernel: [    0.119091] pcpu-alloc: s184320 r8192 d28672 u524288 alloc=1*2097152
May 24 01:17:02 pve kernel: [    0.119093] pcpu-alloc: [0] 0 1 2 3
May 24 01:17:02 pve kernel: [    0.135844] Calgary: detecting Calgary via BIOS EBDA area
May 24 01:17:02 pve kernel: [    0.135846] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
May 24 01:17:02 pve kernel: [    0.285545] TSC deadline timer enabled
May 24 01:17:02 pve kernel: [    0.414781] libata version 3.00 loaded.
May 24 01:17:02 pve kernel: [    0.441904] PCI: pci_cache_line_size set to 64 bytes
May 24 01:17:02 pve kernel: [    0.441985] e820: reserve RAM buffer [mem 0x0003e000-0x0003ffff]
May 24 01:17:02 pve kernel: [    0.441988] e820: reserve RAM buffer [mem 0x0009e000-0x0009ffff]
May 24 01:17:02 pve kernel: [    0.441989] e820: reserve RAM buffer [mem 0x69ce6000-0x6bffffff]
May 24 01:17:02 pve kernel: [    0.441991] e820: reserve RAM buffer [mem 0x6adaa000-0x6bffffff]
May 24 01:17:02 pve kernel: [    0.441992] e820: reserve RAM buffer [mem 0x6d675000-0x6fffffff]
May 24 01:17:02 pve kernel: [    0.441994] e820: reserve RAM buffer [mem 0x6e4c2000-0x6fffffff]
May 24 01:17:02 pve kernel: [    0.441995] e820: reserve RAM buffer [mem 0x6ec00000-0x6fffffff]
May 24 01:17:02 pve kernel: [    0.472504] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
May 24 01:17:02 pve kernel: [    0.473367] pnp 00:01: [dma 0 disabled]
May 24 01:17:02 pve kernel: [    0.473456] pnp 00:01: Plug and Play ACPI device, IDs PNP0501 (active)
May 24 01:17:02 pve kernel: [    0.473560] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
May 24 01:17:02 pve kernel: [    0.474472] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active)
May 24 01:17:02 pve kernel: [    0.474967] pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
May 24 01:17:02 pve kernel: [    1.658220] intel_idle: MWAIT substates: 0x11242020
May 24 01:17:02 pve kernel: [    1.658222] intel_idle: v0.4.1 model 0x7A
May 24 01:17:02 pve kernel: [    1.658640] intel_idle: lapic_timer_reliable_states 0xffffffff
May 24 01:17:02 pve kernel: [    2.117434] ahci 0000:00:12.0: version 3.0
May 24 01:17:02 pve kernel: [    2.607267] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
May 24 01:17:02 pve kernel: [    2.607810] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00

david83 · May 25, 2020

Teil 3

Ausgabe var/log/syslog:

Code:

May 24 01:15:00 pve systemd[1]: Starting Proxmox VE replication runner...
May 24 01:15:01 pve systemd[1]: pvesr.service: Succeeded.
May 24 01:15:01 pve systemd[1]: Started Proxmox VE replication runner.
May 24 01:15:01 pve CRON[28237]: (root) CMD (/var/dyndns/dyndns.sh > /dev/null 2>&1)
May 24 01:16:00 pve systemd[1]: Starting Proxmox VE replication runner...
May 24 01:16:01 pve systemd[1]: pvesr.service: Succeeded.
May 24 01:16:01 pve systemd[1]: Started Proxmox VE replication runner.
May 24 01:17:02 pve systemd-modules-load[450]: Inserted module 'iscsi_tcp'
May 24 01:17:02 pve dmeventd[469]: dmeventd ready for processing.
May 24 01:17:02 pve systemd-modules-load[450]: Inserted module 'ib_iser'
May 24 01:17:02 pve lvm[469]: Monitoring thin pool pve-data-tpool.
May 24 01:17:02 pve systemd-modules-load[450]: Inserted module 'vhost_net'
May 24 01:17:02 pve systemd[1]: Starting Flush Journal to Persistent Storage...
May 24 01:17:02 pve lvm[453]:   14 logical volume(s) in volume group "pve" monitored
May 24 01:17:02 pve systemd[1]: Started Flush Journal to Persistent Storage.
May 24 01:17:02 pve systemd[1]: Started udev Coldplug all Devices.
May 24 01:17:02 pve systemd[1]: Starting udev Wait for Complete Device Initialization...
May 24 01:17:02 pve systemd[1]: Starting Helper to synchronize boot up for ifupdown...
May 24 01:17:02 pve systemd-udevd[485]: Using default interface naming scheme 'v240'.
May 24 01:17:02 pve systemd-udevd[485]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 24 01:17:02 pve systemd-udevd[486]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 24 01:17:02 pve systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
May 24 01:17:02 pve systemd[1]: Found device SATA_SSD 2.
May 24 01:17:02 pve systemd[1]: Found device /dev/pve/swap.
May 24 01:17:02 pve systemd[1]: Activating swap /dev/pve/swap...
May 24 01:17:02 pve systemd[1]: Created slice system-lvm2\x2dpvscan.slice.

david83 · May 25, 2020

Ausgabe var/log/kern.log

Code:

May 24 01:17:02 pve kernel: [    0.000000] Linux version 5.3.18-3-pve (build@pve) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PVE 5.3.18-3 (Tue, 17 Mar 2020 16:33:19 +0100) ()
May 24 01:17:02 pve kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-3-pve root=/dev/mapper/pve-root ro quiet
May 24 01:17:02 pve kernel: [    0.000000] KERNEL supported cpus:
May 24 01:17:02 pve kernel: [    0.000000]   Intel GenuineIntel
May 24 01:17:02 pve kernel: [    0.000000]   AMD AuthenticAMD
May 24 01:17:02 pve kernel: [    0.000000]   Hygon HygonGenuine
May 24 01:17:02 pve kernel: [    0.000000]   Centaur CentaurHauls
May 24 01:17:02 pve kernel: [    0.000000]   zhaoxin   Shanghai 
May 24 01:17:02 pve kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
May 24 01:17:02 pve kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
May 24 01:17:02 pve kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
May 24 01:17:02 pve kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
May 24 01:17:02 pve kernel: [    0.000000] x86/fpu: xstate_offset[3]:  576, xstate_sizes[3]:   64
May 24 01:17:02 pve kernel: [    0.000000] x86/fpu: xstate_offset[4]:  640, xstate_sizes[4]:   64
May 24 01:17:02 pve kernel: [    0.000000] x86/fpu: Enabled xstate features 0x1b, context size is 704 bytes, using 'compacted' format.
May 24 01:17:02 pve kernel: [    0.000000] BIOS-provided physical RAM map:
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000003dfff] usable
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x000000000003e000-0x000000000003ffff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x0000000000040000-0x000000000009dfff] usable
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000000fffffff] usable
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x0000000010000000-0x0000000012150fff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x0000000012151000-0x000000006ada9fff] usable
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x000000006adaa000-0x000000006d653fff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x000000006d654000-0x000000006d674fff] usable
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x000000006d675000-0x000000006d6ccfff] ACPI NVS
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x000000006d6cd000-0x000000006d9e9fff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x000000006d9ea000-0x000000006da9afff] type 20
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x000000006da9b000-0x000000006e4c1fff] usable
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x000000006e4c2000-0x000000006e56dfff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x000000006e56e000-0x000000006ebfffff] usable
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x000000006ec00000-0x000000007fffffff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000d0000000-0x00000000d0ffffff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000d3709000-0x00000000d3709fff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fe042000-0x00000000fe044fff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fe900000-0x00000000fe902fff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed01000-0x00000000fed01fff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
May 24 01:17:02 pve kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000047fffffff] usable
May 24 01:17:02 pve kernel: [    0.000000] NX (Execute Disable) protection: active
May 24 01:17:02 pve kernel: [    0.000000] efi: EFI v2.60 by American Megatrends
May 24 01:17:02 pve kernel: [    0.000000] efi:  ACPI 2.0=0x6d675000  ACPI=0x6d675000  TPMFinalLog=0x6d69b000  SMBIOS=0x6d947000  SMBIOS 3.0=0x6d946000  ESRT=0x69ce6c18  MEMATTR=0x67b13018
May 24 01:17:02 pve kernel: [    0.000000] secureboot: Secure boot could not be determined (mode 0)
May 24 01:17:02 pve kernel: [    0.000000] SMBIOS 3.1.1 present.

jan-t · May 25, 2020

Hallo david83,

bei dir stimmt etwas nicht.

Installiertes Image: proxmox-ve_6.1-2.iso
Server laüft seit 1,5 Monaten
Seitdem 6 ungeklärte reboots.
Es sind 2 vm und ein Lxc am laufen.

Seit 1,5 Monaten gibt es das
proxmox-ve_6.2-1.iso,
ist mit Kernel 5.4 LTS
gar nicht.

Den Kernel 5.4 LTS würde ich ausprobieren, und zwar mit dem proxmox-ve_6.2-1.iso, als saubere Installation.

VG
jan-t

david83 · May 25, 2020

jan-t said:
https://forum.proxmox.com/threads/ungeklärter-reboot.70271/#post-315379

Wie kommst Du zu dem Kernel "kernel: 5.3.18-3-pve"?

Das stimmt auch meiner Sicht irgendwas nicht, entweder verbastelt, falsches Iso oder besondere älteren Kernel installiert.

proxmox-ve_6.1-2.iso -- Released 12. May 2020

Hallo,
Ich habe lediglich das Image instaliert welches ich heruntergeladen habe.
Des weiteren habe ich nur bereitstehende Updates installiert.

Meine sources.list

Code:

deb http://ftp.de.debian.org/debian buster main contrib

deb http://ftp.de.debian.org/debian buster-updates main contrib

# security updates
deb http://security.debian.org buster/updates main contrib

# PVE pve-no-subscription repository provided by proxmox.com, NOT
# recommended for production use
deb http://download.proxmox.com/debian/pve buster pve-no-subscription

david83 · May 25, 2020

jan-t said:
Hallo david83,

bei dir stimmt etwas nicht.

Seit 1,5 Monaten gibt es das
proxmox-ve_6.2-1.iso,
ist mit Kernel 5.4 LTS
gar nicht.

Den Kernel 5.4 LTS würde ich ausprobieren, und zwar mit dem proxmox-ve_6.2-1.iso, als saubere Insallation.

VG
jan-t

Ja da hast du recht. Ich habe mich im Image vertan. Deshalb habe ich für meine heutigen Posts alles genau nachgesehen und oben aufgeführt. Es handelt sich um dieses Image: proxmox-ve_6.1-2.iso

jan-t · May 25, 2020

Code:

May 24 01:17:02 pve kernel: [    0.000000] Linux version 5.3.18-3-pve (build@pve) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PVE 5.3.18-3 (Tue, 17 Mar 2020 16:33:19 +0100) ()

Du hast immer noch nicht den Kernel 5.4!

Ich habe mich im Image vertan. D

Wo hast Du dich noch überall vertan?

Hast Du eine sauber Installation mit dem proxmox-ve_6.2-1.iso erstellt?
Vermutlich eher nicht.

Wenn man sich "viel vertut" kann dir niemand helfen, Du benötigst einen reproduzierbaren sauber installierten Zustand.
Den hast Du nicht, Du hast eine angepaßte david83 Installation.

Ungeklärter Reboot

Member

Member

Member

Member

Proxmox Staff Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member