System booting/running awfully slow

So, my system has been running a little “sub-optimal” for the past month. installing new software, either by using pacman, pamac or appimage makes kde unresponsive and the application launcher keeps updating itself for several seconds while being unreasonably slow, but it goes away eventually.

Disconnecting/Connecting from the network (System Settings > Connections) also causes kde to become unresponsive for a few seconds.
Sometimes i get “Filesystem mounted at ‘/’ is not responding” and booting times are awful. besides these issues the system runs fine as it was running before these issues began occurring.

Now, i’m running off a HDD but this looks like either bad sectors, file corruption or something like that. what i want i some help to diagnose and fix this issues, some logs:

[manjaro@manjaro ~]$ sudo fsck -vcf /dev/sda3
fsck from util-linux 2.36.2
e2fsck 1.46.2 (28-Feb-2021)
Checking for bad blocks (read-only test): done
/dev/sda3: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****

      520937 inodes used (3.08%, out of 16900096)
        2706 non-contiguous files (0.5%)
         724 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 460642/359
    57057528 blocks used (84.44%, out of 67569800)
           0 bad blocks
           9 large files

      425480 regular files
       32688 directories
           0 character device files
           0 block device files
           1 fifo
        7061 links
       62758 symbolic links (59926 fast symbolic links)
           1 socket
------------
      527989 files
[manjaro@manjaro ~]$

systemd-analyze blame:

5.939s dev-sda3.device
3.723s udisks2.service
3.233s systemd-journal-flush.service
2.893s systemd-random-seed.service
2.892s systemd-sysusers.service
1.563s ldconfig.service
1.248s upower.service
 621ms systemd-modules-load.service
 613ms apparmor.service
 481ms user@1000.service
 468ms cups.service
 326ms systemd-tmpfiles-clean.service
 318ms systemd-tmpfiles-setup.service
 310ms dev-disk-by\x2duuid-61bfbf7f\x2d2e60\x2d4c29\x2d994b\x2d162fa5eab2ef.swap
 246ms modprobe@drm.service
 210ms systemd-journal-catalog-update.service
 162ms modprobe@fuse.service
 143ms avahi-daemon.service
 137ms systemd-update-done.service
 134ms NetworkManager.service
 128ms systemd-udevd.service
 123ms systemd-logind.service
 119ms systemd-journald.service
 116ms systemd-update-utmp.service
  88ms dev-hugepages.mount
  88ms dev-mqueue.mount
  87ms sys-kernel-debug.mount
  86ms sys-kernel-tracing.mount
  85ms systemd-udev-trigger.service
  85ms kmod-static-nodes.service
  84ms modprobe@configfs.service
  83ms systemd-timesyncd.service
  60ms systemd-remount-fs.service
  59ms polkit.service
  54ms systemd-binfmt.service
  45ms proc-sys-fs-binfmt_misc.mount
  33ms systemd-tmpfiles-setup-dev.service
  31ms sys-kernel-config.mount
  22ms user-runtime-dir@1000.service
  22ms alsa-restore.service
  10ms linux-module-cleanup.service
   9ms snapd.apparmor.service
   5ms systemd-user-sessions.service
   4ms tmp.mount
   4ms systemd-sysctl.service
   4ms rtkit-daemon.service
   2ms sys-fs-fuse-connections.mount

systemd-analyze critical-chain:

graphical.target @11.010s
└─sddm.service @11.009s
  └─systemd-user-sessions.service @11.001s +5ms
    └─network.target @10.996s
      └─NetworkManager.service @10.860s +134ms
        └─dbus.service @10.854s
          └─basic.target @10.844s
            └─sockets.target @10.844s
              └─dbus.socket @10.844s
                └─sysinit.target @10.801s
                  └─systemd-update-done.service @10.663s +137ms
                    └─ldconfig.service @9.097s +1.563s
                      └─local-fs.target @9.095s
                        └─tmp.mount @9.091s +4ms
                          └─swap.target @9.089s
                            └─dev-disk-by\x2duuid-61bfbf7f\x2d2e60\x2d4c29\x2d994b\x2d162fa5eab2ef.swap @8.778s +310ms
                              └─dev-disk-by\x2duuid-61bfbf7f\x2d2e60\x2d4c29\x2d994b\x2d162fa5eab2ef.device @8.776s

journalctl -b -1:

