[SOLVED] Proxmox startet nach herrunterfahren neu

simstra19958

New Member
Sep 7, 2022
5
0
1
Hallo zusammen,

bei mir startet Proxmox neu wenn ich denn Herrunterfahren Button klicke.

hier mal das Syslog:

Code:
Sep 07 13:15:36 homelab systemd[1]: systemd-poweroff.service: Succeeded.
Sep 07 13:15:36 homelab systemd[1]: Finished Power-Off.
Sep 07 13:15:36 homelab systemd[1]: Reached target Power-Off.
Sep 07 13:15:36 homelab systemd[1]: Shutting down.
Sep 07 13:15:36 homelab systemd-shutdown: Syncing filesystems and block devices.
Sep 07 13:15:36 homelab systemd-shutdown: Sending SIGTERM to remaining processes...
Sep 07 13:15:36 homelab systemd-journald[575]: Journal stopped
-- Reboot --
Sep 07 13:16:03 homelab kernel: Linux version 5.15.53-1-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PVE 5.15.53-1 (Fri, 26 Aug 2022 16:53:52 +0200) ()
Sep 07 13:16:03 homelab kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.53-1-pve root=/dev/mapper/pve-root ro quiet
Sep 07 13:16:03 homelab kernel: KERNEL supported cpus:
Sep 07 13:16:03 homelab kernel:   Intel GenuineIntel
Sep 07 13:16:03 homelab kernel:   AMD AuthenticAMD
Sep 07 13:16:03 homelab kernel:   Hygon HygonGenuine
Sep 07 13:16:03 homelab kernel:   Centaur CentaurHauls
Sep 07 13:16:03 homelab kernel:   zhaoxin   Shanghai 
Sep 07 13:16:03 homelab kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Sep 07 13:16:03 homelab kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Sep 07 13:16:03 homelab kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Sep 07 13:16:03 homelab kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Sep 07 13:16:03 homelab kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Sep 07 13:16:03 homelab kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Sep 07 13:16:03 homelab kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Sep 07 13:16:03 homelab kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Sep 07 13:16:03 homelab kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Sep 07 13:16:03 homelab kernel: signal: max sigframe size: 2032
Sep 07 13:16:03 homelab kernel: BIOS-provided physical RAM map:
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x0000000000100000-0x000000006cf53fff] usable
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x000000006cf54000-0x000000006f057fff] reserved
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x000000006f058000-0x000000006f0d9fff] ACPI data
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x000000006f0da000-0x000000006f0e0fff] ACPI NVS
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x000000006f0e1000-0x000000006f0e1fff] reserved
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x000000006f0e2000-0x000000006f1b3fff] ACPI NVS
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x000000006f1b4000-0x000000006fba2fff] reserved
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x000000006fba3000-0x000000006fc4dfff] type 20
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x000000006fc4e000-0x000000006fc4efff] usable
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x000000006fc4f000-0x000000007cffffff] reserved
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 07 13:16:03 homelab kernel: BIOS-e820: [mem 0x0000000100000000-0x0000001080ffffff] usable
Sep 07 13:16:03 homelab kernel: NX (Execute Disable) protection: active
Sep 07 13:16:03 homelab kernel: efi: EFI v2.70 by American Megatrends
Sep 07 13:16:03 homelab kernel: efi: ACPI=0x6f119000 ACPI 2.0=0x6f119014 TPMFinalLog=0x6f121000 SMBIOS=0x6f9df000 SMBIOS 3.0=0x6f9de000 MEMATTR=0x66a81018 ESRT=0x68fe8c98
Sep 07 13:16:03 homelab kernel: secureboot: Secure boot could not be determined (mode 0)
Sep 07 13:16:03 homelab kernel: SMBIOS 3.3.0 present.
Sep 07 13:16:03 homelab kernel: DMI: Intel(R) Client Systems NUC10i7FNH/NUC10i7FNB, BIOS FNCML357.0052.2021.0409.1144 04/09/2021
Sep 07 13:16:03 homelab kernel: tsc: Detected 1600.000 MHz processor
Sep 07 13:16:03 homelab kernel: tsc: Detected 1599.960 MHz TSC
Sep 07 13:16:03 homelab kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 07 13:16:03 homelab kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 07 13:16:03 homelab kernel: last_pfn = 0x1081000 max_arch_pfn = 0x400000000
Sep 07 13:16:03 homelab kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT 
Sep 07 13:16:03 homelab kernel: last_pfn = 0x6fc4f max_arch_pfn = 0x400000000
Sep 07 13:16:03 homelab kernel: esrt: Reserving ESRT space from 0x0000000068fe8c98 to 0x0000000068fe8cd0.
Sep 07 13:16:03 homelab kernel: e820: update [mem 0x68fe8000-0x68fe8fff] usable ==> reserved
Sep 07 13:16:03 homelab kernel: Using GB pages for direct mapping

Irgendwelche Ideen woran das liegen könnte.

P.S.: WoL ist bei mir aus.

Beste Grüße
Simon
 
Hallo zusammen,

kurzes Updates was ich bis jetzt schon probiert habe.
  1. Alle USB Festplatten ausgesteckt = selbes ergbnis
  2. Lan Kabel ausgesteckt = selbes ergenis
Was noch in Planung ist:
BIOS anschauen
BIOS updaten.

Ansonsten bin Ich der Meinung das es am Kernel Update liegt da ja zuvor alles Funktioniert hat.

Beste Grüße
Simon
 
Ich würde auf eine Einstellung in BIOS oder auf einen Hardware-Defekt tippen. Schau dir mal an, was das BIOS zu den Power-Optionen zu sagen hat.
 
er bleibt wieder aus ;), was geholfen hat was ich jetzt leider nicht auf jeden fall war wol im bios aktviert habe ich dann deaktviert und ein bios update war auch noch verfügbar
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!