Helmonder Posted May 1, 2012 Share Posted May 1, 2012 Well... the original 4 sectors were apparently re-written in place, and not re-allocated, but then on the second cycle one additional sector was not readable initially, but re-written in place on the zeroing phase. I'd run it through another few cycles. If it still has an occasional sector show as un-readable, I'd not trust it for anything critical. If it is all OK, then go ahead and use it if you like... (Or RMA it, if in warranty) Of course, you can always put it in a windows OS, and blame any future data corruption on Microsoft. Thanks ! Quote Link to comment
VelcroBP Posted May 4, 2012 Share Posted May 4, 2012 Just ran a couple preclears on an older drive I had in an external. There are consistently 5 reallocated sectors but no changes through 3 preclears and it is reported as PASS in the SMART reports. This would be the first NON brand-new drive I am considering adding to my array, and I'm not certain what red-flags to watch out for in the results to warrant excluding from the array. And advice is welcome.. or perhaps a link to a detailed discussion/explanation of results?? preclear_WD_EADS_pass3.txt preclear_WD_EADS_pass2.txt preclear_WD_EADS_pass1.txt Quote Link to comment
RobJ Posted May 4, 2012 Share Posted May 4, 2012 Just ran a couple preclears on an older drive I had in an external. There are consistently 5 reallocated sectors but no changes through 3 preclears and it is reported as PASS in the SMART reports. This would be the first NON brand-new drive I am considering adding to my array, and I'm not certain what red-flags to watch out for in the results to warrant excluding from the array. And advice is welcome.. or perhaps a link to a detailed discussion/explanation of results?? The drive looks fine, and with only about 8000 hours on it, is relatively young. Nothing to be concerned about in your SMART reports for it. Helmonder: I could not seem to find time to respond before, and Joe's answer is essentially what I would have said, except I'm not as succinct! He noted the one concern I had, about that one sector that popped up. I'll just add the one comment, that sectors marked 'Pending' are not necessarily permanently bad, they may have physically perfect media under them but have been scrambled by a power spike or outage during a past write to them, or some other corrupting event. Once rewritten (the Preclear zeroing), they prove to be fine. Quote Link to comment
Johnm Posted May 16, 2012 Share Posted May 16, 2012 My latest pre-clear... Hmmm. Disk: /dev/sdp smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-9YN166 Serial Number: WxxxxxX Firmware Version: CC4C User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Tue May 15 00:20:04 2012 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 575) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 116 100 006 Pre-fail Always - 105440000 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 067 060 030 Pre-fail Always - 5806444 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 30 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 2 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 065 063 045 Old_age Always - 35 (Min/Max 26/37) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 194 Temperature_Celsius 0x0022 035 040 000 Old_age Always - 35 (0 26 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 155671089643550 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 9657625742636 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 36526120157 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
RobJ Posted May 16, 2012 Share Posted May 16, 2012 My latest pre-clear... Hmmm. Your drive is as near perfect as it can be. In fact, it is a perfect example of modern Seagate drives. Seagate is the only one that displays the raw values for raw reads and seeks, and you can ignore them. What is more important is that Raw_Read_Error_Rate has a value of 116, which could be considered better than perfect (100). What is also very typical of Seagates - the Seek_Error_Rate starts and stays in the 60's, and I have no idea why they do that. So long as it does not start dropping towards 30, everything is fine. Enjoy what looks like a great drive! Quote Link to comment
Johnm Posted May 16, 2012 Share Posted May 16, 2012 thank you. I am so not used to these seagates. too bad they are such crap drives. they have nice specs.. Quote Link to comment
adrayic Posted May 17, 2012 Share Posted May 17, 2012 Just finished preclearing my seagate 1.5TB drive with the intent on using it as a data disk in my array. May 17 17:05:24 Tower preclear_disk-diff[29590]: ========================================================================1.13 May 17 17:05:24 Tower preclear_disk-diff[29590]: == invoked as: ./preclear_disk.sh -A /dev/sdf May 17 17:05:24 Tower preclear_disk-diff[29590]: == ST31500341AS 9VS1L2YX May 17 17:05:24 Tower preclear_disk-diff[29590]: == Disk /dev/sdf has been successfully precleared May 17 17:05:24 Tower preclear_disk-diff[29590]: == with a starting sector of 64 May 17 17:05:24 Tower preclear_disk-diff[29590]: == Ran 1 cycle May 17 17:05:24 Tower preclear_disk-diff[29590]: == May 17 17:05:24 Tower preclear_disk-diff[29590]: == Using :Read block size = 8225280 Bytes May 17 17:05:24 Tower preclear_disk-diff[29590]: == Last Cycle's Pre Read Time : 4:35:09 (90 MB/s) May 17 17:05:24 Tower preclear_disk-diff[29590]: == Last Cycle's Zeroing time : 5:07:40 (81 MB/s) May 17 17:05:24 Tower preclear_disk-diff[29590]: == Last Cycle's Post Read Time : 9:28:34 (43 MB/s) May 17 17:05:24 Tower preclear_disk-diff[29590]: == Last Cycle's Total Time : 19:12:23 May 17 17:05:24 Tower preclear_disk-diff[29590]: == May 17 17:05:24 Tower preclear_disk-diff[29590]: == Total Elapsed Time 19:12:24 May 17 17:05:24 Tower preclear_disk-diff[29590]: == May 17 17:05:24 Tower preclear_disk-diff[29590]: == Disk Start Temperature: 24C May 17 17:05:24 Tower preclear_disk-diff[29590]: == May 17 17:05:24 Tower preclear_disk-diff[29590]: == Current Disk Temperature: 25C, May 17 17:05:24 Tower preclear_disk-diff[29590]: == May 17 17:05:24 Tower preclear_disk-diff[29590]: ============================================================================ May 17 17:05:24 Tower preclear_disk-diff[29590]: ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf May 17 17:05:24 Tower preclear_disk-diff[29590]: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE May 17 17:05:24 Tower preclear_disk-diff[29590]: Spin_Retry_Count = 100 100 97 near_thresh 0 May 17 17:05:24 Tower preclear_disk-diff[29590]: End-to-End_Error = 100 100 99 near_thresh 0 May 17 17:05:24 Tower preclear_disk-diff[29590]: High_Fly_Writes = 1 42 0 near_thresh 138 May 17 17:05:24 Tower preclear_disk-diff[29590]: Airflow_Temperature_Cel = 75 76 45 ok 25 May 17 17:05:24 Tower preclear_disk-diff[29590]: Temperature_Celsius = 25 24 0 near_thresh 25 May 17 17:05:24 Tower preclear_disk-diff[29590]: Hardware_ECC_Recovered = 58 48 0 ok 231659445 May 17 17:05:24 Tower preclear_disk-diff[29590]: No SMART attributes are FAILING_NOW May 17 17:05:24 Tower preclear_disk-diff[29590]: May 17 17:05:24 Tower preclear_disk-diff[29590]: 0 sectors were pending re-allocation before the start of the preclear. May 17 17:05:24 Tower preclear_disk-diff[29590]: 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. May 17 17:05:24 Tower preclear_disk-diff[29590]: 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. May 17 17:05:24 Tower preclear_disk-diff[29590]: 0 sectors are pending re-allocation at the end of the preclear, May 17 17:05:24 Tower preclear_disk-diff[29590]: the number of sectors pending re-allocation did not change. May 17 17:05:24 Tower preclear_disk-diff[29590]: 36 sectors had been re-allocated before the start of the preclear. May 17 17:05:24 Tower preclear_disk-diff[29590]: 36 sectors are re-allocated at the end of the preclear, May 17 17:05:24 Tower preclear_disk-diff[29590]: the number of sectors re-allocated did not change. May 17 17:05:24 Tower preclear_disk-diff[29590]: ============================================================================ May 17 17:05:24 Tower preclear_disk-diff[29590]: ============================================================================ It says the preclear was successful but I have re-allocated sectors. Should I be worried about using this drive? I have attached the full report also if it helps. preclear_results.txt Quote Link to comment
Joe L. Posted May 19, 2012 Share Posted May 19, 2012 You should be fine. The number of re-allocated sectors did not change. If you are unsure, preclear it once more. If the number of re-allocated sectors changes, then you might see them from time to time, and the disk is not a great candidate. But... if it stays the same, use the disk. I've got one disk that has 100 re-allocated sectors, and that number has never changed. I trust it. Most disks have several thousand spare sectors to be used for re-allocation. The 36 is not an issue. Joe L. Quote Link to comment
adrayic Posted May 19, 2012 Share Posted May 19, 2012 Thanks Joe. Thats kinda what I gathered by your previous responses but I wanted to be sure. Quote Link to comment
crankbearing Posted May 21, 2012 Share Posted May 21, 2012 I just finished a pre clear on a Seagate 3TB same drive as johnm's post above, I though I would post the values as a comp. Disk: /dev/sdh smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-9YN166 Serial Number: S1F06HXE Firmware Version: CC4C User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sun May 20 22:16:14 2012 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 584) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 116 100 006 Pre-fail Always - 111987840 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 061 060 030 Pre-fail Always - 1408709 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 26 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 2 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 070 068 045 Old_age Always - 30 (Min/Max 26/32) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 194 Temperature_Celsius 0x0022 030 040 000 Old_age Always - 30 (0 26 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 43108586749978 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 110463446854697 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 66137344287 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. thx for a great script Joe. Dave Quote Link to comment
ZeroK Posted May 23, 2012 Share Posted May 23, 2012 What do you think about drive sdd? Brand new and only 1 preclear so far. Should I RMA it or run it through another 2 preclears first? May 22 18:58:24 Tower emhttp: shcmd (101): /usr/local/sbin/emhttp_event driver_loaded (System) May 22 18:58:24 Tower emhttp_event: driver_loaded (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 00 30 00 00 04 00 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 12288 (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 00 34 00 00 04 00 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 13312 (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 00 38 00 00 04 00 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 14336 (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 00 3c 00 00 02 c1 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 15360 (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 bf 12 f6 38 00 02 00 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 3205690936 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711367 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711368 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711369 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711370 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711371 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711372 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711373 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711374 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711375 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711376 (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 97 de 03 88 00 02 00 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 2547909512 (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 47 b6 3a c8 00 02 00 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 1203124936 (Errors) May 23 04:03:31 Tower kernel: sdc: sdc1 (Drive related) May 23 04:17:20 Tower kernel: sde: sde1 (Drive related) May 23 04:17:39 Tower kernel: sdb: sdb1 (Drive related) May 23 04:48:50 Tower kernel: sda: sda1 (Drive related) May 23 05:11:11 Tower kernel: sdd: sdd1 (Drive related) Quote Link to comment
Joe L. Posted May 23, 2012 Share Posted May 23, 2012 What do you think about drive sdd? Brand new and only 1 preclear so far. Should I RMA it or run it through another 2 preclears first? May 22 18:58:24 Tower emhttp: shcmd (101): /usr/local/sbin/emhttp_event driver_loaded (System) May 22 18:58:24 Tower emhttp_event: driver_loaded (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 00 30 00 00 04 00 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 12288 (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 00 34 00 00 04 00 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 13312 (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 00 38 00 00 04 00 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 14336 (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 00 00 3c 00 00 02 c1 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 15360 (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 bf 12 f6 38 00 02 00 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 3205690936 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711367 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711368 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711369 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711370 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711371 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711372 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711373 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711374 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711375 (Errors) May 22 20:44:48 Tower kernel: Buffer I/O error on device sdd, logical block 400711376 (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 97 de 03 88 00 02 00 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 2547909512 (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Unhandled error code (Errors) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x06 (System) May 22 20:44:48 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 47 b6 3a c8 00 02 00 00 (Drive related) May 22 20:44:48 Tower kernel: end_request: I/O error, dev sdd, sector 1203124936 (Errors) May 23 04:03:31 Tower kernel: sdc: sdc1 (Drive related) May 23 04:17:20 Tower kernel: sde: sde1 (Drive related) May 23 04:17:39 Tower kernel: sdb: sdb1 (Drive related) May 23 04:48:50 Tower kernel: sda: sda1 (Drive related) May 23 05:11:11 Tower kernel: sdd: sdd1 (Drive related) Can't tell. you did not post a SMART report. All we see is a snip of your syslog, and those errors could be power supply, disk controller, loose cabling, or disk related. Quote Link to comment
RobJ Posted May 24, 2012 Share Posted May 24, 2012 I have to agree with Joe, there's not enough info there to tell if there is anything at all wrong with the drive. The snip is especially confusing, because it appears to be missing a lot of lines between the ones showing. It is always best to include the entire syslog. If you don't want to, then the next best is to include that section of the syslog containing the very first errors related to a drive. They are usually the most important. Quote Link to comment
ZeroK Posted May 25, 2012 Share Posted May 25, 2012 Sorry, is this what you need? This is the 2nd preclear results for disk sdd. May 25 09:22:34 Tower preclear_disk-diff[1138]: == S.M.A.R.T Initial Report for /dev/sdd (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Disk: /dev/sdd (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: === START OF INFORMATION SECTION === (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Device Model: ST2000DL004 HD204UI (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Serial Number: S2H7J9GC305362 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Firmware Version: 1AQ10001 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: User Capacity: 2,000,398,934,016 bytes (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Device is: Not in smartctl database [for details use: -P showall] (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ATA Version is: 8 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ATA Standard is: ATA-8-ACS revision 6 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Local Time is: Thu May 24 04:35:04 2012 EDT (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART support is: Available - device has SMART capability. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART support is: Enabled (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: === START OF READ SMART DATA SECTION === (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART overall-health self-assessment test result: PASSED (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Offline data collection status: (0x00)^IOffline data collection activity (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^Iwas never started. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^IAuto Offline Data Collection: Disabled. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Self-test execution status: ( 0)^IThe previous self-test routine completed (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^Iwithout error or no self-test has ever (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^Ibeen run. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Total time to complete Offline (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: data collection: ^I^I (20820) seconds. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Offline data collection (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: capabilities: ^I^I^I (0x5b) SMART execute Offline immediate. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^IAuto Offline data collection on/off support. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISuspend Offline collection upon new (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^Icommand. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^IOffline surface scan supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISelf-test supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^INo Conveyance Self-test supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISelective Self-test supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART capabilities: (0x0003)^ISaves SMART data before entering (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^Ipower-saving mode. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISupports SMART auto save timer. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Error logging capability: (0x01)^IError logging supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^IGeneral Purpose Logging supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Short self-test routine (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: recommended polling time: ^I ( 2) minutes. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Extended self-test routine (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: recommended polling time: ^I ( 255) minutes. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SCT capabilities: ^I (0x003f)^ISCT Status supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISCT Error Recovery Control supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISCT Feature Control supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISCT Data Table supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART Attributes Data Structure revision number: 16 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Vendor Specific SMART Attributes with Thresholds: (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 1898 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 3 Spin_Up_Time 0x0023 067 067 025 Pre-fail Always - 10177 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 3 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 36 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 181 Program_Fail_Cnt_Total 0x0022 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 194 Temperature_Celsius 0x0002 064 064 000 Old_age Always - 26 (Min/Max 22/30) (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART Error Log Version: 1 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: No Errors Logged (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART Self-test log structure revision number 1 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: No self-tests have been logged. [To run self-tests, use: smartctl -t] (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART Selective self-test log data structure revision number 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Note: revision number not 1 implies that no selective self-test has ever been run (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 1 0 0 Completed [00% left] (0-65535) (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 2 0 0 Not_testing (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 3 0 0 Not_testing (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 4 0 0 Not_testing (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 5 0 0 Not_testing (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Selective self-test flags (0x0): (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: After scanning selected spans, do NOT read-scan remainder of disk. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: If Selective self-test is pending on power-up, resume after 0 minute delay. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: == S.M.A.R.T Final Report for /dev/sdd (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Disk: /dev/sdd (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: === START OF INFORMATION SECTION === (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Device Model: ST2000DL004 HD204UI (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Serial Number: S2H7J9GC305362 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Firmware Version: 1AQ10001 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: User Capacity: 2,000,398,934,016 bytes (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Device is: Not in smartctl database [for details use: -P showall] (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ATA Version is: 8 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ATA Standard is: ATA-8-ACS revision 6 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Local Time is: Fri May 25 09:22:29 2012 EDT (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART support is: Available - device has SMART capability. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART support is: Enabled (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: === START OF READ SMART DATA SECTION === (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART overall-health self-assessment test result: PASSED (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: General SMART Values: (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Offline data collection status: (0x00)^IOffline data collection activity (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^Iwas never started. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^IAuto Offline Data Collection: Disabled. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Self-test execution status: ( 0)^IThe previous self-test routine completed (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^Iwithout error or no self-test has ever (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^Ibeen run. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Total time to complete Offline (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: data collection: ^I^I (20820) seconds. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Offline data collection (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: capabilities: ^I^I^I (0x5b) SMART execute Offline immediate. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^IAuto Offline data collection on/off support. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISuspend Offline collection upon new (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^Icommand. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^IOffline surface scan supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISelf-test supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^INo Conveyance Self-test supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISelective Self-test supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART capabilities: (0x0003)^ISaves SMART data before entering (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^Ipower-saving mode. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISupports SMART auto save timer. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Error logging capability: (0x01)^IError logging supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^IGeneral Purpose Logging supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Short self-test routine (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: recommended polling time: ^I ( 2) minutes. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Extended self-test routine (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: recommended polling time: ^I ( 255) minutes. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SCT capabilities: ^I (0x003f)^ISCT Status supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISCT Error Recovery Control supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISCT Feature Control supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ^I^I^I^I^ISCT Data Table supported. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART Attributes Data Structure revision number: 16 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Vendor Specific SMART Attributes with Thresholds: (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 2765 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 3 Spin_Up_Time 0x0023 067 067 025 Pre-fail Always - 10177 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 3 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 64 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 181 Program_Fail_Cnt_Total 0x0022 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 194 Temperature_Celsius 0x0002 064 064 000 Old_age Always - 28 (Min/Max 22/31) (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART Error Log Version: 1 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: No Errors Logged (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART Self-test log structure revision number 1 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: No self-tests have been logged. [To run self-tests, use: smartctl -t] (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SMART Selective self-test log data structure revision number 0 (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Note: revision number not 1 implies that no selective self-test has ever been run (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 1 0 0 Completed [00% left] (0-65535) (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 2 0 0 Not_testing (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 3 0 0 Not_testing (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 4 0 0 Not_testing (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: 5 0 0 Not_testing (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: Selective self-test flags (0x0): (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: After scanning selected spans, do NOT read-scan remainder of disk. (Misc) May 25 09:22:34 Tower preclear_disk-diff[1138]: If Selective self-test is pending on power-up, resume after 0 minute delay. (Misc) Quote Link to comment
Joe L. Posted May 25, 2012 Share Posted May 25, 2012 Sorry, is this what you need? This is the 2nd preclear results for disk sdd. no, it is not. The results can be found in the /boot/preclear_reports directory. There are three files for each disk (the last set is saved on any given day). The "start" SMART report, the "finish" SMART report, and the actual "rpt" analysis. Joe L. Quote Link to comment
RobJ Posted May 25, 2012 Share Posted May 25, 2012 However, that SMART report is enough to say that your drive looks great! That is, if this SMART report is for the same drive that was producing the errors in your previous snippet. I think that what would be most helpful is the entire syslog that that snip came from. Please try to zip and attach it. Quote Link to comment
Joe L. Posted May 26, 2012 Share Posted May 26, 2012 However, that SMART report is enough to say that your drive looks great! That is, if this SMART report is for the same drive that was producing the errors in your previous snippet. I think that what would be most helpful is the entire syslog that that snip came from. Please try to zip and attach it. unfortunately, the SMART reports do NOT tell if the preclear was successful, or if there were issues reading back the zeros that were written to the drive. The smart reports can only tell you if there are sectors re-allocated/pending reallocation. (or other smart attributes failing or near failing) For that information, you really need the preclear "rpt" file. Quote Link to comment
Flomaster Posted May 29, 2012 Share Posted May 29, 2012 here is my preclear on a Seagate Barracuda 2TB 7200 RPM drive. I only ran one pass and didn't use a -a or a -A I am running the 4.7 version of unraid. The results look good, but I was wondering if I need to run it again with an -A or -a or put it into service http://pastebin.com/A12P3Ciu -=Jason=- preclear.txt Quote Link to comment
Lacehim Posted May 30, 2012 Share Posted May 30, 2012 Flomaster, I'm running 4.7 too, and I've got the same drive ST2000DM001 and I've just started a preclear with -A. I read a post by Joe L. http://lime-technology.com/forum/index.php?topic=10198.msg99785;topicseen#msg99785 that stated "Use the MBR-4k alignment for everything. A disk that is aligned at a 4096 byte boundary is automatically also aligned at a 512 byte boundary." I'm not sure if it's a good idea in my situation because I have 3xdrives (2x1Tb & 1x250Gb) precleared without the -A, and MBR unaligned set in unraid. I posted up my query in another thread, but no reply yet. Maybe I should have posted it in here? I figured I would be making 2 preclears anyway, so I can always change it on the second run. Are you in the same boat as me with unaligned drives in unraid, but wanting to add a bigger advanced format drive? What's your MBR set to in unraid? By the way I noticed that your drive started with sector of 64 on it's preclear, wouldn't that suggest that preclear aligned to 4k even though you didn't set it? I noticed when I loaded preclear that my drive, stock was listed as starting 63 with a 512 byte boundary and I then ran preclear it changed it to 64 (I used the -A command). Seagate state on their website that it's got some new "SmartAlign™ technology for no-hassle transition to Advanced Format 4K sector technology" but I'm not sure how that effects my preclear. I hope someone can help sort point us in the right direction, I've searched and searched and I haven't really found an answer. Quote Link to comment
Flomaster Posted May 30, 2012 Share Posted May 30, 2012 Flomaster, I'm running 4.7 too, and I've got the same drive ST2000DM001 and I've just started a preclear with -A. I read a post by Joe L. http://lime-technology.com/forum/index.php?topic=10198.msg99785;topicseen#msg99785 that stated "Use the MBR-4k alignment for everything. A disk that is aligned at a 4096 byte boundary is automatically also aligned at a 512 byte boundary." I'm not sure if it's a good idea in my situation because I have 3xdrives (2x1Tb & 1x250Gb) precleared without the -A, and MBR unaligned set in unraid. I posted up my query in another thread, but no reply yet. Maybe I should have posted it in here? I figured I would be making 2 preclears anyway, so I can always change it on the second run. Are you in the same boat as me with unaligned drives in unraid, but wanting to add a bigger advanced format drive? What's your MBR set to in unraid? By the way I noticed that your drive started with sector of 64 on it's preclear, wouldn't that suggest that preclear aligned to 4k even though you didn't set it? I noticed when I loaded preclear that my drive, stock was listed as starting 63 with a 512 byte boundary and I then ran preclear it changed it to 64 (I used the -A command). Seagate state on their website that it's got some new "SmartAlign™ technology for no-hassle transition to Advanced Format 4K sector technology" but I'm not sure how that effects my preclear. I hope someone can help sort point us in the right direction, I've searched and searched and I haven't really found an answer. It's been a while since I have fiddled with my unRaid server. I might have had a setting in the purchase script to set it at 4K alignment. I'll wait and see what the guru's say. All my other drives are Wd20Ears green drives with jumpers on them edit: as noted in the first post not using an -a or -A will use the unraid default settings on //tower I have mine set at MBR-4K-aligned and preclear will use those settings if you are running 4.7 or higher. so I think I am in the clear and can assign my drive to the array. If you are running unRAID 4.7 onward, in the absence of either a "-a" or "-A" option specified on the command line, preclear_disk.sh will use the alignment preference you specified in the unRAID settings screen as its default. (-a will force MBR-unaligned. -A will force MBR-4k-aligned ) Quote Link to comment
Lacehim Posted May 30, 2012 Share Posted May 30, 2012 That makes sense flomaster. Hopefully someone can confirm if mine will be okay, currently running unraid as unaligned, but preclearing I force -A aligned. Will it be okay? Also, what speeds did you get during preclear? The first read I was getting great speed, starting at 150MB/s, and the same during writing to the drive, then when I checked the post read it's only at 1/3 of the speed at 50MB/s. Any idea if that's normal? Quote Link to comment
chuck23322 Posted May 30, 2012 Share Posted May 30, 2012 That makes sense flomaster. Hopefully someone can confirm if mine will be okay, currently running unraid as unaligned, but preclearing I force -A aligned. Will it be okay? Also, what speeds did you get during preclear? The first read I was getting great speed, starting at 150MB/s, and the same during writing to the drive, then when I checked the post read it's only at 1/3 of the speed at 50MB/s. Any idea if that's normal? Each drive "stands alone". While if you have some drives formatted poorly, you may have lower performance on those drives. "Back in the day" you could set a jumper on AF drives and format them "without alignment", or remove (or not install) the jumper and format them with the "alignment". Where you got into trouble is if you did it backwards -- 'aligned' with a jumper, or didn't align without the jumper. {And note: Removing/Adding a jumper AFTER the drive is active in your array is bad juju. You need to effectively remove the drive, safely from the array, and decide whether to jumper and format without alignment {the jumper "fakes out" the drive to effectively do the alignment internally} -- or, as many are now doing, not jumpering and formatting with alignment} Since most modern AF drives are shipped without the jumper now, the proper behavior (of 4.7 +) is to format ALL drives as aligned. This works fine on old and new drives now. So yes, you can mix/match. Just if you get it wrong, you'll get worse performance. There are long threads here on the whole subject. Quote Link to comment
Joe L. Posted May 30, 2012 Share Posted May 30, 2012 here is my preclear on a Seagate Barracuda 2TB 7200 RPM drive. I only ran one pass and didn't use a -a or a -A I am running the 4.7 version of unraid. The results look good, but I was wondering if I need to run it again with an -A or -a or put it into service http://pastebin.com/A12P3Ciu -=Jason=- You do not need to do anything more. The disk looks great. In the absence of a "-a" or "-A" option, the value you've elected in your unRAID preferences is used. (apparently, you have your set to 4k-aligned.) The partition starting on sector 64 is perfect;y fine in any array and with any disk. There is only one model of disk from one manufacturer (EARS drives) that performed poorly when partitioned to start on sector 63 and even that only shows the lesser performance when dealing with small files. When reading music or movie media files, most people will never notice the difference, even with an EARS drive partitioned on sector63, since the performance is still more than enough listen/view with no issues. Joe L. Quote Link to comment
EddieA Posted June 1, 2012 Share Posted June 1, 2012 I just added 5 new 2T Seagate drives attached to an IBM 1015 controller, flashed to a LSI 9211/IT mode, and ran pre-clears on all 5 drives. All 5 show the same near_thresh warnings: Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Is this something to worry about, or it just a mis-interpretation of the values returned by SMART. All 5 drives passed the SMART tests, and all 5 have 0 re-allocated sectors. Cheers. preclear_rpts.zip Quote Link to comment
Joe L. Posted June 1, 2012 Share Posted June 1, 2012 I just added 5 new 2T Seagate drives attached to an IBM 1015 controller, flashed to a LSI 9211/IT mode, and ran pre-clears on all 5 drives. All 5 show the same near_thresh warnings: Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Is this something to worry about, or it just a mis-interpretation of the values returned by SMART. All 5 drives passed the SMART tests, and all 5 have 0 re-allocated sectors. Cheers. It is not anything to worry about, and not a mis-interpertation either. The normalized value for those two parameters is 100. The failure threshold is 97 and 99 respectively. Only the manufacturer knows how many errors would cause the value to decrement from 100 to 97 (or 100 to 99) It might be 1 to 1. It could just as easily be 100 to 1 or 10000 to 1. (there is no real standard for setting the starting value or thresholds...) The raw counts are both zero, so you''ve apparently never had to re-try spinning up. (or had an end-to-end error, whatever that is) Joe L. 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.