Error server EXT4-fs error (device dm1) ext4_jurnal_check_start:64

Андрей

New Member
Jan 22, 2025
8
0
1
Hello!
Error "EXT4-fs error (device dm1) ext4_jurnal_check_start:64" in proxmox 8.3.2
Proxmox 8.3.2
Linux pve1 6.8.12-5-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-5 (2024-12-03T10:26Z) 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: Fri Nov 29 15:17:18 +07 2024 on pts/0
root@pve1:~# fdisk -l
Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Samsung SSD 990 PRO with Heatsink 2TB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 14DE26AE-9692-4B0E-ADAB-83F8F00DA96B

Device Start End Sectors Size Type
/dev/nvme0n1p1 34 2047 2014 1007K BIOS boot
/dev/nvme0n1p2 2048 2099199 2097152 1G EFI System
/dev/nvme0n1p3 2099200 3907029134 3904929935 1.8T Linux LVM


Disk /dev/mapper/pve-swap: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-root: 96 GiB, 103079215104 bytes, 201326592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 870
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: TOSHIBA MG08ADA4
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/SSD-vm--100--disk--0: 931 GiB, 999653638144 bytes, 1952448512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D01FC996-DA11-4472-81D3-7B88384ABF79

Device Start End Sectors Size Type
/dev/mapper/SSD-vm--100--disk--0-part1 34 32767 32734 16M Microsoft reserved
/dev/mapper/SSD-vm--100--disk--0-part2 32768 1952444415 1952411648 931G Microsoft basic data


Disk /dev/mapper/Backup-vm--100--disk--0: 3.64 TiB, 3999688294400 bytes, 7811891200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9973224F-ABCF-4D24-B670-4E30FCAD494A

Device Start End Sectors Size Type
/dev/mapper/Backup-vm--100--disk--0-part1 34 32767 32734 16M Microsoft reserved
/dev/mapper/Backup-vm--100--disk--0-part2 32768 7811620863 7811588096 3.6T Microsoft basic data


Disk /dev/mapper/pve-vm--100--disk--0: 300 GiB, 322122547200 bytes, 629145600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: dos
Disk identifier: 0xbfb637b1

Device Boot Start End Sectors Size Id Type
/dev/mapper/pve-vm--100--disk--0-part1 * 2048 1126399 1124352 549M 7 HPFS/NTFS/exFAT
/dev/mapper/pve-vm--100--disk--0-part2 1126400 629039103 627912704 299.4G 7 HPFS/NTFS/exFAT
/dev/mapper/pve-vm--100--disk--0-part3 629039104 629141503 102400 50M e W95 FAT16 (LBA)


Disk /dev/mapper/pve-vm--101--disk--0: 200 GiB, 214748364800 bytes, 419430400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: dos
Disk identifier: 0x59f80405

Device Boot Start End Sectors Size Id Type
/dev/mapper/pve-vm--101--disk--0-part1 * 2048 1126399 1124352 549M 7 HPFS/NTFS/exFAT
/dev/mapper/pve-vm--101--disk--0-part2 1126400 419325951 418199552 199.4G 7 HPFS/NTFS/exFAT
/dev/mapper/pve-vm--101--disk--0-part3 419325952 419426303 100352 49M e W95 FAT16 (LBA)
 

Attachments

  • Без имени.jpg
    Без имени.jpg
    68.9 KB · Views: 6
  • Screenshot_3.jpg
    Screenshot_3.jpg
    56.2 KB · Views: 6
  • Screenshot_1.jpg
    Screenshot_1.jpg
    33.5 KB · Views: 6
Hello Андрей! It sounds like a failing drive. Is this a new server you installed PVE on? I would recommend the following:
  1. Try to check the drive S.M.A.R.T. values to see if it shows any errors.
  2. Check the journal shortly before the issues started to happen (use journalctl --since with a time shortly before the issues started to happen, e.g. 30 minutes before).
 
Hello Андрей! It sounds like a failing drive. Is this a new server you installed PVE on? I would recommend the following:
  1. Try to check the drive S.M.A.R.T. values to see if it shows any errors.
  2. Check the journal shortly before the issues started to happen (use journalctl --since with a time shortly before the issues started to happen, e.g. 30 minutes before).
Hi!
The disk is new. New system PVE installed. New power supply.
 

Attachments

  • Screenshot_1.jpg
    Screenshot_1.jpg
    63.5 KB · Views: 9
  • Screenshot_2.jpg
    Screenshot_2.jpg
    36.6 KB · Views: 9
  • Screenshot_3.jpg
    Screenshot_3.jpg
    98.2 KB · Views: 9