Sounds like your HDD is dying. Better make backups now while you can, and then get the thing replaced ASAP.

3 Likes

Do what @Aragorn said first:
Make a backup of your documents ASAP!

After doing that, provide the output to:

inxi --admin --verbosity=7 --filter --no-host --width

And please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.

2 Likes

@Fabby @Aragorn Thanks for the heads up guys, but no important files are on the drive, what i actually need is to diagnose the state of the drive. otherwise I’m just giving up on trying to find what is happening.

btw i forgot to include that this happened after a unexpected shutdown (power went down) so it sounds more like file corruption.

[ian@ian-manjaro ~]$ inxi --admin --verbosity=7 --filter --no-host --width
System:
  Kernel: 5.10.60-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 
  root=UUID=5222c916-df1a-4521-a528-7f3095a0d71a rw 
  init=/usr/bin/e4rat-lite-preload radeon.cik_support=0 amdgpu.cik_support=1 
  radeon.si_support=0 amdgpu.si_support=1 usbhid.mousepoll=2 quiet apparmor=1 
  security=apparmor udev.log_priority=3 
  Desktop: KDE Plasma 5.22.4 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM 
  Distro: Manjaro Linux base: Arch Linux 
Machine:
  Type: Desktop Mobo: ASUSTeK model: M5A78L-M LX/BR v: Rev X.0x 
  serial: <filter> BIOS: American Megatrends v: 1101 date: 04/19/2013 
Battery:
  Message: No system battery data found. Is one present? 
Memory:
  RAM: total: 7.75 GiB used: 2.99 GiB (38.6%) 
  RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
