Joe L. Posted February 28, 2013 Share Posted February 28, 2013 I've got a 3TB WD Green drive that flip/flops pending sectors. One pass it's 65535 then next it's zero then 65535 then zero etc.. for at least 6 passes. I'm going to RMA since the last pass left it at 65535. That was the highest I've ever seen too. <snip> It's just a bad drive . Wow... really buggy firmware. It should never do that... I'd stay clear of that make/model/firmware; Device Model: WDC WD30EZRS-11J99B1 Firmware Version: 80.00A80 Joe L. Quote Link to comment
shooga Posted February 28, 2013 Share Posted February 28, 2013 Thanks for the reply on my slow preclear Joe. I am seeing the following errors: This one is repeated over and over again: Feb 26 21:46:17 Bunker kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Feb 26 21:46:17 Bunker kernel: ata4.00: BMDMA2 stat 0xd0009 Feb 26 21:46:17 Bunker kernel: ata4.00: failed command: READ DMA Feb 26 21:46:17 Bunker kernel: ata4.00: cmd c8/00:00:20:a2:ed/00:00:00:00:00/e0 tag 0 dma 131072 in Feb 26 21:46:17 Bunker kernel: res 51/40:df:3c:a2:ed/00:00:00:00:00/f0 Emask 0x9 (media error) Feb 26 21:46:17 Bunker kernel: ata4.00: status: { DRDY ERR } Feb 26 21:46:17 Bunker kernel: ata4.00: error: { UNC } Feb 26 21:46:25 Bunker kernel: ata4.00: configured for UDMA/100 Feb 26 21:46:25 Bunker kernel: ata4: EH complete This one shows up less frequently: Feb 26 21:46:39 Bunker kernel: end_request: I/O error, dev sdd, sector 15573615 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946701 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946702 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946703 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946704 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946705 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946706 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946707 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946708 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946709 Feb 26 21:46:39 Bunker kernel: Buffer I/O error on device sdd, logical block 1946710 Strangely though, it looks like later in the log those errors are showing for a different drive: complete Feb 27 16:10:51 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:10:51 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:10:51 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:10:51 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:10:51 Bunker kernel: ata2.00: cmd c8/00:00:e8:10:0a/00:00:00:00:00/e1 tag 0 dma 131072 in Feb 27 16:10:51 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:10:51 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:10:51 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:10:51 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:10:51 Bunker kernel: ata2: EH complete Feb 27 16:10:54 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:10:54 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:10:54 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:10:54 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:10:54 Bunker kernel: ata2.00: cmd c8/00:00:e8:10:0a/00:00:00:00:00/e1 tag 0 dma 131072 in Feb 27 16:10:54 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:10:54 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:10:54 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:10:54 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:10:54 Bunker kernel: ata2: EH complete Feb 27 16:10:57 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:10:57 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:10:57 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:10:57 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:10:57 Bunker kernel: ata2.00: cmd c8/00:00:e8:10:0a/00:00:00:00:00/e1 tag 0 dma 131072 in Feb 27 16:10:57 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:10:57 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:10:57 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:10:57 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] Unhandled sense code Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor] Feb 27 16:10:57 Bunker kernel: Descriptor sense data with sense descriptors (in hex): Feb 27 16:10:57 Bunker kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Feb 27 16:10:57 Bunker kernel: 01 0a 11 2b Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] ASC=0x11 ASCQ=0x4 Feb 27 16:10:57 Bunker kernel: sd 1:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 01 0a 10 e8 00 01 00 00 Feb 27 16:10:57 Bunker kernel: end_request: I/O error, dev sdb, sector 17436971 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179621 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179622 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179623 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179624 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179625 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179626 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179627 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179628 Feb 27 16:10:57 Bunker kernel: Buffer I/O error on device sdb, logical block 2179629 Feb 27 16:10:57 Bunker kernel: ata2: EH complete Feb 27 16:11:00 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:11:00 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:11:00 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:11:00 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:11:00 Bunker kernel: ata2.00: cmd c8/00:08:28:11:0a/00:00:00:00:00/e1 tag 0 dma 4096 in Feb 27 16:11:00 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:11:00 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:11:00 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:11:00 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:11:00 Bunker kernel: ata2: EH complete Feb 27 16:11:03 Bunker kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x200000 action 0x0 Feb 27 16:11:03 Bunker kernel: ata2.00: BMDMA2 stat 0x6c0009 Feb 27 16:11:03 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:11:03 Bunker kernel: ata2.00: failed command: READ DMA Feb 27 16:11:03 Bunker kernel: ata2.00: cmd c8/00:08:28:11:0a/00:00:00:00:00/e1 tag 0 dma 4096 in Feb 27 16:11:03 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:11:03 Bunker kernel: ata2.00: status: { DRDY ERR } Feb 27 16:11:03 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:11:03 Bunker kernel: ata2.00: configured for UDMA/100 Feb 27 16:11:03 Bunker kernel: ata2: EH complete Advice? Are these drives hosed? Quote Link to comment
trurl Posted February 28, 2013 Share Posted February 28, 2013 Can I preclear an external drive that's connected via USB? I've been using this for pre-clears since my case is full and I have one sata port left over: eSATA enclosure This particular one even came with an eSATA bracket Quote Link to comment
RobJ Posted February 28, 2013 Share Posted February 28, 2013 The number 65535 is not 65 thousand something, it's the unsigned integer representation of the 2 byte signed integer value of -1, so I wouldn't put too much significance in it. A return of -1 is usually a flag value, indicating a possible error or the current unavailability of the true number or something else but not a valid return value. If possible and I saw a value of 65535, I would grab a few more SMART reports, to see if it would change to a valid value. If not, I'd reboot and check again. If still not, then I would have to assume a bug in the SMART functions of the drive's firmware. As to the End-to-End error, I'm not sure we should give that much significance either, because it is a relatively new attribute, and looks to me to be still experimental. That does not mean it is not significant, it IS informational, but the SMART reports where both of these occurred (this one and one a week or 2 ago) both indicate that this was flagged 'Old_age' not 'Pre-fail', and therefore this is NOT considered a critical attribute. Since it is not considered critical, it is only informational, and as such that may be useful, but I'm not sure it should carry much weight in your decision making. There are many critics of the SMART system, and both of these situations just give them more ammo. Some don't trust SMART reports at all, but I feel that once you understand and have some experience with the vagaries and inconsistencies of SMART numbers and report info, then there is useful info there. I just wish they would get their act together a little better. Quote Link to comment
RobJ Posted February 28, 2013 Share Posted February 28, 2013 Thanks for the reply on my slow preclear Joe. I am seeing the following errors: This one is repeated over and over again: Feb 26 21:46:17 Bunker kernel: res 51/40:df:3c:a2:ed/00:00:00:00:00/f0 Emask 0x9 (media error) Feb 26 21:46:17 Bunker kernel: ata4.00: error: { UNC } Feb 26 21:46:39 Bunker kernel: end_request: I/O error, dev sdd, sector 15573615 Strangely though, it looks like later in the log those errors are showing for a different drive: Feb 27 16:10:51 Bunker kernel: ata2: SError: { BadCRC } Feb 27 16:10:51 Bunker kernel: res 51/40:00:2b:11:0a/00:00:00:00:00/11 Emask 0x9 (media error) Feb 27 16:10:51 Bunker kernel: ata2.00: error: { UNC } Feb 27 16:10:57 Bunker kernel: end_request: I/O error, dev sdb, sector 17436971 Advice? Are these drives hosed? Not hosed, but you do have some bad sectors on 2 drives, sdd and sdb. You also probably have a bad SATA cable to the drive sdb. Quote Link to comment
shooga Posted February 28, 2013 Share Posted February 28, 2013 Thanks Rob. Which error indicates the bad cable? These drives are connected via a 4 port SATA card. Could that have something to do with it? (I haven't noticed errors for the other two drives on that card though.) Quote Link to comment
RobJ Posted February 28, 2013 Share Posted February 28, 2013 Thanks Rob. Which error indicates the bad cable? These drives are connected via a 4 port SATA card. Could that have something to do with it? (I haven't noticed errors for the other two drives on that card though.) This error line, with the BadCRC flag set: Feb 27 16:10:51 Bunker kernel: ata2: SError: { BadCRC } It indicates corrupted packets across the cabling. That is almost always a bad SATA cable, easily replaced. It could also be a power issue to the drive, but if it was a power issue you would probably have had more BadCRC errors on other drives too. Since you didn't indicate any others, it's probably a bad cable to this drive. Both drives, after the bad sector handling, indicated "configured for UDMA/100", so I figured you must have them connected to an older disk controller, with UDMA/100 speed only. That is going to significantly impact their read and write speeds. Quote Link to comment
Joe L. Posted February 28, 2013 Share Posted February 28, 2013 It indicates corrupted packets across the cabling. That is almost always a bad SATA cable, easily replaced. It could also be a power issue to the drive, but if it was a power issue you would probably have had more BadCRC errors on other drives too. Since you didn't indicate any others, it's probably a bad cable to this drive. Or, it could be somebody who has tie-wrapped all the SATA cables together, or worse, tie-wrapped them to power cables, making it neat looking, and inadvertently maximizing the noise pickup potential from one to another. (In other words, making the likelihood of induced noise CRC/corrupted packets issues much higher) Memo to builders... do not bundle unshielded SATA cables.. It is a recipe for CRC errors. Joe L. Quote Link to comment
shooga Posted February 28, 2013 Share Posted February 28, 2013 I haven't tie wrapped any cables together...but I'll admit that I was tempted to do that before closing my case. I'll make sure I don't and will re-route SATA cables to spread them out a bit more. I went back and double checked my log and don't see any other CRC errors, so hopefully it's not a power issue. What's the best way to keep an eye on this? Just check the log periodically while using the drives? Should I preclear again with a new cable to test? Do the bad sectors indicate a drive that is nearing end of life? Is it still worth adding these to my array? The SATA controller card is from Monoprice and it's SATA I, so yes it's slow. I think it'll be fast enough for my media streaming and I do have a cache drive to help with write performance. Thanks again for all the info guys. I really appreciate that the unRAID community is so responsive and helpful. I definitely have a lot to learn. Quote Link to comment
BobPhoenix Posted February 28, 2013 Share Posted February 28, 2013 The number 65535 is not 65 thousand something, it's the unsigned integer representation of the 2 byte signed integer value of -1, so I wouldn't put too much significance in it. A return of -1 is usually a flag value, indicating a possible error or the current unavailability of the true number or something else but not a valid return value. If possible and I saw a value of 65535, I would grab a few more SMART reports, to see if it would change to a valid value. If not, I'd reboot and check again. If still not, then I would have to assume a bug in the SMART functions of the drive's firmware.FYI. The drive I posted about has been in a box to RMA back to WD several times and now several months (just haven't had the opportunity to start the process yet). I got it out last night and put it back in my preclear station to get the smart report - like I've done several times before. The 65535 is a permanent reading until I initiate another preclear cycle. It also isn't always a 65535, 0, 65535. The first set of 3 preclear cycles I ran was 65535 cycle 1, 128? cycle 2 and 0 cycle 3 - so I thought it was a good drive. The last time I ran a cycle of 3 (there may have been other cycles in-between) it was 65535, 0, 65535. So I haven't run one since so that it is in that state when I send it back to WD. So far every time I put it back into my preclear station(s) (I have two cpus that I clear drives on) it comes back with the same smart report I posted above. Quote Link to comment
RobJ Posted February 28, 2013 Share Posted February 28, 2013 FYI. The drive I posted about has been in a box to RMA back to WD several times and now several months (just haven't had the opportunity to start the process yet). I got it out last night and put it back in my preclear station to get the smart report - like I've done several times before. The 65535 is a permanent reading until I initiate another preclear cycle. It also isn't always a 65535, 0, 65535. The first set of 3 preclear cycles I ran was 65535 cycle 1, 128? cycle 2 and 0 cycle 3 - so I thought it was a good drive. The last time I ran a cycle of 3 (there may have been other cycles in-between) it was 65535, 0, 65535. So I haven't run one since so that it is in that state when I send it back to WD. So far every time I put it back into my preclear station(s) (I have two cpus that I clear drives on) it comes back with the same smart report I posted above. I agree with Joe, that combo of drive model and firmware is not confidence inspiring. Any chance of a firmware update for it? Quote Link to comment
BobPhoenix Posted February 28, 2013 Share Posted February 28, 2013 FYI. The drive I posted about has been in a box to RMA back to WD several times and now several months (just haven't had the opportunity to start the process yet). I got it out last night and put it back in my preclear station to get the smart report - like I've done several times before. The 65535 is a permanent reading until I initiate another preclear cycle. It also isn't always a 65535, 0, 65535. The first set of 3 preclear cycles I ran was 65535 cycle 1, 128? cycle 2 and 0 cycle 3 - so I thought it was a good drive. The last time I ran a cycle of 3 (there may have been other cycles in-between) it was 65535, 0, 65535. So I haven't run one since so that it is in that state when I send it back to WD. So far every time I put it back into my preclear station(s) (I have two cpus that I clear drives on) it comes back with the same smart report I posted above. I agree with Joe, that combo of drive model and firmware is not confidence inspiring. Any chance of a firmware update for it? Probably - I've got some 2TB greens with 81.xxx I believe. At this point unless it is out of waranty I'm not going to mess with a firmware update - just RMA the drive. I have 2 other 3TB models - they may all be the same model - will have to check when I get home. Only one of the 3 is working correctly. The other problem drive is slow and has some of the same smart errors as this one just not the pending. At one point I really liked the green drives - have 30 currently. But have 12 with smart errors I don't trust - multi zone, read errors etc... another 12 were perfectly fine until I fried them with a case fan that died and they got to ~60c on a parity check. Of the 6 2 TB drives left in working condition at least one is slow now - 30 MB/s parity checks when in array. I finally got the drives replaced with Hitachi/WD Reds in 2TB and 3TB sizes in my 2 unRAID servers. I could RMA most of these but I no longer have a good idea of which ones were over heated and which ones weren't. I don't think they should pay for my mistake anyway and I can use them for offline backups until they are dead. Quote Link to comment
Automatic Posted March 1, 2013 Share Posted March 1, 2013 Sorry for asking this again (And I'll probably be asking a few more times) but I like to have a second opinion from someone who knows this stuff more than me. Here's the preclear start SMART report:- Disk: /dev/sdf smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD1002FAEX-00Z3A0 Serial Number: WD-WCATR4008155 Firmware Version: 05.01D05 User Capacity: 1,000,204,886,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: Wed Feb 27 17:38:37 2013 GMT 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: (0x02) Offline data collection activity was completed without error. 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: (17160) 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: ( 199) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) 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 172 171 021 Pre-fail Always - 4358 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2121 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 076 076 000 Old_age Always - 18200 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 447 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 284 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1836 194 Temperature_Celsius 0x0022 123 097 000 Old_age Always - 24 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 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 2 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Conveyance offline Completed without error 00% 17722 - 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. Here's the preclear finish SMART report:- Disk: /dev/sdf smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD1002FAEX-00Z3A0 Serial Number: WD-WCATR4008155 Firmware Version: 05.01D05 User Capacity: 1,000,204,886,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: Thu Feb 28 23:59:52 2013 GMT 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: (0x02) Offline data collection activity was completed without error. 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: (17160) 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: ( 199) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) 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 172 171 021 Pre-fail Always - 4358 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2121 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 076 076 000 Old_age Always - 18225 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 447 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 284 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1836 194 Temperature_Celsius 0x0022 122 097 000 Old_age Always - 25 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 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 2 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Conveyance offline Completed without error 00% 17722 - 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. Here's the preclear report:- ========================================================================1.13 == invoked as: ./preclear_disk.sh -c 3 -A /dev/sdf == WDC WD1002FAEX-00Z3A0 WD-WCATR4008155 == Disk /dev/sdf has been successfully precleared == with a starting sector of 64 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 3:08:13 (88 MB/s) == Last Cycle's Zeroing time : 2:48:33 (98 MB/s) == Last Cycle's Post Read Time : 6:14:23 (44 MB/s) == Last Cycle's Total Time : 9:03:55 == == Total Elapsed Time 30:21:15 == == Disk Start Temperature: 24C == == Current Disk Temperature: 25C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 122 123 0 ok 25 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ Other than the read speed, it seems okay to me, but, like I said, I'd rather have a second opinion on this. Quote Link to comment
Joe L. Posted March 1, 2013 Share Posted March 1, 2013 Sorry for asking this again (And I'll probably be asking a few more times) but I like to have a second opinion from someone who knows this stuff more than me. <snip> Other than the read speed, it seems okay to me, but, like I said, I'd rather have a second opinion on this. Looks like a perfectly fine drive to me. Only issue, probably in its prior life, are the power off retracts 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 284 These were where power was turned off when the disk heads were still loaded. (apparently you just hit the power switch) however, the normalized value of 200 has not budged, and nowhere near the failure threshold of 0, so no need to worry. Quote Link to comment
peter_sm Posted March 1, 2013 Share Posted March 1, 2013 Just pree cleared my new 2TB disk, any concern ? ======================================================================== 1.14 = unRAID server Pre-Clear disk /dev/sdo = cycle 1 of 1, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 23C, Elapsed Time: 26:13:28 ======================================================================== == WDC WD20EARX-00MMMB0 WD-WCAWZ2744524 == Disk /dev/sdo has been successfully precleared == with a starting sector of 64 ======================================================================== ** Changed attributes in files: /tmp/smart_start_sdo /tmp/smart_finish_sdo ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 129 130 0 ok 23 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. SMART status Info for /dev/sdo smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARX-00MMMB0 Serial Number: WD-WCAWZ2744524 Firmware Version: 80.00A80 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: Fri Mar 1 06:03:28 2013 CET 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: ( 248) Self-test routine in progress... 80% of test remaining. Total time to complete Offline data collection: (39600) 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 161 161 021 Pre-fail Always - 8950 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 7 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 33 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 - 7 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 6 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 13 194 Temperature_Celsius 0x0022 130 120 000 Old_age Always - 22 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 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. //Peter Quote Link to comment
Automatic Posted March 1, 2013 Share Posted March 1, 2013 Sorry for asking this again (And I'll probably be asking a few more times) but I like to have a second opinion from someone who knows this stuff more than me. <snip> Other than the read speed, it seems okay to me, but, like I said, I'd rather have a second opinion on this. Looks like a perfectly fine drive to me. Only issue, probably in its prior life, are the power off retracts 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 284 These were where power was turned off when the disk heads were still loaded. (apparently you just hit the power switch) however, the normalized value of 200 has not budged, and nowhere near the failure threshold of 0, so no need to worry. Would this value increase if I had something along the lines of a BSOD? There was a phase where I literally had BSODs every minute, and, I wouldn't be surprised if I racked up at-least 200 in the time it took me to fix it (Which was just saying "Fuck it" and reinstalling windows). Quote Link to comment
Automatic Posted March 1, 2013 Share Posted March 1, 2013 Also, this is another drive that finished preclearing overnight. It seems to have a different read value that what it thought it wrote and failed the preclear. Is there anything I can do to attempt to fix it? It's out of warranty so no RMA. Start:- Disk: /dev/sdh smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: SAMSUNG SpinPoint F1 DT series Device Model: SAMSUNG HD103UJ Serial Number: S13PJ90QC12628 Firmware Version: 1AA01113 User Capacity: 1,000,204,886,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Wed Feb 27 17:39:09 2013 GMT 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: (11579) 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: ( 194) minutes. Conveyance self-test routine recommended polling time: ( 21) minutes. SCT capabilities: (0x003f) 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 0x000f 100 100 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 076 076 011 Pre-fail Always - 7960 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2339 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 9906 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 22716 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 4 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 747 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 0 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 083 059 000 Old_age Always - 17 (Min/Max 16/17) 194 Temperature_Celsius 0x0022 083 058 000 Old_age Always - 17 (Min/Max 16/18) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 1277 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 099 000 Old_age Always - 1 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 22316 - 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. End:- Disk: /dev/sdh smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: SAMSUNG SpinPoint F1 DT series Device Model: SAMSUNG HD103UJ Serial Number: S13PJ90QC12628 Firmware Version: 1AA01113 User Capacity: 1,000,204,886,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Fri Mar 1 02:07:45 2013 GMT 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: (11579) 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: ( 194) minutes. Conveyance self-test routine recommended polling time: ( 21) minutes. SCT capabilities: (0x003f) 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 0x000f 100 100 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 076 076 011 Pre-fail Always - 7960 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2339 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 9906 9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 22749 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 4 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 747 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 0 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 082 059 000 Old_age Always - 18 (Min/Max 16/19) 194 Temperature_Celsius 0x0022 082 058 000 Old_age Always - 18 (Min/Max 15/20) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 332403667 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 099 000 Old_age Always - 1 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 22316 - 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. Report:- ========================================================================1.13 == invoked as: ./preclear_disk.sh -c 3 -A /dev/sdh == == Disk /dev/sdh has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 3:10:16 (87 MB/s) == Last Cycle's Zeroing time : 3:12:26 (86 MB/s) == Last Cycle's Post Read Time : 6:32:29 (42 MB/s) == Last Cycle's Total Time : 9:45:54 == == Total Elapsed Time 32:28:36 == == Disk Start Temperature: 17C == == Current Disk Temperature: 18C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Power_On_Hours = 95 96 0 ok 22749 Airflow_Temperature_Cel = 82 83 0 ok 18 Temperature_Celsius = 82 83 0 ok 18 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ Quote Link to comment
Joe L. Posted March 1, 2013 Share Posted March 1, 2013 Just pree cleared my new 2TB disk, any concern ? ======================================================================== 1.14 Version 1.14 of the preclear script does not exist here, and I wrote the preclear script. I only go up to 1.13. Sorry. you'll have to go to its author for analysis. Joe L. Quote Link to comment
Joe L. Posted March 1, 2013 Share Posted March 1, 2013 Sorry for asking this again (And I'll probably be asking a few more times) but I like to have a second opinion from someone who knows this stuff more than me. <snip> Other than the read speed, it seems okay to me, but, like I said, I'd rather have a second opinion on this. Looks like a perfectly fine drive to me. Only issue, probably in its prior life, are the power off retracts 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 284 These were where power was turned off when the disk heads were still loaded. (apparently you just hit the power switch) however, the normalized value of 200 has not budged, and nowhere near the failure threshold of 0, so no need to worry. Would this value increase if I had something along the lines of a BSOD? There was a phase where I literally had BSODs every minute, and, I wouldn't be surprised if I racked up at-least 200 in the time it took me to fix it (Which was just saying "Fuck it" and reinstalling windows). Yup, that would do it. Joe L. Quote Link to comment
Joe L. Posted March 1, 2013 Share Posted March 1, 2013 Also, this is another drive that finished preclearing overnight. It seems to have a different read value that what it thought it wrote and failed the preclear. Is there anything I can do to attempt to fix it? It's out of warranty so no RMA. I'd say use it in a "Windows" computer, where an occasional crash or data corruption would never be noticed. Unless it is power supply related, there is little else you can do. Joe L. Quote Link to comment
CHBMB Posted March 3, 2013 Share Posted March 3, 2013 Would someone be so kind to cast an eye over this, it's an old drive I used in a WHS build. Preclear Start: Disk: /dev/sdi smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: SAMSUNG HD203WI Serial Number: S1UYJ1WZ400099 Firmware Version: 1AN10002 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 6 Local Time is: Fri Mar 1 19:12:45 2013 GMT 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: (26220) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. SCT capabilities: (0x003f) 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 0x002f 100 100 051 Pre-fail Always - 808 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 072 060 025 Pre-fail Always - 8708 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1149 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 4743 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 373 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 5947 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 052 000 Old_age Always - 35 (Min/Max 16/48) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 199 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 4866 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] Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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. Preclear Finish: Disk: /dev/sdi smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: SAMSUNG HD203WI Serial Number: S1UYJ1WZ400099 Firmware Version: 1AN10002 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 6 Local Time is: Sun Mar 3 04:10:20 2013 GMT 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: (26220) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. SCT capabilities: (0x003f) 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 0x002f 100 100 051 Pre-fail Always - 880 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 072 060 025 Pre-fail Always - 8708 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1149 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 4776 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 373 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 5949 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 059 052 000 Old_age Always - 41 (Min/Max 16/48) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 200 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 4866 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] Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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. Preclear Report: ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sdi == SAMSUNG HD203WI S1UYJ1WZ400099 == Disk /dev/sdi has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 9:18:09 (59 MB/s) == Last Cycle's Zeroing time : 6:53:27 (80 MB/s) == Last Cycle's Post Read Time : 16:44:51 (33 MB/s) == Last Cycle's Total Time : 32:57:36 == == Total Elapsed Time 32:57:36 == == Disk Start Temperature: 35C == == Current Disk Temperature: -->42<--C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 59 64 0 ok 41 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ Thanks very much guys, especially Joe for all his hard work! Quote Link to comment
Joe L. Posted March 3, 2013 Share Posted March 3, 2013 Would someone be so kind to cast an eye over this, it's an old drive I used in a WHS build. Looks fine other than this 194 Temperature_Celsius 0x0002 059 052 000 Old_age Always - 41 (Min/Max 16/48) It appears as if the disk has gotten as high as 48C degrees. That is a but higher than I like to see. (I prefer to stay under 40C) Make sure the disk has enough cooling. The preclear shows it got up to 42C in it. so it is not just in its old life where more cooling is needed. Thanks very much guys, especially Joe for all his hard work! You are welcome. Quote Link to comment
CHBMB Posted March 3, 2013 Share Posted March 3, 2013 Bloody hell that was quick! I think I'll ramp up the noctua fans I've got in the case. That should cool it down a bit. Thanks Joe. Quote Link to comment
mobias1313 Posted March 3, 2013 Share Posted March 3, 2013 I just picked up some new drives the other day and was going through the preclear but seem to have hit a snag. The first disk precleared with no problems at all. The second however seems to fail for some reason at either 36% or 37% on the disk pre-read everytime I try to run it. It will just seem to stop reading and the script will no longer update. Any thoughts are greatly appreciated. smart_start_sdb.txt Quote Link to comment
RobJ Posted March 3, 2013 Share Posted March 3, 2013 I just picked up some new drives the other day and was going through the preclear but seem to have hit a snag. The first disk precleared with no problems at all. The second however seems to fail for some reason at either 36% or 37% on the disk pre-read everytime I try to run it. It will just seem to stop reading and the script will no longer update. Any thoughts are greatly appreciated. It's probably getting bogged down, waiting for the drive to deal with all of the bad sectors. Current count of reallocated sectors is 3168, and there are 4904 bad sectors still to be dealt with, and as you said, it's only gotten through about a third of the drive. Not good. 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.