Jan 21 09:35:37 pve1 kernel: ata6: SATA max UDMA/133 abar m2048@0xf732b000 port 0xf732b380 irq 132 lpm-pol 0
Jan 21 09:35:37 pve1 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 21 09:35:37 pve1 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 21 09:35:37 pve1 kernel: ata6: SATA link down (SStatus 4 SControl 300)
Jan 21 09:35:37 pve1 kernel: ata3: SATA link down (SStatus 4 SControl 300)
Jan 21 09:35:37 pve1 kernel: ata4: SATA link down (SStatus 4 SControl 300)
Jan 21 09:35:37 pve1 kernel: ata5: SATA link down (SStatus 4 SControl 300)
Jan 21 09:35:37 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Jan 21 09:35:37 pve1 kernel:
Jan 21 09:35:37 pve1 kernel: No Local Variables are initialized for Method [_GTF]
Jan 21 09:35:37 pve1 kernel:
Jan 21 09:35:37 pve1 kernel: No Arguments are initialized for method [_GTF]
Jan 21 09:35:37 pve1 kernel:
Jan 21 09:35:37 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Jan 21 09:35:37 pve1 kernel: ata1.00: supports DRM functions and may not be fully accessible
Jan 21 09:35:37 pve1 kernel: ata1.00: ATA-11: Samsung SSD 870 EVO 1TB, SVT02B6Q, max UDMA/133
Jan 21 09:35:37 pve1 kernel: ata1.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32), AA
Jan 21 09:35:37 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Jan 21 09:35:37 pve1 kernel:
Jan 21 09:35:37 pve1 kernel: No Local Variables are initialized for Method [_GTF]
Jan 21 09:35:37 pve1 kernel:
Jan 21 09:35:37 pve1 kernel: No Arguments are initialized for method [_GTF]
Jan 21 09:35:37 pve1 kernel:
Jan 21 09:35:37 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Jan 21 09:35:37 pve1 kernel: ata2.00: ATA-10: TOSHIBA MG08ADA400N, 4304, max UDMA/133
Jan 21 09:35:37 pve1 kernel: ata2.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Jan 21 09:35:37 pve1 kernel: ata2.00: Features: NCQ-prio
Jan 21 09:35:37 pve1 kernel: ata1.00: Features: Trust Dev-Sleep NCQ-sndrcv
Jan 21 09:35:37 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Jan 21 09:35:37 pve1 kernel:
Jan 21 09:35:37 pve1 kernel: No Local Variables are initialized for Method [_GTF]
Jan 21 09:35:37 pve1 kernel:
Jan 21 09:35:37 pve1 kernel: No Arguments are initialized for method [_GTF]
Jan 21 09:35:37 pve1 kernel:
Jan 21 09:35:37 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Jan 21 09:35:37 pve1 kernel: ata1.00: supports DRM functions and may not be fully accessible
Jan 21 09:35:37 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Jan 21 09:35:37 pve1 kernel:
Jan 21 09:35:37 pve1 kernel: No Local Variables are initialized for Method [_GTF]
Jan 21 09:35:37 pve1 kernel:
Jan 21 09:35:37 pve1 kernel: No Arguments are initialized for method [_GTF]
Jan 21 09:35:37 pve1 kernel:
Jan 21 09:35:37 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
 
The ACPI errors you are seeing should not be related to your issues. Generally, this means that your motherboard's BIOS does not implement ACPI correctly, causing the kernel to print error messages. This can be often fixed with a BIOS update (the recommended solution if the errors annoy you). However, as long as this doesn't cause other issues (or spam the journal the whole time), you can also ignore the errors.

Also, if I'm not mistaken, the journal logs you posted here are, more or less, from the time when you posted in the forum, instead of the time of the crash (feel free to correct me if I'm wrong). Could you please post the journal shortly before the time of the crash and during the crash?
 
Hi!
Help me,

