Sign in with
Sign up | Sign in
Your question

Hard Disk problem with chkdsk

Tags:
  • Chkdsk
  • Hard Drives
  • Windows XP
Last response: in Windows XP
Share
April 16, 2005 10:39:45 AM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Hello, Im having some problems with my hard disk.
When I ran chkdsk inside windows, it found some errors:

C:\Documents and Settings\Daniel>chkdsk c:
The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Deleting index entry Professional_32_1033.dat in index $I30 of file
6640.
Deleting index entry Professional_32_1033.dat.bak in index $I30 of file
6640.
Deleting index entry PROFES~1.BAK in index $I30 of file 6640.
Deleting index entry PROFES~1.DAT in index $I30 of file 6640.
Deleting index entry tmp.edb in index $I30 of file 6641.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

I ran it again with swith /r and it ran after restarting. Im kind of
sure id didnt find errors, but I still havent found a log in my pc
about it running, but if what I saw on the screen it ran fine.

Inside the event viewer I have a repeated set of mistakes:
The first one is repeated 5 times.
Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 11
Date: 4/15/2005
Time: 8:48:41 PM
User: N/A
Computer: DANIK
Description:
The driver detected a controller error on \Device\Harddisk0\D.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 03 00 68 00 01 00 b6 00 ..h...¶.
0008: 00 00 00 00 0b 00 04 c0 .......À
0010: 01 01 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 1e c5 4b 0f 00 00 00 ..ÅK....
0028: 09 75 00 00 00 00 00 00 .u......
0030: ff ff ff ff 03 00 00 00 ÿÿÿÿ....
0038: 40 00 00 8f 02 00 00 00 @......
0040: 00 20 0a 12 40 03 20 40 . ..@. @
0048: 00 00 00 00 0a 00 00 00 ........
0050: 00 00 00 00 a8 bf f9 85 ....¨¿ù…
0058: 00 00 00 00 60 c3 06 86 ....`Ã.†
0060: 02 00 00 00 8f e2 a5 07 ....â¥.
0068: 28 00 07 a5 e2 8f 00 00 (..¥â..
0070: 80 00 00 00 00 00 00 00 €.......
0078: f0 00 04 00 00 00 00 0b ð.......
0080: 00 00 00 00 08 03 00 00 ........
0088: 00 00 00 00 00 00 00 00 ........

Then comes this one once:
Event Type: Error
Event Source: atapi
Event Category: None
Event ID: 5
Date: 4/15/2005
Time: 8:49:08 PM
User: N/A
Computer: DANIK
Description:
A parity error was detected on \Device\Ide\IdePort0.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0f 00 50 00 01 00 a4 00 ..P...¤.
0008: 00 00 00 00 05 00 04 c0 .......À
0010: 03 00 00 80 00 00 00 00 ...€....
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 06 00 00 00 00 00 00 00 ........
0030: 00 00 00 00 07 00 00 00 ........
0038: 40 00 00 8f 02 00 00 00 @......
0040: 00 20 0a 12 40 03 20 40 . ..@. @
0048: 00 00 00 00 0a 00 00 00 ........
0050: 00 00 00 00 a8 bf f9 85 ....¨¿ù…
0058: 00 00 00 00 60 c3 06 86 ....`Ã.†
0060: 02 00 00 00 97 eb 97 07 ....—ë—.
0068: 28 00 07 97 eb 97 00 00 (..—ë—..
0070: 80 00 00 00 00 00 00 00 €.......

And then the first one agagin twice.
This patters repeats itself all around the System Log.
What could be the problem. If I check the disk inside windows it finds
errors, if I check it after restarting before going in, its ok.

Thanks for your help,
/Dan States

More about : hard disk problem chkdsk

Anonymous
April 16, 2005 1:48:33 PM

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Don't bother even running CHKDSK in read-only mode. More info follows.

1. In My Computer or Windows Explorer, right-click the volume you want to
check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Do one of the following:

o To run Chkdsk by using the /f parameter, select the Automatically fix file
system errors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking. All files must be closed for this program to run. If the drive is
currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your drive is
not available to run other tasks while the disk is being checked.]]

o To run Chkdsk by using the /r parameter, select the Scan for and attempt
recovery of bad sectors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking, locates bad sectors, and recovers readable information. All files
must be closed for this program to run. If the drive is currently in use, a
message asks if you want to reschedule the disk checking for the next time
you restart your computer. Your drive is not available to run other tasks
while the disk is being checked. If you select this option, you do not need
to select Automatically fix file system errors. Windows fixes any errors on
the disk.]]
-----

[[Chkdsk might not accurately report information in read-only mode.]]

Chkdsk
http://www.microsoft.com/resources/documentation/Window...

[[If you run chkdsk without the /f command-line option on an active
partition, it might report spurious errors because it cannot lock the
drive.]]

[[Using chkdsk with open files
If you specify the /f command-line option, chkdsk sends an error message if
there are open files on the disk. If you do not specify the /f command-line
option and open files exist, chkdsk might report lost allocation units on
the disk. This could happen if open files have not yet been recorded in the
file allocation table. If chkdsk reports the loss of a large number of
allocation units, consider repairing the disk.]]

Chkdsk
http://www.microsoft.com/resources/documentation/window...

[[In read-only mode, CHKDSK quits before it completes all three phases if it
encounters errors in earlier phases, and CHKDSK is prone to falsely
reporting errors. For example, CHKDSK may report disk corruption if NTFS
happens to modify areas of a disk while CHKDSK is examining the disk. For
correct verification, a volume must be static, and the only way to guarantee
a static state is to lock the volume. CHKDSK locks the volume only if you
specify the /F switch (or the /R switch, which implies /F). You may need to
run CHKDSK more than once to get CHKDSK to complete all its passes
in read-only mode. ]]

