| | <SNIP> Chkdsk stops at 60 % with "unspecified error" during
| file data verification. <SNIP>
I was unable to find any documentation in the Microsoft Knowledge
Base Article using your keywords. However, I did find the
following in the "Windows 2000 Chkdsk Management" document.
"Verifying file data. In this stage, Chkdsk
tries to read all the user data. If a read on a cluster fails,
Chkdsk allocates a fresh cluster in place of the
bad cluster and adds the bad cluster to the list of bad
clusters."
Microsoft Product Support Services White Paper
Microsoft Windows 2000 Server
Windows 2000 Chkdsk Management
http://www.microsoft.com/Windows2000/techinfo/administration/fileandprint/chkdsk.asp
Now given the above, and the fact that I have had 3 hard drives
fail in as many months, I read your problem this way:
Not only is a "read on a cluster" failing, chkdsk is unable to
"allocate a fresh cluster in place of the bad cluster".
bad cluster = failing hard drive
And if I were experiencing the same problem with a computer that
contained data that I wanted to preserve I would immediately
perform an backup, then replace the hard drive ASAP.
Also, you may want to post in the following newsgroup since they
discuss hard drives with great frequency:
microsoft.public.windowsxp.hardware
If you read the newsgroups via Microsoft Communities Web Page:
http://communities2.microsoft.com/c...t.aspx?dg=microsoft.public.windowsxp.hardware
If you read newsgroups using a NNTP newsreader, such as Outlook
Express, and use the msnews.microsoft.com news server:
news://msnews.microsoft.com/microsoft.public.windowsxp.hardware
And if you post to that newsgroup I suggest that you include
information such as:
- Any relevant information found in your Event Viewer
(eventvwr.msc) logs. For example, look in your System Event Log
for Event Source: dmio. And look through any unrecognizable
Error (Red X) events.
- Details about your hard drive such as manufacturer, whether or
not it has suffered any physical abuse and/or runs in a harsh
environment
- Whether or not you have run any diagnostics tests using
software from your disk manufacturer. And if the answer is yes
include the relevant details.
