Superorb Posted June 1, 2011 Share Posted June 1, 2011 What is the command to print the preclear script version? Quote Link to comment
Joe L. Posted June 1, 2011 Share Posted June 1, 2011 What is the command to print the preclear script version? preclear_disk.sh -v Quote Link to comment
Superorb Posted June 1, 2011 Share Posted June 1, 2011 Thanks Joe. For some reason I thought there was a button in unMenu for preclear version, but I only found one for unMNenu version. Quote Link to comment
ilovegoodnugz Posted June 2, 2011 Share Posted June 2, 2011 ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 095 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 168 100 050 Pre-fail Offline - 162 3 Spin_Up_Time 0x0007 106 099 024 Pre-fail Always - 492 (Average 447) 4 Start_Stop_Count 0x0012 099 099 000 Old_age Always - 6544 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 1 (0, 1) 7 Seek_Error_Rate 0x000b 100 076 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 132 100 020 Pre-fail Offline - 33 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 4045 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 6539 192 Power-Off_Retract_Count 0x0032 095 095 000 Old_age Always - 6548 193 Load_Cycle_Count 0x0012 095 095 000 Old_age Always - 6548 194 Temperature_Celsius 0x0002 171 127 000 Old_age Always - 35 (Min/Max 15/49) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 1 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 47 (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 47 occurred at disk power-on lifetime: 4036 hours (168 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 08 a8 40 5b e1 Error: UNC 8 sectors at LBA = 0x015b40a8 = 22757544 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 a8 40 5b e0 08 01:23:06.200 READ DMA EXT ec 00 00 00 00 00 a0 08 01:23:06.200 IDENTIFY DEVICE ef 03 45 00 00 00 a0 08 01:23:06.200 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 01:23:06.200 IDENTIFY DEVICE 25 00 08 a8 40 5b e0 08 01:23:00.400 READ DMA EXT Error 46 occurred at disk power-on lifetime: 4036 hours (168 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 08 a8 40 5b e1 Error: UNC 8 sectors at LBA = 0x015b40a8 = 22757544 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 a8 40 5b e0 08 01:23:00.400 READ DMA EXT ec 00 00 00 00 00 a0 08 01:23:00.400 IDENTIFY DEVICE ef 03 45 00 00 00 a0 08 01:23:00.400 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 01:23:00.400 IDENTIFY DEVICE 25 00 08 a8 40 5b e0 08 01:22:54.700 READ DMA EXT Error 45 occurred at disk power-on lifetime: 4036 hours (168 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 08 a8 40 5b e1 Error: UNC 8 sectors at LBA = 0x015b40a8 = 22757544 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 a8 40 5b e0 08 01:22:54.700 READ DMA EXT ec 00 00 00 00 00 a0 08 01:22:54.700 IDENTIFY DEVICE ef 03 45 00 00 00 a0 08 01:22:54.700 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 01:22:54.700 IDENTIFY DEVICE 25 00 08 a8 40 5b e0 08 01:22:49.000 READ DMA EXT Error 44 occurred at disk power-on lifetime: 4036 hours (168 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 08 a8 40 5b e1 Error: UNC 8 sectors at LBA = 0x015b40a8 = 22757544 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 a8 40 5b e0 08 01:22:49.000 READ DMA EXT ec 00 00 00 00 00 a0 08 01:22:49.000 IDENTIFY DEVICE ef 03 45 00 00 00 a0 08 01:22:49.000 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 01:22:49.000 IDENTIFY DEVICE 25 00 08 a8 40 5b e0 08 01:22:43.300 READ DMA EXT Error 43 occurred at disk power-on lifetime: 4036 hours (168 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 08 a8 40 5b e1 Error: UNC 8 sectors at LBA = 0x015b40a8 = 22757544 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 a8 40 5b e0 08 01:22:43.300 READ DMA EXT ec 00 00 00 00 00 a0 08 01:22:43.300 IDENTIFY DEVICE ef 03 45 00 00 00 a0 08 01:22:43.300 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 01:22:43.300 IDENTIFY DEVICE 25 00 08 a8 40 5b e0 08 01:22:37.700 READ 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 without error 00% 4033 - 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.[list] See alot of problems with the hex codes, can someone help? Trash or good? Quote Link to comment
Joe L. Posted June 3, 2011 Share Posted June 3, 2011 ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 095 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 168 100 050 Pre-fail Offline - 162 3 Spin_Up_Time 0x0007 106 099 024 Pre-fail Always - 492 (Average 447) 4 Start_Stop_Count 0x0012 099 099 000 Old_age Always - 6544 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 1 (0, 1) 7 Seek_Error_Rate 0x000b 100 076 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 132 100 020 Pre-fail Offline - 33 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 4045 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 6539 192 Power-Off_Retract_Count 0x0032 095 095 000 Old_age Always - 6548 193 Load_Cycle_Count 0x0012 095 095 000 Old_age Always - 6548 194 Temperature_Celsius 0x0002 171 127 000 Old_age Always - 35 (Min/Max 15/49) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 1 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 47 (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 47 occurred at disk power-on lifetime: 4036 hours (168 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 08 a8 40 5b e1 Error: UNC 8 sectors at LBA = 0x015b40a8 = 22757544 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 a8 40 5b e0 08 01:23:06.200 READ DMA EXT ec 00 00 00 00 00 a0 08 01:23:06.200 IDENTIFY DEVICE ef 03 45 00 00 00 a0 08 01:23:06.200 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 01:23:06.200 IDENTIFY DEVICE 25 00 08 a8 40 5b e0 08 01:23:00.400 READ DMA EXT Error 46 occurred at disk power-on lifetime: 4036 hours (168 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 08 a8 40 5b e1 Error: UNC 8 sectors at LBA = 0x015b40a8 = 22757544 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 a8 40 5b e0 08 01:23:00.400 READ DMA EXT ec 00 00 00 00 00 a0 08 01:23:00.400 IDENTIFY DEVICE ef 03 45 00 00 00 a0 08 01:23:00.400 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 01:23:00.400 IDENTIFY DEVICE 25 00 08 a8 40 5b e0 08 01:22:54.700 READ DMA EXT Error 45 occurred at disk power-on lifetime: 4036 hours (168 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 08 a8 40 5b e1 Error: UNC 8 sectors at LBA = 0x015b40a8 = 22757544 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 a8 40 5b e0 08 01:22:54.700 READ DMA EXT ec 00 00 00 00 00 a0 08 01:22:54.700 IDENTIFY DEVICE ef 03 45 00 00 00 a0 08 01:22:54.700 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 01:22:54.700 IDENTIFY DEVICE 25 00 08 a8 40 5b e0 08 01:22:49.000 READ DMA EXT Error 44 occurred at disk power-on lifetime: 4036 hours (168 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 08 a8 40 5b e1 Error: UNC 8 sectors at LBA = 0x015b40a8 = 22757544 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 a8 40 5b e0 08 01:22:49.000 READ DMA EXT ec 00 00 00 00 00 a0 08 01:22:49.000 IDENTIFY DEVICE ef 03 45 00 00 00 a0 08 01:22:49.000 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 01:22:49.000 IDENTIFY DEVICE 25 00 08 a8 40 5b e0 08 01:22:43.300 READ DMA EXT Error 43 occurred at disk power-on lifetime: 4036 hours (168 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 08 a8 40 5b e1 Error: UNC 8 sectors at LBA = 0x015b40a8 = 22757544 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 a8 40 5b e0 08 01:22:43.300 READ DMA EXT ec 00 00 00 00 00 a0 08 01:22:43.300 IDENTIFY DEVICE ef 03 45 00 00 00 a0 08 01:22:43.300 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 01:22:43.300 IDENTIFY DEVICE 25 00 08 a8 40 5b e0 08 01:22:37.700 READ 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 without error 00% 4033 - 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.[list] See alot of problems with the hex codes, can someone help? Trash or good? You can ignore almost all of that in the smart report. There is one re-allocated sector, none pending re-allocation. Unless you know something we do not, it is fine. Run it through a preclear cycle. If no more sectors show up as being re-allocated, then use the drive. Joe L. Quote Link to comment
axeman Posted June 4, 2011 Share Posted June 4, 2011 gaaaaaaaaaaaaaaaa i was toying with esxi and it auto formatted one of the drives (i'm guessing sda)... will unraid think it's not pre-cleared, meaning i'll have to run another cycle on it? Quote Link to comment
Joe L. Posted June 4, 2011 Share Posted June 4, 2011 If it formatted the drive, it is no longer cleared. You can test with preclear_disk.sh -t /dev/sdX It will tell you if it thinks it is cleared. Quote Link to comment
axeman Posted June 4, 2011 Share Posted June 4, 2011 blech! == Disk /dev/sda is NOT precleared also i'm new to linux - is it "normal" to have the drives listed 2x in the main of Unmenu? i see /dev/sdb and then right below it /dev/sdb1 on the devices tab of unraid, the drop downs only show the actual number of disks.... so i should run another pre-clear then right? Quote Link to comment
BRiT Posted June 4, 2011 Share Posted June 4, 2011 One is the entire drive [/dev/sdb] and the other is the first partition of the drive [/dev/sdb1]. Quote Link to comment
axeman Posted June 4, 2011 Share Posted June 4, 2011 One is the entire drive [/dev/sdb] and the other is the first partition of the drive [/dev/sdb1]. ah makes sense. i saw the esxi formatted drive have like 1/2 dozen. ty learned something today. Quote Link to comment
cherritaker Posted June 5, 2011 Share Posted June 5, 2011 Hello posting a preclear result for a friend if you guys can help out determining if its good or bad thank you. ========================================================================1.11 == invoked as: ./preclear_disk.sh -M 4 /dev/sdf == WDC WD20EARS-00MVWB0 WD-WCAZA5998739 == Disk /dev/sdf 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:20:29 (87 MB/s) == Last Cycle's Zeroing time : 6:13:53 (89 MB/s) == Last Cycle's Post Read Time : 12:44:24 (43 MB/s) == Last Cycle's Total Time : 25:19:54 == == Total Elapsed Time 25:19:54 == == Disk Start Temperature: 24C == == Current Disk Temperature: 26C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 124 126 0 ok 26 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. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. ============================================================================ ============================================================================ == == S.M.A.R.T Initial Report for /dev/sdf == Disk: /dev/sdf smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA5998739 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Jun 3 18:26:53 2011 Local time zone must be set--see zic m 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: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. 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: (36480) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status 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 100 253 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 1025 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 10 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 0 10 Spin_Retry_Count 0x0032 100 253 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 - 8 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 7 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 16 194 Temperature_Celsius 0x0022 126 122 000 Old_age Always - 24 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 253 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 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. == ============================================================================ ============================================================================ == == S.M.A.R.T Final Report for /dev/sdf == Disk: /dev/sdf smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA5998739 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Jun 4 19:46:46 2011 Local time zone must be set--see zic m 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: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. 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: (36480) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status 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 253 021 Pre-fail Always - 1025 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 10 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 24 10 Spin_Retry_Count 0x0032 100 253 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 - 8 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 7 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 17 194 Temperature_Celsius 0x0022 124 122 000 Old_age Always - 26 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 100 253 000 Old_age Offline - 0 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. == ============================================================================ Quote Link to comment
BRiT Posted June 5, 2011 Share Posted June 5, 2011 Here is all that you need to know: ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 124 126 0 ok 26 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. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. Quote Link to comment
vinnie Posted June 5, 2011 Share Posted June 5, 2011 I've just started putting together my first unRAID server and I'm putting my disks through at least one preclear each...for now. I have a WD20EARS disk that is causing an issue though. So far I have run it through 4 preclear cylcles but I'm constantly getting pending sector reallocations yet none actually get reallocated. Here are the results from all four preclears: 1st: ========================================================================1.11 == invoked as: ./preclear_disk.sh /dev/sda == WDC WD20EARS-00MVWB0 WD-WCAZA2953831 == Disk /dev/sda has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:56:37 (80 MB/s) == Last Cycle's Zeroing time : 6:09:35 (90 MB/s) == Last Cycle's Post Read Time : 19:21:43 (28 MB/s) == Last Cycle's Total Time : 32:29:03 == == Total Elapsed Time 32:29:03 == == Disk Start Temperature: 23C == == Current Disk Temperature: 24C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 189 100 51 ok 1198 Temperature_Celsius = 126 127 0 ok 24 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. 52 sectors are pending re-allocation at the end of the preclear, a change of 52 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. ============================================================================ 2nd: ========================================================================1.11 == invoked as: ./preclear_disk.sh /dev/sda == WDC WD20EARS-00MVWB0 WD-WCAZA2953831 == Disk /dev/sda has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:01:17 (79 MB/s) == Last Cycle's Zeroing time : 6:13:34 (89 MB/s) == Last Cycle's Post Read Time : 19:01:40 (29 MB/s) == Last Cycle's Total Time : 32:17:39 == == Total Elapsed Time 32:17:39 == == Disk Start Temperature: 22C == == Current Disk Temperature: 26C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 187 189 51 ok 2935 Temperature_Celsius = 124 128 0 ok 26 No SMART attributes are FAILING_NOW 52 sectors were pending re-allocation before the start of the preclear. 54 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. 47 sectors are pending re-allocation at the end of the preclear, a change of -5 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. ============================================================================ 3rd: ========================================================================1.11 == invoked as: ./preclear_disk.sh /dev/sda == WDC WD20EARS-00MVWB0 WD-WCAZA2953831 == Disk /dev/sda has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:00:12 (79 MB/s) == Last Cycle's Zeroing time : 6:11:21 (89 MB/s) == Last Cycle's Post Read Time : 19:09:52 (28 MB/s) == Last Cycle's Total Time : 32:22:33 == == Total Elapsed Time 32:22:33 == == Disk Start Temperature: 26C == == Current Disk Temperature: 27C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 186 187 51 ok 4613 Temperature_Celsius = 123 124 0 ok 27 No SMART attributes are FAILING_NOW 47 sectors were pending re-allocation before the start of the preclear. 47 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. 44 sectors are pending re-allocation at the end of the preclear, a change of -3 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. ============================================================================ 4th: ========================================================================1.11 == invoked as: ./preclear_disk.sh /dev/sdf == WDC WD20EARS-00MVWB0 WD-WCAZA2953831 == Disk /dev/sdf has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:59:59 (79 MB/s) == Last Cycle's Zeroing time : 6:07:23 (90 MB/s) == Last Cycle's Post Read Time : 19:22:29 (28 MB/s) == Last Cycle's Total Time : 32:30:58 == == Total Elapsed Time 32:30:58 == == Disk Start Temperature: 31C == == Current Disk Temperature: 29C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 121 119 0 ok 29 No SMART attributes are FAILING_NOW 44 sectors were pending re-allocation before the start of the preclear. 45 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. 44 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. ============================================================================ After the 3rd cycle I put the disk to one side and ran preclears on my other new disks in the same slot in my 5-in-3 that I had used for this disk thinking that I might also see problems with preclearing other disks if it was a power or data connection issue etc. However all the other disks precleared without a problem. I then ran a 4th cycle on this disk and it's still showing Pending Sector Realloation. I have been seeing a slow reduction of Raw_Read_Error_Rate with each cycle and and increase in its RAW value. The Normalised value didn't decrease in the last cycle however the RAW value did still increase (to 6225). During the read phase of the preclear I have been seeing UNC errors in the syslog and in the preclear final results. Please see attached preclear results for details. I've read though this entire thread and have seen others have this problem in the past. I'm wondering what others have done with their disks after having such problems - put in the Array or RMA it?. The disk still doesn't actually have any reallocated sectors but the Raw_Read_Error_Rate is slowly getting worse. I think I might start with a 5th cycle and then see how it looks. Any thoughts or comments would be much appreciated. Cheers Vin WCAZA2953831_cycle_4_preclear_finish_2011-06-05.txt Quote Link to comment
Joe L. Posted June 5, 2011 Share Posted June 5, 2011 First step is to ensure your power supply is up to the task of powering all your disks. Please list the exact make model and the number of disks connected to it. Every "read" phase seems to identify un-readable sectors. The subsequent "write" phase seems to re-write them in place, but then the post-read cannot read them again, and again they are marked as pending re-allocation. If it were me, and the disk was connected to a good power supply, I'd RMA it. Quote Link to comment
vinnie Posted June 5, 2011 Share Posted June 5, 2011 Hi Joe, thanks for a really quick response. My Server is: Supermicro X7SPA-HF-D525 Crucial 2 x 2GB SODIMM PC3 - 10600 Nexus Prominent 9 Case 3 x XCase X-531 5-in-3 racks (Same as Norco SS-500) Corsair TX650 Power supply I've since addded a Supermicro AOC-SASLP-MV8 card but the first three cycles were done without this card and the problem Disk was the only disk powered up in the case. The first three cycles were done before I added any Disks to the array. I'm now just running with 3 Disks in the array (1 Pariity 2 Data). I'm just waiting for a copy operation to complete before I can take the array down and copy over my shiny new unRAID Pro license file to the Thumb Drive. I'm not using any Molex splitters and all the the 5-in-3's are being powered directly from the Power supply connectors (two per 5-in-3). I've precleared 3 other Disks (1 x WD20EARS, 2 x Hitachi 5K3000) in the same setup without a problem, so I don't think it's the power or data cabling and I think the power supply should be plenty enough for what I currently have in the case, certainly for the small amount of Disks that I currently have powered in the machine (~5). I think I'll run a 5th cycle and see that happens, but if I want to RMA it to Scan rather than Western Digital then I'm getting close to the end of my 28 day return window. I'll post my results in another 32hrs. Quote Link to comment
dark_avenger Posted June 6, 2011 Share Posted June 6, 2011 Hi, I've had a 1.5tb drive in my array for ~6 months and the other day unraid flagged it as having an error so I've swapped the drive out with another 1.5tb drive. I plugged the old drive into a test unraid machine and ran 2 passes of preclear on it to check SMART status, etc. I've attached the preclear log, are any of the SMART attributes bad enough for RMA? Thanks in advance, David EDIT: Attached the other 2 log files preclear_finish_sdb_2011-06-02.txt preclear_rpt_sdb_2011-06-02.txt preclear_start_sdb_2011-06-02.txt Quote Link to comment
erikm101 Posted June 6, 2011 Share Posted June 6, 2011 Hello. Just completed my first cycle of preclear on two drives. Results file attached. This is my first build, still in preproduction config/testing, first two drives that will be added to the array. While both drives precelared successfully with no reallocations, I am a little concerned over the apparent power loss to the drives 7 times. Both drive's results show 7 start/stops, 7 power cycles and 7 power off retracts. Both drives are powered through a single SATA power cable from the Seasonic modular PS. The only draws on the PS are the two drives and the mobo/cpu. BTW, I am aware of the high temps on both drives. I had disconnected the front intake fan for noise purposes and to see how the temps fared. I stupidly started the preclear without reconnecting the fan and was 12+ hours in when I realized my mistake. I went ahead and let the preclear run its cycle without the fan. I watched it pretty closely during the warmer parts of the day and saw temps peak at 42/43C (sda/sdb). Front fan is now back in and idle temps are back to around 27C and falling, so I the feel heat issue is resolved, but wonder if the heat had anything to do with the power downs. Any insight on the power downs (or any other standout items in the results) would be greatly appreciated. I am now starting cycle #2 on both drives. I have also attached a syslog from about 24 hours ago during the write process. I shut down the server to reinstall the front fan and do not have any log data after the attached (again stupid, but I hope not to make these mistakes again). TIA, erik preclear_results_6-5-11_cycle1.txt syslog.txt.html.zip Quote Link to comment
Joe L. Posted June 6, 2011 Share Posted June 6, 2011 Hello. Just completed my first cycle of preclear on two drives. Results file attached. This is my first build, still in preproduction config/testing, first two drives that will be added to the array. While both drives precelared successfully with no reallocations, I am a little concerned over the apparent power loss to the drives 7 times. Both drive's results show 7 start/stops, 7 power cycles and 7 power off retracts. Both drives are powered through a single SATA power cable from the Seasonic modular PS. The only draws on the PS are the two drives and the mobo/cpu. BTW, I am aware of the high temps on both drives. I had disconnected the front intake fan for noise purposes and to see how the temps fared. I stupidly started the preclear without reconnecting the fan and was 12+ hours in when I realized my mistake. I went ahead and let the preclear run its cycle without the fan. I watched it pretty closely during the warmer parts of the day and saw temps peak at 42/43C (sda/sdb). Front fan is now back in and idle temps are back to around 27C and falling, so I the feel heat issue is resolved, but wonder if the heat had anything to do with the power downs. Any insight on the power downs (or any other standout items in the results) would be greatly appreciated. I am now starting cycle #2 on both drives. I have also attached a syslog from about 24 hours ago during the write process. I shut down the server to reinstall the front fan and do not have any log data after the attached (again stupid, but I hope not to make these mistakes again). TIA, erik The power cycles are over then entire life of the drive, not just the pre-clear time. Here is an example from one new 2TB Hitachi drives recently pre-cleared 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 224 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 5 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 5 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 5 and here is one from a 500Gig Hitachi drive that has been in operation for much longer in my older server (At the time, it was the largest you could buy). 9 Power_On_Hours 0x0012 094 094 000 Old_age Always - 47780 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 274 192 Power-Off_Retract_Count 0x0032 097 097 050 Old_age Always - 4757 193 Load_Cycle_Count 0x0012 097 097 050 Old_age Always - 4757 47780 hours = nearly 5 1/2 years. Looks like the oldest drives in my array are now out of warranty. I hope our new drives last as long... Joe L. Quote Link to comment
wsume99 Posted June 6, 2011 Share Posted June 6, 2011 I've read though this entire thread and have seen others have this problem in the past. I'm wondering what others have done with their disks after having such problems - put in the Array or RMA it?. The disk still doesn't actually have any reallocated sectors but the Raw_Read_Error_Rate is slowly getting worse. I had a WD20EARS that showed the same behavior that you are seeing. I RMA'd that drive. I suppose WD would say that technically there is nothing wrong with the drive because it is passing the SMART test but I opted the RMA it back to the vendor I purchased it from anyway. I did this because I just didn't feel comfortable adding the drive to my array. The replacement drive cleared without any problems. Quote Link to comment
Joe L. Posted June 6, 2011 Share Posted June 6, 2011 I think I'll run a 5th cycle and see that happens, but if I want to RMA it to Scan rather than Western Digital then I'm getting close to the end of my 28 day return window. I'll post my results in another 32hrs. Based on what you said, I'd RMA the drive. Last thing you want is one that constantly has problems reading sectors. Quote Link to comment
axeman Posted June 6, 2011 Share Posted June 6, 2011 does unraid need the files in the preclear_reports folder? The reason i'm asking is because the unraid install where i ran the pre-clears probably wont be the final production version. do i need to copy these over or *if* i decide to start fresh, can i just let all of these go? thanks! every little bit gets me closer to a finished product (and happier wife) Quote Link to comment
wsume99 Posted June 6, 2011 Share Posted June 6, 2011 does unraid need the files in the preclear_reports folder? The reason i'm asking is because the unraid install where i ran the pre-clears probably wont be the final production version. do i need to copy these over or *if* i decide to start fresh, can i just let all of these go? thanks! every little bit gets me closer to a finished product (and happier wife) Simple answer - No. But ... personally I keep my preclear reports so I can use them as a historical comparison so that when I run SMART reports on a disk I can go back and compare the results to when the disk was new. Quote Link to comment
axeman Posted June 6, 2011 Share Posted June 6, 2011 does unraid need the files in the preclear_reports folder? The reason i'm asking is because the unraid install where i ran the pre-clears probably wont be the final production version. do i need to copy these over or *if* i decide to start fresh, can i just let all of these go? thanks! every little bit gets me closer to a finished product (and happier wife) Simple answer - No. But ... personally I keep my preclear reports so I can use them as a historical comparison so that when I run SMART reports on a disk I can go back and compare the results to when the disk was new. ty - i didn't know if UR needs it, for my uses, i did keep the .txt exports, the files in the folder, and all the emails. another question ... i have an older 500GB drive that isn't Advanced format. I have the setting in UR set to always do AF... how do i go about and pre-clear this drive? i thought I saw something somewhere about -a but can't for the life of me find it. OR should i just change the setting in UR and pre-clear? ./preclear_disk.sh -M -a 4 /dev/sda ? edit: found it in tutorial Note: if you do not supply either a "-a" or "-A" option, the preclear_disk.sh script will use the setting you've elected in the unRAID "settings" screen as its default partition type. -a will override the default and create an MBR-un-aligned partition starting on sector 63. -A will override the default and create an MBR-4k-aligned partition starting on sector 64. Quote Link to comment
Superorb Posted June 6, 2011 Share Posted June 6, 2011 Starting an older drive on sector 64 won't harm anything. Quote Link to comment
axeman Posted June 6, 2011 Share Posted June 6, 2011 Ty Super. i already started it with the -a. now another dilemna... this drive is HOT. it's at 41 degree before starting it. already at 43. it's at least 4 years old. so i'm hoping it doesn't croak on me oh it was a WD mybook that the power supply died on. 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.