PC Review


Reply
Thread Tools Rate Thread

W2K's event logs showed \\?\Volume{107944b6-439b-11d7-9e57-806d6172696f}?Failing HDD?

 
 
Ant
Guest
Posts: n/a
 
      9th May 2010
Hello.

I am fixing a client's old Dell Optiplex PC with updated Windows 2000
SP4. Its event logs showed a bunch of "The device,
\Device\Harddisk0\DR0, has a bad block." like:

Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 7
Date: 5/9/2010
Time: 12:20:29 PM
User: N/A
Computer: DELLOPTIPLEX
Description:
The device, \Device\Harddisk0\DR0, has a bad block.
Data:
0000: 03 00 18 00 01 00 72 00 ......r.
0008: 00 00 00 00 07 00 04 c0 .......
0010: 00 01 00 00 9c 00 00 c0 ......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 fc 84 01 00 00 00 00 .
.....
0028: 00 00 00 00 00 00 00 00 ........
0030: 00 00 00 00 28 00 00 00 ....(...
0038: 02 84 00 00 00 00 03 00 .
......
--

Ironically, this started after uninstalling NAV CE and rebooting! In
W2K's cmd.exe, I did a long chkdsk /r /f c:, rebooted, chkdsk'ed a long
time, and then back to Windows. However, I still got some errors as
shown in the event logs:

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 5/9/2010
Time: 12:22:26 PM
User: N/A
Computer: DELLOPTIPLEX
Description:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 18 unused index entries from index $SII of file 0x9.
Cleaning up 18 unused index entries from index $SDH of file 0x9.
Cleaning up 18 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Windows has made corrections to the file system.

40106272 KB total disk space.
27262777 KB in 55959 files.
17756 KB in 5063 indexes.
0 KB in bad sectors.
164511 KB in use by the system.
65536 KB occupied by the log file.
12661227 KB available on disk.

512 bytes in each allocation unit.
80212544 total allocation units on disk.
25322454 allocation units available on disk.

Windows has finished checking your disk.
Please wait while your computer restarts.

--

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
Date: 5/9/2010
Time: 12:22:26 PM
User: N/A
Computer: DELLOPTIPLEX
Description:
Checking file system on \\?\Volume{107944b6-439b-11d7-9e57-806d6172696f}
The type of the file system is FAT.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Volume Serial Number is 07D3-0207
Read failure with status 0xc000009c at offset 0x183f600 for 0xd800 bytes.
Read failure with status 0xc000009c at offset 0x1847e00 for 0x800 bytes.
Windows replaced bad clusters in file \RAID.MDM
of name (null).
Windows is verifying free space...
Free space verification is complete.
Windows has made corrections to the file system.

32786432 bytes total disk space.
217088 bytes in 3 hidden files.
2048 bytes in 1 folders.
4878336 bytes in 68 files.
2048 bytes in bad sectors.
27686912 bytes available on disk.

2048 bytes in each allocation unit.
16009 total allocation units on disk.
13519 allocation units available on disk.


What's up? Bad sectors looked scary. I wonder if the drive is failing so
I ran the latest smartctl's long test and checked its results:

smartctl 5.39.1 2010-01-28 r3054 [i686-pc-mingw32-2000-sp4]
(sf-win32-5.39.1-1)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: Maxtor DiamondMax Plus 8 family
Device Model: Maxtor 6E040L0
Serial Number: E155KPHE
Firmware Version: NAR61590
User Capacity: 41,110,142,976 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Sun May 09 13:25:38 2010 PDT
SMART support is: Available - device has SMART capability.
Enabled status cached by OS, trying SMART RETURN
STATUS cmd.
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: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 116) The previous self-test completed
having
the read element of the test failed.
Total time to complete Offline
data collection: (1021) 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 17) 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
3 Spin_Up_Time 0x0027 227 221 063 Pre-fail
Always - 5826
4 Start_Stop_Count 0x0032 253 253 000 Old_age
Always - 1454
5 Reallocated_Sector_Ct 0x0033 252 252 063 Pre-fail
Always - 9
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail
Offline - 0
7 Seek_Error_Rate 0x000a 253 252 000 Old_age
Always - 0
8 Seek_Time_Performance 0x0027 246 239 187 Pre-fail
Always - 35175
9 Power_On_Minutes 0x0032 239 239 000 Old_age
Always - 655h+56m
10 Spin_Retry_Count 0x002b 253 252 157 Pre-fail
Always - 0
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0032 250 250 000 Old_age
Always - 1451
192 Power-Off_Retract_Count 0x0032 252 252 000 Old_age Always
- 1448
193 Load_Cycle_Count 0x0032 253 253 000 Old_age Always
- 3200
194 Temperature_Celsius 0x0032 253 253 000 Old_age Always
- 30
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age Always
- 10331
196 Reallocated_Event_Count 0x0008 251 251 000 Old_age
Offline - 2
197 Current_Pending_Sector 0x0008 253 253 000 Old_age
Offline - 2
198 Offline_Uncorrectable 0x0008 252 251 000 Old_age
Offline - 1
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age
Offline - 0
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age Always
- 0
201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age Always
- 19
202 Data_Address_Mark_Errs 0x000a 253 251 000 Old_age Always
- 0
203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail Always
- 63
204 Soft_ECC_Correction 0x000a 253 251 000 Old_age Always
- 0
205 Thermal_Asperity_Rate 0x000a 253 252 000 Old_age Always
- 0
207 Spin_High_Current 0x002a 253 252 000 Old_age Always
- 0
208 Spin_Buzz 0x002a 253 252 000 Old_age Always
- 0
209 Offline_Seek_Performnce 0x0024 188 187 000 Old_age
Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age
Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age
Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age
Offline - 0

