• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About _Nemo_

  • Rank
  1. Thanks for the reply. Or it was only ever in the drive's fevered imagination... BTW, the drive is a T7K250, not a 7K250 as I originally said. It's zero. Here's the full smartctl output: smartctl 5.39 2009-08-26 r2878 [i686-pc-mingw32-xp-mc-sp2] (cf-win32-20090826) Copyright (C) 2002-9 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Hitachi Deskstar T7K250 series Device Model: HDT722525DLA380 Serial Number: VDS41BT4****** Firmware Version: V44OA96A User Capacity: 250,059,350,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 1 Local Time is: Thu Oct 22 12:51:12 2009 GMTDT 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: (4797) 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: ( 80) minutes. 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 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 229 229 024 Pre-fail Always - 155 (Average 150) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 745 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 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 096 096 000 Old_age Always - 29501 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 450 192 Power-Off_Retract_Count 0x0032 099 099 050 Old_age Always - 1973 193 Load_Cycle_Count 0x0012 099 099 050 Old_age Always - 1973 194 Temperature_Celsius 0x0002 161 161 000 Old_age Always - 34 (Lifetime Min/Max 17/53) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 29354 hours (1223 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 00 51 01 10 00 00 00 Error: Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 2f 00 01 10 00 00 00 00 03:59:49.300 READ LOG EXT 60 00 00 00 59 1c 40 00 03:59:45.900 READ FPDMA QUEUED 60 00 00 00 58 1c 40 00 03:59:45.800 READ FPDMA QUEUED c6 00 10 00 00 00 00 00 03:59:45.300 SET MULTIPLE MODE ef 10 02 00 00 00 00 00 03:59:45.300 SET FEATURES [Reserved for Serial ATA] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 29498 - # 2 Short offline Completed without error 00% 29415 - # 3 Short offline Completed without error 00% 29350 - Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum. 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. Part of Jetico's BestCrypt package. BCWipe is a utility for wiping free space. It's been around for well over 10 years, and seems to work pretty well. It writes a file that occupies the whole of the free space on the drive, then deletes it (+ other options). That, combined with an XP format, should rewrite all of the partition (maybe parts of the MFT might escape?) - though not the full drive, it is >99.9%. No errors were shown during this. Well, I know that some people don't like the claims that are made for it, but I don't really want to get into a discussion about that. If you take it for what it is - a utility for sequentially reading and writing blocks - it has its uses. In this case, it's advantage is that it's non-destructive. I've 7 drives on this system (1 PATA and 6 SATA) and it's just too easy to wipe the wrong drive when zero-wiping from DOS, especially when drives are being moved around and some utilities don't see all drives. As I said, Spinrite read and re-wrote every sector, without any errors. It's beginning to look like Hitachi's DFT is going to be the only way forward, but it's a pain, because I'll have to move the suspect drive from the motherboard's built-in SiI3132 (not recognised by DFT) to the (also built-in) Intel ICHR7. And moving a drive means that there's a non-zero possibility of a "drive numbering error", which would be too unpleasant to deal with, so I'll have to disconnect/power off all the other drives, too. As you say, it's probably not a real problem, though my money's on an internal corruption in the SMART system, caused by the power outage (unfortunately, the drive was in an wall-wart-powered external eSATA bay at the time, and didn't have the protection of the large PSU that allowed the rest of the PC to survive it). _Nemo_
  2. _Nemo_

    WTB: WD2500BB-00gua0

    And sometimes they stab you in the back when you're not paying attention! :-( Curse your fuzzy matching, Google! The ones I quoted are HSBHCTJAA not HSBHCTJAH. Regards, _Nemo_
  3. _Nemo_

    WTB: WD2500BB-00gua0

    And sometimes they stab you in the back when you're not paying attention! :-( Curse your fuzzy matching, Google! The ones I quoted are HSBHCTJAA not HSBHCTJAH. However, there are 4 other sellers with HSBHCTJAH (all in the US, and some rather overpriced): http://shop.ebay.co.uk/?_from=R40&_trk...;_nkw=HSBHCTJAH Regards, _Nemo_
  4. _Nemo_

    WTB: WD2500BB-00gua0

    Google and/or eBay are (occasionally) your friends... http://cgi.ebay.co.uk/ws/eBayISAPI.dll?Vie...%3D1&_rdc=1 Seller (in Germany - I note you're in Denmark, so it's just around the corner :-) has 12 for sale: Western Digital WD2500BB 250 GB 8.9 cm IDE LBA 488397168 DCM HSBHCTJAA Cache 2 MB P/N WD2500BB-00GUA0 No dates specified, but I guess you could ask. Price seems a little high, but they are claimed to be new rather than pulls. _Nemo_
  5. I have a drive (Hitachi Deskstar 7K250) that is currently showing a current pending sector count of 1. This appeared during a brief mains power glitch (the PC didn't crash, and I happened to have a SMART monitoring app on the desktop at the time) so the disk may or may not have actual damage. The drive had no valuable data on it at the time, and was just about to be used to back up data. In order to identify the problematic sector (if any) and to clear the current pending sector count, I formatted (XP) the drive, then wiped the free space with BCWipe (safer than BCWipePD: I don't like to specify target drive by drive number - too prone to nasty mistakes). Unfortunately, the current pending sector count stayed at 1, so I did a complete surface refresh with Spinrite. Current pending sector count is still 1, however. My understanding is that current pending sector count should have been returned to zero as soon as the relevant sector was either successfully written to or reallocated. Since I've written successfully to every sector, how can current pending sector count remain at 1? Does this mean there's still a questionable sector on the drive, or is the current value for current pending sector count some sort of glitch? Thanks _Nemo_