|
Posted by Craig on February 19, 2007, 11:28 am
Please log in for more thread options AllanF, thanks that did the trick. chkntfs showed the disk was dirty, a
chkntfs /d c: reset the flag on the drive, and then a chkntfs /c c: ran a
good chkdsk on startup. So all is well again.
Appreciate the help on this.
Craig
"AllanF" wrote:
> Hi Craig,
>
> Just a suggestion...
>
> When you schedule chkdsk.exe, autochk.exe runs at the next start up. It
> sounds like you have autochk.exe OK because you have the countdown. But if
> you have volume flagged as "dirty", autochk.exe will automatically try to run
> at start up. However, you can prevent autochk.exe > chkdsk.exe from running,
> by using chkntfs.exe with /x parameter from the command prompt. It may be
> possible, that c: has been flagged as dirty, and that chkntfs.exe has
> excluded c: from being repaired. Try this: schedule a chkdsk, then run
> "chkntfs c:" from cmd, just to check the status of the volume and whether the
> autochk > chkdsk has been scheduled... Look up chkntfs in Help and Support.
>
> I'm not sure if a manual schedule of chkdsk.exe will override an exclusion
> by chkntfs.exe when the volume is flagged as dirty... perhaps others who have
> experienced a dirty volume may provide some insight.
>
> Alternatively, build yourself a BartPE boot disk and run chkdsk from there. ;)
>
> "Craig" wrote:
>
> > When I setup a chkdsk c: /f to run at the next boot of my computer, chkdsk
> > doesn't start. I reboot the computer and when the screen appears saying to
> > cancel chkdsk hit any key within 10 seconds (or whatever the exact message
> > is), another message appears saying the chkdsk was cancelled, even though I
> > did not press any key. This has been happening for about 3 weeks.
> >
> > Any suggestions on what the problem is and how to correct it?
> >
> > Thanks
> > Craig
| 
XML Sitemap