CheckDisk problem

  • Thread starter Thread starter Bagwash
  • Start date Start date
B

Bagwash

I'm trying to defrag a large drive partition, but first ran CheckDisk. When
I click on Analyse or Defragment I now get a message <Disk Defragmenter has
detected that CheckDisk is scheduled to run on the volume (E:). Please run
Chksdk /f>.
I attempt that, and get a message <Chkdsk cannot run because the volume is
in use by another process [NB Nothing else is running as far as I can see].
Would you like to reschedule this volume to be checked the next time the
system restarts? (Y/N)>. I say Y [I've also tried N]. I restart, and allow
Chkdsk to run. But after that my attempt to defrag still gives me that
original message.
I'm using XP SP3. Suggestions appreciated as to how I get it to defrag.
 
Bagwash said:
I'm trying to defrag a large drive partition, but first ran CheckDisk. When I
click on Analyse or Defragment I now get a message <Disk Defragmenter has
detected that CheckDisk is scheduled to run on the volume (E:). Please run
Chksdk /f>.
I attempt that, and get a message <Chkdsk cannot run because the volume is in
use by another process [NB Nothing else is running as far as I can see]. Would
you like to reschedule this volume to be checked the next time the system
restarts? (Y/N)>. I say Y [I've also tried N]. I restart, and allow Chkdsk to
run. But after that my attempt to defrag still gives me that original message.
I'm using XP SP3. Suggestions appreciated as to how I get it to defrag.
Click to expand...

It may be caused by a virus checker program or a disk monitoring program, the
most common one being SpyDoctor.

Read the comments by Wesley Vogel in this article for more details:

http://www.keyongtech.com/3478041-chkdsk
 
Bagwash said:
I'm trying to defrag a large drive partition, but first ran CheckDisk.
When I click on Analyse or Defragment I now get a message <Disk
Defragmenter has detected that CheckDisk is scheduled to run on the
volume (E:). Please run Chksdk /f>.
I attempt that, and get a message <Chkdsk cannot run because the volume
is in use by another process [NB Nothing else is running as far as I can
see]. Would you like to reschedule this volume to be checked the next
time the system restarts? (Y/N)>. I say Y [I've also tried N]. I restart,
and allow Chkdsk to run. But after that my attempt to defrag still gives
me that original message.
I'm using XP SP3. Suggestions appreciated as to how I get it to defrag.
Click to expand...


It may be caused by a virus checker program or a disk monitoring program,
the most common one being SpyDoctor.

Read the comments by Wesley Vogel in this article for more details:

http://www.keyongtech.com/3478041-chkdsk
Click to expand...
Thanks - I'll try that over the weekend. Incidentally, using only AVG 9 as
virus checker.
 
I'm trying to defrag a large drive partition, but first ran CheckDisk. When
I click on Analyse or Defragment I now get a message <Disk Defragmenter has
detected that CheckDisk is scheduled to run on the volume (E:). Please run
Chksdk /f>.
I attempt that, and get a message <Chkdsk cannot run because the volume is
in use by another process [NB Nothing else is running as far as I can see].
Would you like to reschedule this volume to be checked the next time the
system restarts? (Y/N)>. I say Y [I've also tried N]. I restart, and allow
Chkdsk to run. But after that my attempt to defrag still gives me that
original message.
I'm using XP SP3. Suggestions appreciated as to how I get it to defrag.
Click to expand...

That means as far as Windows is concerned, there is an outstanding
chkdsk command that needs to complete, so it does not make sense to
ask it to set up another one.. If you have one set up to run on the
next reboot, the result will not stay on the screen, but will end up
in the Event Log instead.

I would NOT follow the advice in the link about the /SAFEBOOT
thing... It may have been sound advice 5 years ago, but there is
malware afoot nowadays that if you happen to have it and add the /
SAFEBOOT option in msconfig, your system will never boot again
(without some help). /SAFEBOOT is very risky if you are
troubleshooting and don't know how to fix the issue when you add it
and your system will now longer boot at all. It is not hard to fix
though - and there is of course no need to reinstall Windows for that
silly problem.

You need to determine what happens when your chkdsk runs on reboot:

When chkdsk runs automatically on a reboot, the results are shown in
the Event Viewer Application
log.

To see the Event Viewer logs, click Start, Settings, Control Panel,
Administrative Tools, Event Viewer.

A shortcut to Event Viewer is to click Start, Run and in the box
enter:

%SystemRoot%\system32\eventvwr.msc

Click OK to launch the Event Viewer.

Look in the Application log for an event sourced by Winlogon,
something like:

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
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.

CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

39070048 KB total disk space.
25151976 KB in 78653 files.
48256 KB in 10264 indexes.
0 KB in bad sectors.
237080 KB in use by the system.
65536 KB occupied by the log file.
13632736 KB available on disk.

4096 bytes in each allocation unit.
9767512 total allocation units on disk.
3408184 allocation units available on disk.

Windows has finished checking your disk.
Please wait while your computer restarts.
 
I'm trying to defrag a large drive partition, but first ran CheckDisk.
When
I click on Analyse or Defragment I now get a message <Disk Defragmenter
has
detected that CheckDisk is scheduled to run on the volume (E:). Please run
Chksdk /f>.
I attempt that, and get a message <Chkdsk cannot run because the volume is
in use by another process [NB Nothing else is running as far as I can
see].
Would you like to reschedule this volume to be checked the next time the
system restarts? (Y/N)>. I say Y [I've also tried N]. I restart, and allow
Chkdsk to run. But after that my attempt to defrag still gives me that
original message.
I'm using XP SP3. Suggestions appreciated as to how I get it to defrag.
Click to expand...

That means as far as Windows is concerned, there is an outstanding
chkdsk command that needs to complete, so it does not make sense to
ask it to set up another one.. If you have one set up to run on the
next reboot, the result will not stay on the screen, but will end up
in the Event Log instead.

I would NOT follow the advice in the link about the /SAFEBOOT
thing... It may have been sound advice 5 years ago, but there is
malware afoot nowadays that if you happen to have it and add the /
SAFEBOOT option in msconfig, your system will never boot again
(without some help). /SAFEBOOT is very risky if you are
troubleshooting and don't know how to fix the issue when you add it
and your system will now longer boot at all. It is not hard to fix
though - and there is of course no need to reinstall Windows for that
silly problem.

You need to determine what happens when your chkdsk runs on reboot:

When chkdsk runs automatically on a reboot, the results are shown in
the Event Viewer Application
log.

To see the Event Viewer logs, click Start, Settings, Control Panel,
Administrative Tools, Event Viewer.

A shortcut to Event Viewer is to click Start, Run and in the box
enter:

%SystemRoot%\system32\eventvwr.msc

Click OK to launch the Event Viewer.

Look in the Application log for an event sourced by Winlogon,
something like:

Event Type: Information
Event Source: Winlogon
Event Category: None
Event ID: 1001
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.

CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

39070048 KB total disk space.
25151976 KB in 78653 files.
48256 KB in 10264 indexes.
0 KB in bad sectors.
237080 KB in use by the system.
65536 KB occupied by the log file.
13632736 KB available on disk.

4096 bytes in each allocation unit.
9767512 total allocation units on disk.
3408184 allocation units available on disk.

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

---

Thanks Jose. So I've found the latest Winlogon event:

Checking file system on E:

The type of the file system is NTFS.

Volume label is Media.



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.

CHKDSK is verifying Usn Journal...

Usn Journal verification completed.

Windows has checked the file system and found no problems.



195358400 KB total disk space.

163283912 KB in 18766 files.

8488 KB in 971 indexes.

4 KB in bad sectors.

232884 KB in use by the system.

65536 KB occupied by the log file.

31833112 KB available on disk.



4096 bytes in each allocation unit.

48839600 total allocation units on disk.

7958278 allocation units available on disk.



Internal Info:

90 50 02 00 25 4d 00 00 9e 78 00 00 00 00 00 00 .P..%M...x......

cb 1d 00 00 00 00 00 00 19 00 00 00 00 00 00 00 ................

9c 11 d8 01 00 00 00 00 f0 90 bd 0c 00 00 00 00 ................

e0 9d a3 01 00 00 00 00 00 00 00 00 00 00 00 00 ................

00 00 00 00 00 00 00 00 7e e3 17 18 00 00 00 00 ........~.......

99 9e 36 00 00 00 00 00 00 3f 07 00 4e 49 00 00 ..6......?..NI..

00 00 00 00 00 20 0f ee 26 00 00 00 cb 03 00 00 ..... ..&.......





For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



Where do I go from here? (Was a further instruction lost in your post?)
 
Where do I go from here? (Was a further instruction lost in your
post?)
Click to expand...

Messages like that come and go sometimes. In any case, try running
chkdsk in full repair mode:

chkdsk C: /F /V /R /X

This assumes you are checking the 'C' partition. The '/R' flag implies
the '/F' flag; however, it does not hurt to include it.

Obviously, you have to enter this at the command prompt. If you don't
know how to do that, write back.

--
Carmel

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________

You are only young once, but you can stay immature indefinitely.
 
Last time a similar thing happened to me I had to boot into the recovery
console and run chkdsk from there.
Neil
 
Thanks Jose. So I've found the latest Winlogon event:

Checking file system on E:

The type of the file system is NTFS.

Volume label is Media.

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.

CHKDSK is verifying Usn Journal...

Usn Journal verification completed.

Windows has checked the file system and found no problems.

 195358400 KB total disk space.

 163283912 KB in 18766 files.

      8488 KB in 971 indexes.

         4 KB in bad sectors.

    232884 KB in use by the system.

     65536 KB occupied by the log file.

  31833112 KB available on disk.

      4096 bytes in each allocation unit.

  48839600 total allocation units on disk.

   7958278 allocation units available on disk.

Internal Info:

90 50 02 00 25 4d 00 00 9e 78 00 00 00 00 00 00  .P..%M...x......

cb 1d 00 00 00 00 00 00 19 00 00 00 00 00 00 00  ................

9c 11 d8 01 00 00 00 00 f0 90 bd 0c 00 00 00 00  ................

e0 9d a3 01 00 00 00 00 00 00 00 00 00 00 00 00  ................

00 00 00 00 00 00 00 00 7e e3 17 18 00 00 00 00  ........~.......

99 9e 36 00 00 00 00 00 00 3f 07 00 4e 49 00 00  ..6......?..NI..

00 00 00 00 00 20 0f ee 26 00 00 00 cb 03 00 00  ..... ..&.......

For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.

Where do I go from here? (Was a further instruction lost in your post?)
Click to expand...

I'm not quite getting it - that looks like chkdsk ran on your E drive,
which could be what you expect.

Does chkdsk keep running on your E drive and you think it should not
be? It should only run one if needed unless you tell it to run again.

Needed means the dirty bit is set (maybe from a power failure) and if
there is nothing else wrong, chkdsk /r should take care of it. I have
heard it may take a couple passes, but to me, that is just hearsay.
XP normally checks all the drive when you boot - if the DB is set,
chkdsk will run.

Needed could also mean it is scheduled to run because you told it to,
but that should go away when complete. That adds a command in the
system startup after the normal dirty bit check so chkdsk will run not
matter what the DB condition is. If chkdsk completes successfully,
the command is removed.(the normal DB check remains). At some point,
there should be no chkdsk on reboot.

Sometimes a drive can be dirty and chkdsk /r will not clear the DB.
Then you have some kind of a hardware failure since the DB will not
clear. You can tell XP not to check the drive anymore if you want. I
have a drive like that. chkdsk /r will not fix it or clear the DB,
but I don't care so I told XP not to bother checking that particular
drive anymore, but please still check my other drives (and it does).

You can check the dirty bit on a volume from a command prompt to help
understand more:

fsutil dirty query c:

The volume is Dirty or it is NOT Dirty

You cannot manually clear the dirty bit though - you should only let
chkdsk /r do that. If the DB will never clear, your drive is
defective but still may be usable to you. It is annoying to have
chkdsk run every time, so you can tell XP just to skip the afflicted
drive from now on. If you need to do that, holler.

Try to get a handle on just what you see that you don't think you
should be seeing or what you don't see you think you should, etc. I
don't understand the problem exactly, but it should not be hard to
figure out.

Yes - running chkdsk /r from the Recovery Console on your suspicious
volume is a good idea too and then you can see what it is doing. Your
system must be in a "static" state for chkdsk to be reliable and there
are only two ways to achieve a static state - when XP is not quite
loaded (at startup like you see) or from the Recovery Console. You
can someday find your self in need of a bootable Recovery Console CD
if you don't have one. If you need to make a RC CD, read this:

You can create a bootable XP Recovery Console CD when no XP media is
available:

http://www.bleepingcomputer.com/forums/topic276527.html
 
Thanks enormously, Carmel - that did the trick, having run that for all
three of my partitions (C:, D: & E:).

I'll post similarly at the end of the thread.
 
Thanks everyone who offered solutions. Carmel's solution worked (which was
fortunate because for some of the others I'd have needed holding by the
hand!)

Keep up the good work everyone - greatly appreciated.

neil said:
Last time a similar thing happened to me I had to boot into the recovery
console and run chkdsk from there.
Neil

Bagwash said:
I'm trying to defrag a large drive partition, but first ran CheckDisk.
When I click on Analyse or Defragment I now get a message <Disk
Defragmenter has detected that CheckDisk is scheduled to run on the
volume (E:). Please run Chksdk /f>.
I attempt that, and get a message <Chkdsk cannot run because the volume
is in use by another process [NB Nothing else is running as far as I can
see]. Would you like to reschedule this volume to be checked the next
time the system restarts? (Y/N)>. I say Y [I've also tried N]. I restart,
and allow Chkdsk to run. But after that my attempt to defrag still gives
me that original message.
I'm using XP SP3. Suggestions appreciated as to how I get it to defrag.
Click to expand...
Click to expand...
 
Back
Top