CHKDSK Problems

[Mark]

When running CHKDSK on XP (Home) I get the following message.....

Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

I can't seem to set /F to fix the problem. Even if I start in safe mode (command prompt only) it tells me the volume was locked.

Any ideas?

Mark

 

[Guest]

Hi Mark,

Try running the CHKDSK /r command from the Recovery Console. Here is a
description of the Recovery Console, including how to boot into it:
http://support.microsoft.com/kb/314058/en-us

If XP came pre-installed on your system and came with a Recovery or Restore
CD or partition, you may need to create the set of six setup floppy disks and
boot from the floppies in order to run Recovery Console.
How to obtain Windows XP Setup boot disks
http://support.microsoft.com/kb/310994/en-us



Regards,

 

[Dave Patrick]

If you get an error something to the effect "cannot open volume for direct
access" There is some system/boot start device that is reading/writing to
the drive before chkdsk can get a lock on the drive. Some anti-virus
applications do this.

After backup you can run chkdsk from the RC.

chkdsk /r
from the recovery console command line. (/r implies /f and /p)

To start the Recovery Console, start the computer from the Windows XP
CD-Rom. At the "Welcome to Setup" screen. Press F10 or R to repair a Windows
XP installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
When running CHKDSK on XP (Home) I get the following message.....

Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

I can't seem to set /F to fix the problem. Even if I start in safe mode
(command prompt only) it tells me the volume was locked.

Any ideas?

Mark

 

[Guest]

Go to run,type:cmd In cmd type:CHKNTFS /c C: Type:CHKNTFS /? for all cmds

 

[Glen]

Are you by chance running Spyware Doctor? If so there is a known fault. You
need to search for and rename ikhlayer.sys. Thjis will disable kernal mode
protection but will allow disk utilities to run. After running rename the
file back again. Hopefully a patch will be released to fix the problem.
--
Please repost if you find the fault

Glen P
~~~~~~~~~~~~~~~~~~~~~
When running CHKDSK on XP (Home) I get the following message.....

Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

I can't seem to set /F to fix the problem. Even if I start in safe mode
(command prompt only) it tells me the volume was locked.

Any ideas?

Mark

 

[Wesley Vogel]

Cannot lock volume for direct access
or
Cannot open volume for direct access

Symantec AntiVirus Corporate Edition 9.0 can cause the problem.

Chkdsk.exe or ScanDisk fails to run on Windows XP or Windows 2003 after
installing Symantec AntiVirus Corporate Edition 9.0
http://service1.symantec.com/SUPPOR...6e22005026f1/52d79c84c363973488256ea600542b5a

A program called Hitman Pro can cause the problem.

A really old version of ZoneAlarm (a version from 2004) can cause the
problem.

BitDefender Internet Security 9 can cause the problem.

Spyware Doctor can also cause the problem.

The /x switch doesn't work if Spyware Doctor is installed. Spyware Doctor
needs to be uninstalled or you can do this...

Quoted from *PCTools*, *Spyware* *Doctor*...
1. Exit from Spyware Doctor (to exit from Spyware
Doctor please right click on the Spyware Doctor icon in
the notification area (next to the clock on the Windows
taskbar) and select Exit from the menu that appears)

2. Delete the file
ikhlayer.sys from %windir%\system32\drivers\
or
from c:\windows\system32\drivers\

3. Restart Spyware Doctor

Chkdsk, defrag and error-checking should now work.
-----

[[There is currently no fix for this problem.]]
[[NOTE: You may have success if you schedule Chkdsk to run at startup and
use the /X switch, which will force a dismount. ]]
from...
JSI Tip 7079. You receive 'Cannot open volume for direct access' when Chkdsk
runs during Windows XP startup
http://www.jsifaq.com/subO/tip7000/rh7079.htm

To run chkdsk from a command prompt.

Start | Run | Type: cmd | Click OK |
In the command prompt, type:

chkdsk C: /x

Hit your Enter key.

The following error message appears:
Chkdsk cannot run because the volume is in use by another process. Would you
like to schedule this volume to be checked the next time the system
restarts? (Y/N)

Type Y, hit Enter and close the command prompt.

Reboot.

The /x switch: Use with NTFS only. Forces the volume to dismount first, if
necessary. All open handles to the drive are invalidated. /x also includes
the functionality of /f. The /F switch fixes errors on the disk.

Unable to run CHKDSK
http://support.microsoft.com/kb/555484

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Greg Hayes/Raxco Software]

Mark,

This particular CHKDSK message is likely a transient error. Meaning that it
occurs because the file system is in use at the time that the readonly
chkdsk is performed. Assuming you are able to run chkdsk at boot with the
/f switch, it won't likely find/fix any errors. As far as your inability to
run chkdsk at boot, I'd suggest booting into the recovery console and
running it from there.

- Greg/Raxco Software
Microsoft MVP - Windows File System

Want to email me? Delete ntloader.

When running CHKDSK on XP (Home) I get the following message.....

Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

I can't seem to set /F to fix the problem. Even if I start in safe mode
(command prompt only) it tells me the volume was locked.

Any ideas?

Mark

 

[Guest]

Hi,

This tip was right on. I have been using Recovery Console for quite awhile
to run chkdsk /r. Renamed the ikhlayer.sys file, set chkdsk /f and rebooted.
Chkdsk ran just like it supposed to.

Thanks Man,
Jim