September 1, 201312 yr This drive has been in the array for years, and it's never given any trouble, despite the current pending sector count being wrong. Has anyone else seen something similar? smartctl -a -d ata /dev/sdi smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD15EARS-00MVWB0 Serial Number: WD-WMAZ20152581 Firmware Version: 50.0AB50 User Capacity: 1,500,301,910,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: Sun Sep 1 12:09:48 2013 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: 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: (40200) 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 184 164 021 Pre-fail Always - 5775 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1568 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 065 065 000 Old_age Always - 26192 10 Spin_Retry_Count 0x0032 100 100 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 - 57 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 18 193 Load_Cycle_Count 0x0032 195 195 000 Old_age Always - 17374 194 Temperature_Celsius 0x0022 126 110 000 Old_age Always - 24 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 001 001 000 Old_age Always - 65535 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 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 Short offline Completed without error 00% 35 - 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.
September 1, 201312 yr Author ... despite the current pending sector count being wrong. Why would you say that? Looks like it's approaching the failing treshold. The raw value of 65535 has been like that since the drive was brand new, and has never changed. My other WD drives show the actual number of pending sectors in the raw field, so I (ass)umed this drive should be the same. I was wondering if anyone else has seen this special number as the raw value in the pending sector field.
September 1, 201312 yr Author I was wondering if anyone else has seen this special number A "special number" with its own wiki? You are joking, right? If you are deep asleep, and somebody wakes you up and asks you, you should be able to answer that without even thinking: It's 2^16-1. It's just two bytes with all bits set to ones. If the manufecturer has set aside two bytes to hold the number of pending sectors, (16-bit unsigned integer), then 65535 is as high as that value would go. Exactly. Now you get the point of my asking the question. I am pretty certain that the drive does not have any pending sectors, and the smart report is not pointing to the right address, or something like that.
September 1, 201312 yr It was suggested to me when I posted that I have a drive that was reporting 0, 65535, 0, 65535, etc... on a Brand New 3TB that it was a firmware problem. So you might see if you can upgrade the firmware on the drive. I RMA'd my drive so I don't know if it would have been effective or not.
Archived
This topic is now archived and is closed to further replies.