calypsocowboy Posted February 15, 2011 Share Posted February 15, 2011 See Reply #4 and #5 for resolution. ------------ I bought a boxed WD Ears 2TB drive to add to my array. Drive was unopened. I started preclearing it last night and it was really slow, but in the past I've had the preclear take 24+ hours so I left it running. I checked tonight after 24 hours and still on the first step, so I killed the process. I looked in the syslog and found some errors, this is what I tried. Drive is jumpered, I'm running 4.6c 1. The cables on the PCI addon card were not on all the way, there was a physical problem with the plug and card, I fixed that. Tried 3 different cables. Same issue. 2. I tried a different SATA cable from controller to hard drive, no luck, here is an exerpt of the logs. Feb 14 22:24:42 CASCADE kernel: ata2.00: cmd c8/00:00:c8:39:3a/00:00:00:00:00/e0 tag 0 dma 131072 in (Drive related) Feb 14 22:24:42 CASCADE kernel: res 51/84:8f:c8:39:3a/84:01:00:00:00/e0 Emask 0x12 (ATA bus error) (Errors) Feb 14 22:24:42 CASCADE kernel: ata2.00: status: { DRDY ERR } (Drive related) Feb 14 22:24:42 CASCADE kernel: ata2.00: error: { ICRC ABRT } (Errors) Feb 14 22:24:42 CASCADE kernel: ata2: hard resetting link (Minor Issues) Feb 14 22:24:43 CASCADE kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related) Feb 14 22:24:43 CASCADE kernel: ata2.00: configured for UDMA/33 (Drive related) Feb 14 22:24:43 CASCADE kernel: ata2: EH complete (Drive related) Feb 14 22:24:43 CASCADE kernel: ata2.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 (Errors) Feb 14 22:24:43 CASCADE kernel: ata2.00: BMDMA stat 0x5 (Drive related) Feb 14 22:24:43 CASCADE kernel: ata2: SError: { UnrecovData Proto TrStaTrns } (Errors) Feb 14 22:24:43 CASCADE kernel: ata2.00: failed command: READ DMA (Minor Issues) Feb 14 22:24:43 CASCADE kernel: ata2.00: cmd c8/00:00:c8:c9:3a/00:00:00:00:00/e0 tag 0 dma 131072 in (Drive related) Feb 14 22:24:43 CASCADE kernel: res 51/84:af:c8:c9:3a/84:01:00:00:00/e0 Emask 0x12 (ATA bus error) (Errors) Feb 14 22:24:43 CASCADE kernel: ata2.00: status: { DRDY ERR } (Drive related) Feb 14 22:24:43 CASCADE kernel: ata2.00: error: { ICRC ABRT } (Errors) Feb 14 22:24:43 CASCADE kernel: ata2: hard resetting link (Minor Issues) Feb 14 22:24:43 CASCADE kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related) Feb 14 22:24:43 CASCADE kernel: ata2.00: configured for UDMA/33 (Drive related) Feb 14 22:24:43 CASCADE kernel: ata2: EH complete (Drive related) 3. I Checked the power plugs and moved the molex connector to another rail on my power supply. Same type of errors. Feb 14 22:43:23 CASCADE kernel: ata2.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 Feb 14 22:43:23 CASCADE kernel: ata2.00: BMDMA stat 0x5 Feb 14 22:43:23 CASCADE kernel: ata2: SError: { UnrecovData Proto TrStaTrns } Feb 14 22:43:23 CASCADE kernel: ata2.00: failed command: READ DMA Feb 14 22:43:23 CASCADE kernel: ata2.00: cmd c8/00:00:00:5a:01/00:00:00:00:00/e0 tag 0 dma 131072 in Feb 14 22:43:23 CASCADE kernel: res 51/84:7f:00:5a:01/00:00:00:00:00/e0 Emask 0x12 (ATA bus error) Feb 14 22:43:23 CASCADE kernel: ata2.00: status: { DRDY ERR } Feb 14 22:43:23 CASCADE kernel: ata2.00: error: { ICRC ABRT } Feb 14 22:43:23 CASCADE kernel: ata2: hard resetting link Feb 14 22:43:24 CASCADE kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 14 22:43:24 CASCADE kernel: ata2.00: configured for UDMA/133 Feb 14 22:43:24 CASCADE kernel: ata2: EH complete Feb 14 22:43:24 CASCADE kernel: ata2.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 Feb 14 22:43:24 CASCADE kernel: ata2.00: BMDMA stat 0x5 Feb 14 22:43:24 CASCADE kernel: ata2: SError: { UnrecovData Proto TrStaTrns } Feb 14 22:43:24 CASCADE kernel: ata2.00: failed command: READ DMA Feb 14 22:43:24 CASCADE kernel: ata2.00: cmd c8/00:00:00:5c:01/00:00:00:00:00/e0 tag 0 dma 131072 in Feb 14 22:43:24 CASCADE kernel: res 51/84:bf:00:5c:01/00:00:00:00:00/e0 Emask 0x12 (ATA bus error) Feb 14 22:43:24 CASCADE kernel: ata2.00: status: { DRDY ERR } Feb 14 22:43:24 CASCADE kernel: ata2.00: error: { ICRC ABRT } Feb 14 22:43:24 CASCADE kernel: ata2: hard resetting link Feb 14 22:43:24 CASCADE kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 14 22:43:24 CASCADE kernel: ata2.00: configured for UDMA/133 Feb 14 22:43:24 CASCADE kernel: ata2: EH complete Feb 14 22:43:24 CASCADE kernel: ata2.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 4. I moved the cables on the controller card around, the controller card is currently controlling one sata drive without issue.Same error different port would lead me to believe it is a hard drive issue. Feb 14 23:18:59 CASCADE kernel: ata1.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 Feb 14 23:18:59 CASCADE kernel: ata1.00: BMDMA stat 0x5 Feb 14 23:18:59 CASCADE kernel: ata1: SError: { UnrecovData Proto TrStaTrns } Feb 14 23:18:59 CASCADE kernel: ata1.00: failed command: READ DMA EXT Feb 14 23:18:59 CASCADE kernel: ata1.00: cmd 25/00:00:00:00:00/00:04:00:00:00/e0 tag 0 dma 524288 in Feb 14 23:18:59 CASCADE kernel: res 51/84:5f:00:00:00/84:02:00:00:00/e0 Emask 0x12 (ATA bus error) Feb 14 23:18:59 CASCADE kernel: ata1.00: status: { DRDY ERR } Feb 14 23:18:59 CASCADE kernel: ata1.00: error: { ICRC ABRT } Feb 14 23:18:59 CASCADE kernel: ata1: hard resetting link Feb 14 23:18:59 CASCADE kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 14 23:18:59 CASCADE kernel: ata1.00: configured for UDMA/133 Feb 14 23:18:59 CASCADE kernel: ata1: EH complete Feb 14 23:18:59 CASCADE kernel: ata1.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 Feb 14 23:18:59 CASCADE kernel: ata1.00: BMDMA stat 0x5 Feb 14 23:18:59 CASCADE kernel: ata1: SError: { UnrecovData Proto TrStaTrns } Feb 14 23:18:59 CASCADE kernel: ata1.00: failed command: READ DMA EXT Feb 14 23:18:59 CASCADE kernel: ata1.00: cmd 25/00:00:00:00:00/00:04:00:00:00/e0 tag 0 dma 524288 in Feb 14 23:18:59 CASCADE kernel: res 51/84:df:00:00:00/84:03:00:00:00/e0 Emask 0x12 (ATA bus error) Feb 14 23:18:59 CASCADE kernel: ata1.00: status: { DRDY ERR } Feb 14 23:18:59 CASCADE kernel: ata1.00: error: { ICRC ABRT } Feb 14 23:18:59 CASCADE kernel: ata1: hard resetting link Feb 14 23:19:00 CASCADE kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 14 23:19:00 CASCADE kernel: ata1.00: configured for UDMA/133 Feb 14 23:19:00 CASCADE kernel: ata1: EH complete Feb 14 23:19:00 CASCADE kernel: ata1.00: limiting speed to UDMA/100:PIO4 Feb 14 23:19:00 CASCADE kernel: ata1.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 5. I ran a low level format that appears to work dd if=/dev/zero count=8 of=/dev/sda 8+0 records in 8+0 records out 4096 bytes (4.1 kB) copied, 0.0522217 s, 78.4 kB/s Ran preclear again. Same issue Feb 14 23:37:00 CASCADE kernel: ata1.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 Feb 14 23:37:00 CASCADE kernel: ata1.00: BMDMA stat 0x5 Feb 14 23:37:00 CASCADE kernel: ata1: SError: { UnrecovData Proto TrStaTrns } Feb 14 23:37:00 CASCADE kernel: ata1.00: failed command: READ DMA EXT Feb 14 23:37:00 CASCADE kernel: ata1.00: cmd 25/00:00:00:24:00/00:02:00:00:00/e0 tag 0 dma 262144 in Feb 14 23:37:00 CASCADE kernel: res 51/84:2f:00:24:00/84:00:00:00:00/e0 Emask 0x12 (ATA bus error) Feb 14 23:37:00 CASCADE kernel: ata1.00: status: { DRDY ERR } Feb 14 23:37:00 CASCADE kernel: ata1.00: error: { ICRC ABRT } Feb 14 23:37:00 CASCADE kernel: ata1: hard resetting link Feb 14 23:37:00 CASCADE kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 14 23:37:00 CASCADE kernel: ata1.00: configured for UDMA/33 Feb 14 23:37:00 CASCADE kernel: ata1: EH complete Feb 14 23:37:02 CASCADE kernel: ata1.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 Feb 14 23:37:02 CASCADE kernel: ata1.00: BMDMA stat 0x5 Feb 14 23:37:02 CASCADE kernel: ata1: SError: { UnrecovData Proto TrStaTrns } Feb 14 23:37:02 CASCADE kernel: ata1.00: failed command: READ DMA Feb 14 23:37:02 CASCADE kernel: ata1.00: cmd c8/00:00:00:93:02/00:00:00:00:00/e0 tag 0 dma 131072 in Feb 14 23:37:02 CASCADE kernel: res 51/84:6f:00:93:02/84:00:00:00:00/e0 Emask 0x12 (ATA bus error) Feb 14 23:37:02 CASCADE kernel: ata1.00: status: { DRDY ERR } Feb 14 23:37:02 CASCADE kernel: ata1.00: error: { ICRC ABRT } Feb 14 23:37:02 CASCADE kernel: ata1: hard resetting link Feb 14 23:37:02 CASCADE kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 14 23:37:02 CASCADE kernel: ata1.00: configured for UDMA/33 Feb 14 23:37:02 CASCADE kernel: ata1: EH complete Feb 14 23:37:02 CASCADE kernel: ata1.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 What is next, the low level format seemed to work fine and ran quick. Do I need to run the low level format differently and do more of the drive than just 8? Is the hard drive bad? Here is the smart information if that helps. 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-WMAZA2802606 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: Mon Feb 14 23:55:42 2011 Local time zone must be set--see zic m SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (37080) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 991 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 16 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 - 25 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 - 14 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 9 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 62 194 Temperature_Celsius 0x0022 112 109 000 Old_age Always - 38 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 188 000 Old_age Always - 189997 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. Thanks, Josh Quote Link to comment
Rajahal Posted February 15, 2011 Share Posted February 15, 2011 The average time to preclear a 2 TB WD EARS is 35 hours. So taking longer than 24 hours is normal, but of course the first step should finish sooner than that. SMART indicates a cabling problem (huge CRC count), but since you've already exhausted that option then I guess it must be a bad drive. It is a bit odd. By the way, I recently precleared a brand new OEM WD EARS that took 74 hours - far longer than usual. Still, it passed preclear with no SMART errors so I ran it through another preclear. Second pass came up clean and finished in the standard time (35 hours). I've since been running it through a few more passes of preclear and all seems normal. So once in a while I guess a drive will just be slow at first and then figure itself out... Quote Link to comment
vca Posted February 15, 2011 Share Posted February 15, 2011 By the way, I recently precleared a brand new OEM WD EARS that took 74 hours - far longer than usual. Still, it passed preclear with no SMART errors so I ran it through another preclear. Second pass came up clean and finished in the standard time (35 hours). I've since been running it through a few more passes of preclear and all seems normal. So once in a while I guess a drive will just be slow at first and then figure itself out... I had a slow preclear on a 2TB EARS back in January, it was a bit more than twice as long as it should have been (normally about 28 hours for me). There was nothing wrong according to the SMART reports (even a long SMART test) so I ran a second preclear thinking that maybe the first might have "fixed things". However the second preclear was just as slow so I returned the drive, the replacement ran through its preclear at the normal speed. Regards, Stephen Quote Link to comment
calypsocowboy Posted February 16, 2011 Author Share Posted February 16, 2011 Ugh what a mess. I thought I'd start with an update to 4.7, well it turns out one of my drives had HPA enabled. So I spent all night getting that working, hdparm wouldn't work, so I was used HDAT2, that didn't work because it didn't recognize my controller on my sata card, so I plugged the hard drive into a motherboard sata slot to get HDAT2 working, got the HPA removed and the array is rebuilding right now. One thing I've learned is it may be my controller card. I've read reports on the internet or problems with the VT6421 cards with Sata II drives and with Linux kernals giving the same error I was getting. I tried again clearing the MBR but got the same errors Feb 16 00:00:46 CASCADE kernel: ata2.00: exception Emask 0x12 SAct 0x0 SErr 0x1000500 action 0x6 Feb 16 00:00:46 CASCADE kernel: ata2.00: BMDMA stat 0x5 Feb 16 00:00:46 CASCADE kernel: ata2: SError: { UnrecovData Proto TrStaTrns } Feb 16 00:00:46 CASCADE kernel: ata2.00: failed command: READ DMA EXT Feb 16 00:00:46 CASCADE kernel: ata2.00: cmd 25/00:c0:60:00:00/00:01:00:00:00/e0 tag 0 dma 229376 in Feb 16 00:00:46 CASCADE kernel: res 51/84:2f:60:00:00/84:00:00:00:00/e0 Emask 0x12 (ATA bus error) Feb 16 00:00:46 CASCADE kernel: ata2.00: status: { DRDY ERR } Feb 16 00:00:46 CASCADE kernel: ata2.00: error: { ICRC ABRT } Feb 16 00:00:46 CASCADE kernel: ata2: hard resetting link Feb 16 00:00:46 CASCADE kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 16 00:00:46 CASCADE kernel: ata2.00: configured for UDMA/100 Feb 16 00:00:46 CASCADE kernel: ata2: EH complete So I'm not going to even try a preclear. I have set the jumper on the drive to Sata I mode but that doesn't seem to be having any affect. I'm going to let the array rebuild overnight and then tomorrow night try the upgrade to 4.7 and see if that makes a different since the EARS drive will be unjumpered. I suspect it won't impact it. I broke down today and got a 4 port PCI SATA card from Monoprice with the Sil3114 chipset, I believe, I'm hoping I'll have better luck with that card and will try that before I take the hard drive back. Stay tuned for more.... Quote Link to comment
calypsocowboy Posted February 19, 2011 Author Share Posted February 19, 2011 Update.. 4.7 Upgrade complete, still same errors. I found an updated bios for my VT6421 card, tried that, no dice still same errors. My Sil3114 card from Monoprice showed up today, got it installed, bios flashed, and now have preclear started. It's running at 80 MB/s and no errors so far. So it looks like it was the add-on card or the chipset VT6421 that was the issue. Bonus out of the deal is the new card has 4 ports instead of 2 like my old card, so that will be nice for the future. I'll post another update tomorrow when preclear finishes. -Josh Quote Link to comment
calypsocowboy Posted February 22, 2011 Author Share Posted February 22, 2011 Preclear finished with no errors in about 36 hours. Drive was added and the array is rebuilding. Hope this thread helps out someone in the future if they see the same errors. Old Card: Rosewill RC-212 - worked with 500GB drive, didn't work with 2.0TB drive New Card: Monoprice Sil3114 - worked with 2.0TB drive. -Josh 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.