jncunha Posted April 21, 2022 Share Posted April 21, 2022 Hi! One of my array drives is giving me the "Reported uncorrect" error. This is a normal Seagate Barracuda 4TB disk. I'm wondering if it's time to replace the disk or if there is something that can be done to fix the error (I know this might be a dumb question but I know zero of SMART errors and what they mean). I've attached the diagnostics .zip if anyone is able to help and point me in the right direction. Also I would like to start understanding what drives the decision of replacing the drive or to keep running according to the specificity to the SMART error. I think I started having this error after a power outage. I ran the SMART self-test (the short one) and it passes. I can try the extended one if that helps for the diagnostic. Thanks for the help! jonas-nas-diagnostics-20220421-1237.zip Quote Link to comment
JorgeB Posted April 21, 2022 Share Posted April 21, 2022 Never a great sign but it should still be OK unless it keeps climbing, you can run an extended SMART test to confirm. Quote Link to comment
jncunha Posted April 21, 2022 Author Share Posted April 21, 2022 7 minutes ago, JorgeB said: Never a great sign but it should still be OK unless it keeps climbing, you can run an extended SMART test to confirm. Ok sounds good. Thanks for the help. I will do the extended test and post the result here. If I acknowledge the error in the dashboard and the number keeps climbing will I get the warning again? Quote Link to comment
JorgeB Posted April 21, 2022 Share Posted April 21, 2022 2 minutes ago, jncunha said: If I acknowledge the error in the dashboard and the number keeps climbing will I get the warning again? Yep. Quote Link to comment
jncunha Posted April 22, 2022 Author Share Posted April 22, 2022 17 hours ago, JorgeB said: Never a great sign but it should still be OK unless it keeps climbing, you can run an extended SMART test to confirm. So I left the extended test running during the night and this is what I've got as a result: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 17359 - # 2 Short offline Completed without error 00% 17338 - # 3 Short offline Completed without error 00% 9732 - # 4 Short offline Completed without error 00% 9084 - # 5 Short offline Completed without error 00% 8634 - # 6 Short offline Completed without error 00% 8159 - # 7 Short offline Completed without error 00% 7416 - # 8 Short offline Completed without error 00% 6008 - # 9 Short offline Completed without error 00% 5376 - #10 Short offline Completed without error 00% 4656 - #11 Short offline Completed without error 00% 3912 - #12 Short offline Completed without error 00% 3046 - #13 Short offline Completed without error 00% 2318 - #14 Short offline Completed without error 00% 1922 - #15 Extended offline Completed without error 00% 1572 - #16 Short offline Completed without error 00% 676 - ATA Error Count: 6 (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 6 occurred at disk power-on lifetime: 17332 hours (722 days + 4 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 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 10 ff ff ff 4f 00 02:02:19.032 READ FPDMA QUEUED 60 00 38 ff ff ff 4f 00 02:02:19.031 READ FPDMA QUEUED 61 00 08 ff ff ff 4f 00 02:02:19.031 WRITE FPDMA QUEUED 61 00 e0 ff ff ff 4f 00 02:02:19.031 WRITE FPDMA QUEUED 61 00 08 ff ff ff 4f 00 02:02:19.030 WRITE FPDMA QUEUED Error 5 occurred at disk power-on lifetime: 17332 hours (722 days + 4 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 ff ff ff 0f Error: WP 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 40 ff ff ff 4f 00 02:02:13.319 WRITE FPDMA QUEUED 60 00 08 ff ff ff 4f 00 02:02:13.308 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 02:02:13.308 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 02:02:13.307 READ FPDMA QUEUED 60 00 e0 ff ff ff 4f 00 02:02:13.306 READ FPDMA QUEUED Error 4 occurred at disk power-on lifetime: 17332 hours (722 days + 4 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 ff ff ff 0f Error: WP 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 e8 ff ff ff 4f 00 02:02:07.911 WRITE FPDMA QUEUED 60 00 30 ff ff ff 4f 00 02:02:07.911 READ FPDMA QUEUED 60 00 98 ff ff ff 4f 00 02:02:07.910 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 02:02:07.910 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 02:02:07.910 READ FPDMA QUEUED Error 3 occurred at disk power-on lifetime: 17332 hours (722 days + 4 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 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 40 ff ff ff 4f 00 02:02:03.511 READ FPDMA QUEUED 61 00 20 ff ff ff 4f 00 02:02:03.511 WRITE FPDMA QUEUED 60 00 98 ff ff ff 4f 00 02:02:03.510 READ FPDMA QUEUED 60 00 30 ff ff ff 4f 00 02:02:03.510 READ FPDMA QUEUED 60 00 f0 ff ff ff 4f 00 02:02:03.509 READ FPDMA QUEUED Error 2 occurred at disk power-on lifetime: 17332 hours (722 days + 4 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 ff ff ff 0f Error: WP 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 20 ff ff ff 4f 00 02:01:58.635 WRITE FPDMA QUEUED 60 00 40 ff ff ff 4f 00 02:01:58.618 READ FPDMA QUEUED 60 00 f0 ff ff ff 4f 00 02:01:58.616 READ FPDMA QUEUED 60 00 30 ff ff ff 4f 00 02:01:58.615 READ FPDMA QUEUED 60 00 98 ff ff ff 4f 00 02:01:58.615 READ FPDMA QUEUED Also the SMART report file in attachment. Thanks! ST4000DM004-2CV104_ZFN0WN16-20220422-0758.txt Quote Link to comment
JorgeB Posted April 22, 2022 Share Posted April 22, 2022 Disk is OK for now, just keep monitoring. Quote Link to comment
Recommended Posts
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.