January 2, 201610 yr How you doing and happy new year. I just logged into my unraid and was unplesantly informed about errors on my disk 12. Disk 12 was installed in December and was precleared with 3 passes showing no issues. Enclosed is a syslog of the errors and a smart report for disk 12. I have a new precleaed disk ready to go just curious on how to proceed. SMART REPORT ATA Error Count: 11 (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 11 occurred at disk power-on lifetime: 657 hours (27 days + 9 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 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 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 ff ff ff 4f 00 27d+09:25:28.440 READ FPDMA QUEUED 61 00 08 ff ff ff 4f 00 27d+09:25:28.430 WRITE FPDMA QUEUED 61 00 08 ff ff ff 4f 00 27d+09:25:28.420 WRITE FPDMA QUEUED 61 00 08 ff ff ff 4f 00 27d+09:25:28.410 WRITE FPDMA QUEUED 61 00 08 ff ff ff 4f 00 27d+09:25:28.400 WRITE FPDMA QUEUED Error 10 occurred at disk power-on lifetime: 657 hours (27 days + 9 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 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 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 ff ff ff 4f 00 27d+09:25:22.458 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 27d+09:25:22.452 READ FPDMA QUEUED 61 00 08 ff ff ff 4f 00 27d+09:25:22.442 WRITE FPDMA QUEUED 61 00 08 ff ff ff 4f 00 27d+09:25:22.432 WRITE FPDMA QUEUED 61 00 08 ff ff ff 4f 00 27d+09:25:22.422 WRITE FPDMA QUEUED Error 9 occurred at disk power-on lifetime: 657 hours (27 days + 9 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 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 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 ff ff ff 4f 00 27d+09:25:16.808 READ FPDMA QUEUED 61 00 08 ff ff ff 4f 00 27d+09:25:16.797 WRITE FPDMA QUEUED 61 00 08 ff ff ff 4f 00 27d+09:25:16.787 WRITE FPDMA QUEUED 61 00 08 ff ff ff 4f 00 27d+09:25:16.777 WRITE FPDMA QUEUED 61 00 08 ff ff ff 4f 00 27d+09:25:16.767 WRITE FPDMA QUEUED Error 8 occurred at disk power-on lifetime: 657 hours (27 days + 9 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 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 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 ff ff ff 4f 00 27d+09:25:11.126 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 27d+09:25:11.119 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 27d+09:25:11.117 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 27d+09:25:11.116 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 27d+09:25:11.115 READ FPDMA QUEUED Error 7 occurred at disk power-on lifetime: 657 hours (27 days + 9 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 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 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 ff ff ff 4f 00 27d+09:25:04.848 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 27d+09:25:04.791 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 27d+09:25:02.324 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 27d+09:25:02.315 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 27d+09:25:02.313 READ FPDMA QUEUED SYSLOG SYSLOG.txt
January 2, 201610 yr Looks like the disk has bad sectors, but without the full smart report (or diagnostics), its hard to tell
January 2, 201610 yr Author What test need to be run? Or should I replace the disk and RMA? ST4000VN000-1H416820160102-1336.txt
January 2, 201610 yr Probably a bad drive, but you should post the resulting file from Tools - Diagnostics. Your SMART report is only the command error log and doesn't display the attributes. Also, there may be more information in the syslog prior to the read errors which may pin down what the issue actually is
January 2, 201610 yr Author The full syslog will not post to large. I am currently running a long smart test attributes are attached to my last post.
January 2, 201610 yr 187 Reported_Uncorrect 0x0032 089 089 000 Old_age Always - 11 I don't have much experience with this attribute, but according to blackblaze it's one of the bad ones, any number above 0 is not good and the likelihood of the drive failing is much higher.
January 3, 201610 yr Author Thanks for the prompt replies. I have started the RMA process and a data rebuild is occurring on the new backup disk I have on hand.
Archived
This topic is now archived and is closed to further replies.