A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Performance and Maintainance of XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Cannot schedule chkdsk



 
 
Thread Tools Display Modes
  #16  
Old December 27th 04, 08:20 PM
Dave Patrick
external usenet poster
 
Posts: n/a
Default Cannot schedule chkdsk

Earlier you told us you succeeded in running chkdsk /r on the suspect drive
from the RC. What result was echoed to the screen? You can also run chkdsk
read-only mode while the OS is running. What result was echoed to the
screen?

From a command prompt;
chkdsk D:
(where D: is the suspect drive letter)

--
Regards,

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

"hardy" wrote:
| Thank you for the information on how to properly relocate the pagefile.
It
| is comforting to learn that I was at least on the right track in my
earlier
| efforts. As you say, it may be moot at this point. I was informed that
the
| pagefile.sys had been overwritten when I reduced the size, and my [perhaps
| faulty] thinking leads me to believe this would have eleviated any
existing
| file corruption. I can try it again however.
|
| Regarding whether or not Bootex.log is ever written or not, all I can say
is
| what I earlier reported. I get a blue screen advising me that my drive
needs
| to be checked for consistency, followed by a warning that I can terminate
| this operation if I so chose but advising me that I should allow it to
| continue. This is followed by a series of periods (. . . .) allowing me
time
| to press any key to abort the operation. This then is followed by the
notice
| that the chkdsk has been cancelled. While normally appearing over some
| elapsed seconds, all of this appears on my screen in a sudden flash. Now,
| whether all of these messages are actually the first few operations
executed
| by chkdsk or whether it is the work of some other service which later
calls
| in chkdsk, I have no idea. I need to rely upon the Windows experts to
| provide me this type of technical detail. After describing all of this to
| you earlier, it was YOUR suggestion that I check the event viewer for an
| entry from Winlogon. Now you seem to be short that I point out I could
never
| find such an entry! In the end however, it seems as though I am right
where
| I started.
|
| I am sorry if my questions seem tedious. Naturally, I have no clue
whether
| this is an SP2 issue, a hardware issue, the result of system file
corruption,
| etc. I am only capable of reporting what I observe as it happens. I
admit
| that I am grasping at straws in an attempt to understand this problem and
| clear it, however it now would seem that I am not the only one so doing.
|
| I appreciate your time in sharing those things that you do know to help me
| troubleshoot this problem. Unfortunately, aside from having eliminated
your
| suggested ideas about the problem, I am really no closer to having a real
| solution. I am at least thankful that unlike that poor guy who wrote about
| the same problem on 11/23 and went unanswered, you have at least offered
me
| some sort of help and I credit you for giving it your best shot.
|
| Unless you care to offer me any last minute suggestions, it appears that I
| will need to refer this issue to someone in New Delhi even though I really
| dislike the thought of doing so. When I stop to consider the last time I
had
| to call Microsoft/India, I have to laugh at the prospect of doing it
again.
| At $35 for a five hour phone call routed through Bombay, I can at least be
| assured of getting my money's worth.


Ads
  #17  
Old January 7th 05, 08:55 AM
hardy
external usenet poster
 
Posts: n/a
Default Cannot schedule chkdsk

Please know that your willingness to stay with me on this problem, in spite
of my earlier cynical remarks (for which I apologize) demonstrate that you
are truly a good man. In answer to our question, here are the results of
chkdsk run against my primary boot drive (C. In this instance, I have
booted from my F: drive in order to run it, so that my regular C: drive is
now D:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\XXXX XXXXXXX XXXXXchkdsk d: /r
The type of file system is NTFS.
Volume label is WDC.

CHKDSK is verifying files (stage 1 of 5)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 5)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 5)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

78140128 KB total disk space.
33730488 KB is 69985 files.
27984 KB is 6766 indexes.
0 KB is bad sectors.
200144 KB is use by the system.
65536 KB occupied by the log file.
44181512 KB available on disk.

4096 bytes in each allocation unit.
19535032 total allocation units on disk.
11045378 allocation units available on disk.

C:\Documents and Settings\XXXX XXXXXXX XXXXX

