Hi guys,

 

Can someone with more experience spare a moment to look at my diagnostics file. I came home today and have noticed `Disk 11` is being emulated and various errors in the log file. Has this drive failed or should I look at maybe the sata cable first? If the drive has failed, would I need to replace the drive or is it possible to remove disk 11 from the array and rebuild the missing data into existing drives as i have plenty of extra storage. 

 

Also i just noticed that a pool device is also reporting a smart error `Reported uncorrect` ?

 

holy-grail-diagnostics-20230823-1539.zip

Edited August 23, 20232 yr by KeyBoardDabbler

It's logged as a disk problem, and there's a pending sector, run an extended SMART test.

14 hours ago, JorgeB said:

It's logged as a disk problem, and there's a pending sector, run an extended SMART test.

 

I followed your suggestion and ran the extended SMART test on both effected drives, reported no errors found and disks still are still down. I dont realy understand the error log file for the pool device because there is a error but it states the test completed with 0 errors.

 

Disk 11 (disabled, contents emulated)

SMART self-test history:

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     46186         -
# 2  Extended offline    Completed without error       00%     29232         -

SMART error log:

No Errors Logged

 

 

Pool device (1 smart error)

SMART self-test history:

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     23636         -

SMART error log:

ATA Error Count: 2
	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 2 occurred at disk power-on lifetime: 23612 hours (983 days + 20 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 c8 18 08 04  Error: UNC at LBA = 0x040818c8 = 67639496

  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 48 e0 35 08 44 00   4d+09:58:45.407  READ FPDMA QUEUED
  60 00 a0 00 34 08 44 00   4d+09:58:45.407  READ FPDMA QUEUED
  60 00 40 98 33 08 44 00   4d+09:58:45.407  READ FPDMA QUEUED
  60 00 10 08 32 08 44 00   4d+09:58:45.407  READ FPDMA QUEUED
  60 00 40 58 31 08 44 00   4d+09:58:45.407  READ FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 23608 hours (983 days + 16 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 b8 18 08 04  Error: UNC at LBA = 0x040818b8 = 67639480

  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 e0 3f 08 44 00   4d+05:58:54.385  READ FPDMA QUEUED
  60 00 00 e0 35 08 44 00   4d+05:58:54.384  READ FPDMA QUEUED
  60 00 00 e0 2b 08 44 00   4d+05:58:54.382  READ FPDMA QUEUED
  60 00 00 e0 21 08 44 00   4d+05:58:54.382  READ FPDMA QUEUED
  60 00 a8 38 1f 08 44 00   4d+05:58:48.725  READ FPDMA QUEUED

 

Since the SMART text passed the disk is OK for now, if the emulated disk is still mounting and contents look correct you can rebuild on top:

https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

 

Any more errors from that disk in the near future I would consider replacing it.