disk defrag

[MikeD]

HI. I have a very unusual problem with disk defrag and
chkdsk. I try to run defrag and the following shows
up"disk defrag has detected that chkdsk is scheduled to
run in the volumn C. Please run chkdsk /f. When I try to
run chkdsk with the /f switch. I try to run this in the
cmd prompt and I receive the following:"chkdsk cannot run
because the volumn is in use by another process. Would you
like to schedule this volumn to be checked the next time
the system restarts?" I answer yes. When it restarts it is
unable to run because it was unable to lock? the volumn.
My wording may be off somewhat. I checked to see if chkdsk
is scheduled to run in Control Panel/ Scheduled tasks and
it is not. When I run chkdsk /c it tells me I have damaged
files and to run chkdsk /f. Catch 22. I have read that
there is a dirty bit but I do not know how to resolve it.
HELP!!

 

[Phillips]

I rem. reading it somwhere else - www.mcs.ms:
1. check Diagnostic Startup (in msconfig)
2. reboot
3. do your thing (type chkdsk /f in Run)
4. reboot - chkdsk should run now (with the fix switch)
5. resume normal startup in msconfig

Others blame chdsk problems on ZoneAlarm 5.xx - loads True Vector before
chek disk or so.
Michael

 

[davetest]

I rem. reading it somwhere else - www.mcs.ms:
1. check Diagnostic Startup (in msconfig)
2. reboot
3. do your thing (type chkdsk /f in Run)
4. reboot - chkdsk should run now (with the fix switch)
5. resume normal startup in msconfig

Others blame chdsk problems on ZoneAlarm 5.xx - loads True Vector before
chek disk or so.
Michael

Apparently Zonealarm (5?) can cause the problem of the
drive being locked at boottime.
DAve

 

[Carrie Garth]

| "MikeD" <http://www.microsoft.com/communities/privacy.mspx>
| wrote in message | <SNIP> I try to run this in the cmd prompt and I receive the
| following:"chkdsk cannot run because the volumn is in use by another
| process. Would you like to schedule this volumn to be checked the
| next time the system restarts?" I answer yes. When it restarts it is
| unable to run because it was unable to lock? the volumn. My
| wording may be off somewhat. <SNIP>

If the message is: "Cannot Open Volume for Direct Access" this is a
well-known problem. For more information see the following
Microsoft Knowledge Base article:

KB823439 - "Cannot Open Volume for Direct Access" Error
Message When Chkdsk Runs at Startup
http://support.microsoft.com/default.aspx?Product=winxp&scid=kb;en-us;823439

Furthermore, there appears that there can be more than one cause
of the problem and, as such, more than one solution.

One solution to try if the file system is NTFS is to schedule chkdsk
to run at startup with the /X parameter which forces a dismount.
And if you are having "Boot-Time Defragmentation issues while
running ZoneAlarm," Executive Diskeeper Tech Support has
issued a FAQ by that title the explains how to solve the problem
by temporarily disabling the VSDATANT device.

For more information see the following web page on the subject
authored by Jerold Schulman: Windows - General MVP:

JSI Tip 7079_ You receive 'Cannot open volume for direct access'
when Chkdsk runs during Windows XP startup
http://www.jsiinc.com/SUBO/tip7000/rh7079.htm

Note: According to the following newsgroup post updating
ZoneAlarm solved the problem for Joan:

----- Begin Original Message -----
From: "Joan Archer" <[email protected]>
Subject: Re: chekdisk problem
Date: Wed, 7 Jul 2004 20:48:29 +0100
Message-ID: <[email protected]>
Newsgroups: microsoft.public.windowsxp.basics

You should have no problems with Zone Alarm if you have the
latest version. I had problems with chkdisk and defrag when I first
installed v5 of Zone Alarm but on the 23rd of June was offered an
update which I downloaded and installed and that cleared up the
problems. The version number is 5.0.590.043

Joan
----- End Original Message -----

And if another 3rd party product such as a Firewall or AntiVirus
could be the problem try searching the Support Pages of the 3rd
party product for information.

For example, as follows is what Symantec has to say about the
chkdsk.exe error message and Symantec AntiVirus Corporate
Edition 9.0 on Microsoft Windows XP:

Document ID: 2004060108192148
Last Modified: 06/21/2004

"Symantec is aware of this problem, and there is no solution at this
time. We will continue to track this problem, and this document
will be updated if new information or a solution is found.
Workaround <SNIP>"

For more information see the following Web Page:

Chkdsk_exe or ScanDisk fails to run on Windows XP after
installing Symantec AntiVirus Corporate Edition 9_0
http://service1.symantec.com/SUPPOR...6e22005026f1/52d79c84c363973488256ea600542b5a

 

[Guest]

-----Original Message-----
| "MikeD"

| wrote in message [email protected]
| <SNIP> I try to run this in the cmd prompt and I receive the
| following:"chkdsk cannot run because the volumn is in use by another
| process. Would you like to schedule this volumn to be checked the
| next time the system restarts?" I answer yes. When it restarts it is
| unable to run because it was unable to lock? the volumn. My
| wording may be off somewhat. <SNIP>

If the message is: "Cannot Open Volume for Direct Access" this is a
well-known problem. For more information see the following
Microsoft Knowledge Base article:

KB823439 - "Cannot Open Volume for Direct Access" Error
Message When Chkdsk Runs at Startup
http://support.microsoft.com/default.aspx? Product=winxp&scid=kb;en-us;823439

