December 25, 201312 yr It hasn't been disabled, which means all of the errors were correctable ... most likely they were writes that reported an error but were okay when re-tried. Had you pre-cleared this drive before installing it? I'd shut down; re-seat the cables for the drive (or better yet use a new SATA cable with locking tabs and be sure it's securely attached at both ends); and then reboot the system. Clear the status (so everything is zero to start); then run a parity check, and see if the drive is error-free after the check. In addition, take a look at the SMART report for the drive and see what the reallocated sector counters look like. If all looks okay during that process, it's probably fine. Otherwise, I'd replace the drive.
December 25, 201312 yr It hasn't been disabled, which means all of the errors were correctable ... most likely they were writes that reported an error but were okay when re-tried. Had you pre-cleared this drive before installing it?Any SINGLE WRITE that failed would have taken the disk out of service. Since it still has a "green" indicator, the errors were "read" errors. The errors are far more likely to have been un-readable sectors than anything else. Their contents would have been re-constructed by parity and the remaining drives. They probably were then re-allocated when unRAID wrote the re-constructed contents back to the unreadable disk sectors. I would get a smart report on that disk and see what it says. Odds are you have one or two sectors pending-re-alocation/ or already re-allocated. I would look in the syslog to see if it mentions "media error" (and un-readable sector) or CRC error )noise pickup on SATA cable most common as they are NOT designed to be tie-wrapped together or run parallel to each other for neatness unless "shielded" (and most cables are not) I doubt there is anything wrong with the cabling itself and you'll find "media errors" in the syslog. Joe L.
December 25, 201312 yr Author ^^ Thanks guys. So...I should clear stats, run a parity check, and post my syslog? BTW...I did pre-clear; would posting my results shed any light? If so, if someone will remind me where to find the log, I'll do so.
December 25, 201312 yr The pre-clear results are stored on the flash drive in a folder called "preclear_reports"
December 25, 201312 yr Author Disk: /dev/sde smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-1CH166 Serial Number: W1F2WRKK LU WWN Device Id: 5 000c50 0608a92d2 Firmware Version: CC24 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Dec 19 20:31:56 2013 EST ==> WARNING: A firmware update for this drive may be available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en 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: ( 89) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 329) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 24624 3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 56 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 0 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 4 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 253 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 075 073 045 Old_age Always - 25 (Min/Max 17/25) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 9 194 Temperature_Celsius 0x0022 025 040 000 Old_age Always - 25 (0 16 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 0h+03m+22.149s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 0 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 524 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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 25, 201312 yr Author ========================================================================1.8 == invoked as: ./preclear_disk.sh /dev/sde == ST3000DM001-1CH166 W1F2WRKK == Disk /dev/sde has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:01:40 (138 MB/s) == Last Cycle's Zeroing time : 5:12:36 (159 MB/s) == Last Cycle's Post Read Time : 13:45:46 (60 MB/s) == Last Cycle's Total Time : 25:01:03 == == Total Elapsed Time 25:01:03 == == Disk Start Temperature: 25C == == Current Disk Temperature: 29C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 108 100 6 ok 16258616 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Reported_Uncorrect = 91 100 0 ok 9 High_Fly_Writes = 98 100 0 ok 2 Airflow_Temperature_Cel = 71 75 45 ok 29 Temperature_Celsius = 29 25 0 ok 29 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 16 sectors are pending re-allocation at the end of the preclear, a change of 16 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================
December 25, 201312 yr Author Disk: /dev/sde smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-1CH166 Serial Number: W1F2WRKK LU WWN Device Id: 5 000c50 0608a92d2 Firmware Version: CC24 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Fri Dec 20 21:32:59 2013 EST ==> WARNING: A firmware update for this drive may be available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en 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: ( 89) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 329) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 108 099 006 Pre-fail Always - 16258616 3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 404712 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 25 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 4 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 091 091 000 Old_age Always - 9 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 190 Airflow_Temperature_Cel 0x0022 071 067 045 Old_age Always - 29 (Min/Max 17/33) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 9 194 Temperature_Celsius 0x0022 029 040 000 Old_age Always - 29 (0 16 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 16 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 16 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 25h+04m+24.763s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 5860533216 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 17886279368 SMART Error Log Version: 1 ATA Error Count: 9 (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 9 occurred at disk power-on lifetime: 13 hours (0 days + 13 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 08 ff ff ff 4f 00 12:59:59.190 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 12:59:59.164 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 12:59:59.163 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 12:59:59.163 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 12:59:59.163 SET FEATURES [set transfer mode] Error 8 occurred at disk power-on lifetime: 13 hours (0 days + 13 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 08 ff ff ff 4f 00 12:59:55.723 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 12:59:53.091 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 12:59:53.090 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 12:59:53.090 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 12:59:53.090 IDENTIFY DEVICE Error 7 occurred at disk power-on lifetime: 13 hours (0 days + 13 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 08 ff ff ff 4f 00 12:59:49.862 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 12:59:49.862 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 12:59:49.861 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 12:59:49.861 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 12:59:49.861 IDENTIFY DEVICE Error 6 occurred at disk power-on lifetime: 13 hours (0 days + 13 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 12:59:31.941 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 12:59:31.940 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 12:59:31.939 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 12:59:31.939 READ FPDMA QUEUED 60 00 00 ff ff ff 4f 00 12:59:31.938 READ FPDMA QUEUED Error 5 occurred at disk power-on lifetime: 13 hours (0 days + 13 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 08 ff ff ff 4f 00 12:59:23.532 READ FPDMA QUEUED ef 10 02 00 00 00 a0 00 12:59:23.532 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 12:59:23.532 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 12:59:23.531 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 12:59:23.531 SET FEATURES [set transfer mode] SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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 25, 201312 yr The pre-clear showed you had 16 sectors pending reallocation. I suspect that when you started using the disk, the sector reads that precede a write (as part of the normal process for keeping parity up-to-date) failed, and the sectors were likely reallocated when UnRAID did a correcting write (and since the write was okay, the disk was not disabled). I'd do another SMART report to see what the disk looks like now.
December 25, 201312 yr Author The pre-clear showed you had 16 sectors pending reallocation. I suspect that when you started using the disk, the sector reads that precede a write (as part of the normal process for keeping parity up-to-date) failed, and the sectors were likely reallocated when UnRAID did a correcting write (and since the write was okay, the disk was not disabled). I'd do another SMART report to see what the disk looks like now. Short test results... === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST3000DM001-1CH166 Serial Number: W1F2WRKK LU WWN Device Id: 5 000c50 0608a92d2 Firmware Version: CC24 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Wed Dec 25 15:25:01 2013 EST ==> WARNING: A firmware update for this drive may be available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en 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: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: ( 89) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 329) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 67939976 3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 16 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 665736 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 139 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 4 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 082 082 000 Old_age Always - 18 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 096 096 000 Old_age Always - 4 190 Airflow_Temperature_Cel 0x0022 072 067 045 Old_age Always - 28 (Min/Max 17/33) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 129 194 Temperature_Celsius 0x0022 028 040 000 Old_age Always - 28 (0 16 0 0 0) 197 Current_Pending_Sector 0x0012 100 099 000 Old_age Always - 8 198 Offline_Uncorrectable 0x0010 100 099 000 Old_age Offline - 8 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 56h+53m+25.317s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 12849279704 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 24459994610 SMART Error Log Version: 1 ATA Error Count: 18 (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 18 occurred at disk power-on lifetime: 124 hours (5 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 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 5d+04:11:48.987 READ DMA EXT 25 00 00 ff ff ff ef 00 5d+04:11:48.968 READ DMA EXT ef 10 02 00 00 00 a0 00 5d+04:11:48.967 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 5d+04:11:48.967 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 5d+04:11:48.967 IDENTIFY DEVICE Error 17 occurred at disk power-on lifetime: 124 hours (5 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 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 5d+04:11:45.805 READ DMA EXT ef 10 02 00 00 00 a0 00 5d+04:11:45.804 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 5d+04:11:45.804 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 5d+04:11:45.803 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 5d+04:11:45.803 SET FEATURES [set transfer mode] Error 16 occurred at disk power-on lifetime: 124 hours (5 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 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 5d+04:11:42.295 READ DMA EXT ef 10 02 00 00 00 a0 00 5d+04:11:42.294 SET FEATURES [Enable SATA feature] 27 00 00 00 00 00 e0 00 5d+04:11:42.294 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3] ec 00 00 00 00 00 a0 00 5d+04:11:42.293 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 5d+04:11:42.293 SET FEATURES [set transfer mode] Error 15 occurred at disk power-on lifetime: 124 hours (5 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 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 5d+04:11:37.057 READ DMA EXT 25 00 08 ff ff ff ef 00 5d+04:11:37.039 READ DMA EXT 35 00 18 ff ff ff ef 00 5d+04:11:37.033 WRITE DMA EXT 35 00 e8 ff ff ff ef 00 5d+04:11:36.578 WRITE DMA EXT 35 00 00 ff ff ff ef 00 5d+04:11:36.576 WRITE DMA EXT Error 14 occurred at disk power-on lifetime: 124 hours (5 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 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 -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 5d+04:11:31.936 READ DMA EXT 25 00 00 ff ff ff ef 00 5d+04:11:31.932 READ DMA EXT 35 00 00 ff ff ff ef 00 5d+04:11:31.879 WRITE DMA EXT 35 00 00 ff ff ff ef 00 5d+04:11:31.877 WRITE DMA EXT 35 00 00 ff ff ff ef 00 5d+04:11:31.874 WRITE DMA EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 139 728698256 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 25, 201312 yr The drive has reallocated the 16 pendings it had after the pre-clear; and has developed 8 more pendings. It's clearly having issues ... so I'd RMA it and get a replacement.
December 25, 201312 yr Author The drive has reallocated the 16 pendings it had after the pre-clear; and has developed 8 more pendings. It's clearly having issues ... so I'd RMA it and get a replacement. $h*t; thanks.
December 25, 201312 yr Author OK, one last thing: I've already put it in my array, and (directly) copied about 500G of files to this new drive. How do I safely move the data? I can just move the directly copied files, to another drive with the space...right? And then...it's been a while; how do I pull this drive out of the array? Thanks
December 25, 201312 yr I'd copy everything off the drive to a backup drive on another system; then replace the drive and let UnRAID rebuild it. Alternatively, you can copy everything off the drive; then do a "New Config" and don't include that drive in the configuration.
December 26, 201312 yr Author I'd copy everything off the drive to a backup drive on another system; then replace the drive and let UnRAID rebuild it. Alternatively, you can copy everything off the drive; then do a "New Config" and don't include that drive in the configuration. So Gary...you're saying, if I just wait on the RMA'd drive; I can just pull the bad one, insert the new one...and have unRAID re-build the array, without moving the data off the bad drive first? If so...I think I'll go that route. I've already RMA'd the drive; so I'll just check back in, once it arrives...for further instructions. Thanks so much.
December 26, 201312 yr I'd copy everything off the drive to a backup drive on another system; then replace the drive and let UnRAID rebuild it. Alternatively, you can copy everything off the drive; then do a "New Config" and don't include that drive in the configuration. So Gary...you're saying, if I just wait on the RMA'd drive; I can just pull the bad one, insert the new one...and have unRAID re-build the array, without moving the data off the bad drive first? If so...I think I'll go that route. I've already RMA'd the drive; so I'll just check back in, once it arrives...for further instructions. Thanks so much. Run some preclear cycles on the replacement to help make sure it won't go the same route as the drive you are replacing.
December 26, 201312 yr I can just pull the bad one, insert the new one...and have unRAID re-build the array, without moving the data off the bad drive first? If so...I think I'll go that route. Agree with Bob's suggestion to do a pre-clear cycle or two to test the replacement before you do that. Also, although it's conceptually that simple, the process isn't exactly just pull/replace and go. You need to Stop the array; unassign the old drive; then Start the array so it shows a "missing" drive. Then shut down; physically swap the drive; and reboot. Stop the array (if it auto-started); assign the new drive to the same slot the old one was in; and then Start the array ... and it will now do the rebuild.
December 27, 201312 yr No reboot is required. Stop the array, un-assign the old drive, assign the new drive. Start the array and rebuild will comence.
December 27, 201312 yr No reboot is required IF the new drive is already installed and connected. I was simply noting the process IF you need to physically replace the drive.
December 28, 201312 yr Author ^^ Thanks guys. I'm waiting impatiently, for Amazon to replace the drive. Then I will check back in, and follow your directions to a tee...lol. Actually, I do have a question about the pre-clear: 1) I think all my slots are full (I'll have to double-check; and while I have the case open, I'll double-check my cables to this drive too). If they are, I probably will have to pull the bad drive first; so I can pre-clear the replacement. Only other thing I can think of, is to use a SATA/USB dock; but I assume that would take MUCH longer? 2) Even though I did a pre-clear last time...when I added this drive to the array, it still wrote all the zeros to the disk; whereas I was expecting, it was only supposed to format, and go much quicker. Any thoughts on why? Thanks, CD
December 28, 201312 yr If you added it as a replacement drive, it won't write zeroes, but it will take a long time as it has to rebuld the drive -- a pre-clear doesn't eliminate that. In the current case, since you'll be adding it to replace another drive, a pre-clear won't save any time ... but will give you some confidence that the drive doesn't have any infant mortality issues. Given your slot situation, I'd do the following: (a) Stop the array and unassign the bad drive. (b) Shut down and physically remove the old drive and replace it with the new. © Boot, and let the array start -- it will show a missing drive. Then Stop the array; and now run your pre-clear. (d) After the pre-clear completes; assign the drive to the old slot; then Start the array ... it will see the replacement drive and start the rebuild process.
January 3, 201412 yr Author If you added it as a replacement drive, it won't write zeroes, but it will take a long time as it has to rebuld the drive -- a pre-clear doesn't eliminate that. In the current case, since you'll be adding it to replace another drive, a pre-clear won't save any time ... but will give you some confidence that the drive doesn't have any infant mortality issues. Given your slot situation, I'd do the following: (a) Stop the array and unassign the bad drive. (b) Shut down and physically remove the old drive and replace it with the new. © Boot, and let the array start -- it will show a missing drive. Then Stop the array; and now run your pre-clear. (d) After the pre-clear completes; assign the drive to the old slot; then Start the array ... it will see the replacement drive and start the rebuild process. Replacement finally arrived today. Following the above steps, and will post as needed. Thanks!! Pre-clear is running. I never really know what are good or bad results...lol. So I'll post them, once it's done.
January 4, 201412 yr Author OK; pre-clear is done. What is the proper method, to add the new drive...replacing the old drive; so unRAID will rebuild the array? TIA Oh wait...I'll try Gary's step d from above.
Archived
This topic is now archived and is closed to further replies.