PVE Random reboot

lucascatani

Member
May 28, 2021
11
0
6
39
My pve reboots after certain time. The log:

Kernel Version
Linux 6.1.10-1-pve #1 SMP PREEMPT_DYNAMIC PVE 6.1.10-1 (2023-02-07T13:10Z

PVE Manager Version
pve-manager/8.0.4/d258a813cfa6b390


Nov 01 13:42:49 pve systemd[1]: apt-daily.service: Deactivated successfully. Nov 01 13:42:49 pve systemd[1]: Finished apt-daily.service - Daily apt download activities. Nov 01 14:06:56 pve smartd[2085]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 65 to 64 Nov 01 14:06:56 pve smartd[2085]: Device: /dev/sdc [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 66 to 65 Nov 01 14:06:56 pve smartd[2085]: Device: /dev/sdc [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 34 to 35 Nov 01 14:17:01 pve CRON[2502420]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Nov 01 14:17:03 pve CRON[2502421]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Nov 01 14:17:03 pve CRON[2502420]: pam_unix(cron:session): session closed for user root Nov 01 14:36:56 pve smartd[2085]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 64 to 60 Nov 01 14:36:56 pve smartd[2085]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 62 to 56 -- Reboot -- Nov 01 14:43:29 pve kernel: Linux version 6.1.10-1-pve (user@bookworm) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PVE 6.1.10-1 (2023-02-07T13:10Z) Nov 01 14:43:29 pve kernel: Command line: initrd=\EFI\proxmox\6.1.10-1-pve\initrd.img-6.1.10-1-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs Nov 01 14:43:29 pve kernel: KERNEL supported cpus: Nov 01 14:43:29 pve kernel: Intel GenuineIntel

Any help?
 
Hi,
please upgrade to a more recent kernel. Kernel 6.2 is the default for Proxmox VE 8 and now there is also kernel 6.5 as an opt-in: https://forum.proxmox.com/threads/o...-2-for-proxmox-ve-8-available-on-test.135635/

If the issue still occurs, you can try connecting from another host via SSH and running journalctl -f. If you are lucky, you can get an actual log there when the crash/reboot happens (it might not be persisted to disk in time).
 
Hi,
please upgrade to a more recent kernel. Kernel 6.2 is the default for Proxmox VE 8 and now there is also kernel 6.5 as an opt-in: https://forum.proxmox.com/threads/o...-2-for-proxmox-ve-8-available-on-test.135635/

If the issue still occurs, you can try connecting from another host via SSH and running journalctl -f. If you are lucky, you can get an actual log there when the crash/reboot happens (it might not be persisted to disk in time).
Here is the inicialization LOG (dmesg -T)
Bash:
[Fri Nov  3 12:54:10 2023] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Nov  3 12:54:10 2023] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Nov  3 12:54:10 2023] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Nov  3 12:54:10 2023] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[Fri Nov  3 12:54:10 2023] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)

[Fri Nov  3 12:54:10 2023] No Local Variables are initialized for Method [_GTF]

[Fri Nov  3 12:54:10 2023] No Arguments are initialized for method [_GTF]

[Fri Nov  3 12:54:10 2023] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[Fri Nov  3 12:54:10 2023] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)

[Fri Nov  3 12:54:10 2023] No Local Variables are initialized for Method [_GTF]

[Fri Nov  3 12:54:10 2023] No Arguments are initialized for method [_GTF]

[Fri Nov  3 12:54:10 2023] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[Fri Nov  3 12:54:10 2023] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)

[Fri Nov  3 12:54:10 2023] No Local Variables are initialized for Method [_GTF]

[Fri Nov  3 12:54:10 2023] No Arguments are initialized for method [_GTF]

[Fri Nov  3 12:54:10 2023] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[Fri Nov  3 12:54:10 2023] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)

[Fri Nov  3 12:54:10 2023] No Local Variables are initialized for Method [_GTF]

[Fri Nov  3 12:54:10 2023] No Arguments are initialized for method [_GTF]

[Fri Nov  3 12:54:10 2023] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[Fri Nov  3 12:54:10 2023] ata1.00: ATA-10: WDC WDS100T2G0A-00JH30, UH450400, max UDMA/133
[Fri Nov  3 12:54:10 2023] ata1.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32)
[Fri Nov  3 12:54:10 2023] ata2.00: ATA-10: WD Green 2.5 1000GB, UW210400, max UDMA/133
[Fri Nov  3 12:54:10 2023] ata2.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32)
[Fri Nov  3 12:54:10 2023] ata3.00: ATA-8: ST1000DM010-2EP102, CC43, max UDMA/133
[Fri Nov  3 12:54:10 2023] ata4.00: ATA-8: ST1000DM010-2EP102, CC43, max UDMA/133
[Fri Nov  3 12:54:10 2023] ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[Fri Nov  3 12:54:10 2023] ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[Fri Nov  3 12:54:10 2023] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)

[Fri Nov  3 12:54:10 2023] No Local Variables are initialized for Method [_GTF]

[Fri Nov  3 12:54:10 2023] No Arguments are initialized for method [_GTF]

[Fri Nov  3 12:54:10 2023] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[Fri Nov  3 12:54:10 2023] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)

[Fri Nov  3 12:54:10 2023] No Local Variables are initialized for Method [_GTF]

[Fri Nov  3 12:54:10 2023] No Arguments are initialized for method [_GTF]

[Fri Nov  3 12:54:10 2023] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT3._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[Fri Nov  3 12:54:10 2023] ata3.00: configured for UDMA/133
[Fri Nov  3 12:54:10 2023] ata4.00: configured for UDMA/133
[Fri Nov  3 12:54:10 2023] ata2.00: Features: Dev-Sleep
[Fri Nov  3 12:54:10 2023] ata1.00: Features: Dev-Sleep
[Fri Nov  3 12:54:10 2023] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)

[Fri Nov  3 12:54:10 2023] No Local Variables are initialized for Method [_GTF]

[Fri Nov  3 12:54:10 2023] No Arguments are initialized for method [_GTF]

[Fri Nov  3 12:54:10 2023] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[Fri Nov  3 12:54:10 2023] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)

[Fri Nov  3 12:54:10 2023] No Local Variables are initialized for Method [_GTF]

[Fri Nov  3 12:54:10 2023] No Arguments are initialized for method [_GTF]

[Fri Nov  3 12:54:10 2023] ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[Fri Nov  3 12:54:10 2023] ata1.00: configured for UDMA/133
[Fri Nov  3 12:54:10 2023] scsi 0:0:0:0: Direct-Access     ATA      WDC WDS100T2G0A- 0400 PQ: 0 ANSI: 5
[Fri Nov  3 12:54:10 2023] ata2.00: configured for UDMA/133
[Fri Nov  3 12:54:10 2023] sd 0:0:0:0: Attached scsi generic sg0 type 0
[Fri Nov  3 12:54:10 2023] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[Fri Nov  3 12:54:10 2023] sd 0:0:0:0: [sda] Write Protect is off
[Fri Nov  3 12:54:10 2023] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00

There some erros like "ACPI BIOS Error (bug):" and "CPI Error: Aborting method \_"

Now im testing with kernel 6.5. Soon as possible i will report to you the results.
 
Last edited:

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!