HDD error logs on manjaro

durjoyundefined · 6 June 2021 18:57

I do not understand the error log and the current condition of my HDD:

Is there any way to solve these error
Can I continue using this HDD or should I change it immediately ?

Error Logs :

Complete error log:

SMART Extended Comprehensive Error Log Version: 1 (2 sectors)
Device Error Count: 206 (device log contains only the most recent 8 errors)
	CR     = Command Register
	FEATR  = Features Register
	COUNT  = Count (was: Sector Count) Register
	LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
	LH     = LBA High (was: Cylinder High) Register    ]   LBA
	LM     = LBA Mid (was: Cylinder Low) Register      ] Register
	LL     = LBA Low (was: Sector Number) Register     ]
	DV     = Device (was: Device/Head) Register
	DC     = Device Control Register
	ER     = Error register
	ST     = Status register
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 206 [5] occurred at disk power-on lifetime: 12014 hours (500 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 41 00 08 00 00 00 22 f2 f8 40 00  Error: UNC at LBA = 0x0022f2f8 = 2290424

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 00 22 f2 f8 40 08     00:00:00.123  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f2 f8 40 08     00:00:00.161  READ FPDMA QUEUED
  27 00 00 00 00 00 00 00 00 00 00 e0 08     00:00:00.161  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     00:00:00.161  IDENTIFY DEVICE
  ef 00 03 00 46 00 00 00 00 00 00 a0 08     00:00:00.161  SET FEATURES [Set transfer mode]

Error 205 [4] occurred at disk power-on lifetime: 12014 hours (500 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 41 00 08 00 00 00 22 f2 f8 40 00  Error: UNC at LBA = 0x0022f2f8 = 2290424

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 da 00 08 00 00 00 22 f2 f8 40 08     00:00:00.121  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f2 f8 40 08     00:00:00.159  READ FPDMA QUEUED
  27 00 00 00 00 00 00 00 00 00 00 e0 08     00:00:00.159  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     00:00:00.159  IDENTIFY DEVICE
  ef 00 03 00 46 00 00 00 00 00 00 a0 08     00:00:00.159  SET FEATURES [Set transfer mode]

Error 204 [3] occurred at disk power-on lifetime: 12014 hours (500 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 41 00 08 00 00 00 22 f2 f8 40 00  Error: UNC at LBA = 0x0022f2f8 = 2290424

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 da 00 08 00 00 00 22 f2 f8 40 08     00:00:00.121  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f2 f8 40 08     00:00:00.157  READ FPDMA QUEUED
  60 00 00 00 20 00 00 00 22 f1 28 40 08     00:00:00.157  READ FPDMA QUEUED
  60 00 da 00 08 00 00 00 22 f1 20 40 08     00:00:00.157  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f0 d0 40 08     00:00:00.157  READ FPDMA QUEUED

Error 203 [2] occurred at disk power-on lifetime: 12014 hours (500 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 41 00 08 00 00 00 22 f2 f8 40 00  Error: UNC at LBA = 0x0022f2f8 = 2290424

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 da 00 08 00 00 00 22 f2 f8 40 08     00:00:00.082  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f2 f8 40 08     00:00:00.126  READ FPDMA QUEUED
  27 00 00 00 00 00 00 00 00 00 00 e0 08     00:00:00.126  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     00:00:00.126  IDENTIFY DEVICE
  ef 00 03 00 46 00 00 00 00 00 00 a0 08     00:00:00.126  SET FEATURES [Set transfer mode]

Error 202 [1] occurred at disk power-on lifetime: 12014 hours (500 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 41 00 08 00 00 00 22 f2 f8 40 00  Error: UNC at LBA = 0x0022f2f8 = 2290424

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 da 00 08 00 00 00 22 f2 f8 40 08     00:00:00.043  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f2 f8 40 08     00:00:00.123  READ FPDMA QUEUED
  27 00 00 00 00 00 00 00 00 00 00 e0 08     00:00:00.123  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 00 00 00 00 00 a0 08     00:00:00.123  IDENTIFY DEVICE
  ef 00 03 00 46 00 00 00 00 00 00 a0 08     00:00:00.123  SET FEATURES [Set transfer mode]

Error 201 [0] occurred at disk power-on lifetime: 12014 hours (500 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 41 00 08 00 00 00 22 f2 f8 40 00  Error: UNC at LBA = 0x0022f2f8 = 2290424

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 da 00 08 00 00 00 22 f2 f8 40 08     00:00:00.043  READ FPDMA QUEUED
  60 00 da 00 08 00 00 00 22 f2 f8 40 08     00:00:00.121  READ FPDMA QUEUED
  60 00 da 00 20 00 00 00 22 f1 28 40 08     00:00:00.121  READ FPDMA QUEUED
  60 00 da 00 08 00 00 00 22 f1 20 40 08     00:00:00.121  READ FPDMA QUEUED
  60 00 da 00 08 00 00 00 22 f0 d0 40 08     00:00:00.121  READ FPDMA QUEUED

Error 200 [7] occurred at disk power-on lifetime: 12014 hours (500 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 41 00 08 00 00 00 22 f2 f8 40 00  Error: UNC at LBA = 0x0022f2f8 = 2290424

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 00 22 f2 f8 40 08     00:00:00.029  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f3 e8 40 08     00:00:00.029  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f3 e0 40 08     00:00:00.029  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f3 d8 40 08     00:00:00.029  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f3 d0 40 08     00:00:00.029  READ FPDMA QUEUED

Error 199 [6] occurred at disk power-on lifetime: 12014 hours (500 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 41 00 08 00 00 00 22 f2 f8 40 00  Error: UNC at LBA = 0x0022f2f8 = 2290424

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 00 22 f2 f8 40 08     00:00:00.057  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f3 08 40 08     00:00:00.088  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f4 48 40 08     00:00:00.088  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f3 18 40 08     00:00:00.088  READ FPDMA QUEUED
  60 00 00 00 08 00 00 00 22 f3 10 40 08     00:00:00.088  READ FPDMA QUEUED

Fabby · 7 June 2021 09:28

Welcome to Manjaro!

Please read this:
How to provide good information
and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information… (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.
We’re missing the most important part of your smartctl --all /dev/XdY output. Please provide the full output where X and Y denominate your HDD. (/dev/sda in 90% of all cases)

P.S. If you enter a bit more details in your profile, we can also see which Desktop Environment you’re using, which CPU/GPU or Kernel, … you have without typing it every time

cfinnberg · 7 June 2021 09:32

I think what you want is in here: How to interpret smartctl messages like ‘Error: UNC at LBA’? – TechOverflow

Spoiler alert: There is no definitive answer by default