GSmartControl test report

[sorcerer]

I seem to have a real mental block when it comes to interpreting the output of GSmartControl tests. I'm trying, I really am (or at least that's what my wife tells me ), but I still can't understand what it's telling me.

This drive is BSODing at boot time with UNMOUNTABLE_BOOT_VOLUME and I usually have success with this after running chkdsk /r but this time chkdsk won't run due to an I/O error. The drive passed WD's own Data Lifeguard diagnostics but I'd like your opinions on the results of the GSmartControl tests please.

smartctl 5.41 2011-06-09 r3365 [i686-linux-3.0.0-pmagic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Scorpio Blue Serial ATA
Device Model: WDC WD3200BEVT-22A23T0
Serial Number: WD-WXH1A50A5884
LU WWN Device Id: 5 0014ee 259f1d8da
Firmware Version: 01.01A01
User Capacity: 320,072,933,376 bytes [320 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Oct 8 12:05:23 2012 UTC
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: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 8400) 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: ( 100) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x7037) 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 197 197 051 Pre-fail Always - 10812
3 Spin_Up_Time 0x0027 155 131 021 Pre-fail Always - 1250
4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 3968
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 - 345
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 - 558
191 G-Sense_Error_Rate 0x0032 001 001 000 Old_age Always - 177
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 53
193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 33258
194 Temperature_Celsius 0x0022 115 097 000 Old_age Always - 28
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 17
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
Warning: ATA error count 10241 inconsistent with error log pointer 3

ATA Error Count: 10241 (device log contains only the most recent five errors)
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 10241 occurred at disk power-on lifetime: 344 hours (14 days + 8 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
-- -- -- -- -- -- --
40 51 01 33 18 03 e2 Error: UNC 1 sectors at LBA = 0x02031833 = 33757235

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 01 33 18 03 e2 00 00:01:30.582 READ DMA
ec 00 00 00 00 00 a0 00 00:01:30.580 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:01:30.580 SET FEATURES [Set transfer mode]

Error 10240 occurred at disk power-on lifetime: 344 hours (14 days + 8 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
-- -- -- -- -- -- --
40 51 01 33 18 03 e2 Error: UNC 1 sectors at LBA = 0x02031833 = 33757235

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 01 33 18 03 e2 00 00:01:28.173 READ DMA
ec 00 00 00 00 00 a0 00 00:01:28.171 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:01:28.171 SET FEATURES [Set transfer mode]

Error 10239 occurred at disk power-on lifetime: 344 hours (14 days + 8 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
-- -- -- -- -- -- --
40 51 01 33 18 03 e2 Error: UNC 1 sectors at LBA = 0x02031833 = 33757235

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 01 33 18 03 e2 00 00:01:25.775 READ DMA
ec 00 00 00 00 00 a0 00 00:01:25.773 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:01:25.773 SET FEATURES [Set transfer mode]

Error 10238 occurred at disk power-on lifetime: 344 hours (14 days + 8 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
-- -- -- -- -- -- --
40 51 01 33 18 03 e2 Error: UNC 1 sectors at LBA = 0x02031833 = 33757235

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 01 33 18 03 e2 00 00:01:23.320 READ DMA
ec 00 00 00 00 00 a0 00 00:01:23.319 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:01:23.319 SET FEATURES [Set transfer mode]

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 90% 345 33757235
# 2 Conveyance offline Completed without error 00% 342 -

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 very much.

 

[SilverLeaf]

The extended test failed with a read failure. Time to replace the drive.

 

[ZenTree]

# 1 Extended offline Completed: read failure 90% 345 33757235

Along with the previous records of the drive having issues in the logs and the symptoms you have mentioned I would backup data and look at replacing the drive.

These logs give you a ton of information, but basically search for anything saying fail or failure There is more info than that but good place to start

 

[sorcerer]

Thanks very much guys, I really appreciate your help

John

 

[PCX]

You really need to test the hard drive before you destroy it with CHKDSK /R.

As for the diagnostic results. Look for bad sector count and the short and extended test results. If it passes the short test, then do the extended test. If it fails the short test, then your done. Read errors are probably the most common failures you will see.

 

[FremontPC]

Yeah, check the Current Pending Sector count. Not good news. It may be that somebody bounced this laptop around a bit too much.