Jump to content

Disk Error - Help needed to understand


Go to solution Solved by JorgeB,

Recommended Posts

I woke up to a disk with read errors today. 

 

Here is what is on the disk smart error log:

ATA Error Count: 1
	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 1 occurred at disk power-on lifetime: 58269 hours (2427 days + 21 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 41 00 00 00 00 00  Error: UNC at LBA = 0x00000000 = 0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 f8 83 3f 40 00  16d+08:16:05.319  READ FPDMA QUEUED
  60 00 00 f8 7f 3f 40 00  16d+08:16:02.537  READ FPDMA QUEUED
  60 b8 00 40 7d 3f 40 00  16d+08:16:02.536  READ FPDMA QUEUED
  60 d0 00 70 79 3f 40 00  16d+08:16:02.529  READ FPDMA QUEUED
  60 00 00 70 75 3f 40 00  16d+08:16:02.528  READ FPDMA QUEUED

 

Could someone please help me understand what this means? If this is critical enough to warrant a disk replacement. I recently had a lot of reads from and writes to this disk (and a few other ones) for converting FS from reiserfs to xfs. This disk was a reiserfs disk until last week, just converted it to xfs, I'm not sure if that is what caused this to have the error.

 

All help is appreciated. I am basically trying to understand whether I'm risking the disk failing so, should be prepared with a replacement, or is there anything I should do to prevent these errors.

Edited by abhi.ko
Link to comment
1 hour ago, JorgeB said:

It's also logged in the syslog as a disk problem, though the UNC @ LBA 0 doesn't make much sense, I would run an extended test on the disk.

Thanks for taking a look, disabled spin down delay and just kicked an extended test off. Will report back once done.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...