Jump to content
Sign in to follow this  
TexasDave

Read errors on disk...

6 posts in this topic Last Reply

Recommended Posts

 

Happy 2019 to all the "unRAIDERs" out there...

 

I was alerted to some disk errors (thanks to "Fix Common Problems") and wanted to see how bad this is. 

 

One of my disks has errors - see below. I do not know enough about hardware to know if this is just normal wear and tear or not? And more importantly, should I start to worry? 

 

Extended SMART test says all ok and I do regular parity checks and those are fine too. I also attach my diagnostics. 

 

Should I start thinking about replacing this drive and others? 

 

Thanks!

 

---

 

ATA Error Count: 7 (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 7 occurred at disk power-on lifetime: 36305 hours (1512 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 53 00 58 9a 0e 01  Error: UNC at LBA = 0x010e9a58 = 17734232

  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 00 80 78 96 0e e1 00  38d+22:51:24.116  READ DMA EXT
  25 00 40 38 91 0e e1 00  38d+22:51:24.108  READ DMA EXT
  35 00 40 b8 8a 0e e1 00  38d+22:51:24.104  WRITE DMA EXT
  25 00 40 f8 8f 0e e1 00  38d+22:51:24.080  READ DMA EXT
  47 00 01 30 06 00 a0 00  38d+22:51:24.079  READ LOG DMA EXT

Error 6 occurred at disk power-on lifetime: 36305 hours (1512 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 53 00 98 8d 0e 01  Error: UNC at LBA = 0x010e8d98 = 17730968

  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 00 40 b8 8a 0e e1 00  38d+22:51:20.068  READ DMA EXT
  35 00 80 f8 7f 0e e1 00  38d+22:51:20.065  WRITE DMA EXT
  25 00 00 b8 86 0e e1 00  38d+22:51:20.063  READ DMA EXT
  25 00 40 78 81 0e e1 00  38d+22:51:20.042  READ DMA EXT
  47 00 01 30 06 00 a0 00  38d+22:51:20.040  READ LOG DMA EXT

Error 5 occurred at disk power-on lifetime: 36305 hours (1512 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 53 00 d0 80 0e 01  Error: UNC at LBA = 0x010e80d0 = 17727696

  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 00 80 f8 7f 0e e1 00  38d+22:51:15.991  READ DMA EXT
  25 00 40 b8 7a 0e e1 00  38d+22:51:15.984  READ DMA EXT
  35 00 40 00 74 0e e1 00  38d+22:51:15.979  WRITE DMA EXT
  25 00 78 40 79 0e e1 00  38d+22:51:15.961  READ DMA EXT
  47 00 01 30 06 00 a0 00  38d+22:51:15.960  READ LOG DMA EXT

Error 4 occurred at disk power-on lifetime: 36305 hours (1512 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 53 00 10 74 0e 01  Error: UNC at LBA = 0x010e7410 = 17724432

  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 00 40 00 74 0e e1 00  38d+22:51:12.235  READ DMA EXT
  c8 00 08 f8 73 0e e1 00  38d+22:51:12.233  READ DMA
  25 00 40 78 69 0e e1 00  38d+22:51:12.226  READ DMA EXT
  25 00 78 00 68 0e e1 00  38d+22:51:11.826  READ DMA EXT
  25 00 40 80 51 0e e1 00  38d+22:51:11.229  READ DMA EXT

Error 3 occurred at disk power-on lifetime: 36305 hours (1512 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 53 00 e8 4c 0e 01  Error: UNC at LBA = 0x010e4ce8 = 17714408

  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 00 08 50 49 0e e1 00  38d+22:51:06.731  READ DMA EXT
  35 00 d0 80 45 0e e1 00  38d+22:51:06.728  WRITE DMA EXT
  35 00 28 50 3d 0e e1 00  38d+22:51:06.726  WRITE DMA EXT
  47 00 01 30 06 00 a0 00  38d+22:51:06.725  READ LOG DMA EXT
  47 00 01 30 00 00 a0 00  38d+22:51:06.724  READ LOG DMA EXT

 

 

zack-unraid-diagnostics-20190109-1831.zip

Share this post


Link to post

It's showing some warnings, though it passed the SMART test so it's OK for now, but considering the model and how old it is I would would start thinking about replacing it.

Share this post


Link to post

That is what I was thinking... Can you comment on the other drives as my initial install had three of these put in from the start so if this one is getting close, the others must be too? Thanks!

Share this post


Link to post

Disk3 has a reallocated sector, it appears that was some time ago, so as long at it remains stable it should be fine for now, a couple of read raw errors here and there on the other disks but nothing to worry about for now.

  • Like 1

Share this post


Link to post

@johnnie.black Many thanks for this. Is there a good set of docs or web page where I can learn more about the various errors and which ones I should worry about? Would like to learn this and get a bit more self sufficient.

 

Also - I do regular parity checks (one a week) but in looking around on this error, it seems most folks do once a month? Is once a month enough? 

 

Thanks!!

Edited by TexasDave

Share this post


Link to post

If you google SMART attributes explained you'll get several results.

 

Once a month is usually considered enough.

Edited by johnnie.black
  • Like 1

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this