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

Андрей

New Member
Jan 22, 2025
3
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: 4
  • Screenshot_3.jpg
    Screenshot_3.jpg
    56.2 KB · Views: 4
  • Screenshot_1.jpg
    Screenshot_1.jpg
    33.5 KB · Views: 4
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: 2
  • Screenshot_2.jpg
    Screenshot_2.jpg
    36.6 KB · Views: 2
  • Screenshot_3.jpg
    Screenshot_3.jpg
    98.2 KB · Views: 2
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)
 

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!