Arch Linux

InFerYes

Member

Registered: 2012-11-13

Posts: 62

FS (ext4) keeps corrupting on nvme disk

I have a strange issue with an nvme disk since yesterday. I want to make sure there's no software issue, however unlikely. I had this issue yesterday, fixed it but ran into the same issue today. All output below is from today.

The nvme is automatically mounted on boot, automatically configured by GNOME Disks. The last updates were on the 8th of this month. The issues started yesterday, on the 10th. Here is the output from the last update https://pastebin.com/raw/2E5N0xRE

My son has been playing War Thunder on this computer every day for the past days since this update, even yesterday when the issue started. He left his PC for a moment and when he came back he noticed his games had disappeared. The computer had been running, no sleep or shutdown/reboot. The disk was still visible in GNOME Files, but I needed to mount it again. I did not mount the disk, but first checked a few things. I opened GNOME Disks and saw there no longer was a filesystem. lsblk shows the disk's partition, but not in a little tree like the disks/partitions of the other disks (see output at bottom of this post).

I have then run sudo fsck -y /dev/nvme0n1, which took a while. It repaired the filesystem after which I mounted it. All files were "missing", moved to lost+found. Before I could use the disk in Steam again I had to run sudo chmod ugo+rw /mnt/0df9ba34-3a02-4db4-aa1c-6678949413ec/, then Steam could create it's SteamApp directory. I then had to move all files from lost+found into this SteamApp directory. For some reason, this top level directory was not found/restored. There was no corruption in these files as I verified them through Steam.

Today, as I ran into this issue again, the output of fsck was different, it didn't take so long.

dmesg: https://pastebin.com/raw/hNQ4PwF8
fsck (today): https://pastebin.com/raw/eAAyHhW7

When I wanted to mount it GNOME Files gave me this error:

mount -a:

mount: /mnt/0df9ba34-3a02-4db4-aa1c-6678949413ec: fsconfig() failed: Structure needs cleaning.
       dmesg(1) may have more information after failed mount system call.

dmesg:

[ 3468.386722] EXT4-fs (nvme0n1): warning: mounting fs with errors, running e2fsck is recommended
[ 3468.393306] EXT4-fs error (device nvme0n1): ext4_init_orphan_info:583: inode #12: comm mount: iget: special inode unallocated
[ 3468.393316] EXT4-fs (nvme0n1): get orphan inode failed
[ 3468.394126] EXT4-fs (nvme0n1): mount failed

Running fsck again:

fsck from util-linux 2.42
e2fsck 1.47.4 (6-Mar-2025)
Lexar_2TB: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Feature orphan_present is set but orphan file is clean.
Clear? yes


Lexar_2TB: ***** FILE SYSTEM WAS MODIFIED *****
Lexar_2TB: 133860/122101760 files (7.5% non-contiguous), 82102852/488378646 blocks

Now left with unmountable partition, will reboot and see if it makes any difference. Would like some advice for additional troubleshooting. I'll start RMA process regardless. I hope it's a disk issue

Additional information
smartctl gives the following output:

smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.19.11-arch1-1] (local build)
Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Lexar SSD NQ790 2TB
Serial Number:                      QBC838R012857P220C
Firmware Version:                   SN19644
PCI Vendor/Subsystem ID:            0x1d97
IEEE OUI Identifier:                0xcaf25b
Total NVM Capacity:                 2,000,398,934,016 [2.00 TB]
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       2.0
Number of Namespaces:               1
Namespace 1 Size/Capacity:          2,000,398,934,016 [2.00 TB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            caf25b 034e0004a7
Local Time is:                      Sat Apr 11 10:16:10 2026 CEST
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     90 Celsius
Critical Comp. Temp. Threshold:     95 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     6.50W       -        -    0  0  0  0        0       0
 1 +     5.80W       -        -    1  1  1  1        0       0
 2 +     3.60W       -        -    2  2  2  2        0       0
 3 -   0.0500W       -        -    3  3  3  3     5000   10000
 4 -   0.0025W       -        -    4  4  4  4     8000   45000

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, NSID 0xffffffff)
Critical Warning:                   0x00
Temperature:                        37 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    2,355,910 [1.20 TB]
Data Units Written:                 1,841,787 [942 GB]
Host Read Commands:                 7,500,507
Host Write Commands:                2,366,416
Controller Busy Time:               18
Power Cycles:                       102
Power On Hours:                     10
Unsafe Shutdowns:                   5
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               37 Celsius
Temperature Sensor 2:               26 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Self-test Log (NVMe Log 0x06, NSID 0xffffffff)
Self-test status: No self-test in progress
No Self-tests Logged