Now booting back on my normal C: drive, I perform the same operation on the
F: drive. As you will see, I need to dismount the volume in order to get it
to run. Originally, even this dismount was not successful creating the need
to run chkdsk from RC. Apparently however, your instructions to make
adjustments to pagefile corrected this problem so that I no longer have to do
that. Results appear basically the same, although the chkdsk on the F: drive
did not verify the Usn Journal (I am not really sure what that means):

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\XXXX XX XXXXXchkdsk f: /r
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process. Chdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount of this volume? (Y/N) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is Seagate.

CHKDSK is verifying files (stage 1 of 5)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 5)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 5)...
Security descriptor verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
FIle data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

78148160 KB total disk space.
27830364 KB in 95097 files.
36224 KB in 8170 indexes.
0 KB in bad sectors.
195332 KB in use by the system.
65536 KB occupied by the log file.
50086240 KB available on disk.

4096 bytes in each allocation unit.
19537040 total allocation units on disk.
12521560 allocation units available on disk.

C:\Documents and Settings\XXXX XX XXXXX


"Dave Patrick" wrote:

Earlier you told us you succeeded in running chkdsk /r on the suspect drive
from the RC. What result was echoed to the screen? You can also run chkdsk
read-only mode while the OS is running. What result was echoed to the
screen?

From a command prompt;
chkdsk D:
(where D: is the suspect drive letter)

--
Regards,

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

"hardy" wrote:
| Thank you for the information on how to properly relocate the pagefile.
It
| is comforting to learn that I was at least on the right track in my
earlier
| efforts. As you say, it may be moot at this point. I was informed that
the
| pagefile.sys had been overwritten when I reduced the size, and my [perhaps
| faulty] thinking leads me to believe this would have eleviated any
existing
| file corruption. I can try it again however.
|
| Regarding whether or not Bootex.log is ever written or not, all I can say
is
| what I earlier reported. I get a blue screen advising me that my drive
needs
| to be checked for consistency, followed by a warning that I can terminate
| this operation if I so chose but advising me that I should allow it to
| continue. This is followed by a series of periods (. . . .) allowing me
time
| to press any key to abort the operation. This then is followed by the
notice
| that the chkdsk has been cancelled. While normally appearing over some
| elapsed seconds, all of this appears on my screen in a sudden flash. Now,
| whether all of these messages are actually the first few operations
executed
| by chkdsk or whether it is the work of some other service which later
calls
| in chkdsk, I have no idea. I need to rely upon the Windows experts to
| provide me this type of technical detail. After describing all of this to
| you earlier, it was YOUR suggestion that I check the event viewer for an
| entry from Winlogon. Now you seem to be short that I point out I could
never
| find such an entry! In the end however, it seems as though I am right
where
| I started.
|
| I am sorry if my questions seem tedious. Naturally, I have no clue
whether
| this is an SP2 issue, a hardware issue, the result of system file
corruption,
| etc. I am only capable of reporting what I observe as it happens. I
admit
| that I am grasping at straws in an attempt to understand this problem and
| clear it, however it now would seem that I am not the only one so doing.
|
| I appreciate your time in sharing those things that you do know to help me
| troubleshoot this problem. Unfortunately, aside from having eliminated
your
| suggested ideas about the problem, I am really no closer to having a real
| solution. I am at least thankful that unlike that poor guy who wrote about
| the same problem on 11/23 and went unanswered, you have at least offered
me
| some sort of help and I credit you for giving it your best shot.
|
| Unless you care to offer me any last minute suggestions, it appears that I
| will need to refer this issue to someone in New Delhi even though I really
| dislike the thought of doing so. When I stop to consider the last time I
had
| to call Microsoft/India, I have to laugh at the prospect of doing it
again.
| At $35 for a five hour phone call routed through Bombay, I can at least be
| assured of getting my money's worth.



  #18  
Old January 7th 05, 11:29 AM
Dave Patrick
external usenet poster
 
Posts: n/a
Default Cannot schedule chkdsk

OK, looks good. Does this mean the issue is resolved?

--
Regards,

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

