NVMe Error - Delayed block allocation failed for inode ...

F

feigenblatt

New Member
Jun 17, 2025
7
1
3
My 3 week old, single node proxmox froze and I saw this on the terminal:

[90866.627297) EXT4-fs (dm-1): Delayed block allocation failed for inode 3540431 at logical offset 364339 with max blocks 1024 with error 5
[90866.627320] EXT4-fs (dm-1): This should not happen!! Data will be lost
[90866.627320)
[90866.627335) EXT4-fs error (device dm-1) in ext4_do_uritepages:2724: IO failure
[90866.627354] EXT4-fs (dm-1) : Remounting filesystem read-only
[90866.627547] EXT4-fs (dm-1): ext4_do_ur itepages: jbd2_start: 1010 pages, 4 1019 pae 70 3549461 91 0 9540461; err -5
(90866.633412) EXT4-fs (dm-1): ext_do_uritepages: jbd2_start: 9223372036854775960 pages, ino 3540461; err -5

The machine was completely frozen and needed a hard reboot.

From systemct.:

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 39 Celsius
Available Spare: 100%
Available Spare Threshold: 5%
Percentage Used: 0%
Data Units Read: 12,161,670 [6.22 TB]
Data Units Written: 2,198,214 [1.12 TB]
Host Read Commands: 98,618,676
Host Write Commands: 26,123,373
Controller Busy Time: 137
Power Cycles: 27
Power On Hours: 355
Unsafe Shutdowns: 6
Media and Data Integrity Errors: 0
Error Information Log Entries: 126
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 39 Celsius
Temperature Sensor 2: 45 Celsius
Temperature Sensor 8: 39 Celsius


The NVMe *seems* healthy, right?
Any advice on how to track this, or if proxmox/debian needs any special config for NVMes?
The computer is a (also 3 week old) Beelink EQ14 and it has been running 24/7 without issues, but then it crashed twice since this morning.

Thanks!
 
Last edited:
Looks like a drive error but it could also be memory corruption (or worse). Start testing and/or replacing hardware parts to see if you can find the culprit.
 
feigenblatt said:
My 3 week old, single node proxmox froze and I saw this on the terminal:

[90866.627297) EXT4-fs (dm-1): Delayed block allocation failed for inode 3540431 at logical offset 364339 with max blocks 1024 with error 5
[90866.627320] EXT4-fs (dm-1): This should not happen!! Data will be lost
[90866.627320)
[90866.627335) EXT4-fs error (device dm-1) in ext4_do_uritepages:2724: IO failure
[90866.627354] EXT4-fs (dm-1) : Remounting filesystem read-only
[90866.627547] EXT4-fs (dm-1): ext4_do_ur itepages: jbd2_start: 1010 pages, 4 1019 pae 70 3549461 91 0 9540461; err -5
(90866.633412) EXT4-fs (dm-1): ext_do_uritepages: jbd2_start: 9223372036854775960 pages, ino 3540461; err -5

The machine was completely frozen and needed a hard reboot.

From systemct.:

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 39 Celsius
Available Spare: 100%
Available Spare Threshold: 5%
Percentage Used: 0%
Data Units Read: 12,161,670 [6.22 TB]
Data Units Written: 2,198,214 [1.12 TB]
Host Read Commands: 98,618,676
Host Write Commands: 26,123,373
Controller Busy Time: 137
Power Cycles: 27
Power On Hours: 355
Unsafe Shutdowns: 6
Media and Data Integrity Errors: 0
Error Information Log Entries: 126
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 39 Celsius
Temperature Sensor 2: 45 Celsius
Temperature Sensor 8: 39 Celsius


The NVMe *seems* healthy, right?
Any advice on how to track this, or if proxmox/debian needs any special config for NVMes?
The computer is a (also 3 week old) Beelink EQ14 and it has been running 24/7 without issues, but then it crashed twice since this morning.

Thanks!
Click to expand...

What was the solution? We have a similar problem on one of our proxmox hosts (this one is not that old, it was build earlier this year), it occured yesterday for the first time, and today again ;(
 

Attachments

  • Screenshot From 2025-10-07 09-05-42.png
    Screenshot From 2025-10-07 09-05-42.png
    221.8 KB · Views: 6
Last edited:
But smart is just fine...
Code: 
root@proxmox15:~# smartctl -a /dev/nvme0n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.8.4-2-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 990 PRO 1TB
Serial Number:                      S7HDNJ0Y124709Y
Firmware Version:                   5B2QJXD7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      1
NVMe Version:                       2.0
Number of Namespaces:               1
Namespace 1 Size/Capacity:          1,000,204,886,016 [1.00 TB]
Namespace 1 Utilization:            32,740,478,976 [32.7 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 4151439cdc
Local Time is:                      Tue Oct  7 10:45:05 2025 CEST
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0055):     Comp DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x2f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg *Other*
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     9.61W       -        -    0  0  0  0        0       0
 1 +     9.61W       -        -    1  1  1  1        0       0
 2 +     9.61W       -        -    2  2  2  2        0       0
 3 -   0.0500W       -        -    3  3  3  3     4200    3500
 4 -   0.0050W       -        -    4  4  4  4     2200   22200

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        40 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    60,091 [30.7 GB]
Data Units Written:                 3,474,927 [1.77 TB]
Host Read Commands:                 619,124
Host Write Commands:                74,521,214
Controller Busy Time:               602
Power Cycles:                       24
Power On Hours:                     2,761
Unsafe Shutdowns:                   18
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               40 Celsius
Temperature Sensor 2:               47 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged
 
You must log in or register to reply here.
Top Bottom