fstab:

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdb2
UUID=fa30d039-c0c8-430e-959a-cd03cd99d589	/         	ext4      	rw,relatime	0 1

# /dev/sdb1
UUID=4EC3-0AA3      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2
/dev/disk/by-uuid/0df9ba34-3a02-4db4-aa1c-6678949413ec /mnt/0df9ba34-3a02-4db4-aa1c-6678949413ec auto nosuid,nodev,nofail,x-gvfs-show 0 0

lsblk

NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda       8:0    0 447.1G  0 disk 
├─sda1    8:1    0   100M  0 part 
├─sda2    8:2    0    16M  0 part 
├─sda3    8:3    0 446.2G  0 part 
└─sda4    8:4    0   821M  0 part 
sdb       8:16   0 465.8G  0 disk 
├─sdb1    8:17   0   512M  0 part /boot
└─sdb2    8:18   0 465.3G  0 part /
zram0   253:0    0     4G  0 disk [SWAP]
nvme0n1 259:0    0   1.8T  0 disk 

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

I've been trying a couple of things, following this answer on stackoverflow: https://serverfault.com/a/1195921

When going through 1 to 4, everything went as expected, but when trying to mount the partition as read-only, it went into the same error again.

mount: /mnt/test: fsconfig() failed: Structure needs cleaning.
       dmesg(1) may have more information after failed mount system call.

It's as if the mounting itself corrupts something. All checks keep coming up positive. When I run fsck back to back, it first appears to find and fix something, but then the 2nd run comes back as clean.

[user@keel ~]$ sudo mount -o ro /dev/nvme0n1 /mnt/test
mount: /mnt/test: fsconfig() failed: Structure needs cleaning.
       dmesg(1) may have more information after failed mount system call.
[user@keel ~]$ sudo fsck.ext4 -y /dev/nvme0n1 
e2fsck 1.47.4 (6-Mar-2025)
Lexar_2TB contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Lexar_2TB: 133860/122101760 files (7.5% non-contiguous), 82102852/488378646 blocks

[user@keel ~]$ sudo fsck.ext4 -y /dev/nvme0n1 
e2fsck 1.47.4 (6-Mar-2025)
Lexar_2TB: clean, 133860/122101760 files, 82102852/488378646 blocks

[user@keel ~]$ sudo fsck.ext4 -y /dev/nvme0n1 
e2fsck 1.47.4 (6-Mar-2025)
Lexar_2TB: clean, 133860/122101760 files, 82102852/488378646 blocks

[user@keel ~]$ sudo mount -o ro /dev/nvme0n1 /mnt/test
mount: /mnt/test: fsconfig() failed: Structure needs cleaning.
       dmesg(1) may have more information after failed mount system call.

[user@keel ~]$ sudo fsck.ext4 -y /dev/nvme0n1 
e2fsck 1.47.4 (6-Mar-2025)
Lexar_2TB contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Lexar_2TB: 133860/122101760 files (7.5% non-contiguous), 82102852/488378646 blocks

[user@keel ~]$ 

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 573

Re: FS (ext4) keeps corrupting on nvme disk

lsblk shows the disk's partition

It shows NVMe namespace but no partition. Did you initially create filesystem on nvme0n1 block device without partitioning it (i.e. nvme0n1p1)?

Last edited by dimich (2026-04-11 20:47:42)

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

I can't remember how it was created. We've had this disk for 4 months now. I'm not sure if I used GNOME Disks or the CLI to do it. The naming including p1 does ring a bell. It's been working fine all this time.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,555

Re: FS (ext4) keeps corrupting on nvme disk

The naming including p1 does ring a bell.

He left his PC for a moment and when he came back he noticed his games had disappeared.

Please post your complete system journal for THAT boot, eg.

sudo journalctl -b -3 | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

for three boots ago (you can inspect the journal before piping it to c-net.org)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

Here is the output: https://paste.c-net.org/HurtsThingies

I think it might start at around 17:00.

I have removed the disk and am about to send it to the seller. Do you want me to hold onto it for a little longer for some further troubleshooting?

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

lsblk shows the disk's partition

It shows NVMe namespace but no partition. Did you initially create filesystem on nvme0n1 block device without partitioning it (i.e. nvme0n1p1)?

I have the checked the boot before that, and it appears for this system I did not partition the disk. I've been searching a bit, and found that when using the entire disk, partitioning is not needed. Is this right or wrong? This is a secondary disk, the system doesn't boot from it.