"hardy" wrote:
| Please know that your willingness to stay with me on this problem, in
spite
| of my earlier cynical remarks (for which I apologize) demonstrate that you
| are truly a good man. In answer to our question, here are the results of
| chkdsk run against my primary boot drive (C. In this instance, I have
| booted from my F: drive in order to run it, so that my regular C: drive is
| now D:
|
| Microsoft Windows XP [Version 5.1.2600]
| (C) Copyright 1985-2001 Microsoft Corp.
| C:\Documents and Settings\XXXX XXXXXXX XXXXXchkdsk d: /r
| The type of file system is NTFS.
| Volume label is WDC.
|
| CHKDSK is verifying files (stage 1 of 5)...
| File verification completed.
| CHKDSK is verifying indexes (stage 2 of 5)...
| Index verification completed.
| CHKDSK is verifying security descriptors (stage 3 of 5)...
| Security descriptor verification completed.
| CHKDSK is verifying Usn Journal...
| Usn Journal verification completed.
| CHKDSK is verifying file data (stage 4 of 5)...
| File data verification completed.
| CHKDSK is verifying free space (stage 5 of 5)...
| Free space verification is complete.
|
| 78140128 KB total disk space.
| 33730488 KB is 69985 files.
| 27984 KB is 6766 indexes.
| 0 KB is bad sectors.
| 200144 KB is use by the system.
| 65536 KB occupied by the log file.
| 44181512 KB available on disk.
|
| 4096 bytes in each allocation unit.
| 19535032 total allocation units on disk.
| 11045378 allocation units available on disk.
|
| C:\Documents and Settings\XXXX XXXXXXX XXXXX
|
| Now booting back on my normal C: drive, I perform the same operation on
the
| F: drive. As you will see, I need to dismount the volume in order to get
it
| to run. Originally, even this dismount was not successful creating the
need
| to run chkdsk from RC. Apparently however, your instructions to make
| adjustments to pagefile corrected this problem so that I no longer have to
do
| that. Results appear basically the same, although the chkdsk on the F:
drive
| did not verify the Usn Journal (I am not really sure what that means):
|
| Microsoft Windows XP [Version 5.1.2600]
| (C) Copyright 1985-2001 Microsoft Corp.
|
| C:\Documents and Settings\XXXX XX XXXXXchkdsk f: /r
| The type of the file system is NTFS.
|
| Chkdsk cannot run because the volume is in use by another
| process. Chdsk may run if this volume is dismounted first.
| ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
| Would you like to force a dismount of this volume? (Y/N) y
| Volume dismounted. All opened handles to this volume are now invalid.
| Volume label is Seagate.
|
| CHKDSK is verifying files (stage 1 of 5)...
| File verification completed.
| CHKDSK is verifying indexes (stage 2 of 5)...
| Index verification completed.
| CHKDSK is verifying security descriptors (stage 3 of 5)...
| Security descriptor verification completed.
| CHKDSK is verifying file data (stage 4 of 5)...
| FIle data verification completed.
| CHKDSK is verifying free space (stage 5 of 5)...
| Free space verification is complete.
|
| 78148160 KB total disk space.
| 27830364 KB in 95097 files.
| 36224 KB in 8170 indexes.
| 0 KB in bad sectors.
| 195332 KB in use by the system.
| 65536 KB occupied by the log file.
| 50086240 KB available on disk.
|
| 4096 bytes in each allocation unit.
| 19537040 total allocation units on disk.
| 12521560 allocation units available on disk.
|
| C:\Documents and Settings\XXXX XX XXXXX


  #19  
Old January 7th 05, 12:57 PM
hardy
external usenet poster
 
Posts: n/a
Default Cannot schedule chkdsk

Is the issue resolved? Well, only in part. When I ran chkdsk from the
recovery console, I noticed that if either that dirty disk bit had been set
earlier, or if I had scheduled to perform a chkdsk at boot time, those
settings still remained in effect after the chkdsk when I subsequently
rebooted. Now, running chkdsk after Windows comes up completely that problem
seems to have vanished so that when I reboot, the system no longer tries to
initiate chkdsk repeatedly. The remaining problem is this: should I run
diskscan from Norton Utilities, or if I should try to run chkdsk and be told
I need to schedule it to run at boottime, it simply will not execute -- on
any of my four disk drives. When I later boot up, it tells me the scan has
been scheduled, is supposed to then let a few seconds elapse so that I can
press a key if I want to abort the operation, and then on the next line tells
me that the operation was aborted. If I have scheduled each of the four
disks to be scanned, it will run through all four of them in succession and
do exactly the same thing. There is no time lapse while the dots appear on
the screen (. . . .). While this may technically be totally inaccurate, it
is as though those extra keystrokes which ultimately abort the scans had been
stacked and were then immediately popped off the moment the scheduled scan
kicked into swing. Of course, I never touch the keyboard. I know that may
not be what's going on, however it ACTS like a running program that is just
popping off it's input from the stack. My problem with this is that it's not
supposed to be that way. If the machine crashes, or power to a disk is cut
before finishing any final write operations (thus setting the dirty bit),
Windows should check the disk for errors at the next boot and my machine
simply will no longer do that. The good news is that you helped me get to a
point where I can run chkdsk manually when I know that it needs to be run,
but I'd rather rely on the system to do this. It's late and I'm a little
foggy headed now, but I hope that I have made this clear and not confused you.

"Dave Patrick" wrote:

OK, looks good. Does this mean the issue is resolved?

--
Regards,

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

"hardy" wrote:
| Please know that your willingness to stay with me on this problem, in
spite
| of my earlier cynical remarks (for which I apologize) demonstrate that you
| are truly a good man. In answer to our question, here are the results of
| chkdsk run against my primary boot drive (C. In this instance, I have
| booted from my F: drive in order to run it, so that my regular C: drive is
| now D:
|
| Microsoft Windows XP [Version 5.1.2600]
| (C) Copyright 1985-2001 Microsoft Corp.
| C:\Documents and Settings\XXXX XXXXXXX XXXXXchkdsk d: /r
| The type of file system is NTFS.
| Volume label is WDC.
|
| CHKDSK is verifying files (stage 1 of 5)...
| File verification completed.
| CHKDSK is verifying indexes (stage 2 of 5)...
| Index verification completed.
| CHKDSK is verifying security descriptors (stage 3 of 5)...
| Security descriptor verification completed.
| CHKDSK is verifying Usn Journal...
| Usn Journal verification completed.
| CHKDSK is verifying file data (stage 4 of 5)...
| File data verification completed.
| CHKDSK is verifying free space (stage 5 of 5)...
| Free space verification is complete.
|
| 78140128 KB total disk space.
| 33730488 KB is 69985 files.
| 27984 KB is 6766 indexes.
| 0 KB is bad sectors.
| 200144 KB is use by the system.
| 65536 KB occupied by the log file.
| 44181512 KB available on disk.
|
| 4096 bytes in each allocation unit.
| 19535032 total allocation units on disk.
| 11045378 allocation units available on disk.
|
| C:\Documents and Settings\XXXX XXXXXXX XXXXX
|
| Now booting back on my normal C: drive, I perform the same operation on
the
| F: drive. As you will see, I need to dismount the volume in order to get
it
| to run. Originally, even this dismount was not successful creating the
need
| to run chkdsk from RC. Apparently however, your instructions to make
| adjustments to pagefile corrected this problem so that I no longer have to
do
| that. Results appear basically the same, although the chkdsk on the F:
drive
| did not verify the Usn Journal (I am not really sure what that means):
|
| Microsoft Windows XP [Version 5.1.2600]
| (C) Copyright 1985-2001 Microsoft Corp.
|
| C:\Documents and Settings\XXXX XX XXXXXchkdsk f: /r
| The type of the file system is NTFS.
|
| Chkdsk cannot run because the volume is in use by another
| process. Chdsk may run if this volume is dismounted first.
| ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
| Would you like to force a dismount of this volume? (Y/N) y
| Volume dismounted. All opened handles to this volume are now invalid.
| Volume label is Seagate.
|
| CHKDSK is verifying files (stage 1 of 5)...
| File verification completed.
| CHKDSK is verifying indexes (stage 2 of 5)...
| Index verification completed.
| CHKDSK is verifying security descriptors (stage 3 of 5)...
| Security descriptor verification completed.
| CHKDSK is verifying file data (stage 4 of 5)...
| FIle data verification completed.
| CHKDSK is verifying free space (stage 5 of 5)...
| Free space verification is complete.
|
| 78148160 KB total disk space.
| 27830364 KB in 95097 files.
| 36224 KB in 8170 indexes.
| 0 KB in bad sectors.
| 195332 KB in use by the system.
| 65536 KB occupied by the log file.
| 50086240 KB available on disk.
|
| 4096 bytes in each allocation unit.
| 19537040 total allocation units on disk.
| 12521560 allocation units available on disk.
|
| C:\Documents and Settings\XXXX XX XXXXX



  #20  
Old January 8th 05, 06:03 AM
Dave Patrick
external usenet poster
 
Posts: n/a
Default Cannot schedule chkdsk

Yes it is clear, but the situation remains that some system/boot start
device is not allowing autochk the required exclusive access to the disks.
This is the cause. Now the other issues you mention are only an immediate
effect or result of this for which I don't have an answer.

Afraid you really have two choices; either remove the device/service or put
up with it and use the RC when necessary.

--
Regards,

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

"hardy" wrote:
| Is the issue resolved? Well, only in part. When I ran chkdsk from the
| recovery console, I noticed that if either that dirty disk bit had been
set
| earlier, or if I had scheduled to perform a chkdsk at boot time, those
| settings still remained in effect after the chkdsk when I subsequently
| rebooted. Now, running chkdsk after Windows comes up completely that
problem
| seems to have vanished so that when I reboot, the system no longer tries
to
| initiate chkdsk repeatedly. The remaining problem is this: should I run
| diskscan from Norton Utilities, or if I should try to run chkdsk and be
told
| I need to schedule it to run at boottime, it simply will not execute -- on
| any of my four disk drives. When I later boot up, it tells me the scan
has
| been scheduled, is supposed to then let a few seconds elapse so that I can
| press a key if I want to abort the operation, and then on the next line
tells
| me that the operation was aborted. If I have scheduled each of the four
| disks to be scanned, it will run through all four of them in succession
and
| do exactly the same thing. There is no time lapse while the dots appear
on
| the screen (. . . .). While this may technically be totally inaccurate,
it
| is as though those extra keystrokes which ultimately abort the scans had
been
| stacked and were then immediately popped off the moment the scheduled scan
| kicked into swing. Of course, I never touch the keyboard. I know that
may
| not be what's going on, however it ACTS like a running program that is
just
| popping off it's input from the stack. My problem with this is that it's
not
| supposed to be that way. If the machine crashes, or power to a disk is
cut
| before finishing any final write operations (thus setting the dirty bit),
| Windows should check the disk for errors at the next boot and my machine
| simply will no longer do that. The good news is that you helped me get to
a
| point where I can run chkdsk manually when I know that it needs to be run,
| but I'd rather rely on the system to do this. It's late and I'm a little
| foggy headed now, but I hope that I have made this clear and not confused
you.


  #21  
Old February 22nd 05, 08:15 AM
hardy
external usenet poster
 
Posts: n/a
Default Cannot schedule chkdsk

Dear Dave Patrick:

Over the past couple of months you helped me as I struggled with the problem
of being unable to schedule a chkdsk on my machine. Of course, throughout
our struggles, the root cause of the problem seemed as elusive as ever.
Today, I am pleased to announce that I have finally discovered that cause and
felt perhaps you would appreciate me sharing this information with you. It
is probably only a matter of time before you presented with the same or
similar problem again by another user.

After my initial installation of Windows XP Pro SP1

"Dave Patrick" wrote:

Yes it is clear, but the situation remains that some system/boot start
device is not allowing autochk the required exclusive access to the disks.
This is the cause. Now the other issues you mention are only an immediate
effect or result of this for which I don't have an answer.

Afraid you really have two choices; either remove the device/service or put
up with it and use the RC when necessary.

--
Regards,

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

"hardy" wrote:
| Is the issue resolved? Well, only in part. When I ran chkdsk from the
| recovery console, I noticed that if either that dirty disk bit had been
set
| earlier, or if I had scheduled to perform a chkdsk at boot time, those
| settings still remained in effect after the chkdsk when I subsequently
| rebooted. Now, running chkdsk after Windows comes up completely that
problem
| seems to have vanished so that when I reboot, the system no longer tries
to
| initiate chkdsk repeatedly. The remaining problem is this: should I run
| diskscan from Norton Utilities, or if I should try to run chkdsk and be
told
| I need to schedule it to run at boottime, it simply will not execute -- on
| any of my four disk drives. When I later boot up, it tells me the scan
has
| been scheduled, is supposed to then let a few seconds elapse so that I can
| press a key if I want to abort the operation, and then on the next line
tells
| me that the operation was aborted. If I have scheduled each of the four
| disks to be scanned, it will run through all four of them in succession
and
| do exactly the same thing. There is no time lapse while the dots appear
on
| the screen (. . . .). While this may technically be totally inaccurate,
it
| is as though those extra keystrokes which ultimately abort the scans had
been
| stacked and were then immediately popped off the moment the scheduled scan
| kicked into swing. Of course, I never touch the keyboard. I know that
may
| not be what's going on, however it ACTS like a running program that is
just
| popping off it's input from the stack. My problem with this is that it's
not
| supposed to be that way. If the machine crashes, or power to a disk is
cut
| before finishing any final write operations (thus setting the dirty bit),
| Windows should check the disk for errors at the next boot and my machine
| simply will no longer do that. The good news is that you helped me get to
a
| point where I can run chkdsk manually when I know that it needs to be run,
| but I'd rather rely on the system to do this. It's late and I'm a little
| foggy headed now, but I hope that I have made this clear and not confused
you.



  #22  
Old February 22nd 05, 08:27 AM
hardy
external usenet poster
 
Posts: n/a
Default Cannot schedule chkdsk

Dear Dave Patrick:

Over the past couple of months you helped me as I struggled with the problem
of being unable to schedule a chkdsk on my machine. Of course, throughout
our struggles, the root cause of the problem seemed as elusive as ever.
Today, I am pleased to announce that I have finally discovered that cause and
felt perhaps you would appreciate me sharing this information with you. It
is probably only a matter of time before you are presented with the same or
similar problem again by another user.

After my initial installation of Windows XP Pro SP1, I installed Recovery
Console on my main boot drive so that RC became a menu option at boot time.
Then, I was quick to install SP2 as soon as it became available, and although
I did not realize it at the time, RC was screwed up due to incompatibility
with SP2. It appears that this was the root cause and that by removing RC
from my hard disk, the problem of being unable to schedule a chkdsk at boot
time completely disappeared.


"Dave Patrick" wrote:

Yes it is clear, but the situation remains that some system/boot start
device is not allowing autochk the required exclusive access to the disks.
This is the cause. Now the other issues you mention are only an immediate
effect or result of this for which I don't have an answer.

Afraid you really have two choices; either remove the device/service or put
up with it and use the RC when necessary.

--
Regards,

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

"hardy" wrote:
| Is the issue resolved? Well, only in part. When I ran chkdsk from the
| recovery console, I noticed that if either that dirty disk bit had been
set
| earlier, or if I had scheduled to perform a chkdsk at boot time, those
| settings still remained in effect after the chkdsk when I subsequently
| rebooted. Now, running chkdsk after Windows comes up completely that
problem
| seems to have vanished so that when I reboot, the system no longer tries
to
| initiate chkdsk repeatedly. The remaining problem is this: should I run
| diskscan from Norton Utilities, or if I should try to run chkdsk and be
told
| I need to schedule it to run at boottime, it simply will not execute -- on
| any of my four disk drives. When I later boot up, it tells me the scan
has
| been scheduled, is supposed to then let a few seconds elapse so that I can
| press a key if I want to abort the operation, and then on the next line
tells
| me that the operation was aborted. If I have scheduled each of the four
| disks to be scanned, it will run through all four of them in succession
and
| do exactly the same thing. There is no time lapse while the dots appear
on
| the screen (. . . .). While this may technically be totally inaccurate,
it
| is as though those extra keystrokes which ultimately abort the scans had
been
| stacked and were then immediately popped off the moment the scheduled scan
| kicked into swing. Of course, I never touch the keyboard. I know that
may
| not be what's going on, however it ACTS like a running program that is
just
| popping off it's input from the stack. My problem with this is that it's
not
| supposed to be that way. If the machine crashes, or power to a disk is
cut
| before finishing any final write operations (thus setting the dirty bit),
| Windows should check the disk for errors at the next boot and my machine
| simply will no longer do that. The good news is that you helped me get to
a
| point where I can run chkdsk manually when I know that it needs to be run,
| but I'd rather rely on the system to do this. It's late and I'm a little
| foggy headed now, but I hope that I have made this clear and not confused
you.



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
CHKDSK - what do these results mean?? Richard Windows XP Help and Support 4 March 14th 05 06:45 AM
CHKDSK simply doesn't work AGAIN Scott Lansbury Performance and Maintainance of XP 2 December 4th 04 09:28 PM
XP / NTSF ...security descriptor / MFT error... RJK General XP issues or comments 3 November 11th 04 07:59 PM
Chkdsk errors in SP2 installation Sam Windows Service Pack 2 8 October 2nd 04 02:27 AM






All times are GMT +1. The time now is 06:31 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.