Logs in 20.01.25:
Jan 20 00:00:18 pve1 systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
Jan 20 00:00:18 pve1 systemd[1]: Starting logrotate.service - Rotate log files...
Jan 20 00:00:18 pve1 systemd[1]: dpkg-db-backup.service: Deactivated successfully.
Jan 20 00:00:18 pve1 systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
Jan 20 00:00:18 pve1 pvefw-logger[802911]: received terminate request (signal)
Jan 20 00:00:18 pve1 pvefw-logger[802911]: stopping pvefw logger
Jan 20 00:00:18 pve1 systemd[1]: Stopping pvefw-logger.service - Proxmox VE firewall logger...
Jan 20 00:00:19 pve1 systemd[1]: pvefw-logger.service: Deactivated successfully.
Jan 20 00:00:19 pve1 systemd[1]: Stopped pvefw-logger.service - Proxmox VE firewall logger.
Jan 20 00:00:19 pve1 systemd[1]: pvefw-logger.service: Consumed 4.062s CPU time.
Jan 20 00:00:19 pve1 systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger...
Jan 20 00:00:19 pve1 pvefw-logger[1038496]: starting pvefw logger
Jan 20 00:00:19 pve1 systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.
Jan 20 00:00:19 pve1 systemd[1]: logrotate.service: Deactivated successfully.
Jan 20 00:00:19 pve1 systemd[1]: Finished logrotate.service - Rotate log files.
Jan 20 00:17:01 pve1 CRON[1041176]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 00:17:01 pve1 CRON[1041177]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 00:17:01 pve1 CRON[1041176]: pam_unix(cron:session): session closed for user root
Jan 20 01:17:01 pve1 CRON[1051008]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 01:17:01 pve1 CRON[1051009]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 01:17:01 pve1 CRON[1051008]: pam_unix(cron:session): session closed for user root
Jan 20 01:35:42 pve1 systemd[1]: Starting fstrim.service - Discard unused blocks on filesystems from /etc/fstab...
Jan 20 01:35:46 pve1 fstrim[1054050]: /: 77.4 GiB (83114258432 bytes) trimmed on /dev/pve/root
Jan 20 01:35:46 pve1 systemd[1]: fstrim.service: Deactivated successfully.
Jan 20 01:35:46 pve1 systemd[1]: Finished fstrim.service - Discard unused blocks on filesystems from /etc/fstab.
Jan 20 01:42:31 pve1 smartd[703]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 72 to 60
Jan 20 02:12:31 pve1 smartd[703]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 60 to 71
Jan 20 02:17:01 pve1 CRON[1061095]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 02:17:01 pve1 CRON[1061096]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 02:17:01 pve1 CRON[1061095]: pam_unix(cron:session): session closed for user root
Jan 20 02:42:31 pve1 smartd[703]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 71 to 72
Jan 20 03:10:01 pve1 CRON[1069709]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 03:10:01 pve1 CRON[1069710]: (root) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /sbin/e2scrub_all -A -r)
Jan 20 03:10:01 pve1 CRON[1069709]: pam_unix(cron:session): session closed for user root
Jan 20 03:17:01 pve1 CRON[1070833]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 03:17:01 pve1 CRON[1070834]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 03:17:01 pve1 CRON[1070833]: pam_unix(cron:session): session closed for user root
Jan 20 03:34:18 pve1 systemd[1]: Starting pve-daily-update.service - Daily PVE download activities...
Jan 20 03:34:22 pve1 pveupdate[1073619]: <root@pam> starting task UPID:pve1:001061D8:0258C421:678D61CE:aptupdate::root@pam:
Jan 20 03:34:24 pve1 pveupdate[1073624]: update new package list: /var/lib/pve-manager/pkgupdates
Jan 20 03:34:26 pve1 pveupdate[1073619]: <root@pam> end task UPID:pve1:001061D8:0258C421:678D61CE:aptupdate::root@pam: OK
Jan 20 03:34:26 pve1 systemd[1]: pve-daily-update.service: Deactivated successfully.
Jan 20 03:34:26 pve1 systemd[1]: Finished pve-daily-update.service - Daily PVE download activities.
Jan 20 03:34:26 pve1 systemd[1]: pve-daily-update.service: Consumed 2.656s CPU time.
Jan 20 04:17:01 pve1 CRON[1080995]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 04:17:01 pve1 CRON[1080996]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 04:17:01 pve1 CRON[1080995]: pam_unix(cron:session): session closed for user root
Jan 20 05:17:01 pve1 CRON[1090669]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 05:17:01 pve1 CRON[1090670]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 05:17:01 pve1 CRON[1090669]: pam_unix(cron:session): session closed for user root
Jan 20 06:17:01 pve1 CRON[1100359]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 06:17:01 pve1 CRON[1100360]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 06:17:01 pve1 CRON[1100359]: pam_unix(cron:session): session closed for user root
Jan 20 06:20:18 pve1 systemd[1]: Starting apt-daily-upgrade.service - Daily apt upgrade and clean activities...
Jan 20 06:20:19 pve1 systemd[1]: apt-daily-upgrade.service: Deactivated successfully.
Jan 20 06:20:19 pve1 systemd[1]: Finished apt-daily-upgrade.service - Daily apt upgrade and clean activities.
Jan 20 06:25:01 pve1 CRON[1101685]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 06:25:01 pve1 CRON[1101686]: (root) CMD (test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
Jan 20 06:25:01 pve1 CRON[1101685]: pam_unix(cron:session): session closed for user root
Jan 20 07:17:01 pve1 CRON[1110114]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 07:17:01 pve1 CRON[1110115]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 07:17:01 pve1 CRON[1110114]: pam_unix(cron:session): session closed for user root
Jan 20 08:17:01 pve1 CRON[1119818]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 08:17:01 pve1 CRON[1119819]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 08:17:01 pve1 CRON[1119818]: pam_unix(cron:session): session closed for user root
Jan 20 09:02:42 pve1 systemd[1]: Starting man-db.service - Daily man-db regeneration...
Jan 20 09:02:43 pve1 systemd[1]: man-db.service: Deactivated successfully.
Jan 20 09:02:43 pve1 systemd[1]: Finished man-db.service - Daily man-db regeneration.
Jan 20 09:17:01 pve1 CRON[1129472]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 09:17:01 pve1 CRON[1129473]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 09:17:01 pve1 CRON[1129472]: pam_unix(cron:session): session closed for user root
Jan 20 09:43:55 pve1 pvestatd[1034]: auth key pair too old, rotating..
Jan 20 10:17:01 pve1 CRON[1139903]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 10:17:01 pve1 CRON[1139904]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 10:17:01 pve1 CRON[1139903]: pam_unix(cron:session): session closed for user root
Jan 20 11:17:01 pve1 CRON[1149842]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 11:17:01 pve1 CRON[1149843]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 11:17:01 pve1 CRON[1149842]: pam_unix(cron:session): session closed for user root
Jan 20 11:42:31 pve1 smartd[703]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 72 to 73
Jan 20 12:17:01 pve1 CRON[1159555]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 12:17:01 pve1 CRON[1159556]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 12:17:01 pve1 CRON[1159555]: pam_unix(cron:session): session closed for user root
Jan 20 13:17:01 pve1 CRON[1169384]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 13:17:01 pve1 CRON[1169385]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 13:17:01 pve1 CRON[1169384]: pam_unix(cron:session): session closed for user root
Jan 20 14:17:01 pve1 CRON[1179151]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 14:17:01 pve1 CRON[1179153]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 14:17:01 pve1 CRON[1179151]: pam_unix(cron:session): session closed for user root
Jan 20 14:32:42 pve1 systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
Jan 20 14:32:42 pve1 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Jan 20 14:32:42 pve1 systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
Jan 20 14:32:42 pve1 systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
Jan 20 15:17:01 pve1 CRON[1189176]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 15:17:01 pve1 CRON[1189177]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 15:17:01 pve1 CRON[1189176]: pam_unix(cron:session): session closed for user root
Jan 20 15:43:18 pve1 systemd[1]: Starting apt-daily.service - Daily apt download activities...
Jan 20 15:43:19 pve1 systemd[1]: apt-daily.service: Deactivated successfully.
Jan 20 15:43:19 pve1 systemd[1]: Finished apt-daily.service - Daily apt download activities.
Jan 20 16:17:01 pve1 CRON[1199302]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 16:17:01 pve1 CRON[1199303]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 16:17:01 pve1 CRON[1199302]: pam_unix(cron:session): session closed for user root
Jan 20 16:42:31 pve1 smartd[703]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 73 to 72
Jan 20 17:17:01 pve1 CRON[1209415]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 17:17:01 pve1 CRON[1209416]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 17:17:01 pve1 CRON[1209415]: pam_unix(cron:session): session closed for user root
Jan 20 18:17:01 pve1 CRON[1219359]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 18:17:01 pve1 CRON[1219360]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 18:17:01 pve1 CRON[1219359]: pam_unix(cron:session): session closed for user root
Jan 20 19:12:31 pve1 smartd[703]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 72 to 73
Jan 20 19:17:01 pve1 CRON[1229088]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 19:17:01 pve1 CRON[1229089]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 19:17:01 pve1 CRON[1229088]: pam_unix(cron:session): session closed for user root
Jan 20 20:17:01 pve1 CRON[1238695]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 20:17:01 pve1 CRON[1238696]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 20:17:01 pve1 CRON[1238695]: pam_unix(cron:session): session closed for user root
Jan 20 15:43:18 pve1 systemd[1]: Starting apt-daily.service - Daily apt download activities...
Jan 20 15:43:19 pve1 systemd[1]: apt-daily.service: Deactivated successfully.
Jan 20 15:43:19 pve1 systemd[1]: Finished apt-daily.service - Daily apt download activities.
Jan 20 16:17:01 pve1 CRON[1199302]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 16:17:01 pve1 CRON[1199303]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 16:17:01 pve1 CRON[1199302]: pam_unix(cron:session): session closed for user root
Jan 20 16:42:31 pve1 smartd[703]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 73 to 72
Jan 20 17:17:01 pve1 CRON[1209415]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 17:17:01 pve1 CRON[1209416]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 17:17:01 pve1 CRON[1209415]: pam_unix(cron:session): session closed for user root
Jan 20 18:17:01 pve1 CRON[1219359]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 18:17:01 pve1 CRON[1219360]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 18:17:01 pve1 CRON[1219359]: pam_unix(cron:session): session closed for user root
Jan 20 19:12:31 pve1 smartd[703]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 72 to 73
Jan 20 19:17:01 pve1 CRON[1229088]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 19:17:01 pve1 CRON[1229089]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 19:17:01 pve1 CRON[1229088]: pam_unix(cron:session): session closed for user root
Jan 20 20:17:01 pve1 CRON[1238695]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 20:17:01 pve1 CRON[1238696]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 20:17:01 pve1 CRON[1238695]: pam_unix(cron:session): session closed for user root
Jan 20 21:17:01 pve1 CRON[1248395]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 21:17:01 pve1 CRON[1248396]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 21:17:01 pve1 CRON[1248395]: pam_unix(cron:session): session closed for user root
Jan 20 22:01:18 pve1 systemd[1]: Starting apt-daily.service - Daily apt download activities...
Jan 20 22:01:19 pve1 systemd[1]: apt-daily.service: Deactivated successfully.
Jan 20 22:01:19 pve1 systemd[1]: Finished apt-daily.service - Daily apt download activities.
Jan 20 22:17:01 pve1 CRON[1258043]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 22:17:01 pve1 CRON[1258044]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 22:17:01 pve1 CRON[1258043]: pam_unix(cron:session): session closed for user root
Jan 20 23:17:01 pve1 CRON[1267721]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 20 23:17:01 pve1 CRON[1267722]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Jan 20 23:17:01 pve1 CRON[1267721]: pam_unix(cron:session): session closed for user root
 
Total errors:

-- Boot 0f4111b9dbb540bebc31fb49980ae4d0 --
Dec 16 09:42:32 pve1 kernel: x86/cpu: SGX disabled by BIOS.
Dec 16 09:42:32 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Dec 16 09:42:32 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Dec 16 09:42:32 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Dec 16 09:42:32 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Dec 16 09:42:32 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Dec 16 09:42:32 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Dec 16 09:42:32 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Dec 16 09:42:32 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
-- Boot d43e5574bc3b491aa9b0ab7440aefc18 --
Dec 26 09:42:41 pve1 kernel: x86/cpu: SGX disabled by BIOS.
Dec 26 09:42:41 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Dec 26 09:42:41 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Dec 26 09:42:41 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Dec 26 09:42:41 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Dec 26 09:42:41 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Dec 26 09:42:41 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Dec 26 09:42:41 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Dec 26 09:42:41 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Dec 26 09:49:10 pve1 pvedaemon[1058]: authentication failure; rhost=::ffff:192.168.1.107 user=root@pam msg=Authentication failure
-- Boot 1828643b947d49abb951ccc3c9add3bc --
Dec 27 13:53:45 pve1 kernel: x86/cpu: SGX disabled by BIOS.
Dec 27 13:53:45 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Dec 27 13:53:45 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Dec 27 13:53:45 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Dec 27 13:53:45 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Dec 27 13:53:45 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Dec 27 13:53:45 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Dec 27 13:53:45 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Dec 27 13:53:45 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Dec 28 00:38:24 pve1 pveproxy[128267]: got inotify poll request in wrong process - disabling inotify
Jan 09 10:49:46 pve1 pvedaemon[3095893]: VM 100 qmp command failed - VM 100 qmp command 'guest-network-get-interfaces' failed - got timeout
Jan 09 13:18:55 pve1 pvedaemon[3140911]: VM 100 qmp command failed - VM 100 qmp command 'guest-network-get-interfaces' failed - got timeout
Jan 11 00:00:34 pve1 pveproxy[3533296]: got inotify poll request in wrong process - disabling inotify
-- Boot 040629ee589248728c7aa91ccbe8b6c6 --
Jan 15 14:12:29 pve1 kernel: x86/cpu: SGX disabled by BIOS.
Jan 15 14:12:30 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Jan 15 14:12:30 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Jan 15 14:12:30 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Jan 15 14:12:30 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Jan 15 14:12:30 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Jan 15 14:12:30 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Jan 15 14:12:30 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Jan 15 14:12:30 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
-- Boot e68dbb476e464bef85ce687be3b4e08b --
Jan 21 09:35:37 pve1 kernel: x86/cpu: SGX disabled by BIOS.
Jan 21 09:35:37 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)
Jan 21 09:35:37 pve1 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Jan 21 09:35:37 pve1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20230628/psargs-330)


