October 18, 201114 yr I have had several precleared hitachi LP 3TB drives sitting as "warm spares" for a while in my unRAID box. I decided to expand my array the other day and add another 3TB drive. I picked one from my pool of spares. err.. yeah.. about that. I decided to add "6umc" next. It did not see the preclear bit and decided to start clearing the drive.. I canceled the clearing and I decided to preclear it using Joe L's wonderful preclear tool (again) It went though the first read and blew up. (see picture) I then took 3 of my spare 3TB drives and put them into a test rig: SM X7SPA-HF, 8gigs of ram. Same blow up at the same point on 6UMC. the other 2 drives finished as expected. I did notice that the Load_Cycle_Count is crazy high for an unused drive. My in use drives are a fraction of that. I grabbed a syslog and it was totally useless, for some reason it restarted right before i grabbed it. Smart Report for drive: === START OF INFORMATION SECTION === Device Model: Hitachi HDS5C3030ALA630 Serial Number: MJ1323YNG16UMC Firmware Version: MEAOA580 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 Oct 18 17:40:27 2011 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: (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: (38769) 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: ( 255) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 134 134 054 Pre-fail Offline - 112 3 Spin_Up_Time 0x0007 154 154 024 Pre-fail Always - 458 (Average 450) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 45 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 132 132 020 Pre-fail Offline - 32 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 2040 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 36 192 Power-Off_Retract_Count 0x0032 046 046 000 Old_age Always - 65535 193 Load_Cycle_Count 0x0012 001 001 000 Old_age Always - 232873 194 Temperature_Celsius 0x0002 200 200 000 Old_age Always - 30 (Min/Max 24/39) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 General Purpose Logging (GPL) feature set supported General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] GP/S Log at address 0x00 has 1 sectors [Log Directory] SMART Log at address 0x01 has 1 sectors [summary SMART error log] GP Log at address 0x03 has 1 sectors [Ext. Comprehensive SMART error log] GP Log at address 0x04 has 7 sectors [Device Statistics] SMART Log at address 0x06 has 1 sectors [sMART self-test log] GP Log at address 0x07 has 1 sectors [Extended self-test log] GP Log at address 0x08 has 1 sectors [Reserved] SMART Log at address 0x09 has 1 sectors [selective self-test log] GP Log at address 0x10 has 1 sectors [NCQ Command Error] GP Log at address 0x11 has 1 sectors [sATA Phy Event Counters] GP Log at address 0x20 has 1 sectors [streaming performance log] GP Log at address 0x21 has 1 sectors [Write stream error log] GP Log at address 0x22 has 1 sectors [Read stream error log] GP/S Log at address 0x80 has 16 sectors [Host vendor specific log] GP/S Log at address 0x81 has 16 sectors [Host vendor specific log] GP/S Log at address 0x82 has 16 sectors [Host vendor specific log] GP/S Log at address 0x83 has 16 sectors [Host vendor specific log] GP/S Log at address 0x84 has 16 sectors [Host vendor specific log] GP/S Log at address 0x85 has 16 sectors [Host vendor specific log] GP/S Log at address 0x86 has 16 sectors [Host vendor specific log] GP/S Log at address 0x87 has 16 sectors [Host vendor specific log] GP/S Log at address 0x88 has 16 sectors [Host vendor specific log] GP/S Log at address 0x89 has 16 sectors [Host vendor specific log] GP/S Log at address 0x8a has 16 sectors [Host vendor specific log] GP/S Log at address 0x8b has 16 sectors [Host vendor specific log] GP/S Log at address 0x8c has 16 sectors [Host vendor specific log] GP/S Log at address 0x8d has 16 sectors [Host vendor specific log] GP/S Log at address 0x8e has 16 sectors [Host vendor specific log] GP/S Log at address 0x8f has 16 sectors [Host vendor specific log] GP/S Log at address 0x90 has 16 sectors [Host vendor specific log] GP/S Log at address 0x91 has 16 sectors [Host vendor specific log] GP/S Log at address 0x92 has 16 sectors [Host vendor specific log] GP/S Log at address 0x93 has 16 sectors [Host vendor specific log] GP/S Log at address 0x94 has 16 sectors [Host vendor specific log] GP/S Log at address 0x95 has 16 sectors [Host vendor specific log] GP/S Log at address 0x96 has 16 sectors [Host vendor specific log] GP/S Log at address 0x97 has 16 sectors [Host vendor specific log] GP/S Log at address 0x98 has 16 sectors [Host vendor specific log] GP/S Log at address 0x99 has 16 sectors [Host vendor specific log] GP/S Log at address 0x9a has 16 sectors [Host vendor specific log] GP/S Log at address 0x9b has 16 sectors [Host vendor specific log] GP/S Log at address 0x9c has 16 sectors [Host vendor specific log] GP/S Log at address 0x9d has 16 sectors [Host vendor specific log] GP/S Log at address 0x9e has 16 sectors [Host vendor specific log] GP/S Log at address 0x9f has 16 sectors [Host vendor specific log] GP/S Log at address 0xe0 has 1 sectors [sCT Command/Status] GP/S Log at address 0xe1 has 1 sectors [sCT Data Transfer] SMART Extended Comprehensive Error Log Version: 1 (1 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 2037 - 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. SCT Status Version: 3 SCT Version (vendor specific): 256 (0x0100) SCT Support Level: 1 Device State: Active (0) Current Temperature: 31 Celsius Power Cycle Min/Max Temperature: 28/31 Celsius Lifetime Min/Max Temperature: 24/39 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -40/70 Celsius Temperature History Size (Index): 128 (106) Index Estimated Time Temperature Celsius 107 2011-10-18 15:33 29 ********** ... ..( 86 skipped). .. ********** 66 2011-10-18 17:00 29 ********** 67 2011-10-18 17:01 30 *********** 68 2011-10-18 17:02 29 ********** 69 2011-10-18 17:03 29 ********** 70 2011-10-18 17:04 29 ********** 71 2011-10-18 17:05 28 ********* ... ..( 4 skipped). .. ********* 76 2011-10-18 17:10 28 ********* 77 2011-10-18 17:11 29 ********** ... ..( 3 skipped). .. ********** 81 2011-10-18 17:15 29 ********** 82 2011-10-18 17:16 30 *********** ... ..( 12 skipped). .. *********** 95 2011-10-18 17:29 30 *********** 96 2011-10-18 17:30 31 ************ 97 2011-10-18 17:31 30 *********** ... ..( 4 skipped). .. *********** 102 2011-10-18 17:36 30 *********** 103 2011-10-18 17:37 31 ************ 104 2011-10-18 17:38 31 ************ 105 2011-10-18 17:39 31 ************ 106 2011-10-18 17:40 30 *********** SCT Error Recovery Control: Read: Disabled Write: Disabled SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0009 2 0 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 0 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FIS I threw it back in the production array and let unraid go down for a day and clear it itself. I now have copied a few TB of test data to it and it looks to be a binary exact match.. call it a fluke or a is there a problem? any Ideas?
October 18, 201114 yr It looks like you may have a power issue. 8 Seek_Time_Performance 0x0005 132 132 020 Pre-fail Offline - 32 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 2040 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 36 192 Power-Off_Retract_Count 0x0032 046 046 000 Old_age Always - 65535 There have been 65535 power off retracts in 2040 hours.
October 19, 201114 yr Author I saw that. I'm guessing that was on my bad backplane.. question is.. trust the drive or not? EDIT: and the answer is.... NO! the drive red balled and ate the data on it when i tried it on another PC... It is the drive and not the backplane, the count is still going up.. Back to Hitachi she goes... I should point out, unRAID did its job again. it emailed me the disk dropped, I stopped the array, warm swapped drives, restated array rebuild began.. (of a blank drive.. lol)
October 19, 201114 yr Your screen shot shows a VERY OLD version of the preclear script. It has no idea how to set the signature correctly for a drive larger than 2.2TB. You should download the newest version. (currently 1.13) It can correctly handle the larger 3TB drives. Joe L.
October 19, 201114 yr Author That version was just downloaded. Brand new server, built just for preclearing. 5B12a with latest preclear I had thought. download from the first post on this thread, http://lime-technology.com/forum/index.php?topic=2817.0 it did the other 2 3tb drives as it should with GPT partitions. I had the same issue with the beta for was it 1.12? EDIT: Interesting... you are right. I had the beta and for some reason 1.9 ?!?! I must have had a brain fart when building the server, downloaded the new version but installed the old version from my install server? Thanks for pointing that out.. I downloaded it yet again... I'll re-run it again. but the drive is on its way out the door. it keeps power cycling itself. bad firmware or or bad controller card on it. the power off retracts are way past the drives limit. it is on deaths door.
Archived
This topic is now archived and is closed to further replies.