Furthermore, there appears that there can be more than one cause
of the problem and, as such, more than one solution.

One solution to try if the file system is NTFS is to schedule chkdsk
to run at startup with the /X parameter which forces a dismount.
And if you are having "Boot-Time Defragmentation issues while
running ZoneAlarm," Executive Diskeeper Tech Support has
issued a FAQ by that title the explains how to solve the problem
by temporarily disabling the VSDATANT device.

For more information see the following web page on the subject
authored by Jerold Schulman: Windows - General MVP:

JSI Tip 7079_ You receive 'Cannot open volume for direct access'
when Chkdsk runs during Windows XP startup
http://www.jsiinc.com/SUBO/tip7000/rh7079.htm

Note: According to the following newsgroup post updating
ZoneAlarm solved the problem for Joan:

----- Begin Original Message -----
From: "Joan Archer" <[email protected]>
Subject: Re: chekdisk problem
Date: Wed, 7 Jul 2004 20:48:29 +0100
Message-ID: <[email protected]>
Newsgroups: microsoft.public.windowsxp.basics

You should have no problems with Zone Alarm if you have the
latest version. I had problems with chkdisk and defrag when I first
installed v5 of Zone Alarm but on the 23rd of June was offered an
update which I downloaded and installed and that cleared up the
problems. The version number is 5.0.590.043

Joan
----- End Original Message -----

And if another 3rd party product such as a Firewall or AntiVirus
could be the problem try searching the Support Pages of the 3rd
party product for information.

For example, as follows is what Symantec has to say about the
chkdsk.exe error message and Symantec AntiVirus Corporate
Edition 9.0 on Microsoft Windows XP:

Document ID: 2004060108192148
Last Modified: 06/21/2004

"Symantec is aware of this problem, and there is no solution at this
time. We will continue to track this problem, and this document
will be updated if new information or a solution is found.
Workaround <SNIP>"

For more information see the following Web Page:

Chkdsk_exe or ScanDisk fails to run on Windows XP after
installing Symantec AntiVirus Corporate Edition 9_0
http://service1.symantec.com/SUPPORT/ent- security.nsf/529c2f9adcf33a1088256e22005026f1/52d79c84c3639
73488256ea600542b5a

Hi. It was Zone Alarm that was causing the problem. I

have the latest and the so called greatest and it still
hosed me up. I went to the web site and followed their
directions and it worked. THANKS!!

 

[Guest]

-----Original Message-----
| "MikeD"

| wrote in message [email protected]
| <SNIP> I try to run this in the cmd prompt and I receive the
| following:"chkdsk cannot run because the volumn is in use by another
| process. Would you like to schedule this volumn to be checked the
| next time the system restarts?" I answer yes. When it restarts it is
| unable to run because it was unable to lock? the volumn. My
| wording may be off somewhat. <SNIP>

If the message is: "Cannot Open Volume for Direct Access" this is a
well-known problem. For more information see the following
Microsoft Knowledge Base article:

KB823439 - "Cannot Open Volume for Direct Access" Error
Message When Chkdsk Runs at Startup
http://support.microsoft.com/default.aspx? Product=winxp&scid=kb;en-us;823439

Furthermore, there appears that there can be more than one cause
of the problem and, as such, more than one solution.

One solution to try if the file system is NTFS is to schedule chkdsk
to run at startup with the /X parameter which forces a dismount.
And if you are having "Boot-Time Defragmentation issues while
running ZoneAlarm," Executive Diskeeper Tech Support has
issued a FAQ by that title the explains how to solve the problem
by temporarily disabling the VSDATANT device.

For more information see the following web page on the subject
authored by Jerold Schulman: Windows - General MVP:

JSI Tip 7079_ You receive 'Cannot open volume for direct access'
when Chkdsk runs during Windows XP startup
http://www.jsiinc.com/SUBO/tip7000/rh7079.htm

Note: According to the following newsgroup post updating
ZoneAlarm solved the problem for Joan:

----- Begin Original Message -----
From: "Joan Archer" <[email protected]>
Subject: Re: chekdisk problem
Date: Wed, 7 Jul 2004 20:48:29 +0100
Message-ID: <[email protected]>
Newsgroups: microsoft.public.windowsxp.basics

You should have no problems with Zone Alarm if you have the
latest version. I had problems with chkdisk and defrag when I first
installed v5 of Zone Alarm but on the 23rd of June was offered an
update which I downloaded and installed and that cleared up the
problems. The version number is 5.0.590.043

Joan
----- End Original Message -----

And if another 3rd party product such as a Firewall or AntiVirus
could be the problem try searching the Support Pages of the 3rd
party product for information.

For example, as follows is what Symantec has to say about the
chkdsk.exe error message and Symantec AntiVirus Corporate
Edition 9.0 on Microsoft Windows XP:

Document ID: 2004060108192148
Last Modified: 06/21/2004

"Symantec is aware of this problem, and there is no solution at this
time. We will continue to track this problem, and this document
will be updated if new information or a solution is found.
Workaround <SNIP>"

For more information see the following Web Page:

Chkdsk_exe or ScanDisk fails to run on Windows XP after
installing Symantec AntiVirus Corporate Edition 9_0
http://service1.symantec.com/SUPPORT/ent- security.nsf/529c2f9adcf33a1088256e22005026f1/52d79c84c3639
73488256ea600542b5a

Hi. It was Zone Alarm that was causing the problem. I

have the latest and the so called greatest and it still
hosed me up. I went to the web site and followed their
directions and it worked. THANKS!!