Endeavouros freezes sometimes and leads to force restart

mdan · April 15, 2025, 1:07pm

I’ve built myself a new pc and been using EndeavourOS for a few months now, and in general, I’m loving it. However, I also been getting some random freezes where I’m forced to hard reset the PC. I’m not sure what’s causing it, although, I noticed it seems to happen after the pc is idle for a time.

Would you please help me troubleshoot and find the cause of these freezes?

Hardware info - inxi -Fxxc0z | eos-sendlog: https://0x0.st/8fWr.txt

Partition and format info - lsblk -o name,type,size,PTTYPE,FSTYPE: https://0x0.st/8fWs.txt

Boot log from the last freeze. (I left the PC on all night and when I woke up I tried to use it, the mouse responded but it froze immediately forcing me to do a hard reset) - journalctl -r -b -1 -k | eos-sendlog: https://0x0.st/8fWi.txt

ricklinux · April 15, 2025, 1:19pm

It’s showing a file system error on reading this drive.

ID-3: /dev/sda vendor: Samsung model: SSD 870 EVO 4TB size: 3.64 TiB
    speed: 6.0 Gb/s serial: <filter>

Edit: Boot log

Apr 15 08:00:08 daniel-box7 kernel: EXT4-fs error (device sda1): ext4_lookup:1813: inode #238834309: comm rm: iget: checksum invalid

Edit: Not sure what you are using this drive for and if it is in your fstab? Is it set up to automatically mount on boot?

fred666 · April 15, 2025, 1:57pm

use fsck to check the drive/partition.

I’m not sure this causes your freeze though

mdan · April 15, 2025, 2:20pm

@ricklinux I use that drive for general storage (files, images, videos, timeshift backups, etc) and it’s setup to automatically mount on boot.

@fred666 I get this when running sudo fsck -f /dev/sda

fsck from util-linux 2.41
e2fsck 1.47.2 (1-Jan-2025)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

/dev/sda contains `DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 "Invalid partition table" at offset 0x17b "Error loading operating system" at offset 0x19a "Missing operating system"; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 4294967295 sectors' data

Stephane · April 15, 2025, 2:26pm

you CANT REPAIR a whole disk like that
you have to repair each partition thare are required
can you report

sudo parted -l 
sudo cat /etc/fstab

weewilliewayne · April 15, 2025, 2:30pm

It’s strange, your lsblk says sda is gpt/ext4, but on the fsck it “contains a dos/mbr boot sector.” I suspect this is where your problems originate.

mdan · April 15, 2025, 2:49pm

@Stephane this is the output

sudo parted -l

Model: ATA Samsung SSD 870 (scsi)
Disk /dev/sda: 4001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      17.4kB  4001GB  4001GB  ext4


Model: KINGSTON SFYRD2000G (nvme)
Disk /dev/nvme0n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name         Flags
 1      2097kB  1076MB  1074MB  fat32        EFI          boot, esp
 2      1076MB  2000GB  1999GB  ext4         endeavouros


Model: KINGSTON SFYRD2000G (nvme)
Disk /dev/nvme1n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      17.4kB  2000GB  2000GB  ext4

sudo cat /etc/fstab

# <file system> <mount point> <type> <options> <dump> <pass>

UUID=5597-2F95	/boot/efi	vfat	fmask=0137,dmask=0027	0	2
UUID=92ab9bfd-1edc-4b28-be40-c4035d31f2c1	/	ext4	noatime	0	1
/swapfile	swap	swap	defaults	0	0
tmpfs	/tmp	tmpfs	noatime,mode=1777	0	0
UUID=7fd9b68f-024e-491a-b32f-72238c3a7617	/run/media/danielm/Games	ext4	nofail	0	0
UUID=97d4a36e-21ca-4763-9e6d-22b533d73471	/run/media/danielm/GeneralStorage/	ext4	nofail	00

Stephane · April 15, 2025, 2:52pm

you should try with

sudo fsck -f /dev/sda1

mdan · April 15, 2025, 3:01pm

@Stephane I ran sudo fsck -f /dev/sda1, this is the output:

This particular line from the output should fix that error for that was showing on journalctl regarding inode #238834309, right?
Inode 238834309 passes checks, but checksum does not match inode. Fix<y>? yes

Stephane · April 15, 2025, 3:02pm

yes

mdan · April 15, 2025, 3:04pm

Awesome. Hopefully that’s what was causing the freezes; I’ll test it out and report back with any updates.

Thank you all for the help.

ricklinux · April 15, 2025, 3:26pm

Here’s a little info for fsck commands @Stephane gave.

https://ostechnix.com/fsck-command-examples/

mdan · April 16, 2025, 12:18am

Sadly, it seems that was not the root cause as I just had another freeze.

This is the boot log for the freeze (journalctl -r -b -1 -k | eos-sendlog): https://0x0.st/8f38.txt

Any idea what else it could be or what other logs I could check?

Edit: Looking at the full logs, it seems Brave crashed around the time the system froze; not sure if that was the cause since it also crashed earlier today without causing the freeze issue:
journalctl -r -b -1 --lines=100 | eos-sendlog
https://0x0.st/8f3O.txt

ricklinux · April 16, 2025, 12:44am

What are you using smokeping for? I see messaging related to that.

Edit: Have you tried using Firefox?

ricklinux · April 16, 2025, 12:48am

I see you’re on Bios version 2.02. There are a number of newer updates. I wonder if updating and going to a higher AMD AGESA might help?

mdan · April 16, 2025, 12:49am

I’m using it to test the latency to a couple MMO game servers that I usually play on. If you are referring to that FPing warning that is showing up, I just fixed it by increasing the step value.

I use both Brave and Firefox most of the time.

Bink · April 16, 2025, 12:54am

Welcome to the community @mdan

Can you share the output of:

sudo inxi -mxxx

Has it crashed when Brave was not running?

mdan · April 16, 2025, 12:57am

Hi @Bink, thanks.

This is the output:

  System RAM: total: 32 GiB available: 30.46 GiB used: 7.4 GiB (24.3%)
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-A DIMM 0 type: no module installed
  Device-2: Channel-A DIMM 1 type: DDR5 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: spec: 4800 MT/s actual: 6000 MT/s
    volts: 1.1 width (bits): data: 64 total: 64 manufacturer: Kingston
    part-no: KF560C36-16 serial: 1814EB89
  Device-3: Channel-B DIMM 0 type: no module installed
  Device-4: Channel-B DIMM 1 type: DDR5 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: spec: 4800 MT/s actual: 6000 MT/s
    volts: 1.1 width (bits): data: 64 total: 64 manufacturer: Kingston
    part-no: KF560C36-16 serial: 1914EB89

And to your question, yes, the freezing issue has happened as well when brave was not running.

Bink · April 16, 2025, 1:01am

Are your RAM timings and voltage using that RAM’s built-in profile, or have you manually set those?

The voltage looks a bit low.

mdan · April 16, 2025, 1:02am

I believe so, I haven’t done any tweaks to that