Probable error with the HDD partition

I recently installed Manjaro Plasma 23.

Linux srikanth-pc 6.6.25-1-MANJARO #1 SMP PREEMPT_DYNAMIC Thu Apr  4 20:32:38 UTC 2024 x86_64 GNU/Linux

Since then the computer has been slow to respond, particularly the HDD.

I have installed the root on SSD and the data is on a HDD partition.
These are the last few lines of the journalctl output:

Apr 13 22:17:43 srikanth-pc kernel: ata4: soft resetting link
Apr 13 22:17:43 srikanth-pc kernel: ata4: found unknown device (class 0)
Apr 13 22:17:43 srikanth-pc kernel: ata4.01: configured for UDMA/33
Apr 13 22:17:43 srikanth-pc kernel: ata4: EH complete
Apr 13 22:17:44 srikanth-pc plasmashell[18478]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:286: Unable to assign [unde>
Apr 13 22:18:16 srikanth-pc kernel: ata4: lost interrupt (Status 0x50)
Apr 13 22:18:16 srikanth-pc kernel: ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Apr 13 22:18:16 srikanth-pc kernel: ata4.01: failed command: WRITE DMA EXT
Apr 13 22:18:16 srikanth-pc kernel: ata4.01: cmd 35/00:08:18:c5:45/00:00:55:00:00/f0 tag 0 dma 4096 out
                                             res 40/00:00:00:4f:c2/00:00:00:00:00/50 Emask 0x4 (timeout)
Apr 13 22:18:16 srikanth-pc kernel: ata4.01: status: { DRDY }
Apr 13 22:18:16 srikanth-pc kernel: ata4: soft resetting link
Apr 13 22:18:16 srikanth-pc kernel: ata4: found unknown device (class 0)
Apr 13 22:18:16 srikanth-pc kernel: ata4.01: configured for UDMA/33
Apr 13 22:18:16 srikanth-pc kernel: ata4: EH complete
Apr 13 22:18:16 srikanth-pc kernel: EXT4-fs (sdb2): Delayed block allocation failed for inode 16657381 at logical offset 0 with max blocks 6 with error 117
Apr 13 22:18:16 srikanth-pc kernel: EXT4-fs (sdb2): This should not happen!! Data will be lost
Apr 13 22:18:16 srikanth-pc kernel: EXT4-fs (sdb2): Delayed block allocation failed for inode 16650054 at logical offset 0 with max blocks 5 with error 117
Apr 13 22:18:16 srikanth-pc kernel: EXT4-fs (sdb2): This should not happen!! Data will be lost
Apr 13 22:18:17 srikanth-pc kernel: EXT4-fs error (device sdb2): ext4_lookup:1857: inode #16646145: comm gvim: deleted inode referenced: 16657332
Apr 13 22:18:17 srikanth-pc kernel: EXT4-fs error (device sdb2): ext4_lookup:1857: inode #16646145: comm gvim: deleted inode referenced: 16657332
Apr 13 22:18:17 srikanth-pc kernel: EXT4-fs error (device sdb2): ext4_lookup:1857: inode #16646145: comm gvim: deleted inode referenced: 16657332
Apr 13 22:18:17 srikanth-pc kernel: EXT4-fs error (device sdb2): ext4_lookup:1857: inode #16646145: comm gvim: deleted inode referenced: 16657332

It appears to be a major error, but I can’t figure out what it is or how to fix it.

Appreciate any help here.

Regards,
Srikk

Welcome to Manjaro! :smiling_face_with_three_hearts:

  1. Please read the information behind this link. It will help you to post necessary information.
  1. Please press the three dots below your post and then press the :pencil2:
  • If you give us information about your system, we can see what we’re talking about and make better suggestions.
  • You can do this by using inxi in a terminal or in console.
sudo inxi --verbosity=8 --filter --width 
  • Personally identifiable information such as serial numbers and MAC addresses are filtered out by this command
  • Presenting the information in this way allows everyone to be familiar with the format and quickly find the items they need without missing anything.
  1. Copy the output from inxi (including the command) and paste it into your post.
  • To make it more readable, add 3 backticks ``` on an extra line before and after the pasted text.

Have you already :mag: for your problem in the forum ? (Wisdom lies in asking → listening → reading :wink: )

My first thought - failing device

Device on ata bus and udma/33 - I looks suspiciously old to me - if that is so - backup data and replace the device.

1 Like

It sounds like it may be a hardware problem. I suggest installing SMART (if you haven’t already got it installed) and running a full scan on the disc with it (I can’t remember the exact commands to do this, but a quick web search should find instructions).

It appears to be low space problem.
I made some space on the drive and this problem is gone

Regards,
Srikk

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.