CPU:
  Info: 6-Core model: AMD FX-6300 bits: 64 type: MCP arch: Bulldozer 
  family: 15 (21) model-id: 2 stepping: 0 microcode: 6000852 cache: L2: 2 MiB 
  bogomips: 42208 
  Speed: 1406 MHz min/max: 1400/3500 MHz boost: enabled Core speeds (MHz): 
  1: 1406 2: 1406 3: 1406 4: 1406 5: 1406 6: 1405 
  Flags: 3dnowprefetch abm aes aperfmperf apic arat avx bmi1 clflush cmov 
  cmp_legacy constant_tsc cpb cpuid cr8_legacy cx16 cx8 de decodeassists 
  extapic extd_apicid f16c flushbyasid fma fma4 fpu fxsr fxsr_opt ht hw_pstate 
  ibpb ibs lahf_lm lbrv lm mca mce misalignsse mmx mmxext monitor msr mtrr 
  nodeid_msr nonstop_tsc nopl npt nrip_save nx osvw pae pat pausefilter 
  pclmulqdq pdpe1gb perfctr_core perfctr_nb pfthreshold pge pni popcnt pse 
  pse36 rdtscp rep_good sep skinit ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 svm 
  svm_lock syscall tbm tce topoext tsc tsc_scale vmcb_clean vme vmmcall wdt 
  xop xsave 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: 
  disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: AMD Tobago PRO [Radeon R7 360 / R9 360 OEM] vendor: XFX Pine 
  driver: amdgpu v: kernel alternate: radeon bus-ID: 01:00.0 
  chip-ID: 1002:665f class-ID: 0300 
  Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: 
  loaded: amdgpu,ati unloaded: modesetting,radeon alternate: fbdev,vesa 
  display-ID: :0 screens: 1 
  Screen-1: 0 s-res: 1280x1024 s-dpi: 76 s-size: 426x341mm (16.8x13.4") 
  s-diag: 546mm (21.5") 
  Monitor-1: DVI-I-1 res: 1280x1024 hz: 60 
  OpenGL: renderer: AMD Radeon R7 300 Series (BONAIRE DRM 3.40.0 
  5.10.60-1-MANJARO LLVM 12.0.1) 
  v: 4.6 Mesa 21.2.1 direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: ASUSTeK M5A78L LE driver: snd_hda_intel 
  v: kernel bus-ID: 00:14.2 chip-ID: 1002:4383 class-ID: 0403 
  Device-2: AMD Tobago HDMI Audio [Radeon R7 360 / R9 360 OEM] 
  vendor: XFX Pine driver: snd_hda_intel v: kernel bus-ID: 01:00.1 
  chip-ID: 1002:aac0 class-ID: 0403 
  Sound Server-1: ALSA v: k5.10.60-1-MANJARO running: yes 
  Sound Server-2: JACK v: 1.9.19 running: no 
  Sound Server-3: PulseAudio v: 15.0 running: yes 
  Sound Server-4: PipeWire v: 0.3.33 running: yes 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK P8P67 and other motherboards driver: r8169 v: kernel 
  port: e800 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200 
  IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter> 
  IP v6: <filter> type: noprefixroute scope: link 
  WAN IP: <filter> 
Bluetooth:
  Message: No bluetooth data found. 
Logical:
  Message: No logical block device data found. 
RAID:
  Message: No RAID data found. 
Drives:
  Local Storage: total: 847.7 GiB used: 675.32 GiB (79.7%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST500DM002-1BC142 
  size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
  type: HDD rpm: 7200 serial: <filter> rev: JC4B scheme: MBR 
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital 
  model: WD1600AAJS-00L7A0 size: 149.05 GiB block-size: physical: 512 B 
  logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 3E01 
  scheme: MBR 
  ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Western Digital 
  model: WD25 00BEVT-60ZCT1 WDC WD2500 size: 232.89 GiB block-size: 
  physical: 512 B logical: 512 B type: N/A serial: <filter> scheme: MBR 
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
  Message: No optical or floppy data found. 
Partition:
  ID-1: / raw-size: 257.76 GiB size: 252.65 GiB (98.02%) 
  used: 203.77 GiB (80.7%) fs: ext4 dev: /dev/sda3 maj-min: 8:3 label: N/A 
  uuid: 5222c916-df1a-4521-a528-7f3095a0d71a 
  ID-2: /run/media/ian/0EB342184C40CCEB raw-size: 29.3 GiB 
  size: 29.3 GiB (100.00%) used: 15.81 GiB (54.0%) fs: ntfs dev: /dev/sdb1 
  maj-min: 8:17 label: N/A uuid: 0EB342184C40CCEB 
  ID-3: /run/media/ian/12A89049A8902CEB raw-size: 232.88 GiB 
  size: 232.88 GiB (100.00%) used: 217.07 GiB (93.2%) fs: ntfs dev: /dev/sdc1 
  maj-min: 8:33 label: N/A uuid: 12A89049A8902CEB 
  ID-4: /run/media/ian/8c0554b5-c319-4bfc-a007-c8d26e1e511f raw-size: 200 GiB 
  size: 195.8 GiB (97.90%) used: 147.39 GiB (75.3%) fs: ext4 dev: /dev/sda2 
  maj-min: 8:2 label: N/A uuid: 8c0554b5-c319-4bfc-a007-c8d26e1e511f 
  ID-5: /run/media/ian/b299298f-697d-44cc-a1a3-9d0455c845cd 
  raw-size: 119.75 GiB size: 117.31 GiB (97.96%) used: 91.21 GiB (77.8%) 
  fs: ext4 dev: /dev/sdb2 maj-min: 8:18 label: N/A 
  uuid: b299298f-697d-44cc-a1a3-9d0455c845cd 
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 8 GiB used: 65.6 MiB (0.8%) priority: -2 
  dev: /dev/sda1 maj-min: 8:1 label: N/A 
  uuid: 61bfbf7f-2e60-4c29-994b-162fa5eab2ef 
Unmounted:
  Message: No unmounted partitions found. 
USB:
  Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Device-1: 1-3:4 info: HP HP Pocket Media Drive type: Mass Storage 
  driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s power: 2mA 
  chip-ID: 03f0:110c class-ID: 0806 serial: <filter> 
  Device-2: 1-4:5 info: Samsung Galaxy A5 (MTP) 
  type: Abstract (modem),CDC-Data driver: cdc_acm,usbfs interfaces: 5 rev: 2.0 
  speed: 480 Mb/s power: 500mA chip-ID: 04e8:6860 class-ID: 0a00 
  serial: <filter> 
  Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Hub-3: 3-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s 
  chip-ID: 1d6b:0001 class-ID: 0900 
  Device-1: 3-1:2 info: China Resource Semico USB Keyboard 
  type: Keyboard,Mouse driver: hid-generic,usbhid interfaces: 2 rev: 1.1 
  speed: 1.5 Mb/s power: 500mA chip-ID: 1a2c:4b81 class-ID: 0301 
  Device-2: 3-2:3 info: USB OPTICAL MOUSE type: Mouse,Keyboard 
  driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s 
  power: 100mA chip-ID: 4e53:5406 class-ID: 0301 
  Hub-4: 4-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s 
  chip-ID: 1d6b:0001 class-ID: 0900 
  Hub-5: 5-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s 
  chip-ID: 1d6b:0001 class-ID: 0900 
  Hub-6: 6-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s 
  chip-ID: 1d6b:0001 class-ID: 0900 
  Hub-7: 7-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
  chip-ID: 1d6b:0001 class-ID: 0900 
Sensors:
  System Temperatures: cpu: 30.0 C mobo: 29.0 C gpu: amdgpu temp: 30.0 C 
  Fan Speeds (RPM): cpu: 2800 case-1: 3358 
  Power: 12v: 11.88 5v: N/A 3.3v: 3.36 vbat: N/A gpu: amdgpu watts: 7.20 
Info:
  Processes: 235 Uptime: 9h 42m wakeups: 0 Init: systemd v: 248 
  tool: systemctl Compilers: gcc: 11.1.0 Packages: pacman: 1443 lib: 400 
  flatpak: 0 Shell: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06 
[ian@ian-manjaro ~]$ 

Use smartctl as root to check the status of your drive, or use the Info Center to view the S.M.A.R.T. status. :arrow_down:

Also check the output of… :arrow_down:

sudo dmesg | less

… to see if the kernel reported hardware issues at boot.

2 Likes
[ian@ian-manjaro ~]$ sudo smartctl -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.60-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST500DM002-1BC142
Serial Number:    W2A1DL5J
LU WWN Device Id: 5 000c50 03d95a986
Firmware Version: JC4B
User Capacity:    500.107.862.016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
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: 3.0 Gb/s)
Local Time is:    Mon Aug 30 22:40:56 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:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
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:                (  600) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        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:        (  81) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x103f) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table 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   109   096   006    Pre-fail  Always       -       25096119
  3 Spin_Up_Time            0x0003   100   100   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   096   096   020    Old_age   Always       -       4609
  5 Reallocated_Sector_Ct   0x0033   059   059   036    Pre-fail  Always       -       1693
  7 Seek_Error_Rate         0x000f   078   060   030    Pre-fail  Always       -       39244322457
  9 Power_On_Hours          0x0032   099   011   000    Old_age   Always       -       1655
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   097   097   020    Old_age   Always       -       4019
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   001   001   000    Old_age   Always       -       177
188 Command_Timeout         0x0032   100   055   000    Old_age   Always       -       8 9 1057
189 High_Fly_Writes         0x003a   097   097   000    Old_age   Always       -       3
190 Airflow_Temperature_Cel 0x0022   067   052   045    Old_age   Always       -       33 (Min/Max 19/37)
194 Temperature_Celsius     0x0022   033   048   000    Old_age   Always       -       33 (0 14 0 0 0)
195 Hardware_ECC_Recovered  0x001a   034   026   000    Old_age   Always       -       25096119
197 Current_Pending_Sector  0x0012   100   083   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   083   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   112   000    Old_age   Always       -       454134
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       88111h+45m+05.805s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       4174838768
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       1822199572

SMART Error Log Version: 1
ATA Error Count: 196 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 196 occurred at disk power-on lifetime: 17057 hours (710 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 01 ff ff ff ef 00      01:56:35.961  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:32.339  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:28.717  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:25.095  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:21.457  READ DMA EXT

Error 195 occurred at disk power-on lifetime: 17057 hours (710 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 01 ff ff ff ef 00      01:56:32.339  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:28.717  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:25.095  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:21.457  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:17.836  READ DMA EXT

Error 194 occurred at disk power-on lifetime: 17057 hours (710 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 01 ff ff ff ef 00      01:56:28.717  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:25.095  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:21.457  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:17.836  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:14.214  READ DMA EXT

Error 193 occurred at disk power-on lifetime: 17057 hours (710 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 01 ff ff ff ef 00      01:56:25.095  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:21.457  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:17.836  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:14.214  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:10.592  READ DMA EXT

Error 192 occurred at disk power-on lifetime: 17057 hours (710 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 01 ff ff ff ef 00      01:56:21.457  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:17.836  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:14.214  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:10.592  READ DMA EXT
  25 03 01 ff ff ff ef 00      01:56:06.992  READ DMA EXT

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.

[ian@ian-manjaro ~]$ 

dmesg | less:

Multiple READ DMA EXT errors on your drive, but all were at the same time (so probably the power loss)

I beg to differ: your OS on this drive!

So do the following:

  • Take a full Cold system backup using a CloneZilla Live USB to an external drive.

  • download, burn and Boot a Manjaro USB stick

  • Go to KDE partition Manager,

  • write down all partitions as they are

  • Write a new GPT partition table on that disk

  • Create the exact same partition(s) as before

  • Write zeroes to all the new partitions

    cat /dev/zero /dev/XdYN
    

    where X, Y and N denominate your partition names
    Why, oh why: this is taking so long!
    You still have 59 spare sectors:

    and the cat will ensure that all sectors in the disk are written to so that the disk can swap out any bad sectors with the spare ones (36 have been used already)

  • Boot the CloneZilla Live USB again

  • Restore your Cold System backup

:crossed_fingers:

Disable Fast Startup

One of the most problematic settings that causes slow boot times in Windows 10 is the fast startup option. This is enabled by default, and is supposed to reduce startup time by pre-loading some boot information before your PC shuts off. (Note that while it applies to shutting down, restarting your computer isn’t affected by this feature.)

While the name sounds promising, it causes issues for a lot of people. Thus, it’s the first step you should try when you have slow boot problems.

To disable it,:

  • open System Settings
  • browse to SystemPower & sleep.
  • On the right side of this screen, click Additional power settings to open the Power Options menu

My systemd-analyze-blame is below:

System Analyzed Boot
5.939s dev-sda3.device
3.723s udisks2.service
3.233s systemd-journal-flush.service
2.893s systemd-random-seed.service
2.892s systemd-sysusers.service
1.563s ldconfig.service
1.248s upower.service
 621ms systemd-modules-load.service
 613ms apparmor.service
 481ms user@1000.service
 468ms cups.service
 326ms systemd-tmpfiles-clean.service
 318ms systemd-tmpfiles-setup.service
 310ms dev-disk-by\x2duuid-61bfbf7f\x2d2e60\x2d4c29\x2d994b\x2d162fa5eab2ef.swap
 246ms modprobe@drm.service
 210ms systemd-journal-catalog-update.service
 162ms modprobe@fuse.service
 143ms avahi-daemon.service
 137ms systemd-update-done.service
 134ms NetworkManager.service
 128ms systemd-udevd.service
 123ms systemd-logind.service
 119ms systemd-journald.service
 116ms systemd-update-utmp.service
  88ms dev-hugepages.mount
  88ms dev-mqueue.mount
  87ms sys-kernel-debug.mount
  86ms sys-kernel-tracing.mount
  85ms systemd-udev-trigger.service
  85ms kmod-static-nodes.service
  84ms modprobe@configfs.service
  83ms systemd-timesyncd.service
  60ms systemd-remount-fs.service
  59ms polkit.service
  54ms systemd-binfmt.service
  45ms proc-sys-fs-binfmt_misc.mount
  33ms systemd-tmpfiles-setup-dev.service
  31ms sys-kernel-config.mount
  22ms user-runtime-dir@1000.service
  22ms alsa-restore.service
  10ms linux-module-cleanup.service
   9ms snapd.apparmor.service
   5ms systemd-user-sessions.service
   4ms tmp.mount
   4ms systemd-sysctl.service
   4ms rtkit-daemon.service
   2ms sys-fs-fuse-connections.mount

Thank you, i’m going to do that eventually (i need to shuffle some files around to make space), but i’m a little bit confused by the following:

  • write down all partitions as they are

so, basically don’t change anything? or should i wipe the disk? this particular disk partitioning scheme looks like this:

Device     Boot     Start       End   Sectors   Size Id Type

/dev/sda1            2048  16779263  16777216     8G 83 Linux
/dev/sda2        16779264 436209663 419430400   200G 83 Linux
/dev/sda3       436209664 976768064 540558401 257,8G 83 Linux
1 Like

Yes, restore as is…

(Full disclosure: In CloneZille, if you use Disk-to-disk or disk-to-image, it doesn’t really matter, but if you use partition-to-image it does matter!)

1 Like

i was having this issue before i had windows installed.