October 31, 201510 yr hi all, i recently removed a drive from my server, so i did a `new config`and rebuilt parity. When parity build was complete, i had 6 errors on disk 5. i have the smart report below. nervous the drive may be going bad. also not sure parity is okay because of the errors. what should i do? 1.Copy all data off drive 5 immediately? 2. or can i just swap in a new drive, and rebuild data onto it? not sure if this will work since there were 6 errors on drive5, so i'm not sure parity is complete please help with some advice! Statistics for /dev/sdd ST3000DM001-9YN166_W1F0A74C smartctl -a -d ata /dev/sdd smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-9YN166 Serial Number: W1F0A74C Firmware Version: CC4C User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sat Oct 31 07:37:37 2015 CDT 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: ( 575) 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: ( 255) 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 - 16057312 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 092 092 020 Old_age Always - 9147 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 076 060 030 Pre-fail Always - 13010399084 9 Power_On_Hours 0x0032 065 065 000 Old_age Always - 31451 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 111 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 089 089 000 Old_age Always - 11 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 068 063 045 Old_age Always - 32 (Min/Max 30/35) 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 - 59 193 Load_Cycle_Count 0x0032 036 036 000 Old_age Always - 128404 194 Temperature_Celsius 0x0022 032 040 000 Old_age Always - 32 (0 19 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 8 198 Offline_Uncorrectable 0x0010 100 100 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 - 51599737099680 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 27102901366198 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 57089185297655 SMART Error Log Version: 1 ATA Error Count: 4 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 4 occurred at disk power-on lifetime: 31441 hours (1310 days + 1 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 08 ff ff ff ef 00 1d+02:59:38.556 READ DMA EXT 25 00 08 ff ff ff ef 00 1d+02:59:38.413 READ DMA EXT 25 00 08 ff ff ff ef 00 1d+02:59:38.406 READ DMA EXT 25 00 08 ff ff ff ef 00 1d+02:59:38.384 READ DMA EXT c8 00 08 c0 00 00 e0 00 1d+02:59:38.362 READ DMA Error 3 occurred at disk power-on lifetime: 31441 hours (1310 days + 1 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 d1 08 ff ff ff ef 00 1d+02:59:34.434 READ DMA EXT 25 d1 08 ff ff ff ef 00 1d+02:59:34.430 READ DMA EXT 25 d1 08 ff ff ff ef 00 1d+02:59:34.412 READ DMA EXT 35 d1 08 ff ff ff ef 00 1d+02:59:34.329 WRITE DMA EXT 35 d1 08 ff ff ff ef 00 1d+02:59:34.328 WRITE DMA EXT Error 2 occurred at disk power-on lifetime: 31431 hours (1309 days + 15 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 d1 00 ff ff ff ef 00 16:53:32.113 READ DMA EXT 25 d1 00 ff ff ff ef 00 16:53:32.103 READ DMA EXT 25 d1 00 ff ff ff ef 00 16:53:32.088 READ DMA EXT 25 d1 00 ff ff ff ef 00 16:53:24.055 READ DMA EXT 25 d1 00 ff ff ff ef 00 16:53:24.040 READ DMA EXT Error 1 occurred at disk power-on lifetime: 12787 hours (532 days + 19 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 d1 00 ff ff ff ef 00 03:13:56.421 READ DMA EXT 25 d1 00 ff ff ff ef 00 03:13:56.401 READ DMA EXT 35 d1 60 ff ff ff ef 00 03:13:56.395 WRITE DMA EXT 35 d1 00 ff ff ff ef 00 03:13:56.392 WRITE DMA EXT 35 d1 a0 ff ff ff ef 00 03:13:56.389 WRITE DMA EXT 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.
October 31, 201510 yr The drive has pending sectors. Did you preclear it before using it? I would preclear another drive and rebuild onto it, then see if you can fix the pending sectors on this drive by preclearing it.
October 31, 201510 yr Author i precleared it years ago, its been in my system for about 3 years. the errors just showed up on the GUI, it showed '6' errors. the funny thing is that i just went to the GUI and it now shows '0'? very odd, i know you may think i imagined it but it def said 6 before I am doing just what you said- currently preclearing a fresh drive, then i will rebuild disk 5 onto the new disk, and then i can run preclear on the former disk thanks for the advice, because of the 6 errors, i wasn't sure i would be able to rebuild a new disk. i thought i had read that if there are errors with parity, the rebuild will fail
Archived
This topic is now archived and is closed to further replies.