Sudden geenral system slowdown and systemd mounting problem

Quatrivius · 2020-12-14 04:04:43

My system worked fine last night, this morning, the first time I booted it, the booting process is fine, but I noticed a serious system slowdown. So, I decided to reboot it. Upon rebooting, I was greeted with this message:

Starting version 247.1-3-arch
/: clean, 132717/1638400 files, 1990346/6553600 blocks
[FAILED] Failed to start File System Check on /dev/disk/by-uuid/<DISK UUID HERE>
[DEPEND] Dependency failed for /home.
[DEPEND] Dependency failed for Local File Systems.
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):

After looking the solution on search engine, I managed to partially solve this problem by manually mounting /home partition. The problem persists through reboot/poweroff, so I have to manually mount it everytime.

Another problem, that I have at the same time, is the general system slowdown and I don't know what happened here. It took me more than 15 seconds to log in from tty1, starting X is really slow, powering off the system from command line produces the following message:

Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to power off system via logind: Connection timed out
Failed to talk to init daemon.

I had to power off the system using sudo poweroff -f

Is the problem possibly caused by a faulty package? I don't think so, because I don't remember the last time I updated my system before the problem arises, and only when I encounter this problem do I update my system, even after updating it, the problem still persists.

Logs:
dmesg output
jouirnalctl log
xorg log

seth · 2020-12-14 08:02:25

There's *plenty* of

[   88.505202] ata1: SError: { CommWake }
[   88.505207] ata1.00: failed command: READ FPDMA QUEUED
[   88.505218] ata1.00: cmd 60/08:00:d0:82:a8/00:00:06:00:00/40 tag 0 ncq dma 4096 in
                        res 41/40:00:d0:82:a8/00:00:06:00:00/40 Emask 0x409 (media error) <F>
[   88.505221] ata1.00: status: { DRDY ERR }
[   88.505224] ata1.00: error: { UNC }
[   88.505237] ata1: hard resetting link
[   88.819138] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   88.823317] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[   88.823421] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[   88.823427] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   88.826486] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[   88.826577] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[   88.826583] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[   88.827164] ata1.00: configured for UDMA/133
[   88.827264] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=3s
[   88.827271] sd 0:0:0:0: [sda] tag#0 Sense Key : Medium Error [current] 
[   88.827276] sd 0:0:0:0: [sda] tag#0 Add. Sense: Unrecovered read error - auto reallocate failed
[   88.827283] sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 06 a8 82 d0 00 00 08 00
[   88.827290] blk_update_request: I/O error, dev sda, sector 111706832 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
[   88.827300] Buffer I/O error on dev sda3, logical block 58723024, async page read
[   88.827306] Buffer I/O error on dev sda3, logical block 58723025, async page read
[   88.827310] Buffer I/O error on dev sda3, logical block 58723026, async page read
[   88.827313] Buffer I/O error on dev sda3, logical block 58723027, async page read
[   88.827316] Buffer I/O error on dev sda3, logical block 58723028, async page read
[   88.827319] Buffer I/O error on dev sda3, logical block 58723029, async page read
[   88.827322] Buffer I/O error on dev sda3, logical block 58723030, async page read
[   88.827325] Buffer I/O error on dev sda3, logical block 58723031, async page read

Either bad connector or the drive is dying.
Prefereably boot some live distro (grml) from a usb key and run

sudo smartctl -a /dev/sda

Post the output.

If it's bad (notably pending/re-allocated sectors) use backup all relevant data immediately - do not use the drive for anything else incl. a self-test before.

Quatrivius · 2020-12-16 12:45:59

This is the smartctl output.

I can't tell whether it's good or bad from the output. My HDD passed the smart test at least.

seth · 2020-12-16 16:07:06

There're two pending sectors (is the drive mounted at that time) but it doesn't look bad™

I still don't like the "Unrecovered read error - auto reallocate failed" message.

From the live distro, mount the partitions on sda to eg. /mnt and run

find /mnt -type f -exec cat '{}' > /dev/null \;

That's gonna take a while but will read all files and yell an error if the file can't be read.

Quatrivius · 2020-12-20 01:51:24

Hey seth, thank you for your response, but I think I'll leave this problem at this point. I have made backups, so if my HDD fails, it fails. With that said, I would like a mod to close this thread, Thank you.

seth · 2020-12-20 08:56:31

You can report the thread for deletion, if you want: https://bbs.archlinux.org/misc.php?report=1943550
Otherwise edit the initial post and alter the subject to include sth. like "[abandoned]" - do not use "[closed]", that's to indicate that a mod has locked the thread (remains, but is read-only to avoid flamewars, necrobumps etc.)

Arch Linux

#1 2020-12-14 04:04:43

Sudden geenral system slowdown and systemd mounting problem

#2 2020-12-14 08:02:25

Re: Sudden geenral system slowdown and systemd mounting problem

#3 2020-12-16 12:45:59

Re: Sudden geenral system slowdown and systemd mounting problem

#4 2020-12-16 16:07:06

Re: Sudden geenral system slowdown and systemd mounting problem

#5 2020-12-20 01:51:24

Re: Sudden geenral system slowdown and systemd mounting problem

#6 2020-12-20 08:56:31

Re: Sudden geenral system slowdown and systemd mounting problem

Board footer