December 14, 201510 yr Sigh what a bloody day! Trying (and failing) to get mysql/mariadb up and running with Kodi and then I see my parity drive is down!!!! Though it looks fine to me. I'm so confused! smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.7-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WD60EFRX-68MYMN1 Serial Number: WD-WX51D6427226 LU WWN Device Id: 5 0014ee 260205560 Firmware Version: 82.00A82 User Capacity: 6,001,175,126,016 bytes [6.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5700 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Mon Dec 14 19:32:21 2015 GMT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 5204) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 705) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 193 021 Pre-fail Always - 4916 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 535 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 10509 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 34 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1516 194 Temperature_Celsius 0x0022 116 108 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 ATA Error Count: 21 (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 21 occurred at disk power-on lifetime: 10475 hours (436 days + 11 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 08 00 e4 00 e0 Error: UNC 8 sectors at LBA = 0x0000e400 = 58368 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 00 e4 00 e0 08 1d+18:35:04.410 READ DMA ca 00 08 f8 e3 00 e0 08 1d+18:35:04.410 WRITE DMA ca 00 08 f0 e3 00 e0 08 1d+18:35:04.410 WRITE DMA ca 00 08 e8 e3 00 e0 08 1d+18:35:04.410 WRITE DMA ec 00 00 00 00 00 a0 08 1d+18:35:04.409 IDENTIFY DEVICE Error 20 occurred at disk power-on lifetime: 10475 hours (436 days + 11 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 -- -- -- -- -- -- -- 10 51 08 e8 e3 00 e0 Error: IDNF at LBA = 0x0000e3e8 = 58344 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ca 00 08 e8 e3 00 e0 08 1d+18:34:57.412 WRITE DMA c8 00 08 f8 e3 00 e0 08 1d+18:34:57.412 READ DMA c8 00 08 f0 e3 00 e0 08 1d+18:34:57.412 READ DMA c8 00 08 e8 e3 00 e0 08 1d+18:34:57.411 READ DMA Error 19 occurred at disk power-on lifetime: 10474 hours (436 days + 10 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 08 a0 e3 00 e0 Error: UNC 8 sectors at LBA = 0x0000e3a0 = 58272 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 a0 e3 00 e0 08 1d+18:32:54.465 READ DMA Error 18 occurred at disk power-on lifetime: 10474 hours (436 days + 10 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 -- -- -- -- -- -- -- 10 51 10 68 e3 00 e0 Error: IDNF at LBA = 0x0000e368 = 58216 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ca 00 10 68 e3 00 e0 08 1d+18:31:29.314 WRITE DMA c8 00 08 78 e3 00 e0 08 1d+18:31:29.314 READ DMA c8 00 08 70 e3 00 e0 08 1d+18:31:29.313 READ DMA c8 00 08 68 e3 00 e0 08 1d+18:31:29.313 READ DMA Error 17 occurred at disk power-on lifetime: 10474 hours (436 days + 10 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 08 40 e3 00 e0 Error: UNC 8 sectors at LBA = 0x0000e340 = 58176 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 40 e3 00 e0 08 1d+18:30:12.563 READ DMA ca 00 08 38 e3 00 e0 08 1d+18:30:12.547 WRITE DMA ca 00 08 30 e3 00 e0 08 1d+18:30:12.527 WRITE DMA ec 00 00 00 00 00 a0 08 1d+18:30:12.526 IDENTIFY DEVICE SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 1258 - # 2 Short offline Completed without error 00% 1206 - # 3 Short offline Completed without error 00% 1206 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
December 14, 201510 yr What exactly do you mean by "down"? Does it have a red X next to it? What do I do if I get a red X next to a hard disk?
December 14, 201510 yr Author Apologies I should have been clearer, yeah red X though for some reason it's a red triangle on my version now... I also should have re-read that report, I missed the errors. Long ass day, sorry. I guess my question is do I get a new one, or do I RMA this one, or do i re-enable? The errors do not mean a lot to me. (It seems to have died since trying to open a mysql connnection into it earlier today, seems like a huge co-incidence but still)
December 14, 201510 yr I think the triangle just means invalid, which it is since it is disabled. Since the parity drive doesn't contain any of your data it is very unlikely that your mysql issue is related. Check your connections and rebuild parity. SMART attributes look OK.
December 14, 201510 yr Author Yeah I know what you mean, it just seems amazingly co-incidental that the mysql connection has become connectable at the same time as the same time as the parity drive. Thanks though Trurl I'll check the connections tomorrow and rebuild it! I'll also read that SMART link, thanks again.
December 15, 201510 yr Author Connections are all good...just got to rebuild about 14gig of parity now...so 15 more hours ha ha.
December 15, 201510 yr Connections are all good...just got to rebuild about 14gig of parity now...so 15 more hours ha ha. I know you said ha ha but I don't get it. Do you mean all but 14GB of parity is complete and that 14GB is going to take an additional 15 hours? Or did you really mean 14TB of data for your array, which is somewhat irrelevant since the size of parity is the main factor in how long it should take unless you have some kind of controller bottleneck.
Archived
This topic is now archived and is closed to further replies.