July 18, 201114 yr I started these 2 preclearing not far apart, perhaps 10 minutes, but as I checkup on the post-read step one is WAY slower than the other. At first I thought one had simply frozen, but the bytes read counter has changed from time to time, although no speed is shown. Not sure it matters, but the difference in elapsed time between the two keeps changing, below it's 5mins, as I just looked again it's only 1 minute. I realize the way it's being calculated in the script, or slow display refreshes, etc., could cause it to fluctuate in a strange manner. WD Green (advanced format): = Post-Read in progress: 0% complete. ( 9,870,336,000 of 2,000,398,934,016 bytes read ) Disk Temperature: 39C, Elapsed Time: 19:11:13 Hitachi 5K3000 (not advanced format): = Post-Read in progress: 49% complete. ( 983,743,488,000 of 2,000,398,934,016 bytes read ) 84.5 MB/s Disk Temperature: 41C, Elapsed Time: 19:05:38 Anyone think this indicates a problem?
July 18, 201114 yr That doesn't look terrible. My WD EARS drives are the slowest in a mix with Hitachi & Samsung 5KRPM drives, not that it's really noticeable in daily use.
July 19, 201114 yr Author Ok, Hitachi finished completely just under 27 hours, WD still at 1%: Post-Read in progress: 1% complete. ( 26,320,896,000 of 2,000,398,934,016 bytes read ) Disk Temperature: 39C, Elapsed Time: 27:40:39 The speed difference for this final step is insane. Any chance it has something to do with advanced format?, the Hitachi is not adv format.
July 19, 201114 yr Things looked okay before the post-read but that's out to lunch. Did anyone mess with things about when you posted before? Can you start another session and give us the syslog?
July 19, 201114 yr Things looked okay before the post-read but that's out to lunch. Did anyone mess with things about when you posted before? Can you start another session and give us the syslog? I'm a complete duffer and can only offer what I think is the "obvious" answer ... the drive just might be bad [shrug]
July 19, 201114 yr Things looked okay before the post-read but that's out to lunch. Did anyone mess with things about when you posted before? Can you start another session and give us the syslog? I'm a complete duffer and can only offer what I think is the "obvious" answer ... the drive just might be bad [shrug] And, we've seen that a number of times already. You might look in the syslog. You might see a number of errors. They would give a clue as to what is happening. (although we've seen drives with no outward errors perform slowly...)
July 19, 201114 yr Author Didn't even think to check the logs, that was kinda stupid ata3.00: configured for UDMA/133 ata3: EH complete ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata3.00: irq_stat 0x40000008 ata3.00: failed command: READ FPDMA QUEUED ata3.00: cmd 60/08:00:20:04:d1/00:00:04:00:00/40 tag 0 ncq 4096 in res 41/40:00:20:04:d1/4d:00:04:00:00/40 Emask 0x409 (media error) <F> ata3.00: status: { DRDY ERR } ata3.00: error: { UNC } ata3.00: configured for UDMA/133 ata3: EH complete ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata3.00: irq_stat 0x40000008 ata3.00: failed command: READ FPDMA QUEUED ata3.00: cmd 60/08:00:20:04:d1/00:00:04:00:00/40 tag 0 ncq 4096 in res 41/40:00:20:04:d1/4d:00:04:00:00/40 Emask 0x409 (media error) <F> ata3.00: status: { DRDY ERR } ata3.00: error: { UNC } ata3.00: configured for UDMA/133 sd 3:0:0:0: [sdc] Unhandled sense code sd 3:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 sd 3:0:0:0: [sdc] Sense Key : 0x3 [current] [descriptor] Descriptor sense data with sense descriptors (in hex): 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 04 d1 04 20 sd 3:0:0:0: [sdc] ASC=0x11 ASCQ=0x4 sd 3:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 04 d1 04 20 00 00 08 00 end_request: I/O error, dev sdc, sector 80806944 Buffer I/O error on device sdc, logical block 10100868 ata3: EH complete ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata3.00: irq_stat 0x40000008 ata3.00: failed command: READ FPDMA QUEUED ata3.00: cmd 60/08:00:b8:42:d1/00:00:04:00:00/40 tag 0 ncq 4096 in res 41/40:00:b8:42:d1/4d:00:04:00:00/40 Emask 0x409 (media error) <F> ata3.00: status: { DRDY ERR } ata3.00: error: { UNC } ata3.00: configured for UDMA/133 ata3: EH complete Had this drive for a few weeks, used it a little before I decided to start the unraid box. Mechanically, noise, errors, there were none on Windows when I wrote about 1TB to it. If anyone has more info on these errors I'd greatly appreciate it. I have another WD Green 2TB preclearing now, but it'll be another 10hrs or so before it reaches the post-read stage.
July 19, 201114 yr Didn't even think to check the logs, that was kinda stupid ata3.00: configured for UDMA/133 ata3: EH complete ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata3.00: irq_stat 0x40000008 ata3.00: failed command: READ FPDMA QUEUED ata3.00: cmd 60/08:00:20:04:d1/00:00:04:00:00/40 tag 0 ncq 4096 in res 41/40:00:20:04:d1/4d:00:04:00:00/40 Emask 0x409 (media error) <F> ata3.00: status: { DRDY ERR } ata3.00: error: { UNC } ata3.00: configured for UDMA/133 ata3: EH complete ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata3.00: irq_stat 0x40000008 ata3.00: failed command: READ FPDMA QUEUED ata3.00: cmd 60/08:00:20:04:d1/00:00:04:00:00/40 tag 0 ncq 4096 in res 41/40:00:20:04:d1/4d:00:04:00:00/40 Emask 0x409 (media error) <F> ata3.00: status: { DRDY ERR } ata3.00: error: { UNC } ata3.00: configured for UDMA/133 sd 3:0:0:0: [sdc] Unhandled sense code sd 3:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 sd 3:0:0:0: [sdc] Sense Key : 0x3 [current] [descriptor] Descriptor sense data with sense descriptors (in hex): 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 04 d1 04 20 sd 3:0:0:0: [sdc] ASC=0x11 ASCQ=0x4 sd 3:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 04 d1 04 20 00 00 08 00 end_request: I/O error, dev sdc, sector 80806944 Buffer I/O error on device sdc, logical block 10100868 ata3: EH complete ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata3.00: irq_stat 0x40000008 ata3.00: failed command: READ FPDMA QUEUED ata3.00: cmd 60/08:00:b8:42:d1/00:00:04:00:00/40 tag 0 ncq 4096 in res 41/40:00:b8:42:d1/4d:00:04:00:00/40 Emask 0x409 (media error) <F> ata3.00: status: { DRDY ERR } ata3.00: error: { UNC } ata3.00: configured for UDMA/133 ata3: EH complete Had this drive for a few weeks, used it a little before I decided to start the unraid box. Mechanically, noise, errors, there were none on Windows when I wrote about 1TB to it. If anyone has more info on these errors I'd greatly appreciate it. I have another WD Green 2TB preclearing now, but it'll be another 10hrs or so before it reaches the post-read stage. UNC Media Errors are un-readable sectors on the disk. Get a SMART report. It will show the sectors pending re-allocation (or re-allocated) growing. smartctl -a /dev/sdc where sdc = your drive with the errors. You can do this while the pre-clear is progressing on the drive. Joe L.
July 19, 201114 yr Author Looks like there are some errors. Funny though I ran this for several days with no problems, and like I said copied about 1TB to it, but I guess maybe the preclear working the entire drive brought them up. So, RMA I guess? smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA4364927 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue Jul 19 14:03:07 2011 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. General SMART Values: Offline data collection status: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (38160) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 001 001 051 Pre-fail Always FAILING_NOW 30401 3 Spin_Up_Time 0x0027 222 204 021 Pre-fail Always - 3900 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 19 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 54 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 12 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 46 194 Temperature_Celsius 0x0022 108 107 000 Old_age Always - 42 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 199 199 000 Old_age Always - 634 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
July 19, 201114 yr This is bad, 634 sectors pending re-allocation when next written. RMA the drive. 197 Current_Pending_Sector 0x0032 199 199 000 Old_age Always - 634 This is exactly why many/most users pre-clear the drives.
Archived
This topic is now archived and is closed to further replies.