root@pve1:~# journalctl -p crit
Nov 23 13:15:52 pve1 smartd[610]: Device: /dev/nvme0, number of Error Log entries increased from 0 to 1
-- Boot 1faf27ce933f44e2af298e6fb94034e4 --
Nov 23 13:28:36 pve1 kernel: watchdog: watchdog0: watchdog did not stop!
-- Boot 517a91bc7f454c0cb6d3a7987c29c404 --
Nov 24 04:34:34 pve1 kernel: watchdog: watchdog0: watchdog did not stop!
-- Boot 129f988806d344938a97d4d3eb9f54cb --
Nov 24 17:31:55 pve1 smartd[669]: Device: /dev/nvme1, number of Error Log entries increased from 826 to 913
Nov 24 17:32:23 pve1 kernel: watchdog: watchdog0: watchdog did not stop!
-- Boot d54bc0eeb74a478fa12fca92d6a510d7 --
Nov 24 23:37:49 pve1 smartd[669]: Device: /dev/nvme0, number of Error Log entries increased from 0 to 1
 

Attachments

I see you have a Gigabyte B365M DS3H motherboard with BIOS version F5. The latest BIOS version for your motherboard is F7. If you are annoyed by the ACPI errors, you can try to install the latest BIOS version and see if it helps. However, I doubt this would help with your filesystem errors.