I could wipe the disk and partition it first, but that would not explain how it worked for several months and then suddenly it doesn't (and unmounts while the system was running).

All previous boots have EXT4-fs (nvme0n1): mounted filesystem in the logs (same as in the log in previous post).

Something is tripping over the mounting process now where it didn't before.

sudo fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Lexar SSD NQ790 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

frostschutz

Member

Registered: 2013-11-15

Posts: 1,639

Re: FS (ext4) keeps corrupting on nvme disk

I've been searching a bit, and found that when using the entire disk, partitioning is not needed. Is this right or wrong?

Linux (the kernel and filesystem) does not really care.

The problem is everything else. Some BIOS/UEFI expect all drives to have a partition table, and might create one (or recover a GPT backup from end of disk, if it exists).

Windows might expect one and create one.

Some Linux live CDs have support for partition creation (persistent partition and the like) and create partition tables unasked.

Plenty of partitioning tools... et cetera prolaps...

And then your filesystem header, raid header, luks header, whatever there was on the unpartitioned disk, is corrupted by the partition table that was created in its place.

So yes, partitioning is not needed technically, but still mandatory in practice. It's the standard and not using it is just more likely to invite trouble.

However very unsure that this is related to your issue in this particular case. Still you should be using partitions in the future regardless.

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 573

Re: FS (ext4) keeps corrupting on nvme disk

I think it might start at around 17:00.

The filesystem was unmounted little earlier:

Apr 10 14:58:30 keel systemd[1]: mnt-0df9ba34\x2d3a02\x2d4db4\x2daa1c\x2d6678949413ec.mount: Deactivated successfully.
Apr 10 14:58:30 keel kernel: EXT4-fs (nvme0n1): unmounting filesystem 0df9ba34-3a02-4db4-aa1c-6678949413ec.

I have removed the disk and am about to send it to the seller.

I'd expect some error messages from kernel if it was a hardware issue. Nowever, depending on how crappy firmware is, the controller can just silently return corrupted data.
Can you run extended self-test first?

# nvme device-self-test /dev/nvme0n1 -s 2

You can check progress with

# nvme device-self-test /dev/nvme0n1 -s 0

And check test results after its completion:
and after its completion check the result with

# nvme self-test-log /dev/nvme0n1

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

I was just checking:
I have another PC that has a very similar setup, the same NQ790 nvme disk bought and installed at the same time, and it also has no partitioning:

lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda       8:0    0 223,6G  0 disk 
├─sda1    8:1    0     1G  0 part /boot
└─sda2    8:2    0 222,6G  0 part /
sdb       8:16   0 111,8G  0 disk 
├─sdb1    8:17   0   100M  0 part 
├─sdb2    8:18   0    16M  0 part 
├─sdb3    8:19   0 110,3G  0 part 
├─sdb4    8:20   0   736M  0 part 
└─sdb5    8:21   0   644M  0 part 
sdc       8:32   0 931,5G  0 disk 
├─sdc1    8:33   0 656,6G  0 part 
└─sdc2    8:34   0 274,9G  0 part 
zram0   253:0    0     4G  0 disk [SWAP]
nvme0n1 259:0    0   1,8T  0 disk /mnt/18c64767-d0c4-45a6-b2c6-11f1e1a767e7

This one still mounts and works.

I have another PC that has 2 nvme (Samsung) disks come over from an older system, they are both partitioned (nvme0n1pX naming scheme in lsblk).

lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 931,5G  0 disk 
└─sda1        8:1    0 931,5G  0 part 
sdb           8:16   0 232,9G  0 disk 
└─sdb1        8:17   0 232,9G  0 part 
nvme0n1     259:0    0 931,5G  0 disk 
├─nvme0n1p1 259:1    0   512M  0 part /boot
├─nvme0n1p2 259:2    0 638,7G  0 part /
├─nvme0n1p3 259:3    0    16M  0 part 
├─nvme0n1p4 259:4    0 291,8G  0 part 
└─nvme0n1p5 259:5    0   515M  0 part 
nvme1n1     259:6    0 931,5G  0 disk 
├─nvme1n1p1 259:7    0    16M  0 part 
├─nvme1n1p2 259:8    0 698,1G  0 part 
└─nvme1n1p3 259:9    0 233,4G  0 part 

I want to be sure that partitioning that particular disk will resolve the issue, and that it's not an underlying hardware issue, now that it's still under warranty.

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

I think it might start at around 17:00.

The filesystem was unmounted little earlier:

