Ext4FS errors

Hello everyone. I have a Seagate P5 SSD that recently has been randomly kicking out errors like this and crashing the computer:

[xxxxx.xxxxxx] Ext4-Fs error: (device nvme0n1p3): ext4_wait_block_bitmap:531: comm IPC I/O Parent: Cannot read block bitmap - block_group = 59 block_bitmap = 1572875
[xxxxx.xxxxxx]Ext4-FS error (device nvme0n1p3) _ext4_find_entry:1612: inode #xxxxx comm systemd: reading directory iblock 0

After that it locks up my system, forcing me to reboot using the magic SYSRQ key.

I ran FSCK and it found no errors. I also checked ssd health using seatools and it said I had 98% life left on the SSD. I’m assuming Linux is trying to warn me that my file system is corrupted somehow and I’ll need to format the partition.

Is that all I’ll need to do? Or is my SSD bad? Why isn’t Linux finding any file system errrors?

Should I try to get all the data off the SSD and RMA or just backup and reformat the partition? The problematic partition is a ext4 home partition.

Currently rebooting the laptop results in no data loss and it boots just as fast as it always has.

1 Like

Can yıu send output of sudo smartctl -a /dev/nvme0n1?

I think these drives use (APST) Autonomous Power State Transitions. You can check this out.
This may be the issue or not as it usually causes freezes which in turn may throw the errors?

To mitigate it include the line nvme_core.default_ps_max_latency_us=0 in the GRUB_CMDLINE_LINUX_DEFAULT options. Then update grub.

This is just a guess. You’d have to try the kernel parameter. If all is okay then you could run the long test first.

sudo smartctl --test=long /dev/nvme0n1

Then to check it after it completes

sudo smartctl -a /dev/nvme0n1
1 Like

Seemed to be an issue with the NVME connector (my macOS partition was acting similar). Thank goodness no data corruption happened! Thanks for the support!