maxse Posted November 11, 2012 Share Posted November 11, 2012 This is the preclear finish file. I don't see anywhere that it says the disk was cleared but I can't tellt hat it is failing either. Can you guys comment? Disk: /dev/sdf 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 === Model Family: Seagate Barracuda 7200.10 family Device Model: ST3750640AS Serial Number: 3QD0RQD1 Firmware Version: 3.AAE User Capacity: 750,155,292,160 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Nov 9 15:57:36 2012 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: (0x82) Offline data collection activity was completed without error. 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: ( 430) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 202) minutes. 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 119 086 006 Pre-fail Always - 212824034 3 Spin_Up_Time 0x0003 094 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 936 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 088 060 030 Pre-fail Always - 675414168 9 Power_On_Hours 0x0032 057 057 000 Old_age Always - 38473 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 243 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 052 051 045 Old_age Always - 48 (Min/Max 38/49) 194 Temperature_Celsius 0x0022 048 049 000 Old_age Always - 48 (0 17 0 0) 195 Hardware_ECC_Recovered 0x001a 059 053 000 Old_age Always - 217344359 197 Current_Pending_Sector 0x0012 094 093 000 Old_age Always - 141 198 Offline_Uncorrectable 0x0010 094 093 000 Old_age Offline - 141 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 94 (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 94 occurred at disk power-on lifetime: 29996 hours (1249 days + 20 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 01 ae 5e 54 e7 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 00 01 ae 5e 54 e7 00 04:05:06.024 SET MAX ADDRESS EXT 27 00 00 ae 5e 54 e0 00 04:05:05.799 READ NATIVE MAX ADDRESS EXT 37 00 00 ae 5e 54 e7 00 04:05:05.735 SET MAX ADDRESS EXT 27 00 01 ae 5e 54 e0 00 04:05:03.655 READ NATIVE MAX ADDRESS EXT 37 00 01 ae 5e 54 e7 00 04:05:03.596 SET MAX ADDRESS EXT Error 93 occurred at disk power-on lifetime: 29996 hours (1249 days + 20 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 01 ae 5e 54 e7 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 00 01 ae 5e 54 e7 00 04:04:58.326 SET MAX ADDRESS EXT 27 00 00 ae 5e 54 e0 00 04:04:58.326 READ NATIVE MAX ADDRESS EXT 37 00 00 ae 5e 54 e7 00 04:04:58.326 SET MAX ADDRESS EXT 27 00 01 ef 66 54 e0 00 04:05:03.655 READ NATIVE MAX ADDRESS EXT 29 00 01 ef 66 54 e0 00 04:05:03.596 READ MULTIPLE EXT Error 92 occurred at disk power-on lifetime: 29993 hours (1249 days + 17 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 01 ae 5e 54 e7 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 00 01 ae 5e 54 e7 00 01:35:25.972 SET MAX ADDRESS EXT 27 00 00 ae 5e 54 e0 00 01:35:25.911 READ NATIVE MAX ADDRESS EXT 37 00 00 ae 5e 54 e7 00 01:35:22.233 SET MAX ADDRESS EXT 27 00 01 ae 5e 54 e0 00 01:35:22.205 READ NATIVE MAX ADDRESS EXT 37 00 01 ae 5e 54 e7 00 01:35:22.205 SET MAX ADDRESS EXT Error 91 occurred at disk power-on lifetime: 29993 hours (1249 days + 17 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 01 ae 5e 54 e7 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 00 01 ae 5e 54 e7 00 01:35:25.972 SET MAX ADDRESS EXT 27 00 00 ae 5e 54 e0 00 01:35:25.911 READ NATIVE MAX ADDRESS EXT 37 00 00 ae 5e 54 e7 00 01:35:22.233 SET MAX ADDRESS EXT 27 00 01 ef 66 54 e0 00 01:35:22.205 READ NATIVE MAX ADDRESS EXT 29 00 01 ef 66 54 e0 00 01:35:22.205 READ MULTIPLE EXT Error 90 occurred at disk power-on lifetime: 29983 hours (1249 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 10 51 01 ae 5e 54 e7 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 37 00 01 ae 5e 54 e7 00 07:07:17.975 SET MAX ADDRESS EXT 27 00 00 ae 5e 54 e0 00 07:07:24.857 READ NATIVE MAX ADDRESS EXT 37 00 00 ae 5e 54 e7 00 07:07:24.798 SET MAX ADDRESS EXT 27 00 01 ae 5e 54 e0 00 07:07:24.573 READ NATIVE MAX ADDRESS EXT 37 00 01 ae 5e 54 e7 00 07:07:24.509 SET MAX ADDRESS EXT 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% 25 - 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
maxse Posted November 11, 2012 Share Posted November 11, 2012 This is the preclear rpt file. Here it says it was cleared, but I don't understand what it means that so many sectors we pending re-allocation. Haven't had a drive do that yet. ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sdf == ST3750640AS 3QD0RQD1 == 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 : 4:00:36 (51 MB/s) == Last Cycle's Zeroing time : 3:27:34 (60 MB/s) == Last Cycle's Post Read Time : 10:01:07 (20 MB/s) == Last Cycle's Total Time : 17:30:21 == == Total Elapsed Time 17:30:21 == == Disk Start Temperature: 41C == == Current Disk Temperature: -->48<--C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 88 87 30 ok 675414168 Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 52 59 45 near_thresh 48 Temperature_Celsius = 48 41 0 ok 48 Hardware_ECC_Recovered = 59 75 0 ok 217344359 Current_Pending_Sector = 94 93 0 ok 141 Offline_Uncorrectable = 94 93 0 ok 141 No SMART attributes are FAILING_NOW 155 sectors were pending re-allocation before the start of the preclear. 155 sectors were pending re-allocation after pre-read in cycle 1 of 1. 141 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 141 sectors are pending re-allocation at the end of the preclear, a change of -14 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. ============================================================================ Ran the preclear again and got everything the same, precleared passed except it showed 141 were pending before the start of preclear as opposed to 155 before. 141 sectors were pending re-allocation before the start of the preclear. 141 sectors were pending re-allocation after pre-read in cycle 1 of 1. 141 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 141 sectors are pending re-allocation at the end of the preclear, Quote Link to comment
Joe L. Posted November 11, 2012 Share Posted November 11, 2012 Hi! My drives just have finished the first preclear-round and I have to admit that I have no idea if everything went ok... https://dl.dropbox.com/u/3485341/temp/preclear_results.txt Right now, the preclear-script is doing it's magic again. In which case the drives should be considered as unsafe to proceed? PS: Wow, It's been 2 years since registering and actually start building a server... Both look great. Enjoy. Quote Link to comment
Joe L. Posted November 11, 2012 Share Posted November 11, 2012 This is the preclear rpt file. Here it says it was cleared, but I don't understand what it means that so many sectors we pending re-allocation. Haven't had a drive do that yet. ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sdf == ST3750640AS 3QD0RQD1 == 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 : 4:00:36 (51 MB/s) == Last Cycle's Zeroing time : 3:27:34 (60 MB/s) == Last Cycle's Post Read Time : 10:01:07 (20 MB/s) == Last Cycle's Total Time : 17:30:21 == == Total Elapsed Time 17:30:21 == == Disk Start Temperature: 41C == == Current Disk Temperature: -->48<--C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 88 87 30 ok 675414168 Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 52 59 45 near_thresh 48 Temperature_Celsius = 48 41 0 ok 48 Hardware_ECC_Recovered = 59 75 0 ok 217344359 Current_Pending_Sector = 94 93 0 ok 141 Offline_Uncorrectable = 94 93 0 ok 141 No SMART attributes are FAILING_NOW 155 sectors were pending re-allocation before the start of the preclear. 155 sectors were pending re-allocation after pre-read in cycle 1 of 1. 141 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 141 sectors are pending re-allocation at the end of the preclear, a change of -14 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. ============================================================================ Ran the preclear again and got everything the same, precleared passed except it showed 141 were pending before the start of preclear as opposed to 155 before. 141 sectors were pending re-allocation before the start of the preclear. 141 sectors were pending re-allocation after pre-read in cycle 1 of 1. 141 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 141 sectors are pending re-allocation at the end of the preclear, Do not use the drive if it has pending sectors that cannot be re-allocated. RMA it (although you could try another preclear cycle or two and see if they go to zero sectors pending re-allocation on the first, and stay at zero on the second, and no additional re-allocated sectors appear.). Joe L. Quote Link to comment
maxse Posted November 11, 2012 Share Posted November 11, 2012 Thanks buddy, but why does it say it is cleared by preclear? Also, the drive is still under warranty, but it passes the SMART tests. IF they get it and test it , won't it show everything is fine? Then they're just going to send me the drive back, no? Quote Link to comment
htpcnewbie Posted November 14, 2012 Share Posted November 14, 2012 Newbie to unraid here, got my first pass of 4 HDD's done and one of them did not pass the preclear. Surprising that I did not find any errors from the output. I have explicitly cleared the MBR with -Z option (there were 3 partitions from Windows) and have started the 2nd pass this morning. Any thoughts on why the preclear did not go through? Report ========================================================================1.13 == invoked as: ./preclear_disk.sh -m [email protected] /dev/sde == == Disk /dev/sde has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 8:12:02 (67 MB/s) == Last Cycle's Zeroing time : 6:03:45 (91 MB/s) == Last Cycle's Post Read Time : 13:47:05 (40 MB/s) == Last Cycle's Total Time : 28:03:59 == == Total Elapsed Time 28:03:59 == == Disk Start Temperature: 21C == == Current Disk Temperature: 23C, == ============================================================================ 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. ============================================================================ Output - ========================================================================1.13 == invoked as: ./preclear_disk.sh -m [email protected] /dev/sde == == Disk /dev/sde has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 8:12:02 (67 MB/s) == Last Cycle's Zeroing time : 6:03:45 (91 MB/s) == Last Cycle's Post Read Time : 13:47:05 (40 MB/s) == Last Cycle's Total Time : 28:03:59 == == Total Elapsed Time 28:03:59 == == Disk Start Temperature: 21C == == Current Disk Temperature: 23C, == ============================================================================ 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/sde == Disk: /dev/sde 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: SAMSUNG HD204UI Serial Number: S2H7J1RZ913400 Firmware Version: 1AQ10001 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: ATA-8-ACS revision 6 Local Time is: Mon Nov 12 21:25:03 2012 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 Quote Link to comment
Joe L. Posted November 14, 2012 Share Posted November 14, 2012 Newbie to unraid here, got my first pass of 4 HDD's done and one of them did not pass the preclear. Surprising that I did not find any errors from the output. I have explicitly cleared the MBR with -Z option (there were 3 partitions from Windows) and have started the 2nd pass this morning. Any thoughts on why the preclear did not go through? Report ========================================================================1.13 == invoked as: ./preclear_disk.sh -m [email protected] /dev/sde == == Disk /dev/sde has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes Yes, and it told you why, you just missed it. The post-read expected the disk to be all zeros. It was not. The actual cause could be almost anything except the "mouse" It could be a bad disk, or bad memory, or a flaky power supply, or motherboard, or disk controller. I'd start with a memory test, preferably overnight. Then, tests using badblocks on the disk itself. Then go from there. Joe L. Quote Link to comment
htpcnewbie Posted November 14, 2012 Share Posted November 14, 2012 Joe - I noticed that bit but didn't see why that would be the case. I also noticed that the MBR on this disk had 3 partitions similar to before the preclear process. I reasoned that since the partitions were not deleted (as I hope they would) and preclear was having issues with it. So I started a second pass of preclear this morning after explicitly deleting the partitions with "preclear.sh -Z" option. I was planning on waiting on the second pass result to see what to do further .. sounds reasonable? I ran stress tests (with prime95) for a day which stressed out both the memory & CPU at 100% before I started converting the machine to unraid server. Newbie to unraid here, got my first pass of 4 HDD's done and one of them did not pass the preclear. Surprising that I did not find any errors from the output. I have explicitly cleared the MBR with -Z option (there were 3 partitions from Windows) and have started the 2nd pass this morning. Any thoughts on why the preclear did not go through? Report ========================================================================1.13 == invoked as: ./preclear_disk.sh -m [email protected] /dev/sde == == Disk /dev/sde has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes Yes, and it told you why, you just missed it. The post-read expected the disk to be all zeros. It was not. The actual cause could be almost anything except the "mouse" It could be a bad disk, or bad memory, or a flaky power supply, or motherboard, or disk controller. I'd start with a memory test, preferably overnight. Then, tests using badblocks on the disk itself. Then go from there. Joe L. Quote Link to comment
htpcnewbie Posted November 15, 2012 Share Posted November 15, 2012 Wanted to give a quick update .. my preclear run from yesterday got done just a while ago and everything looks okay. I am speculating it maybe either due to the 3 windows partitions that preclear did not clear or lack of -A option (first sector started at 63, now it is 64). ============= ========================================================================1.13 == invoked as: ./preclear_disk.sh -A -m [email protected] /dev/sde == SAMSUNG HD204UI S2H7J1RZ913400 == Disk /dev/sde 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:47:42 (81 MB/s) == Last Cycle's Zeroing time : 6:19:39 (87 MB/s) == Last Cycle's Post Read Time : 19:18:59 (28 MB/s) == Last Cycle's Total Time : 32:27:28 == == Total Elapsed Time 32:27:28 == == Disk Start Temperature: 22C == == Current Disk Temperature: 22C, == ============================================================================ 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. ============================================================================= Joe - I noticed that bit but didn't see why that would be the case. I also noticed that the MBR on this disk had 3 partitions similar to before the preclear process. I reasoned that since the partitions were not deleted (as I hope they would) and preclear was having issues with it. So I started a second pass of preclear this morning after explicitly deleting the partitions with "preclear.sh -Z" option. I was planning on waiting on the second pass result to see what to do further .. sounds reasonable? I ran stress tests (with prime95) for a day which stressed out both the memory & CPU at 100% before I started converting the machine to unraid server. Newbie to unraid here, got my first pass of 4 HDD's done and one of them did not pass the preclear. Surprising that I did not find any errors from the output. I have explicitly cleared the MBR with -Z option (there were 3 partitions from Windows) and have started the 2nd pass this morning. Any thoughts on why the preclear did not go through? Report ========================================================================1.13 == invoked as: ./preclear_disk.sh -m [email protected] /dev/sde == == Disk /dev/sde has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes Yes, and it told you why, you just missed it. The post-read expected the disk to be all zeros. It was not. The actual cause could be almost anything except the "mouse" It could be a bad disk, or bad memory, or a flaky power supply, or motherboard, or disk controller. I'd start with a memory test, preferably overnight. Then, tests using badblocks on the disk itself. Then go from there. Joe L. Quote Link to comment
Joe L. Posted November 15, 2012 Share Posted November 15, 2012 The inability to clear the drive had nothing to do with thr existing partitions, or the starting. sector. Existing partitions would have been cleared, that had nothing to do with the error message you saw. Do not fall under a false impression all is well. You will probably experience random parity errors. They are very hard to isolate, so keep this disk in mind if it happens to you. And do not forget to test your memory. It is critical as anything. Quote Link to comment
htpcnewbie Posted November 15, 2012 Share Posted November 15, 2012 Yep, makes sense. I will run the disk for another 2 cycles before setting it in the server. Thanks for the suggestions! The inability to clear the drive had nothing to do with thr existing partitions, or the starting. sector. Existing partitions would have been cleared, that had nothing to do with the error message you saw. Do not fall under a false impression all is well. You will probably experience random parity errors. They are very hard to isolate, so keep this disk in mind if it happens to you. And do not forget to test your memory. It is critical as anything. Quote Link to comment
atom Posted November 17, 2012 Share Posted November 17, 2012 Is it normal for the post read speed to be 1/3 that of the pre read? This is the 2nd preclear of this drive. First time I was running 2 simultaneous preclears of two of the same drives. These results are from a single pass of a single preclear. Other users of the same drive are reporting preclear times of ~36h. Is this something I should be worried about ========================================================================1.13 == invoked as: ./preclear_disk.sh /dev/sda == WDC WD30EZRX-00MMMB0 WD-WMAWZ0333927 == Disk /dev/sda has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 9:20:54 (89 MB/s) == Last Cycle's Zeroing time : 8:27:11 (98 MB/s) == Last Cycle's Post Read Time : 27:30:18 (30 MB/s) == Last Cycle's Total Time : 45:19:25 == == Total Elapsed Time 45:19:25 == == Disk Start Temperature: 31C == == Current Disk Temperature: 30C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 122 121 0 ok 30 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
BobPhoenix Posted November 17, 2012 Share Posted November 17, 2012 Post read has more to do it has to compare the value read to zero. The preread just reads the disk and throws the value away. So yes the post read is much slower than the preread. Quote Link to comment
atom Posted November 17, 2012 Share Posted November 17, 2012 Post read has more to do it has to compare the value read to zero. The preread just reads the disk and throws the value away. So yes the post read is much slower than the preread. You say that post read is comparing values. So what is the defining factor in post read speed? CPU? If is is that would make sense since my MB (ASUS C60M1-I) has SATA3 controller but a weak CPU. Quote Link to comment
BobPhoenix Posted November 17, 2012 Share Posted November 17, 2012 Post read has more to do it has to compare the value read to zero. The preread just reads the disk and throws the value away. So yes the post read is much slower than the preread. You say that post read is comparing values. So what is the defining factor in post read speed? CPU? If is is that would make sense since my MB (ASUS C60M1-I) has SATA3 controller but a weak CPU. It has to perform more operations on a post read so a slower CPU would perform slower than a faster one. But even increasing the processing speed can only do so much. Quote Link to comment
atom Posted November 17, 2012 Share Posted November 17, 2012 Post read has more to do it has to compare the value read to zero. The preread just reads the disk and throws the value away. So yes the post read is much slower than the preread. You say that post read is comparing values. So what is the defining factor in post read speed? CPU? If is is that would make sense since my MB (ASUS C60M1-I) has SATA3 controller but a weak CPU. It has to perform more operations on a post read so a slower CPU would perform slower than a faster one. But even increasing the processing speed can only do so much. So are my results and speed ok? Quote Link to comment
BobPhoenix Posted November 17, 2012 Share Posted November 17, 2012 Here is my final report on a WD RED 3TB on a Quad Core CPU clearing station. I'll let you be the judge on if your results are ok or not. They don't seem out of line to me. ========================================================================1.13 == invoked as: ./preclear_disk.sh -c 3 /dev/sdb == WDC WD30EFRX-68AX9N0 WD-WMC1T0852162 == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 8:18:13 (100 MB/s) == Last Cycle's Zeroing time : 8:22:34 (99 MB/s) == Last Cycle's Post Read Time : 16:59:51 (49 MB/s) == Last Cycle's Total Time : 25:23:24 == == Total Elapsed Time 84:23:53 == == Disk Start Temperature: 30C == == Current Disk Temperature: 32C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 118 120 0 ok 32 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 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 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
garycase Posted November 17, 2012 Share Posted November 17, 2012 I've pre-cleared 5 3TB WD Reds with very similar times. All had "clean" reports at the end (all zeros). My pre-clear times for a single pass were ~ 36 hours (one was just under, the other 3 were a bit more. For 3 cycles they took about 85 hours -- very consistent with the results Bob posted. I suppose it's possible that a notably slower time (e.g. 45 hours) could be CPU-related; but I'd think it much more likely that it's due to a slower SATA controller or perhaps a poor quality SATA cable. My system is an Intel Atom (SuperMicro X7SPA-H-D525) -- not a particularly potent CPU (but a GREAT system -- draws 25w with the disks idle; a max of 45w with all 5 drives active (e.g. during a parity check) When I built this particular system a couple months ago (my 2nd UnRAID server), I did 3 passes of pre-clears on every drive (would have returned any that weren't all zeroes ... but fortunately they all were fine) => then did a parity check every day for a couple weeks (all clean). That was my "burn in". Really cool to see the system doing parity checks on only 45w of power !! [My older C2SEA-based system draws 175w when all the drives are spinning -- granted there are more drives (14)]. Quote Link to comment
prtsmgr Posted November 20, 2012 Share Posted November 20, 2012 Should I worry about these values? Raw_Read_Error_Rate High_Fly_Writes ========================================================================1.13 == invoked as: ./preclear_disk.sh /dev/sdg == ST3000VX000-9YW166 S1F0MJM6 == Disk /dev/sdg has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 5:42:53 (145 MB/s) == Last Cycle's Zeroing time : 5:11:00 (160 MB/s) == Last Cycle's Post Read Time : 12:29:20 (66 MB/s) == Last Cycle's Total Time : 23:24:13 == == Total Elapsed Time 23:24:13 == == Disk Start Temperature: 27C == == Current Disk Temperature: 31C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdg /tmp/smart_finish_sdg ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 113 100 6 ok 55854080 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 69 100 0 ok 31 Airflow_Temperature_Cel = 69 73 45 near_thresh 31 Temperature_Celsius = 31 27 0 ok 31 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
Joe L. Posted November 20, 2012 Share Posted November 20, 2012 Should I worry about these values? Raw_Read_Error_Rate High_Fly_Writes No worry... Not unless their normalized values go below their affiliated failure thresholds. Quote Link to comment
woolooloo Posted November 24, 2012 Share Posted November 24, 2012 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdj /tmp/smart_finish_sdj ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 100 6 ok 207253708 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 85 100 0 ok 15 Airflow_Temperature_Cel = 66 69 45 near_thresh 34 Temperature_Celsius = 34 31 0 ok 34 Hardware_ECC_Recovered = 56 100 0 ok 207253708 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. 30 sectors are re-allocated at the end of the preclear, a change of 30 in the number of sectors re-allocated. I think everything looks good except the "30 sectors are re-alocated at the end of the preclear". I know this is kind of what the preclear is supposed to do, but should I be worried? Most of the logs others have posted have 0 sectors. Is 30 troublesome? Should I worry? Should I run it again and see if it continues to increase? BTW, this is a Seagate recertified drive that they sent me to replace a failed drive. Quote Link to comment
NateCCIE Posted November 25, 2012 Share Posted November 25, 2012 Is there a way to just to the POST read? Some kids turned off the main breakers on my house after a 26 hour write cycle to a USB2 connected 3TB drive. the -T shows a good signature, but I would really like to have it run a complete post read cycle before I open the drive up. Thanks -Nate Quote Link to comment
Evin Posted November 25, 2012 Share Posted November 25, 2012 Hi, I used the script on an old drive... First cycle seemed okay, no "pending sectors". Started the next one and got ONE pending sector... No I've done 5 cycles in a row: Nov 26 15:13:03 Server preclear_disk-diff[2177]: == invoked as: ./preclear_disk.sh -c 5 /dev/sde Nov 26 15:13:03 Server preclear_disk-diff[2177]: == WDC WD20EARS-00MVWB0 WD-WCAZA3274588 Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Disk /dev/sde has been successfully precleared Nov 26 15:13:03 Server preclear_disk-diff[2177]: == with a starting sector of 64 Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Ran 5 cycles Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Using :Read block size = 8225280 Bytes Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Last Cycle's Pre Read Time : 8:08:28 (68 MB/s) Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Last Cycle's Zeroing time : 6:06:48 (90 MB/s) Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Last Cycle's Post Read Time : 18:04:24 (30 MB/s) Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Last Cycle's Total Time : 24:12:12 Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Total Elapsed Time 128:46:02 Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Disk Start Temperature: 33C Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Current Disk Temperature: 35C, Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Nov 26 15:13:03 Server preclear_disk-diff[2177]: ============================================================================ Nov 26 15:13:03 Server preclear_disk-diff[2177]: ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde Nov 26 15:13:03 Server preclear_disk-diff[2177]: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Nov 26 15:13:03 Server preclear_disk-diff[2177]: Raw_Read_Error_Rate = 198 196 51 ok 1341 Nov 26 15:13:03 Server preclear_disk-diff[2177]: Temperature_Celsius = 115 116 0 ok 35 Nov 26 15:13:03 Server preclear_disk-diff[2177]: No SMART attributes are FAILING_NOW Nov 26 15:13:03 Server preclear_disk-diff[2177]: Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors were pending re-allocation before the start of the preclear. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors were pending re-allocation after pre-read in cycle 1 of 5. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors were pending re-allocation after zero of disk in cycle 1 of 5. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors were pending re-allocation after post-read in cycle 1 of 5. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors were pending re-allocation after zero of disk in cycle 2 of 5. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors were pending re-allocation after post-read in cycle 2 of 5. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors were pending re-allocation after zero of disk in cycle 3 of 5. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors were pending re-allocation after post-read in cycle 3 of 5. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors were pending re-allocation after zero of disk in cycle 4 of 5. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors were pending re-allocation after post-read in cycle 4 of 5. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors were pending re-allocation after zero of disk in cycle 5 of 5. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors are pending re-allocation at the end of the preclear, Nov 26 15:13:03 Server preclear_disk-diff[2177]: the number of sectors pending re-allocation did not change. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors had been re-allocated before the start of the preclear. Nov 26 15:13:03 Server preclear_disk-diff[2177]: 0 sectors are re-allocated at the end of the preclear, Nov 26 15:13:03 Server preclear_disk-diff[2177]: the number of sectors re-allocated did not change. Nov 26 15:13:03 Server preclear_disk-diff[2177]: ============================================================================ Nov 26 15:13:03 Server preclear_disk-diff[2177]: ============================================================================ Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Nov 26 15:13:03 Server preclear_disk-diff[2177]: == S.M.A.R.T Initial Report for /dev/sde Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Nov 26 15:13:03 Server preclear_disk-diff[2177]: Disk: /dev/sde Nov 26 15:13:03 Server preclear_disk-diff[2177]: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Nov 26 15:13:03 Server preclear_disk-diff[2177]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Nov 26 15:13:03 Server preclear_disk-diff[2177]: Nov 26 15:13:03 Server preclear_disk-diff[2177]: === START OF INFORMATION SECTION === Nov 26 15:13:03 Server preclear_disk-diff[2177]: Model Family: Western Digital Caviar Green (Adv. Format) family Nov 26 15:13:03 Server preclear_disk-diff[2177]: Device Model: WDC WD20EARS-00MVWB0 Nov 26 15:13:03 Server preclear_disk-diff[2177]: Serial Number: WD-WCAZA3274588 Nov 26 15:13:03 Server preclear_disk-diff[2177]: Firmware Version: 51.0AB51 Nov 26 15:13:03 Server preclear_disk-diff[2177]: User Capacity: 2,000,398,934,016 bytes Nov 26 15:13:03 Server preclear_disk-diff[2177]: Device is: In smartctl database [for details use: -P show] Nov 26 15:13:03 Server preclear_disk-diff[2177]: ATA Version is: 8 Nov 26 15:13:03 Server preclear_disk-diff[2177]: ATA Standard is: Exact ATA specification draft version not indicated Nov 26 15:13:03 Server preclear_disk-diff[2177]: Local Time is: Wed Nov 21 06:26:58 2012 CET Nov 26 15:13:03 Server preclear_disk-diff[2177]: SMART support is: Available - device has SMART capability. Nov 26 15:13:03 Server preclear_disk-diff[2177]: SMART support is: Enabled Nov 26 15:13:03 Server preclear_disk-diff[2177]: Nov 26 15:13:03 Server preclear_disk-diff[2177]: === START OF READ SMART DATA SECTION === Nov 26 15:13:03 Server preclear_disk-diff[2177]: SMART overall-health self-assessment test result: PASSED Nov 26 15:13:03 Server preclear_disk-diff[2177]: Nov 26 15:13:03 Server preclear_disk-diff[2177]: General SMART Values: Nov 26 15:13:03 Server preclear_disk-diff[2177]: Offline data collection status: (0x84)^IOffline data collection activity Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^Iwas suspended by an interrupting command from host. Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^IAuto Offline Data Collection: Enabled. Nov 26 15:13:03 Server preclear_disk-diff[2177]: Self-test execution status: ( 0)^IThe previous self-test routine completed Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^Iwithout error or no self-test has ever Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^Ibeen run. Nov 26 15:13:03 Server preclear_disk-diff[2177]: Total time to complete Offline Nov 26 15:13:03 Server preclear_disk-diff[2177]: data collection: ^I^I (37080) seconds. Nov 26 15:13:03 Server preclear_disk-diff[2177]: Offline data collection Nov 26 15:13:03 Server preclear_disk-diff[2177]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^IAuto Offline data collection on/off support. Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^ISuspend Offline collection upon new Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^Icommand. Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^IOffline surface scan supported. Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^ISelf-test supported. Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^IConveyance Self-test supported. Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^ISelective Self-test supported. Nov 26 15:13:03 Server preclear_disk-diff[2177]: SMART capabilities: (0x0003)^ISaves SMART data before entering Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^Ipower-saving mode. Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^ISupports SMART auto save timer. Nov 26 15:13:03 Server preclear_disk-diff[2177]: Error logging capability: (0x01)^IError logging supported. Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^IGeneral Purpose Logging supported. Nov 26 15:13:03 Server preclear_disk-diff[2177]: Short self-test routine Nov 26 15:13:03 Server preclear_disk-diff[2177]: recommended polling time: ^I ( 2) minutes. Nov 26 15:13:03 Server preclear_disk-diff[2177]: Extended self-test routine Nov 26 15:13:03 Server preclear_disk-diff[2177]: recommended polling time: ^I ( 255) minutes. Nov 26 15:13:03 Server preclear_disk-diff[2177]: Conveyance self-test routine Nov 26 15:13:03 Server preclear_disk-diff[2177]: recommended polling time: ^I ( 5) minutes. Nov 26 15:13:03 Server preclear_disk-diff[2177]: SCT capabilities: ^I (0x3035)^ISCT Status supported. Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^ISCT Feature Control supported. Nov 26 15:13:03 Server preclear_disk-diff[2177]: ^I^I^I^I^ISCT Data Table supported. Nov 26 15:13:03 Server preclear_disk-diff[2177]: Nov 26 15:13:03 Server preclear_disk-diff[2177]: SMART Attributes Data Structure revision number: 16 Nov 26 15:13:03 Server preclear_disk-diff[2177]: Vendor Specific SMART Attributes with Thresholds: Nov 26 15:13:03 Server preclear_disk-diff[2177]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Nov 26 15:13:03 Server preclear_disk-diff[2177]: 1 Raw_Read_Error_Rate 0x002f 196 196 051 Pre-fail Always - 607 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 3 Spin_Up_Time 0x0027 253 223 021 Pre-fail Always - 1050 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 428 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 3129 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 422 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 37 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 8727 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 194 Temperature_Celsius 0x0022 116 107 000 Old_age Always - 34 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Nov 26 15:13:03 Server preclear_disk-diff[2177]: 200 Multi_Zone_Error_Rate 0x0008 200 184 000 Old_age Offline - 69 Nov 26 15:13:03 Server preclear_disk-diff[2177]: Nov 26 15:13:03 Server preclear_disk-diff[2177]: SMART Error Log Version: 1 Nov 26 15:13:03 Server preclear_disk-diff[2177]: No Errors Logged Nov 26 15:13:03 Server preclear_disk-diff[2177]: Nov 26 15:13:03 Server preclear_disk-diff[2177]: SMART Self-test log structure revision number 1 Nov 26 15:13:03 Server preclear_disk-diff[2177]: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error Nov 26 15:13:03 Server preclear_disk-diff[2177]: # 1 Short offline Completed without error 00% 3 - Nov 26 15:13:03 Server preclear_disk-diff[2177]: Nov 26 15:13:03 Server preclear_disk-diff[2177]: SMART Selective self-test log data structure revision number 1 Nov 26 15:13:03 Server preclear_disk-diff[2177]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Nov 26 15:13:03 Server preclear_disk-diff[2177]: 1 0 0 Not_testing Nov 26 15:13:03 Server preclear_disk-diff[2177]: 2 0 0 Not_testing Nov 26 15:13:03 Server preclear_disk-diff[2177]: 3 0 0 Not_testing Nov 26 15:13:03 Server preclear_disk-diff[2177]: 4 0 0 Not_testing Nov 26 15:13:03 Server preclear_disk-diff[2177]: 5 0 0 Not_testing Nov 26 15:13:03 Server preclear_disk-diff[2177]: Selective self-test flags (0x0): Nov 26 15:13:03 Server preclear_disk-diff[2177]: After scanning selected spans, do NOT read-scan remainder of disk. Nov 26 15:13:03 Server preclear_disk-diff[2177]: If Selective self-test is pending on power-up, resume after 0 minute delay. Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Nov 26 15:13:03 Server preclear_disk-diff[2177]: ============================================================================ Nov 26 15:13:03 Server preclear_disk-diff[2177]: Nov 26 15:13:03 Server preclear_disk-diff[2177]: ============================================================================ Nov 26 15:13:03 Server preclear_disk-diff[2177]: == Everything seems fine now. Am I save to use it? Thx! Quote Link to comment
woolooloo Posted November 25, 2012 Share Posted November 25, 2012 I think everything looks good except the "30 sectors are re-alocated at the end of the preclear". I know this is kind of what the preclear is supposed to do, but should I be worried? Most of the logs others have posted have 0 sectors. Is 30 troublesome? Should I worry? Should I run it again and see if it continues to increase? BTW, this is a Seagate recertified drive that they sent me to replace a failed drive. I ran it again and got this: 32 sectors had been re-allocated before the start of the preclear. 32 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. I'm glad that the pre-clear didn't find any more sector to re-allocate, but I'm a little disturbed that the count went from 30 to 32 after the last pre-clear while the drive was sitting unused. I guess I'll go ahead and use the drive, but if anyone finds this really troubling, please let me know. Quote Link to comment
NateCCIE Posted November 30, 2012 Share Posted November 30, 2012 So I have two drives running badblocks, same seagate, connected to the same controller started at the same time. One is running a lot faster than the other, is that indicative of a bad drive? root@NatesNAS2:~# badblocks -sv -w -o /tmp/badblocks.out.sde /dev/sde Checking for bad blocks in read-write mode From block 0 to 2930266583 Testing with pattern 0xaa: done Reading and comparing: done Testing with pattern 0x55: done Reading and comparing: done Testing with pattern 0xff: done Reading and comparing: done Testing with pattern 0x00: 49.41% done, 34:38:31 elapsed root@NatesNAS2:~# badblocks -sv -w -o /tmp/badblocks.out.sdf /dev/sdf Checking for bad blocks in read-write mode From block 0 to 2930266583 Testing with pattern 0xaa: done Reading and comparing: ndone Testing with pattern 0x55: ndone Reading and comparing: done Testing with pattern 0xff: done Reading and comparing: done Testing with pattern 0x00: 78.56% done, 34:39:17 elapsed 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.