SMART Error Log Version: 1
ATA Error Count: 70 (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 70 occurred at disk power-on lifetime: 4709 hours (196 days + 5 hours)
When the command that caused the error occurred, the device was in an
unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 7e c2 00 e0 Error: UNC 1 sectors at LBA = 0x0000c27e = 49790

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 04 7e c2 00 e0 00 17:55:39.616 READ DMA
c8 00 04 7a c2 00 e0 00 17:55:39.616 READ DMA
c8 00 04 76 c2 00 e0 00 17:55:39.616 READ DMA
c8 00 04 72 c2 00 e0 00 17:55:39.616 READ DMA
c8 00 04 6e c2 00 e0 00 17:55:39.616 READ DMA

Error 69 occurred at disk power-on lifetime: 4709 hours (196 days + 5 hours)
When the command that caused the error occurred, the device was in an
unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 25 3a c2 00 e0 Error: UNC 37 sectors at LBA = 0x0000c23a = 49722

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 6c 3a c2 00 e0 00 17:55:38.304 READ DMA
c8 00 2c 0e c2 00 e0 00 17:55:38.304 READ DMA
c8 00 1c f2 c1 00 e0 00 17:55:38.288 READ DMA
c8 00 1c d6 c1 00 e0 00 17:55:38.288 READ DMA
c8 00 4c 8a c1 00 e0 00 17:55:38.288 READ DMA

Error 68 occurred at disk power-on lifetime: 4708 hours (196 days + 4 hours)
When the command that caused the error occurred, the device was in an
unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 7a c2 00 e0 Error: UNC 1 sectors at LBA = 0x0000c27a = 49786

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 da 08 7a c2 00 e0 00 16:14:39.744 READ DMA
ca da 40 ec 46 65 e2 00 16:14:39.728 WRITE DMA
ca da 08 7a 7a 0f e2 00 16:14:39.728 WRITE DMA
c8 da 08 7a c2 00 e0 00 16:14:38.448 READ DMA
ca da 08 ce 67 a2 e1 00 16:14:38.432 WRITE DMA

Error 67 occurred at disk power-on lifetime: 4708 hours (196 days + 4 hours)
When the command that caused the error occurred, the device was in an
unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 7a c2 00 e0 Error: UNC 1 sectors at LBA = 0x0000c27a = 49786

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 da 08 7a c2 00 e0 00 16:14:38.448 READ DMA
ca da 08 ce 67 a2 e1 00 16:14:38.432 WRITE DMA
c8 da 08 7a c2 00 e0 00 16:14:37.152 READ DMA
ca da 08 7a 7a 0f e2 00 16:14:37.152 WRITE DMA
c8 da 08 7a c2 00 e0 00 16:14:35.872 READ DMA

Error 66 occurred at disk power-on lifetime: 4708 hours (196 days + 4 hours)
When the command that caused the error occurred, the device was in an
unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 01 7a c2 00 e0 Error: UNC 1 sectors at LBA = 0x0000c27a = 49786

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 da 08 7a c2 00 e0 00 16:14:37.152 READ DMA
ca da 08 7a 7a 0f e2 00 16:14:37.152 WRITE DMA
c8 da 08 7a c2 00 e0 00 16:14:35.872 READ DMA
ca da 01 7f 00 00 e0 00 16:14:35.840 WRITE DMA
ca da 01 40 00 00 e0 00 16:14:35.840 WRITE DMA

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 40% 4710
49793
# 2 Extended offline Completed: read failure 40% 3882
49793
# 3 Extended offline Interrupted (host reset) 70% 3881
-
# 4 Short offline Completed without error 00% 0
-

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.

Those errors look bad. I also realized that this chkdsk was on a FAT
(not NTFS) and tiny. So I checked Disk Management and saw a no-letter
drive before C: --
http://img243.imageshack.us/img243/4...management.jpg ... I can't
see what is in this tiny partition.

I did another chkdsk on C:. I saw no problems this time in the event
logs. Weird.

Is the drive failing from the SMART and symptoms? Thank you in advance.
--
"I like ants, in chocolate. Crunch, hummmm." --unknown
/\___/\ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) If e-mailing, then axe ANT from its address if needed.
 
