[System] Problems with file system

[javfr]

Hello everyone.
A few days ago, when I turned on the computer I had to run fsck because it could not boot.
Since then, I have been having several problems:

• Application performance got noticeably worse (momentary freezes): for example, in Dolphin, Firefox and Visual Studio Code. On the other hand, I didn't notice any problems with games or graphics.
• I had to re-create the Firefox session twice because it wouldn't start.
• I continually have to run fsck at startup.
• Ussually I have to run fsck
• It takes more time to shut down
• I've heard that the disc works harder

I have no idea what can be the problem. I think it started after a system update

This is my system information:
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-64-generic
OS Type: 64-bit
Uptime: 5 hours, 15 mins
Packages: 2593 (dpkg), 8 (snap)
Shell: zsh 5.8
Resolution: 1920x1080
DE: Plasma
WM: KWin
Theme: Breeze Dark [Plasma], Breeze [GTK2/3]
Icons: breeze-dark [Plasma], breeze-dark [GTK2/3]
Terminal: konsole
CPU: AMD A10-9700 RADEON R7 4C+6G (4) @ 3.500GHz
GPU: AMD ATI Radeon R5/R6/R7 Graphics
Memory: 6205MiB / 15436MiB
Disks:

• HDD 1TB
  • dev/sda1 ->ext4 -> /home
  
  
• SDD 240GB
  • dev/sdb1 -> fat32 -> /boot/efi
  • dev/sdb2 -> ext4 -> /
  • dev/sd3 -> linuxswap -> none
  
  

I also add an extract of a boot.log:
------------ Tue Jan 26 07:02:04 -03 2021 ------------
/dev/sdb2: clean, 665911/13402112 files, 6948191/53582592 blocks
[FAILED] Failed to start File Syste?f-5293-458b-bc58-17b68bc6161b.
[DEPEND] Dependency failed for /home.
[DEPEND] Dependency failed for Local File Systems.
[ OK ] Finished Tell Plymouth To Write Out Runtime Data.
[ OK ] Finished Set console font and keymap.
[ OK ] Mounted Arbitrary Executable File Formats File System.
[ OK ] Finished Enable support fo?nal executable binary formats.
[ OK ] Finished Create Volatile Files and Directories.
Starting Network Name Resolution...
Starting Network Time Synchronization...


Starting Update UTMP about System Boot/Shutdown...
[ OK ] Finished Update UTMP about System Boot/Shutdown.
[ OK ] Finished Load AppArmor profiles.
[ OK ] Started Entropy daemon using the HAVEGE algorithm.
Starting Load AppArmor pro?managed internally by snapd...
[ OK ] Finished Load AppArmor pro?s managed internally by snapd.
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Time Set.
[ OK ] Reached target System Time Synchronized.
[ OK ] Started Network Name Resolution.


[ OK ] Reached target Host and Network Name Lookups.

Thanks a lot for your help

[claydoh]

You may want to see about replacing the larger hard drive, especially as you are constantly having to run fsck on it (assuming so, you don't say which drive is being checked)
More so as you are hearing it struggle.

You can check the large HDD drive by installing and using smartmontools

There is a good tutorial here:
https://linuxconfig.org/how-to-check...using-smartctl

But do back up your files first.

[javfr]

You may want to see about replacing the larger hard drive, especially as you are constantly having to run fsck on it (assuming so, you don't say which drive is being checked)
More so as you are hearing it struggle.

You can check the large HDD drive by installing and using smartmontools

There is a good tutorial here:
https://linuxconfig.org/how-to-check...using-smartctl

But do back up your files first.

Right, I forgot to mention that I was running fsck on the HDD (/dev/sda1). And also, as I watched in the boot logs, the problem is with /home (which I've mounted on the HDD).

It's strange, the disc is less than a year old.
In any case, when I'm done with my work I'll do the backup and then the checkup.

Thanks claydoh

[javfr]

Well, I ran smart on the HDD.

It appears that there were no hardware errors. What do you think?.

Here the report:

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 3.5
Device Model: ST1000DM010-2EP102
Serial Number: ZN1FDC4N
LU WWN Device Id: 5 000c50 0c53d94d5
Firmware Version: CC43
User Capacity: 1.000.204.886.016 bytes [1,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Fri Jan 29 12:17:47 2021 -03
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 108) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x1085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 078 063 006 Pre-fail Always - 67128232
3 Spin_Up_Time 0x0003 099 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2218
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 077 060 045 Pre-fail Always - 58694908
9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 3396
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 098 098 020 Old_age Always - 2212
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 098 000 Old_age Always - 0 7 9
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 061 051 040 Old_age Always - 39 (Min/Max 39/43)
193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 2218
194 Temperature_Celsius 0x0022 039 014 000 Old_age Always - 39 (0 14 0 0 0)
195 Hardware_ECC_Recovered 0x001a 001 001 000 Old_age Always - 67128232
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 3386h+11m+16.474s
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 4798926491
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 4497472150

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 3396 -
# 2 Extended offline Interrupted (host reset) 00% 3392 -
# 3 Conveyance offline Completed without error 00% 3392 -
# 4 Short offline Completed without error 00% 3392 -
# 5 Short offline Completed without error 00% 3392 -
# 6 Extended offline Interrupted (host reset) 00% 2121 -
# 7 Short offline Completed without error 00% 2121 -
# 8 Short offline Completed without error 00% 2121 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

[jglen490]

Well, there is something wrong somewhere. The description sounds like hardware, but if your drive seems to be clean, and there are no particular data errors, then that leaves RAM or the motherboard itself. I would like to think that the motherboard is not having issues, since badness there will cause errors to be written to the drive. You might want to check your RAM modules with memtest. But before doing that, check their physical connection at the motherboard. Sometimes, just pulling the RAM and exchanging their relative positions will fix errors. It's not a sure thing, but I have done that before. Then if it's still running badly, try the memtest toolset.

[oshunluvr]

Have you gone through the basics yet? Re-seat cables, swap cables, etc. I've had more than one time where a loose or cheap sata cable caused issues with a perfectly good drive. I even experienced a sata port failure on a motherboard once. Changing the port on the mobo fixed that one. It's worth trying and free to boot.