Apr 10 14:58:30 keel systemd[1]: mnt-0df9ba34\x2d3a02\x2d4db4\x2daa1c\x2d6678949413ec.mount: Deactivated successfully.
Apr 10 14:58:30 keel kernel: EXT4-fs (nvme0n1): unmounting filesystem 0df9ba34-3a02-4db4-aa1c-6678949413ec.

I have removed the disk and am about to send it to the seller.

I'd expect some error messages from kernel if it was a hardware issue. Nowever, depending on how crappy firmware is, the controller can just silently return corrupted data.
Can you run extended self-test first?

# nvme device-self-test /dev/nvme0n1 -s 2

You can check progress with

# nvme device-self-test /dev/nvme0n1 -s 0

And check test results after its completion:
and after its completion check the result with

# nvme self-test-log /dev/nvme0n1

Here is the output:

sudo nvme self-test-log /dev/nvme0n1
Device Self Test Log for NVME device:nvme0n1
Current operation  : 0
Current Completion : 0%
Self Test Result[0]:
  Operation Result             : 0
  Self Test Code               : 2
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0xa
  Vendor Specific              : 0 0
Self Test Result[1]:
  Operation Result             : 0
  Self Test Code               : 2
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0xa
  Vendor Specific              : 0 0
Self Test Result[2]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[3]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[4]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[5]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[6]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[7]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[8]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[9]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[10]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[11]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[12]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[13]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[14]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[15]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[16]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[17]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[18]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[19]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0

edit: speaking of firmware, booted into Windows on the 11th to check for firmware updates with the Lexar software and it said it was already on the latest firmware.

Last edited by InFerYes (2026-04-13 10:37:52)

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 573

Re: FS (ext4) keeps corrupting on nvme disk

I've been searching a bit, and found that when using the entire disk, partitioning is not needed. Is this right or wrong?

Technically it's possible to have filesystem without partioning. However, it may confuse some high-level disk management software. Also I'm not sure about reliability of filesystem autodetection. Did you try to explicitly specify filesystem type for mount?

# mount -o ro -t ext4 /dev/nvme0n1 /mnt/test

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 573

Re: FS (ext4) keeps corrupting on nvme disk

Current Completion : 0%

It's not completed yet. Extended test can take up to few hours.

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

I've been searching a bit, and found that when using the entire disk, partitioning is not needed. Is this right or wrong?

Technically it's possible to have filesystem without partioning. However, it may confuse some high-level disk management software. Also I'm not sure about reliability of filesystem autodetection. Did you try to explicitly specify filesystem type for mount?

# mount -o ro -t ext4 /dev/nvme0n1 /mnt/test

Unfortunately, specifying the FS yields the same result:

sudo mount -o ro -t ext4 /dev/nvme0n1 /mnt/test
mount: /mnt/test: fsconfig() failed: Structure needs cleaning.
       dmesg(1) may have more information after failed mount system call.

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

Current Completion : 0%

It's not completed yet. Extended test can take up to few hours.

Ah, I may have misinterpreted this output, it jumped to 20% pretty quickly, then stayed there for a while, came back a few minutes later and it said no self test was running so I figured it was done:

[user@keel ~]$ sudo nvme device-self-test /dev/nvme0n1 -s 0
progress 20%
[user@keel ~]$ sudo nvme device-self-test /dev/nvme0n1 -s 0
progress 20%
[user@keel ~]$ sudo nvme device-self-test /dev/nvme0n1 -s 0
progress 20%
[user@keel ~]$ sudo nvme device-self-test /dev/nvme0n1 -s 0
no self test running

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 573

Re: FS (ext4) keeps corrupting on nvme disk

came back a few minutes later and it said no self test was running so I figured it was done

Yes, it's done. Now you can check result with "nvme self-test-log /dev/nvme0n1".

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

came back a few minutes later and it said no self test was running so I figured it was done

Yes, it's done. Now you can check result with "nvme self-test-log /dev/nvme0n1".

Sorry, there is some miscommunication. I already gave the results and you said it was 0%. The output of the log is (still) the same.

[user@keel ~]$ date
µMon Apr 13 12:59:49 PM CEST 2026
[user@keel ~]$ sudo nvme self-test-log /dev/nvme0n1
Device Self Test Log for NVME device:nvme0n1
Current operation  : 0
Current Completion : 0%
Self Test Result[0]:
  Operation Result             : 0
  Self Test Code               : 2
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0xa
  Vendor Specific              : 0 0
Self Test Result[1]:
  Operation Result             : 0
  Self Test Code               : 2
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0xa
  Vendor Specific              : 0 0