An Explanation of the New C and I Switches That Are Available to Use with
Chkdsk.exe
http://support.microsoft.com/default.aspx?scid=kb;en-us;314835

To take advantage of all the Chkdsk parameters, use the command-line version
of Chkdsk.

Describes how to use the chkdsk command at the command line.
http://www.microsoft.com/windowsxp/home/using/productdo...

--------------------

Details
Product: Windows Operating System
ID: 11
Source: disk
[[Explanation
This problem is typically caused by a failing cable that connects the drive
to the computer.

User Action
Replace the cable.]]

http://www.microsoft.com/technet/support/ee/result.aspx...

Click the [+] Related Knowledge Base articles to expand the list
-----

Details
Product: Windows Operating System
ID: 5
Source: atapi

[[Explanation
There was a parity error during a direct memory access (DMA) transfer.
Typically, this means that the cable connecting the drive to the computer is
failing.

User Action
Replace the cable.]]
http://www.microsoft.com/technet/support/ee/result.aspx...

Click the [+] Related Knowledge Base articles to expand the list

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:1113658785.352948.283780@f14g2000cwb.googlegroups.com,
Dan <gamesstate@gmail.com> hunted and pecked:
> Hello, Im having some problems with my hard disk.
> When I ran chkdsk inside windows, it found some errors:
>
> C:\Documents and Settings\Daniel>chkdsk c:
> The type of the file system is NTFS.
>
> WARNING! F parameter not specified.
> Running CHKDSK in read-only mode.
>
> CHKDSK is verifying files (stage 1 of 3)...
> File verification completed.
> CHKDSK is verifying indexes (stage 2 of 3)...
> Deleting index entry Professional_32_1033.dat in index $I30 of file
> 6640.
> Deleting index entry Professional_32_1033.dat.bak in index $I30 of file
> 6640.
> Deleting index entry PROFES~1.BAK in index $I30 of file 6640.
> Deleting index entry PROFES~1.DAT in index $I30 of file 6640.
> Deleting index entry tmp.edb in index $I30 of file 6641.
> Index verification completed.
>
> Errors found. CHKDSK cannot continue in read-only mode.
>
> I ran it again with swith /r and it ran after restarting. Im kind of
> sure id didnt find errors, but I still havent found a log in my pc
> about it running, but if what I saw on the screen it ran fine.
>
> Inside the event viewer I have a repeated set of mistakes:
> The first one is repeated 5 times.
> Event Type: Error
> Event Source: Disk
> Event Category: None
> Event ID: 11
> Date: 4/15/2005
> Time: 8:48:41 PM
> User: N/A
> Computer: DANIK
> Description:
> The driver detected a controller error on \Device\Harddisk0\D.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 03 00 68 00 01 00 b6 00 ..h...¶.
> 0008: 00 00 00 00 0b 00 04 c0 .......À
> 0010: 01 01 00 00 00 00 00 00 ........
> 0018: 00 00 00 00 00 00 00 00 ........
> 0020: 00 1e c5 4b 0f 00 00 00 ..ÅK....
> 0028: 09 75 00 00 00 00 00 00 .u......
> 0030: ff ff ff ff 03 00 00 00 ÿÿÿÿ....
> 0038: 40 00 00 8f 02 00 00 00 @..?....
> 0040: 00 20 0a 12 40 03 20 40 . ..@. @
> 0048: 00 00 00 00 0a 00 00 00 ........
> 0050: 00 00 00 00 a8 bf f9 85 ....¨¿ù…
> 0058: 00 00 00 00 60 c3 06 86 ....`Ã.†
> 0060: 02 00 00 00 8f e2 a5 07 ....?â¥.
> 0068: 28 00 07 a5 e2 8f 00 00 (..¥â?..
> 0070: 80 00 00 00 00 00 00 00 €.......
> 0078: f0 00 04 00 00 00 00 0b ð.......
> 0080: 00 00 00 00 08 03 00 00 ........
> 0088: 00 00 00 00 00 00 00 00 ........
>
> Then comes this one once:
> Event Type: Error
> Event Source: atapi
> Event Category: None
> Event ID: 5
> Date: 4/15/2005
> Time: 8:49:08 PM
> User: N/A
> Computer: DANIK
> Description:
> A parity error was detected on \Device\Ide\IdePort0.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 0f 00 50 00 01 00 a4 00 ..P...¤.
> 0008: 00 00 00 00 05 00 04 c0 .......À
> 0010: 03 00 00 80 00 00 00 00 ...€....
> 0018: 00 00 00 00 00 00 00 00 ........
> 0020: 00 00 00 00 00 00 00 00 ........
> 0028: 06 00 00 00 00 00 00 00 ........
> 0030: 00 00 00 00 07 00 00 00 ........
> 0038: 40 00 00 8f 02 00 00 00 @..?....
> 0040: 00 20 0a 12 40 03 20 40 . ..@. @
> 0048: 00 00 00 00 0a 00 00 00 ........
> 0050: 00 00 00 00 a8 bf f9 85 ....¨¿ù…
> 0058: 00 00 00 00 60 c3 06 86 ....`Ã.†
> 0060: 02 00 00 00 97 eb 97 07 ....—ë—.
> 0068: 28 00 07 97 eb 97 00 00 (..—ë—..
> 0070: 80 00 00 00 00 00 00 00 €.......
>
> And then the first one agagin twice.
> This patters repeats itself all around the System Log.
> What could be the problem. If I check the disk inside windows it finds
> errors, if I check it after restarting before going in, its ok.
>
> Thanks for your help,
> /Dan States
!