Ext4 error on Fedora

XDimensioN · 05-16-2020, 04:12 PM

Hi

I am using Fedora 31 on Asus Laptop X550LC. Recently, my system either keeps crashing or freezing. When It crashes, I have the following error:

Code:

EXT4-fs error (device dm-1): __ext4_find_entry:1536 inode #26217
97: comm gdm-session-wor: reading directory lblock 0

After power-off and start the laptop, Grub fails to start. In fact, the Bios screen appears. This situation can last a couple of time before being able to boot Fedora again.

I have this problem with these kernel versions:

Code:

kernel-5.6.11-200.fc31.x86_64
kernel-5.6.8-200.fc31.x86_64
kernel-5.6.7-200.fc31.x86_64

With the oldest kernel, I noticed that issue only occurs when resuming from suspend. With the others, It happens randomly.

I thought that it could be a bios problem, I upgrade to the latest version and I still got the same issue. I also tried with fsck by adding these kernel boot parameters:

Code:

fsck.mode=force fsck.repair=yes

It did not help.

Here is the information about dm-1:

Code:

Name:              fedora-root
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        1
Event number:      0
Major, minor:      253, 1
Number of targets: 1
UUID: LVM-3Gb8yG3fh1ditXUQHYORtfBzmJBJ7J56Bsj9xDCc86YaBwBhqMTNW9HUdx5o2q1n

Here are informations about my hard drive (taken from gnome-disks):

Code:

Model: ST1000LM024 HN-M101MBB (2AR20002)
Size: 1.0 TB (1,000,204,886,016 bytes)
Partitioning: GUID Partition Table
Serial Number: S2Y4J9ADA18385
Assessement: Disk is OK (31° C / 88° F)

Any comment or suggestion is welcome
Thanks in advance.

BW-userx · 05-16-2020, 04:52 PM

Try booting a live os with gparted and run fix disk on it. See if that works.

ondoho · 05-17-2020, 02:53 AM

Quote:

Originally Posted by XDimensioN

After power-off and start the laptop, Grub fails to start. In fact, the Bios screen appears. This situation can last a couple of time before being able to boot Fedora again.

Sounds like a problem outside of your Linux install.
Possibly a failing hard drive.
I agree with the previous poster, try to boot omitting the hard drive (i.e. a live distro), then try to run deep diagnostics on it, possibly even fix it.

Or, stop. First, back up important data! Now!