MSFN Forum: How to Manually Schedule Chkdsk at Startup? - MSFN Forum

Jump to content


Unattended CD/DVD Guide Homepage · MSFN Forum Rules

If you have questions about customizing Windows XP that are nLite-specific, please post them in the nLite forum, not here. If you have questions regarding the unattended installation of Windows XP, please post them in the Unattended Windows 2000/XP/2003 section.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

How to Manually Schedule Chkdsk at Startup? For all drives Rate Topic: -----

#1 User is offline   spacesurfer 

  • Pharmassist
  • Group: Patrons
  • Posts: 1,668
  • Joined: 31-July 04
  • OS:Windows 7 x86
  • Country: Country Flag

Posted 24 July 2007 - 10:55 AM

You know how you can check your XP partition for errors at startup because it can't check for errors while XP is running... well how do you do that for all drives. I want to check for errors, not while windows is running, but at startup. Is there a way you can pick and choose which drives you want scanned at startup?

Thanks.


#2 User is offline   killerb255 

  • Member
  • PipPip
  • Group: Members
  • Posts: 104
  • Joined: 26-May 07

Posted 24 July 2007 - 12:38 PM

Your best bet would probably be to create a scheduled task that edits the autochk registry key to automatically check all drives on reboot, then resets the key (otherwise, autochk will run on every reboot).

Or...you can create a batch file that runs off of your Scheduled Task with a series of questions asking you if you want to check certain drives. If yes, then it gets entered into the

The reg key is:

HKLM\System\CurrentControlSet\Control\Session Manager

Under that is a string value. The default is:

BootExecute = autocheck autochk *

The asterisk means that no drives are being checked on startup.

I'd give this a read before doing anything:

http://www2.isye.gatech.edu/~mgoetsch/cali...nofCHKDSK_F.htm

#3 User is offline   GrofLuigi 

  • GroupPolicy Tattoo Artist
  • PipPipPipPipPipPip
  • Group: Members
  • Posts: 1,275
  • Joined: 21-April 05
  • OS:none specified
  • Country: Country Flag

Posted 24 July 2007 - 08:36 PM

If you want to shedule drive E: for checking on next startup you would open a comand prompt and type:

fsutil dirty set E:


or even put it in a bach file or whatever.

Reference.

GL

#4 User is offline   spacesurfer 

  • Pharmassist
  • Group: Patrons
  • Posts: 1,668
  • Joined: 31-July 04
  • OS:Windows 7 x86
  • Country: Country Flag

Posted 25 July 2007 - 07:30 AM

thanks for reference.

#5 User is offline   bucketbuster 

  • Senior Member
  • PipPipPipPip
  • Group: Members
  • Posts: 649
  • Joined: 16-November 03

Posted 26 July 2007 - 07:21 AM

Use Scandefrag :whistle:

#6 User is offline   spacesurfer 

  • Pharmassist
  • Group: Patrons
  • Posts: 1,668
  • Joined: 31-July 04
  • OS:Windows 7 x86
  • Country: Country Flag

Posted 31 July 2007 - 02:39 PM

Thanks for great info!

#7 User is offline   spacesurfer 

  • Pharmassist
  • Group: Patrons
  • Posts: 1,668
  • Joined: 31-July 04
  • OS:Windows 7 x86
  • Country: Country Flag

Posted 07 August 2007 - 12:45 PM

I'm having a problem with my I: partition. I set this partition to be dirty. Now, everytime at startup, it checks the disk for errors and hangs up at the end when it says "USN journal verification etc etc completed."

I don't understand why it hangs when it says it's completed. Anyway, I have to press the reset button to restart and Windows comes up normally. However, next time I shutdown, the same thing happens.

How do I manually get it to reset the dirty bit? The MS page only explains how to set it, but not undo the set.

(I types fsutil dirty query I: and it stated the drive is dirty. So I want to restore to not being dirty.)

There is a file called bootex.log that resides in this I: partition and can't be deleted. When virus scan runs, Windows errors when it gets to this file stating you need to check the drive for errors. If I run it from within Windows, then it freezes at stage 4 of 5.

#8 User is offline   gunsmokingman 

  • MSFN Master
  • Group: Super Moderator
  • Posts: 2,352
  • Joined: 02-August 03
  • OS:none specified
  • Country: Country Flag

Posted 07 August 2007 - 02:58 PM

Have you tried this cmd

Quote

ChkNtfs /?

This is what Vista displays with the above cmd

Quote

Displays or modifies the checking of disk at boot time.

CHKNTFS volume [...]
CHKNTFS /D
CHKNTFS /T[:time]
CHKNTFS /X volume [...]
CHKNTFS /C volume [...]

  volume		 Specifies the drive letter (followed by a colon),
				 mount point, or volume name.
  /D			 Restores the machine to the default behavior; all drives are
				 checked at boot time and chkdsk is run on those that are
				 dirty.
  /T:time		Changes the AUTOCHK initiation countdown time to the
				 specified amount of time in seconds.  If time is not
				 specified, displays the current setting.
  /X			 Excludes a drive from the default boot-time check.  Excluded
				 drives are not accumulated between command invocations.
  /C			 Schedules a drive to be checked at boot time; chkdsk will run
				 if the drive is dirty.

If no switches are specified, CHKNTFS will display if the specified drive is
dirty or scheduled to be checked on next reboot.


#9 User is offline   spacesurfer 

  • Pharmassist
  • Group: Patrons
  • Posts: 1,668
  • Joined: 31-July 04
  • OS:Windows 7 x86
  • Country: Country Flag

Posted 07 August 2007 - 07:27 PM

I just tried that, Gunsmoking. It didn't work. So I backed up my data. Then tried to delete, recreate, and format the partition. Formatting froze the computer. I restarted in BartPE and tried to format there. It's still formatting but I see no HDD activity. I'll give it another hour and if nothing, then I'll assum something else is wrong.

I've been getting a lot of errors on that drive. I recently noticed after a chkdsk some bad sectors (640 k) on that drive. I've gotten a lot of iastor.sys errors in system log in computer management. And also some error called ESET error. Wonder if it's my MOBO's SATA port or is it the hard drive itself?

I'm not sure what's happening here. SATA port or bad hard drive? It's 1 year old - Maxtor MaxLine II 300 Gb. Running it as AHCI. Twice, the drive disappeared from my computer. Once, when I started XP, it wasn't there. I restarted and there it was. Second time (yesterday), it vanished while XP was running!

Frustrated.

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

2 User(s) are reading this topic
0 members, 2 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2013 msfn.org
Privacy Policy