gerhard911 Posted August 16, 2011 Share Posted August 16, 2011 I have a drive that has gone to Device status red. I have looked at the Syslog and nothing looks abnormal. It passes SMART short test but SMART status does show the following: SMART Error Log Version: 1 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: 415 hours (17 days + 7 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 -- -- -- -- -- -- -- 84 51 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 a0 08 09:58:49.411 IDENTIFY DEVICE ec 00 01 00 00 00 a0 04 09:58:49.252 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 09:58:34.324 IDENTIFY DEVICE ec 00 00 00 00 00 a0 04 09:58:34.165 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 09:58:29.196 IDENTIFY DEVICE Error 1 occurred at disk power-on lifetime: 415 hours (17 days + 7 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 -- -- -- -- -- -- -- 84 51 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 a0 08 09:58:29.196 IDENTIFY DEVICE e5 00 ff 00 00 00 00 04 09:58:29.037 CHECK POWER MODE e5 00 00 00 00 00 40 08 09:58:11.543 CHECK POWER MODE e5 00 00 00 00 00 40 08 09:58:01.575 CHECK POWER MODE e5 00 00 00 00 00 40 08 09:57:51.607 CHECK POWER MODE Am I correct in assuming the 2 hex 84 errors shown are the reason this drive has a red status in unRAID ? Where can I find the Error Register hex codes ? The drive status went red overnight after upgrading from Beta5.9 to Beta5.11. I rolled back to 5.9 with no change. Syslog and full SMART info attached. TIA for any advice. Aug_16_09.zip MJ1323YNG11W1C.txt Link to comment
dgaschk Posted August 17, 2011 Share Posted August 17, 2011 The disk has a red ball because a write to it failed. You can try to run pre-clear on it a couple of times and see if it passes. I suggest that you replace and rebuild first. Link to comment
dgaschk Posted August 17, 2011 Share Posted August 17, 2011 You can also try to rebuild the disk on to itself. 1) stop the array unassign the disk. 2) start the array with the disk unassigned so unRAID forgets about it. 3) stop the array and assign the disk. 4) start the array and rebuild. Link to comment
gerhard911 Posted August 17, 2011 Author Share Posted August 17, 2011 You can also try to rebuild the disk on to itself. 1) stop the array unassign the disk. 2) start the array with the disk unassigned so unRAID forgets about it. 3) stop the array and assign the disk. 4) start the array and rebuild. After the disk passed a long SMART test overnight, this is what I started this morning. Rebuild is at @ 50%. When unRAID red-balled the drive there should have been no disk activity. It was middle of the night and I would have expected all drives to have been spun down. Pretty strange. Thanks for the response. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.