Seeing the long pause in your journal of the attached file, it seems that the filesystem errors begin to happen before the errors can be written to the journal. In other words, we don't have proper error messages.

Also, I'm a bit confused by the fact that there are many errors on /dev/nvme1, but there is no such device in the newer journal.

You can try reinstalling PVE on another disk to see if the problems still occur. Don't forget to make backups and restore them after reinstalling.
 
The logs look similar to the previous ones. For me it looks like a faulty drive, even if the S.M.A.R.T. values are fine. You should try to install PVE on another disk to see if the problems still occur. Last but not least, if you have important data on that disk, don't forget to make backups in case the disk will fail soon.
 
The first time there was a failure in early November, I did a hardware diagnostic, RAM, disks
 

Attachments

  • Screenshot_1.png
    Screenshot_1.png
    251.8 KB · Views: 5
  • Screenshot_3.png
    Screenshot_3.png
    272.1 KB · Views: 5
Hi!
Updated the BIOS up f7, installed a new disk, the same model, the error is the same
 

Attachments

  • photo_2025-02-18_20-46-49.jpg
    photo_2025-02-18_20-46-49.jpg
    123.4 KB · Views: 3
  • Screenshot_3.jpg
    Screenshot_3.jpg
    40.4 KB · Views: 3
  • Screenshot_4.jpg
    Screenshot_4.jpg
    139.6 KB · Views: 3
  • Без имени.jpg
    Без имени.jpg
    97.1 KB · Views: 3
Hi! Thanks for trying it out. Too bad it didn't help.

As long as you don't have any other issues, you can simply ignore the ACPI errors. While they might theoretically be solved in a future BIOS update, looking at the updates list, Gigabyte will probably not release new updates. Either way, these errors have nothing to do with your filesystem errors.

I would usually recommend trying another M.2 slot on your motherboard, just to rule out that the motherboard's M.2 slot is faulty - but, as far as I see, your motherboard only has one M.2 slot. Otherwise I would recommend trying another drive (either M.2 or SATA), which will probably solve your issues. You will have to play around with your hardware (as I suggested above), as there's not much else we can suggest, I'm afraid.