Reply With Quote
 
 
 
 
Pegasus [MVP]
Guest
Posts: n/a
 
      9th May 2010


"Ant" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello.
>
> I am fixing a client's old Dell Optiplex PC with updated Windows 2000 SP4.
> Its event logs showed a bunch of "The device, \Device\Harddisk0\DR0, has a
> bad block." Ironically, this started after uninstalling NAV CE and
> rebooting! In W2K's cmd.exe, I did a long chkdsk /r /f c:, rebooted,
> chkdsk'ed a long time, and then back to Windows. However, I still got some
> errors.


Just because two events follow each other does not necessarily mean that the
first caused the second. I would download and run the diagnostic tool that
the hard disk manufacturer makes available on his home site.

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: W2K's event logs showed \\?\Volume{107944b6-439b-11d7-9e57-806d6172696f}? Failing HDD? Rod Speed Storage Devices 4 13th May 2010 08:20 PM
Re: W2K's event logs showed \\?\Volume{107944b6-439b-11d7-9e57-806d6172696f}? Failing HDD? Arno Storage Devices 0 10th May 2010 02:47 AM
W2K's event logs showed \\?\Volume{107944b6-439b-11d7-9e57-806d6172696f}?Failing HDD? Ant Microsoft Windows 2000 File System 1 9th May 2010 11:09 PM
W2K's event logs showed \\?\Volume{107944b6-439b-11d7-9e57-806d6172696f}?Failing HDD? Ant Microsoft Windows 2000 1 9th May 2010 11:09 PM
W2K's event logs showed \\?\Volume{107944b6-439b-11d7-9e57-806d6172696f}?Failing HDD? Ant Microsoft Windows 2000 Hardware 1 9th May 2010 11:09 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 11:14 AM.