Self Test Result[2]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[3]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[4]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[5]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[6]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[7]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[8]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[9]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[10]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[11]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[12]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[13]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[14]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[15]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[16]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[17]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[18]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0
Self Test Result[19]:
  Operation Result             : 0
  Self Test Code               : 0
  Valid Diagnostic Information : 0
  Power on hours (POH)         : 0
  Vendor Specific              : 0 0

Last edited by InFerYes (2026-04-13 11:00:31)

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 573

Re: FS (ext4) keeps corrupting on nvme disk

Sorry, there is some miscommunication. I already gave the results and you said it was 0%. The output of the log is (still) the same.

Ah, sorry, now I got it. Power on hours "0xa" looks confusing. How can it be 10 hours? Maybe some firmware bug. But Operation Result shows no errors.

Can you also check error log? No need to copy all entries, just those which status_field is not 0.

# nvme error-log /dev/nvme0n1

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,555

Re: FS (ext4) keeps corrupting on nvme disk

it jumped to 20% pretty quickly, then stayed there for a while, came back a few minutes later and it said no self test was running

1d97:1602
Shenzhen Longsys Electronics Co., Ltd.
Lexar NM790 / Patriot Viper VP4300 Lite NVMe SSD (DRAM-less)

How can it be 10 hours?

When and where did you purchase that device and how much did you pay (roughly)?
There's a shit-ton of counterfeits around on temubabay the pass some GB of actual NAND as several TB but of course any attempt to address those will just result in random data corruption.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

Can you also check error log? No need to copy all entries, just those which status_field is not 0.

# nvme error-log /dev/nvme0n1

None, they are all OK

(Successful Completion: The command completed without error)

sudo nvme error-log /dev/nvme0n1 | grep status_field
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)
status_field	: 0 (Successful Completion: The command completed without error)

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

it jumped to 20% pretty quickly, then stayed there for a while, came back a few minutes later and it said no self test was running

1d97:1602
Shenzhen Longsys Electronics Co., Ltd.
Lexar NM790 / Patriot Viper VP4300 Lite NVMe SSD (DRAM-less)

How can it be 10 hours?

When and where did you purchase that device and how much did you pay (roughly)?
There's a shit-ton of counterfeits around on temubabay the pass some GB of actual NAND as several TB but of course any attempt to address those will just result in random data corruption.

I purchased the drive(s) at Galaxus for 129€ each, which was a good price at the time. I used the Tweakers.net pricewatch to find them. I find Tweakers trustable and Galaxus has a positive user rating there.

https://tweakers.net/pricewatch/2048692 … 0-2tb.html

https://www.galaxus.be/en/s1/product/le … d-47806648

Last edited by InFerYes (2026-04-13 14:53:20)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 74,555

Re: FS (ext4) keeps corrupting on nvme disk

At least the price isn't completely unrealistic (the scams are typically too good to be true) but there seems something wrong w/ the firmware (you didn't only use it for 10h in 5 minute intervals, did you?)
https://wiki.archlinux.org/title/Badblocks - the non-destructive test will take ages.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

No, this PC has been running for _hours_ sometimes.

Am I correct to use the -nsv options? The article says "Read-write test (non destructive)

When I try that command I get

sudo badblocks -nsv /dev/nvme0
badblocks: invalid starting block (0): must be less than 0

edit: had to run it on nvme0n1, it's running now.

Last edited by InFerYes (2026-04-13 15:13:23)

InFerYes

Member

Registered: 2012-11-13

Posts: 62

Re: FS (ext4) keeps corrupting on nvme disk

sudo badblocks -nsv /dev/nvme0n1 
Checking for bad blocks in non-destructive read-write mode
From block 0 to 1953514583
Checking for bad blocks (non-destructive read-write test)
Testing with random pattern: done                                                 
Pass completed, 0 bad blocks found. (0/0/0 errors)

frostschutz

Member

Registered: 2013-11-15

Posts: 1,639

Re: FS (ext4) keeps corrupting on nvme disk

Non-destructive badblocks is still risky (no guarantee data will survive if its malfunctioning storage, or faulty memory, or the like). At the same time badblocks by itself is not good enough to detect fake or misbehaving media. Since it only writes repetitive patterns. For real test you'd have to use cryptsetup (unique, random pattern provided by encryption) and then badblocks -w -t 0 -b 4096 /dev/mapper/cryptodisk (write entire disk before checking, not just one small block at a time like the non-destructive variant). But its destructive so all data gone.

Even so I think it's unlikely and seems like something else seems to be going on. Just not sure what, sorry.

Last edited by frostschutz (2026-04-14 12:35:04)