You are not logged in.
- Topics: Active | Unanswered
#1 2026-05-01 13:13:07
- 5hridhyan
- Member
- Registered: 2025-12-25
- Posts: 825
- Website
NVME invalid field in command (4.5M) errors
└─$ sudo smartctl -a /dev/nvme0
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-7.0.2-arch1-1] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: ABSSDNVMe512GB
Serial Number: 221151208290
Firmware Version: EDFB00.7
PCI Vendor/Subsystem ID: 0x1987
IEEE OUI Identifier: 0x8c1f64
Total NVM Capacity: 512,110,190,592 [512 GB]
Unallocated NVM Capacity: 0
Controller ID: 1
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512,110,190,592 [512 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 8c1f64 70300002d0
Local Time is: Fri May 1 18:18:08 2026 IST
Firmware Updates (0x12): 1 Slot, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005e): Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0a): Cmd_Eff_Lg Telmtry_Lg
Maximum Data Transfer Size: 64 Pages
Warning Comp. Temp. Threshold: 85 Celsius
Critical Comp. Temp. Threshold: 95 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 4.50W - - 0 0 0 0 0 0
1 + 2.70W - - 1 1 1 1 0 0
2 + 2.16W - - 2 2 2 2 0 0
3 - 0.0700W - - 3 3 3 3 1000 1000
4 - 0.0050W - - 4 4 4 4 5000 45000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 1
1 - 4096 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning: 0x00
Temperature: 32 Celsius
Available Spare: 100%
Available Spare Threshold: 5%
Percentage Used: 4%
Data Units Read: 38,140,030 [19.5 TB]
Data Units Written: 39,188,268 [20.0 TB]
Host Read Commands: 526,319,954
Host Write Commands: 650,479,831
Controller Busy Time: 2,810
Power Cycles: 7,247
Power On Hours: 4,701
Unsafe Shutdowns: 443
Media and Data Integrity Errors: 0
Error Information Log Entries: 4,561,694
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 49 Celsius
Error Information (NVMe Log 0x01, 16 of 16 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message
0 4561694 0 0x0014 0x4004 - 0 0 - Invalid Field in Command
1 4561693 0 0xf014 0x4004 - 0 0 - Invalid Field in Command
2 4561692 0 0xe014 0x4004 - 0 0 - Invalid Field in Command
3 4561691 0 0xd014 0x4004 - 0 0 - Invalid Field in Command
4 4561690 0 0xc014 0x4004 - 0 0 - Invalid Field in Command
5 4561689 0 0x8009 0x4004 - 0 0 - Invalid Field in Command
6 4561688 0 0xb014 0x4004 - 0 0 - Invalid Field in Command
7 4561687 0 0xa014 0x4005 - 0 0 - Invalid Field in Command
8 4561686 0 0x7009 0x4005 - 0 0 - Invalid Field in Command
9 4561685 0 0x9014 0x4005 - 0 0 - Invalid Field in Command
10 4561684 0 0x8014 0x4005 - 0 0 - Invalid Field in Command
11 4561683 0 0x7014 0x4005 - 0 0 - Invalid Field in Command
12 4561682 0 0x6014 0x4005 - 0 0 - Invalid Field in Command
13 4561681 0 0x5014 0x4005 - 0 0 - Invalid Field in Command
14 4561680 0 0x6009 0x4005 - 0 0 - Invalid Field in Command
15 4561679 0 0x4014 0x4004 - 0 0 - Invalid Field in Command
Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Short Completed without error 7 - - - - -currently
└─$ uname -r
7.0.2-arch1-1└─$ sudo dmesg | grep -i nvme
[ 1.627549] nvme nvme0: pci function 0000:01:00.0
[ 1.649698] nvme nvme0: missing or invalid SUBNQN field.
[ 1.707847] nvme nvme0: allocated 128 MiB host memory buffer (32 segments).
[ 1.713720] nvme nvme0: 8/0/0 default/read/poll queues
[ 1.719051] nvme0n1: p1 p2 p3 p4
[ 27.196044] nvme nvme0: using unchecked data buffer
[ 9270.072322] nvme nvme0: 8/0/0 default/read/poll queues
[11555.638166] nvme nvme0: 8/0/0 default/read/poll queues
[12450.491223] nvme nvme0: 8/0/0 default/read/poll queues
[16447.017679] nvme nvme0: 8/0/0 default/read/poll queues
[26311.697283] nvme nvme0: 8/0/0 default/read/poll queuesWhat typically causes such a high number of "Invalid Field in Command" errors? related to APST/ASPM or NVMe power management?
should I proactively mitigate it?
I sometimes face lags for microseconds, although it might be a factor w/ hyprland, drivers/AMD, High RAM pressure, I couldn't determine if SSD also responsible for this, since I ran smartctl today, I got those questions... Also for context those micro stutters are NOT reproducible....
Edit:
Typo
Last edited by 5hridhyan (2026-05-04 01:59:46)
Offline
#2 2026-05-01 14:32:57
- dimich
- Member
- From: Kharkiv, Ukraine
- Registered: 2009-11-03
- Posts: 631
Re: NVME invalid field in command (4.5M) errors
5hridhyan wrote:
What typically causes such a high number of "Invalid Field in Command" errors?
Typically protocol mismatch between NVMe driver and firmware.
5hridhyan wrote:
related to APST/ASPM or NVMe power management?
Maybe.
Try to set "nvme_core.default_ps_max_latency_us=0" or/and "nvme.noacpi=1" kernel parameters.
Online
#3 2026-05-01 15:35:07
- 5hridhyan
- Member
- Registered: 2025-12-25
- Posts: 825
- Website
Re: NVME invalid field in command (4.5M) errors
I see, currently I have spaghetti of those
└─$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=c0ae4a73-5088-4f7e-b497-ca1a4baa4dbe rw rootflags=subvol=@ cryptdevice=UUID=63984f23-816d-48d8-9493-119bf15c9a26:root zswap.enabled=1 rootfstype=btrfs loglevel=7 amdgpu.dpm=1 nvme_core.default_ps_max_latency_us=0 nvme.noacpi=1 lsm=landlock,lockdown,yama,apparmor,bpf apparmor=1 security=apparmor iommu=pt amdgpu.noretry=0 pcie_aspm=off amdgpu.aspm=0 amdgpu.gpu_recovery=1 "acpi_osi=Windows 2015" resume=UUID=c0ae4a73-5088-4f7e-b497-ca1a4baa4dbe resume_offset=17423426also w/ those params, it's still increasing
└─$ sudo smartctl -a /dev/nvme0
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-7.0.3-arch1-1] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: ABSSDNVMe512GB
Serial Number: 221151208290
Firmware Version: EDFB00.7
PCI Vendor/Subsystem ID: 0x1987
IEEE OUI Identifier: 0x8c1f64
Total NVM Capacity: 512,110,190,592 [512 GB]
Unallocated NVM Capacity: 0
Controller ID: 1
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512,110,190,592 [512 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 8c1f64 70300002d0
Local Time is: Fri May 1 20:53:21 2026 IST
Firmware Updates (0x12): 1 Slot, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005e): Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0a): Cmd_Eff_Lg Telmtry_Lg
Maximum Data Transfer Size: 64 Pages
Warning Comp. Temp. Threshold: 85 Celsius
Critical Comp. Temp. Threshold: 95 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 4.50W - - 0 0 0 0 0 0
1 + 2.70W - - 1 1 1 1 0 0
2 + 2.16W - - 2 2 2 2 0 0
3 - 0.0700W - - 3 3 3 3 1000 1000
4 - 0.0050W - - 4 4 4 4 5000 45000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 1
1 - 4096 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning: 0x00
Temperature: 33 Celsius
Available Spare: 100%
Available Spare Threshold: 5%
Percentage Used: 4%
Data Units Read: 38,148,116 [19.5 TB]
Data Units Written: 39,197,202 [20.0 TB]
Host Read Commands: 526,414,572
Host Write Commands: 650,702,116
Controller Busy Time: 2,811
Power Cycles: 7,248
Power On Hours: 4,702
Unsafe Shutdowns: 443
Media and Data Integrity Errors: 0
Error Information Log Entries: 4,565,953
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 50 Celsius
Error Information (NVMe Log 0x01, 16 of 16 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message
0 4565953 0 0xc004 0x4005 - 0 0 - Invalid Field in Command
1 4565952 0 0xb004 0x4005 - 0 0 - Invalid Field in Command
2 4565951 0 0x3014 0x4005 - 0 0 - Invalid Field in Command
3 4565950 0 0xa004 0x4004 - 0 0 - Invalid Field in Command
4 4565949 0 0x9004 0x4004 - 0 0 - Invalid Field in Command
5 4565948 0 0xe01d 0x4004 - 0 0 - Invalid Field in Command
6 4565947 0 0x2014 0x4004 - 0 0 - Invalid Field in Command
7 4565946 0 0x1014 0x4004 - 0 0 - Invalid Field in Command
8 4565945 0 0xc01d 0x4004 - 0 0 - Invalid Field in Command
9 4565944 0 0x0014 0x4004 - 0 0 - Invalid Field in Command
10 4565943 0 0xf014 0x4004 - 0 0 - Invalid Field in Command
11 4565942 0 0xe014 0x4005 - 0 0 - Invalid Field in Command
12 4565941 0 0xa01d 0x4005 - 0 0 - Invalid Field in Command
13 4565940 0 0x801d 0x4005 - 0 0 - Invalid Field in Command
14 4565939 0 0xd014 0x4005 - 0 0 - Invalid Field in Command
15 4565938 0 0x601c 0x4005 - 0 0 - Invalid Field in Command
Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Short Completed without error 7 - - - - -Before: 4,561,694 errors
After: 4,565,953 errors
Difference: +4,259 errors
I guess I'd hit 5M very soon
I'd like to know if the kernel itself is doing smtg fancy outside powersaving...
Offline
#4 2026-05-01 17:33:10
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,857
Re: NVME invalid field in command (4.5M) errors
Does https://man.archlinux.org/man/nvme.1 reveal any details about the bogus command?
Offline
#5 2026-05-01 17:38:18
- 5hridhyan
- Member
- Registered: 2025-12-25
- Posts: 825
- Website
Re: NVME invalid field in command (4.5M) errors
└─$ sudo nvme error-log /dev/nvme0
Error Log Entries for device:nvme0 entries:16
.................
Entry[ 0]
.................
error_count : 4570980
sqid : 0
cmdid : 0x401b
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0x1
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 1]
.................
error_count : 4570979
sqid : 0
cmdid : 0x9006
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0x1
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 2]
.................
error_count : 4570978
sqid : 0
cmdid : 0x8006
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0x1
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 3]
.................
error_count : 4570977
sqid : 0
cmdid : 0x7006
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0x1
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 4]
.................
error_count : 4570976
sqid : 0
cmdid : 0xf016
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 5]
.................
error_count : 4570975
sqid : 0
cmdid : 0x4018
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 6]
.................
error_count : 4570974
sqid : 0
cmdid : 0xe016
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 7]
.................
error_count : 4570973
sqid : 0
cmdid : 0xd016
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 8]
.................
error_count : 4570972
sqid : 0
cmdid : 0xc016
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 9]
.................
error_count : 4570971
sqid : 0
cmdid : 0xb016
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[10]
.................
error_count : 4570970
sqid : 0
cmdid : 0x3018
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[11]
.................
error_count : 4570969
sqid : 0
cmdid : 0x2018
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[12]
.................
error_count : 4570968
sqid : 0
cmdid : 0x1018
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0x1
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[13]
.................
error_count : 4570967
sqid : 0
cmdid : 0x1b
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0x1
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[14]
.................
error_count : 4570966
sqid : 0
cmdid : 0x5007
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0x1
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[15]
.................
error_count : 4570965
sqid : 0
cmdid : 0x4007
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0x1
parm_err_loc : 0xffff
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................└─$ sudo nvme id-ctrl /dev/nvme0
NVME Identify Controller:
vid : 0x1987
ssvid : 0x1987
sn : 221151208290
mn : ABSSDNVMe512GB
fr : EDFB00.7
rab : 1
ieee : 8c1f64
cmic : 0
mdts : 6
cntlid : 0x1
ver : 0x10300
rtd3r : 0x124f80
rtd3e : 0x2191c0
oaes : 0
ctratt : 0
rrls : 0
bpcap : 0
nssl : 0
plsi : 0
cntrltype : 0
fguid : 00000000-0000-0000-0000-000000000000
crdt1 : 0
crdt2 : 0
crdt3 : 0
crcap : 0
nvmsr : 0
vwci : 0
mec : 0
oacs : 0x17
acl : 0
aerl : 3
frmw : 0x12
lpa : 0xa
elpe : 15
npss : 4
avscc : 0x1
apsta : 0x1
wctemp : 358
cctemp : 368
mtfa : 100
hmpre : 139672
hmmin : 546
tnvmcap : 512110190592
unvmcap : 0
rpmbs : 0
edstt : 30
dsto : 1
fwug : 4
kas : 1
hctma : 0x1
mntmt : 273
mxtmt : 358
sanicap : 0x6
hmminds : 0
hmmaxd : 0
nsetidmax : 0
endgidmax : 0
anatt : 0
anacap : 0
anagrpmax : 0
nanagrpid : 0
pels : 0
domainid : 0
kpioc : 0
mptfawr : 0
megcap : 0
tmpthha : 0
cqt : 0
sqes : 0x66
cqes : 0x44
maxcmd : 0
nn : 1
oncs : 0x5e
fuses : 0
fna : 0x1
vwc : 0x1
awun : 255
awupf : 0
icsvscc : 1
nwpc : 0
acwu : 0
ocfs : 0
sgls : 0
mnan : 0
maxdna : 0
maxcna : 0
oaqd : 0
rhiri : 0
hirt : 0
cmmrtd : 0
nmmrtd : 0
minmrtg : 0
maxmrtg : 0
trattr : 0
mcudmq : 0
mnsudmq : 0
mcmr : 0
nmcmr : 0
mcdqpc : 0
subnqn :
ioccsz : 0
iorcsz : 0
icdoff : 0
fcatt : 0
msdbd : 0
ofcs : 0
ps 0 : mp:4.50W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
ps 1 : mp:2.70W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
ps 2 : mp:2.16W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
ps 3 : mp:0.0700W non-operational enlat:1000 exlat:1000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
ps 4 : mp:0.0050W non-operational enlat:5000 exlat:45000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -Offline
#6 2026-05-01 17:54:42
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,857
Re: NVME invalid field in command (4.5M) errors
Do you keep smartd running?
https://github.com/linux-nvme/nvme-cli/issues/1224
Offline
#7 2026-05-01 17:58:02
- 5hridhyan
- Member
- Registered: 2025-12-25
- Posts: 825
- Website
Re: NVME invalid field in command (4.5M) errors
Do you keep smartd running?
I was, but now I stoped and disabled and it's been two hours or more also disabled/stoped udisks2
└─$ systemctl status smartd
○ smartd.service - Self Monitoring and Reporting Technology (SMART) Daemon
Loaded: loaded (/usr/lib/systemd/system/smartd.service; disabled; preset: disabled)
Active: inactive (dead)
Docs: man:smartd(8)
man:smartd.conf(5)
May 01 20:44:21 ATRNXA smartd[1268]: Device: /dev/nvme0, is SMART capable. Adding to "monitor" list.
May 01 20:44:21 ATRNXA smartd[1268]: Monitoring 0 ATA/SATA, 0 SCSI/SAS and 1 NVMe devices
May 01 20:44:21 ATRNXA systemd[1]: Started Self Monitoring and Reporting Technology (SMART) Daemon.
May 01 21:14:21 ATRNXA smartd[1268]: Device: /dev/nvme0, NVMe error count increased from 4565593 to 4566819 (0 new, 16 ignored, 1210 unknown)
May 01 21:44:21 ATRNXA smartd[1268]: Device: /dev/nvme0, NVMe error count increased from 4566819 to 4568029 (0 new, 16 ignored, 1194 unknown)
May 01 21:48:09 ATRNXA smartd[1268]: smartd received signal 15: Terminated
May 01 21:48:09 ATRNXA smartd[1268]: smartd is exiting (exit status 0)
May 01 21:48:09 ATRNXA systemd[1]: Stopping Self Monitoring and Reporting Technology (SMART) Daemon...
May 01 21:48:09 ATRNXA systemd[1]: smartd.service: Deactivated successfully.
May 01 21:48:09 ATRNXA systemd[1]: Stopped Self Monitoring and Reporting Technology (SMART) Daemon.└─$ systemctl status udisks2
○ udisks2.service - Disk Manager
Loaded: loaded (/usr/lib/systemd/system/udisks2.service; disabled; preset: disabled)
Active: inactive (dead)
Docs: man:udisks(8)
May 01 21:06:51 ATRNXA systemd[1]: Starting Disk Manager...
May 01 21:06:52 ATRNXA systemd[1]: Started Disk Manager.
May 01 21:48:13 ATRNXA systemd[1]: Stopping Disk Manager...
May 01 21:48:13 ATRNXA systemd[1]: udisks2.service: Deactivated successfully.
May 01 21:48:13 ATRNXA systemd[1]: Stopped Disk Manager.but it's still increasing, currently: 4,571,839
Offline
#8 2026-05-01 18:38:14
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,857
Re: NVME invalid field in command (4.5M) errors
Do you have a non-btrfs partition on that drive? Can you boot some live distro, only interact w/ non-btrfs partitions and see whether the error keeps counting up? (Leaving aside that every smartctl might increment it, Heisenstyle)
The mount the btrfs partition and see whether that ramps up the errors?
Offline
#9 2026-05-01 19:05:53
- 5hridhyan
- Member
- Registered: 2025-12-25
- Posts: 825
- Website
Re: NVME invalid field in command (4.5M) errors
True, I have a non-btrfs partition on the same disk
└─$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
zram0 swap 1 zram0 efde3790-3650-4907-9426-2a844ffd68d9 [SWAP]
nvme0n1
├─nvme0n1p1 vfat FAT32 38E3-7BAD 763.2M 25% /boot
├─nvme0n1p2 crypto_LUKS 2 63984f23-816d-48d8-9493-119bf15c9a26
│ └─root btrfs c0ae4a73-5088-4f7e-b497-ca1a4baa4dbe 133.2G 52% /var/log
│ /var/cache/pacman/pkg
│ /home
│ /
├─nvme0n1p3 apfs 54e376ed-1395-460e-8292-ab20e77e3858
└─nvme0n1p4 exfat 1.0 The_Bridge EFA6-EE9E apfs: macOS, exfat: bridge(sharing files b/w btrfs and apfs)
Before macOS: 4,574,048
After macOS: 4,574,139
Total Increase: +91 errors (I guess it's issue w/ btrfs because if it was w/ macOS/apfs it would have increased thousands, but +91 is I guess when I booted btrfs or Ill need two sane days, one day full Linux, other day macOS and then compare it...) is there any tool on mac like smartctl (or is it available for mac? I have macOS12 so compiling w/ brew gonna be painful 
) I duckduckgo'ed it, I didn't find such tool...
Last edited by 5hridhyan (2026-05-01 19:09:13)
Offline
#10 2026-05-01 19:21:41
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,857
Re: NVME invalid field in command (4.5M) errors
https://www.heise.de/download/product/s … 4/download but the plan was to discriminate the FS from some Linux (the install iso) kernel anyway.
But if this is a macbook there could be some drive quirks (Apple-customization)
Offline
#11 2026-05-01 20:12:51
- dimich
- Member
- From: Kharkiv, Ukraine
- Registered: 2009-11-03
- Posts: 631
Re: NVME invalid field in command (4.5M) errors
Average error rate between #7 and OP seems about 0.6 errors/s (very rough). Assuming uniform rate, errors should start to occur roughly 3 month of power on state ago to reach 4M (if counter hasn't yet overflowed).
If you want to mess around, you can try to trace commands sent to controller.
tracefs seems mounted and tracing is enabled by default in Arch (if not, "mount -t tracefs none /sys/kernel/tracing" and "echo 1 > /sys/kernel/tracing/tracing_on").
In one terminal watch trace output:
# cat /sys/kernel/tracing/trace_pipeIn another start command tracing:
# echo 1 > /sys/kernel/tracing/events/nvme/nvme_setup_cmd/enableIt would be interesting if it was possible to determine which command/commands cause error counter to increase.
Also you can try to enable one of quirks for nvme module with quirks= module parameter. E.g. NVME_QUIRK_NO_APST, NVME_QUIRK_NO_DEEPEST_PS or NVME_QUIRK_QDEPTH_ONE.
Last edited by dimich (2026-05-01 20:18:44)
Online
#12 2026-05-02 02:44:22
- 5hridhyan
- Member
- Registered: 2025-12-25
- Posts: 825
- Website
Re: NVME invalid field in command (4.5M) errors
thanks for the tool
and no, this is not a macbook, it's the same HP 
trace commands sent to controller
Ah sh!t, https://github.com/AdnanHodzic/auto-cpufreq was the culprit, see this https://pastebin.com/viW5eanq
auto-cpufreq-1304 [002] ..... 328.578579: nvme_setup_cmd: nvme0: qid=0, cmdid=32781, nsid=4294967295, flags=0x0, meta=0x0, cmd=(nvme_admin_get_log_page cdw10=02 00 7f 00...)
auto-cpufreq-1304 [002] ..... 328.583908: nvme_setup_cmd: nvme0: qid=0, cmdid=32782, nsid=0, flags=0x0, meta=0x0, cmd=(nvme_admin_get_features fid=0x4, sel=0x0, cdw11=0x0)After stopping it's service, the error count hasn't moved so far
┌──(shridhyan@ATRNXA)-[~]
└─$ sudo nvme error-log /dev/nvme0 | grep error_count | head -1
error_count : 4575256
┌──(shridhyan@ATRNXA)-[~]
└─$ sudo nvme error-log /dev/nvme0 | grep error_count | head -1
error_count : 4575256I even created, and restarted the service
└─$ cat /etc/auto-cpufreq.conf
[system]
nvme_smart_polling = falsebut it still climbed
─$ sudo nvme error-log /dev/nvme0 | grep error_count | head -1
error_count : 4575277
─$ sudo systemctl disable --now auto-cpufreq
─$ sudo nvme error-log /dev/nvme0 | grep error_count | head -1
error_count : 4575298
─$ sudo nvme error-log /dev/nvme0 | grep error_count | head -1
error_count : 4575298
─$ sudo nvme error-log /dev/nvme0 | grep error_count | head -1
error_count : 4575298anyways thanks for the help everyone,
since we got the "culprit" and it doesn't seem there is a way to tell auto-cpufreq to NOT to mess w/ those admin commands, disabling it makes sense, hence
marking the thread as solved
Offline
#13 2026-05-03 04:01:40
- 5hridhyan
- Member
- Registered: 2025-12-25
- Posts: 825
- Website
Re: NVME invalid field in command (4.5M) errors
There is still one service or thing that's probing the same error
└─$ sudo smartctl -a /dev/nvme0
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-7.0.3-arch1-1] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: ABSSDNVMe512GB
Serial Number: 221151208290
Firmware Version: EDFB00.7
PCI Vendor/Subsystem ID: 0x1987
IEEE OUI Identifier: 0x8c1f64
Total NVM Capacity: 512,110,190,592 [512 GB]
Unallocated NVM Capacity: 0
Controller ID: 1
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512,110,190,592 [512 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 8c1f64 70300002d0
Local Time is: Sun May 3 09:18:18 2026 IST
Firmware Updates (0x12): 1 Slot, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005e): Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0a): Cmd_Eff_Lg Telmtry_Lg
Maximum Data Transfer Size: 64 Pages
Warning Comp. Temp. Threshold: 85 Celsius
Critical Comp. Temp. Threshold: 95 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 4.50W - - 0 0 0 0 0 0
1 + 2.70W - - 1 1 1 1 0 0
2 + 2.16W - - 2 2 2 2 0 0
3 - 0.0700W - - 3 3 3 3 1000 1000
4 - 0.0050W - - 4 4 4 4 5000 45000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 1
1 - 4096 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning: 0x00
Temperature: 29 Celsius
Available Spare: 100%
Available Spare Threshold: 5%
Percentage Used: 4%
Data Units Read: 38,183,757 [19.5 TB]
Data Units Written: 39,244,243 [20.0 TB]
Host Read Commands: 526,982,273
Host Write Commands: 651,989,857
Controller Busy Time: 2,814
Power Cycles: 7,255
Power On Hours: 4,714
Unsafe Shutdowns: 443
Media and Data Integrity Errors: 0
Error Information Log Entries: 4,575,300
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 45 Celsius
Error Information (NVMe Log 0x01, 16 of 16 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS Message
0 4575300 0 0x600c 0x4005 0x028 0 0 - Invalid Field in Command
Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Short Completed without error 7 - - - - -└─$ sudo nvme id-ctrl /dev/nvme0
[sudo] password for shridhyan:
NVME Identify Controller:
vid : 0x1987
ssvid : 0x1987
sn : 221151208290
mn : ABSSDNVMe512GB
fr : EDFB00.7
rab : 1
ieee : 8c1f64
cmic : 0
mdts : 6
cntlid : 0x1
ver : 0x10300
rtd3r : 0x124f80
rtd3e : 0x2191c0
oaes : 0
ctratt : 0
rrls : 0
bpcap : 0
nssl : 0
plsi : 0
cntrltype : 0
fguid : 00000000-0000-0000-0000-000000000000
crdt1 : 0
crdt2 : 0
crdt3 : 0
crcap : 0
nvmsr : 0
vwci : 0
mec : 0
oacs : 0x17
acl : 0
aerl : 3
frmw : 0x12
lpa : 0xa
elpe : 15
npss : 4
avscc : 0x1
apsta : 0x1
wctemp : 358
cctemp : 368
mtfa : 100
hmpre : 139672
hmmin : 546
tnvmcap : 512110190592
unvmcap : 0
rpmbs : 0
edstt : 30
dsto : 1
fwug : 4
kas : 1
hctma : 0x1
mntmt : 273
mxtmt : 358
sanicap : 0x6
hmminds : 0
hmmaxd : 0
nsetidmax : 0
endgidmax : 0
anatt : 0
anacap : 0
anagrpmax : 0
nanagrpid : 0
pels : 0
domainid : 0
kpioc : 0
mptfawr : 0
megcap : 0
tmpthha : 0
cqt : 0
sqes : 0x66
cqes : 0x44
maxcmd : 0
nn : 1
oncs : 0x5e
fuses : 0
fna : 0x1
vwc : 0x1
awun : 255
awupf : 0
icsvscc : 1
nwpc : 0
acwu : 0
ocfs : 0
sgls : 0
mnan : 0
maxdna : 0
maxcna : 0
oaqd : 0
rhiri : 0
hirt : 0
cmmrtd : 0
nmmrtd : 0
minmrtg : 0
maxmrtg : 0
trattr : 0
mcudmq : 0
mnsudmq : 0
mcmr : 0
nmcmr : 0
mcdqpc : 0
subnqn :
ioccsz : 0
iorcsz : 0
icdoff : 0
fcatt : 0
msdbd : 0
ofcs : 0
ps 0 : mp:4.50W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
ps 1 : mp:2.70W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
ps 2 : mp:2.16W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
ps 3 : mp:0.0700W non-operational enlat:1000 exlat:1000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
ps 4 : mp:0.0050W non-operational enlat:5000 exlat:45000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
┌──(shridhyan@ATRNXA)-[~]
└─$ sudo nvme error-log /dev/nvme0
Error Log Entries for device:nvme0 entries:16
.................
Entry[ 0]
.................
error_count : 4575300
sqid : 0
cmdid : 0x600c
status_field : 0x2002 (Invalid Field in Command: A reserved coded value or an unsupported value in a defined field)
phase_tag : 0x1
parm_err_loc : 0x28
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 1]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 2]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 3]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 4]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 5]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 6]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 7]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 8]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[ 9]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[10]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[11]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[12]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[13]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[14]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................
Entry[15]
.................
error_count : 0
sqid : 0
cmdid : 0
status_field : 0 (Successful Completion: The command completed without error)
phase_tag : 0
parm_err_loc : 0
lba : 0
nsid : 0
vs : 0
trtype : 0 (The transport type is not indicated or the error is not transport related)
csi : 0
opcode : 0
cs : 0
trtype_spec_info: 0
log_page_version: 0
.................Increases by one, every boot. I couldn't find that w/ trace
So there is still smtg w/ the kernel, or the driver still probing, but since my Drive's firmware is very picky about "rules" I guess I cannot fully stop what's probing
EDiT:
Finally got to know
lspci -nn | grep -i nvme
01:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation PS5013-E13 PCIe3 NVMe Controller (DRAM-less) [1987:5013] (rev 01)it's controler is phison and it's DRAM-less
Edit3:
also about it
└─$ sudo nvme id-ctrl -H /dev/nvme0
NVME Identify Controller:
vid : 0x1987
ssvid : 0x1987
sn : 221151208290
mn : ABSSDNVMe512GB
fr : EDFB00.7
rab : 1
ieee : 8c1f64
cmic : 0
[3:3] : 0 ANA not supported
[2:2] : 0 PCI
[1:1] : 0 Single Controller
[0:0] : 0 Single Port
mdts : 6
cntlid : 0x1
ver : 0x10300
rtd3r : 0x124f80
rtd3e : 0x2191c0
oaes : 0
[31:31] : 0 Discovery Log Change Notice Not Supported
[27:27] : 0 Zone Descriptor Changed Notices Not Supported
[19:19] : 0 Allocated Namespace Attribute Notices Not Supported
[17:17] : 0 Reachability Groups Change Notices Not Supported
[16:16] : 0 Temperature Threshold Hysteresis Recovery Not Supported
[15:15] : 0 Normal NSS Shutdown Event Not Supported
[14:14] : 0 Endurance Group Event Aggregate Log Page Change Notice Not Supported
[13:13] : 0 LBA Status Information Notices Not Supported
[12:12] : 0 Predictable Latency Event Aggregate Log Change Notices Not Supported
[11:11] : 0 Asymmetric Namespace Access Change Notices Not Supported
[9:9] : 0 Firmware Activation Notices Not Supported
[8:8] : 0 Namespace Attribute Changed Event Not Supported
ctratt : 0
[19:19] : 0 Flexible Data Placement Not Supported
[18:18] : 0 Reservations and Host Identifier Interaction Not Supported
[17:17] : 0 HMB Restrict Non-Operational Power State Access Not Supported
[16:16] : 0 MDTS and Size Limits Exclude Metadata Not Supported
[15:15] : 0 Extended LBA Formats Not Supported
[14:14] : 0 Delete NVM Set Not Supported
[13:13] : 0 Delete Endurance Group Not Supported
[12:12] : 0 Variable Capacity Management Not Supported
[11:11] : 0 Fixed Capacity Management Not Supported
[10:10] : 0 Multi Domain Subsystem Not Supported
[9:9] : 0 UUID List Not Supported
[8:8] : 0 SQ Associations Not Supported
[7:7] : 0 Namespace Granularity Not Supported
[6:6] : 0 Traffic Based Keep Alive Not Supported
[5:5] : 0 Predictable Latency Mode Not Supported
[4:4] : 0 Endurance Groups Not Supported
[3:3] : 0 Read Recovery Levels Not Supported
[2:2] : 0 NVM Sets Not Supported
[1:1] : 0 Non-Operational Power State Permissive Not Supported
[0:0] : 0 128-bit Host Identifier Not Supported
rrls : 0
bpcap : 0
[2:2] : 0 Set Features Boot Partition Write Protection Not Supported
[1:0] : 0 RPMB Boot Partition Write Protection Support Not Specified
nssl : 0
plsi : 0
[1:1] : 0 Power Loss Signaling with Forced Quiescence Not Supported
[0:0] : 0 Power Loss Signaling with Emergency Power Fail Not Supported
cntrltype : 0
[7:2] : 0 Reserved
[1:0] : 0 Controller type not reported
fguid : 00000000-0000-0000-0000-000000000000
crdt1 : 0
crdt2 : 0
crdt3 : 0
crcap : 0
[1:1] : 0 RGRPID may change while the namespace is attached to any controller.
[0:0] : 0 Reachability Reporting Not Supported
nvmsr : 0
[1:1] : 0 NVM subsystem Not part of an Enclosure
[0:0] : 0 NVM subsystem Not part of a Storage Device
vwci : 0
[7:7] : 0 VPD Write Cycles Remaining field is Not valid.
[6:0] : 0 VPD Write Cycles Remaining
mec : 0
[1:1] : 0 NVM subsystem Not contains a Management Endpoint on a PCIe port
[0:0] : 0 NVM subsystem Not contains a Management Endpoint on an SMBus/I2C port
oacs : 0x17
[11:11] : 0 Host Managed Live Migration Not Supported
[10:10] : 0 Lockdown Command and Feature Not Supported
[9:9] : 0 Get LBA Status Capability Not Supported
[8:8] : 0 Doorbell Buffer Config Not Supported
[7:7] : 0 Virtualization Management Not Supported
[6:6] : 0 NVMe-MI Send and Receive Not Supported
[5:5] : 0 Directives Not Supported
[4:4] : 0x1 Device Self-test Supported
[3:3] : 0 NS Management and Attachment Not Supported
[2:2] : 0x1 FW Commit and Download Supported
[1:1] : 0x1 Format NVM Supported
[0:0] : 0x1 Security Send and Receive Supported
acl : 0
aerl : 3
frmw : 0x12
[5:5] : 0 Multiple FW or Boot Update Detection Not Supported
[4:4] : 0x1 Firmware Activate Without Reset Supported
[3:1] : 0x1 Number of Firmware Slots
[0:0] : 0 Firmware Slot 1 Read/Write
lpa : 0xa
[6:6] : 0 Telemetry Log Data Area 4 Not Supported
[5:5] : 0 LID 0x0, Scope of each command in LID 0x5, 0x12, 0x13 Not Supported
[4:4] : 0 Persistent Event log Not Supported
[3:3] : 0x1 Telemetry host/controller initiated log page Supported
[2:2] : 0 Extended data for Get Log Page Not Supported
[1:1] : 0x1 Command Effects Log Page Supported
[0:0] : 0 SMART/Health Log Page per NS Not Supported
elpe : 15
[7:0] : 15 (0's based) Error Log Page Entries (ELPE)
npss : 4
[7:0] : 4 (0's based) Number of Power States Support (NPSS)
avscc : 0x1
[0:0] : 0x1 Admin Vendor Specific Commands uses NVMe Format
apsta : 0x1
[0:0] : 0x1 Autonomous Power State Transitions Supported
wctemp : 358
[15:0] : 85 °C (358 K, 185 °F) Warning Composite Temperature Threshold (WCTEMP)
cctemp : 368
[15:0] : 95 °C (368 K, 203 °F) Critical Composite Temperature Threshold (CCTEMP)
mtfa : 100
hmpre : 139672
hmmin : 546
tnvmcap : 512,110,190,592
[127:0] : 512,110,190,592
Total NVM Capacity (TNVMCAP)
unvmcap : 0
[127:0] : 0
Unallocated NVM Capacity (UNVMCAP)
rpmbs : 0
[31:24]: 0 Access Size
[23:16]: 0 Total Size
[5:3] : 0 Authentication Method
[2:0] : 0 Number of RPMB Units
edstt : 30
dsto : 1
[1:1] : 0 Host-Initiated Refresh capability Not Supported
[0:0] : 0x1 NVM subsystem supports only one device self-test operation in progress at a time
fwug : 4
kas : 1
hctma : 0x1
[0:0] : 0x1 Host Controlled Thermal Management Supported
mntmt : 273
[15:0] : 0 °C (273 K, 32 °F) Minimum Thermal Management Temperature (MNTMT)
mxtmt : 358
[15:0] : 85 °C (358 K, 185 °F) Maximum Thermal Management Temperature (MXTMT)
sanicap : 0x6
[31:30] : 0 Additional media modification after sanitize operation completes successfully is not defined
[29:29] : 0 No-Deallocate After Sanitize bit in Sanitize command Supported
[3:3] : 0 Media Verification and Post-Verification Deallocation state Not Supported
[2:2] : 0x1 Overwrite Sanitize Operation Supported
[1:1] : 0x1 Block Erase Sanitize Operation Supported
[0:0] : 0 Crypto Erase Sanitize Operation Not Supported
hmminds : 0
hmmaxd : 0
nsetidmax : 0
endgidmax : 0
anatt : 0
anacap : 0
[7:7] : 0 Non-zero group ID Not Supported
[6:6] : 0 Group ID does change
[4:4] : 0 ANA Change state Not Supported
[3:3] : 0 ANA Persistent Loss state Not Supported
[2:2] : 0 ANA Inaccessible state Not Supported
[1:1] : 0 ANA Non-optimized state Not Supported
[0:0] : 0 ANA Optimized state Not Supported
anagrpmax : 0
nanagrpid : 0
pels : 0
domainid : 0
kpioc : 0
[1:1] : 0 Key Per I/O capability Not apply to all namespaces
[0:0] : 0 Key Per I/O capability Not Supported
mptfawr : 0
megcap : 0
tmpthha : 0
[2:0] : 0 Temperature Threshold Maximum Hysteresis
cqt : 0
sqes : 0x66
[7:4] : 0x6 Max SQ Entry Size (64)
[3:0] : 0x6 Min SQ Entry Size (64)
cqes : 0x44
[7:4] : 0x4 Max CQ Entry Size (16)
[3:0] : 0x4 Min CQ Entry Size (16)
maxcmd : 0
nn : 1
oncs : 0x5e
[12:12] : 0 Namespace Zeroes Not Supported
[11:11] : 0 Maximum Write Zeroes with Deallocate Not Supported
[10:10] : 0 All Fast Copy Not Supported
[9:9] : 0 Copy Single Atomicity Not Supported
[8:8] : 0 Copy Not Supported
[7:7] : 0 Verify Not Supported
[6:6] : 0x1 Timestamp Supported
[5:5] : 0 Reservations Not Supported
[4:4] : 0x1 Save and Select Supported
[3:3] : 0x1 Write Zeroes Supported
[2:2] : 0x1 Data Set Management Supported
[1:1] : 0x1 Write Uncorrectable Supported
[0:0] : 0 Compare Not Supported
fuses : 0
[0:0] : 0 Fused Compare and Write Not Supported
fna : 0x1
[3:3] : 0 Format NVM Broadcast NSID (FFFFFFFFh) Supported
[2:2] : 0 Crypto Erase Not Supported as part of Secure Erase
[1:1] : 0 Crypto Erase Applies to Single Namespace(s)
[0:0] : 0x1 Format Applies to All Namespace(s)
vwc : 0x1
[2:1] : 0 Support for the NSID field set to FFFFFFFFh is not indicated
[0:0] : 0x1 Volatile Write Cache Present
awun : 255
awupf : 0
icsvscc : 1
[0:0] : 0x1 NVM Vendor Specific Commands uses NVMe Format
nwpc : 0
[2:2] : 0 Permanent Write Protect Not Supported
[1:1] : 0 Write Protect Until Power Supply Not Supported
[0:0] : 0 No Write Protect and Write Protect Namespace Not Supported
acwu : 0
ocfs : 0
[3:3] : 0 Controller Copy Format 3h Not Supported
[2:2] : 0 Controller Copy Format 2h Not Supported
[1:1] : 0 Controller Copy Format 1h Not Supported
[0:0] : 0 Controller Copy Format 0h Not Supported
sgls : 0
[15:8] : 0 SGL Descriptor Threshold
[1:0] : 0 Scatter-Gather Lists Not Supported
mnan : 0
maxdna : 0
maxcna : 0
oaqd : 0
rhiri : 0
hirt : 0
cmmrtd : 0
nmmrtd : 0
minmrtg : 0
maxmrtg : 0
trattr : 0
[2:2] : 0 Memory Range Tracking Length Limit
[1:1] : 0 Tracking User Data Changes Not Supported
[0:0] : 0 Track Host Memory Changes Not Supported
mcudmq : 0
mnsudmq : 0
mcmr : 0
nmcmr : 0
mcdqpc : 0
subnqn :
ioccsz : 0
iorcsz : 0
icdoff : 0
fcatt : 0
[0:0] : 0 Dynamic Controller Model
msdbd : 0
ofcs : 0
[0:0] : 0 Disconnect command Not Supported
ps 0 : mp:4.50W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
ps 1 : mp:2.70W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
ps 2 : mp:2.16W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
ps 3 : mp:0.0700W non-operational enlat:1000 exlat:1000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -
ps 4 : mp:0.0050W non-operational enlat:5000 exlat:45000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
active_power_workload:-
emergency power fail recovery time: -
forced quiescence vault time: -
emergency power fail vault time: -Last edited by 5hridhyan (2026-05-03 04:43:26)
Offline
#14 2026-05-03 07:10:27
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,857
Re: NVME invalid field in command (4.5M) errors
Increases by one, every boot. I couldn't find that w/ trace
Every boot or every smartctl call?
Offline
#15 2026-05-03 15:43:20
- 5hridhyan
- Member
- Registered: 2025-12-25
- Posts: 825
- Website
Re: NVME invalid field in command (4.5M) errors
└─$ uptime -p
up 12 hours, 16 minutesso 12 hours of uptime today, only ONE boot today, but it climbed +6
└─$ sudo smartctl -a /dev/nvme0
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-7.0.3-arch1-1] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: ABSSDNVMe512GB
Serial Number: 221151208290
Firmware Version: EDFB00.7
PCI Vendor/Subsystem ID: 0x1987
IEEE OUI Identifier: 0x8c1f64
Total NVM Capacity: 512,110,190,592 [512 GB]
Unallocated NVM Capacity: 0
Controller ID: 1
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512,110,190,592 [512 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 8c1f64 70300002d0
Local Time is: Sun May 3 21:09:11 2026 IST
Firmware Updates (0x12): 1 Slot, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005e): Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0a): Cmd_Eff_Lg Telmtry_Lg
Maximum Data Transfer Size: 64 Pages
Warning Comp. Temp. Threshold: 85 Celsius
Critical Comp. Temp. Threshold: 95 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 4.50W - - 0 0 0 0 0 0
1 + 2.70W - - 1 1 1 1 0 0
2 + 2.16W - - 2 2 2 2 0 0
3 - 0.0700W - - 3 3 3 3 1000 1000
4 - 0.0050W - - 4 4 4 4 5000 45000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 1
1 - 4096 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning: 0x00
Temperature: 35 Celsius
Available Spare: 100%
Available Spare Threshold: 5%
Percentage Used: 4%
Data Units Read: 38,199,713 [19.5 TB]
Data Units Written: 39,283,140 [20.1 TB]
Host Read Commands: 527,237,342
Host Write Commands: 652,999,883
Controller Busy Time: 2,816
Power Cycles: 7,260
Power On Hours: 4,724
Unsafe Shutdowns: 443
Media and Data Integrity Errors: 0
Error Information Log Entries: 4,575,306
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 52 Celsius
Error Information (NVMe Log 0x01, 16 of 16 entries)
No Errors Logged
Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Short Completed without error 7 - - - - -If I run smartctl HUNDRED times the count doesn't increases at all
if I run again it's still the same
└─$ sudo smartctl -a /dev/nvme0
smartctl 7.5 2025-04-30 r5714 [x86_64-linux-7.0.3-arch1-1] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: ABSSDNVMe512GB
Serial Number: 221151208290
Firmware Version: EDFB00.7
PCI Vendor/Subsystem ID: 0x1987
IEEE OUI Identifier: 0x8c1f64
Total NVM Capacity: 512,110,190,592 [512 GB]
Unallocated NVM Capacity: 0
Controller ID: 1
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512,110,190,592 [512 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 8c1f64 70300002d0
Local Time is: Sun May 3 21:12:03 2026 IST
Firmware Updates (0x12): 1 Slot, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005e): Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0a): Cmd_Eff_Lg Telmtry_Lg
Maximum Data Transfer Size: 64 Pages
Warning Comp. Temp. Threshold: 85 Celsius
Critical Comp. Temp. Threshold: 95 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 4.50W - - 0 0 0 0 0 0
1 + 2.70W - - 1 1 1 1 0 0
2 + 2.16W - - 2 2 2 2 0 0
3 - 0.0700W - - 3 3 3 3 1000 1000
4 - 0.0050W - - 4 4 4 4 5000 45000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 1
1 - 4096 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning: 0x00
Temperature: 35 Celsius
Available Spare: 100%
Available Spare Threshold: 5%
Percentage Used: 4%
Data Units Read: 38,199,720 [19.5 TB]
Data Units Written: 39,283,274 [20.1 TB]
Host Read Commands: 527,237,605
Host Write Commands: 653,003,819
Controller Busy Time: 2,816
Power Cycles: 7,260
Power On Hours: 4,724
Unsafe Shutdowns: 443
Media and Data Integrity Errors: 0
Error Information Log Entries: 4,575,306
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 53 Celsius
Error Information (NVMe Log 0x01, 16 of 16 entries)
No Errors Logged
Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
Num Test_Description Status Power_on_Hours Failing_LBA NSID Seg SCT Code
0 Short Completed without error 7 - - - - -Edit:
so not related to reboot, Something else is adding ~0.5 errors/hour...
Last edited by 5hridhyan (2026-05-03 15:53:59)
Offline
#16 2026-05-03 20:14:10
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 75,857
Re: NVME invalid field in command (4.5M) errors
Tracing doesn't reveal the offender?
Is the average also periodic (1 error every 2h) or infrequent?
Are and S3 cycles involved? Do you still have APST disabled?
Offline
#17 2026-05-04 01:54:25
- 5hridhyan
- Member
- Registered: 2025-12-25
- Posts: 825
- Website
Re: NVME invalid field in command (4.5M) errors
Tracing might have revealed the offender, But I checked smartctl late yesterday; it doesn't show a specific pattern on when the errors log; given the 12 hour uptime and +6 errors, I could keep the trace running for 12 hours and check; but it's Monday; for another 12Hour+ uptime, I need sunday or another holiday.
tldr; I don't know if it's periodic...
However, each reboot increases the error count by +1
I tried suspend/resume; the error does not increases
Edit:
Yes, APST disabled.
Last edited by 5hridhyan (2026-05-04 01:56:31)
Offline