Disk check on startup

  • Thread starter Thread starter =?ISO-8859-1?Q?YankFan_=AE?=
  • Start date Start date
?

=?ISO-8859-1?Q?YankFan_=AE?=

Evey time I start my computer it wants to run diskcheck on one of my
partitions. Why is it doing that?

Thanks in advance
--
 
A volume (Partition) can either be in one of two states, Clean or
Dirty. Essentially, Dirty means that the drive has inconsistencies
on it. ( Files or Folders have issues ). When the Dirty bit gets set
XP will attempt to run Chkdsk at startup to find and resolve the
inconsistencies on it. What you probably need to do is queue up
a Chkdsk with the /F or /R (Fix or Repair) qualifier. This causes
XP to run a 5-Phase Chkdsk on the drive. However, it's possible
that in making corrections to the volume Chkdsk may remove
data from the drive. Always have data backed up before turning
a Chkdsk C: /F loose on the drive.
To run a full Chkdsk:
1.) Start, Run (Type) Cmd [Enter]
2.) Chkdsk C: /F
System will respond that the drive cannot be locked, and would
you like to run the Chkdsk at the next reboot - Answer Y
3.) Exit ( Cmd Prompt Window)
4.) Reboot the PC
 
R. McCarty said:
A volume (Partition) can either be in one of two states, Clean or
Dirty. Essentially, Dirty means that the drive has inconsistencies
on it. ( Files or Folders have issues ). When the Dirty bit gets set
XP will attempt to run Chkdsk at startup to find and resolve the
inconsistencies on it. What you probably need to do is queue up
a Chkdsk with the /F or /R (Fix or Repair) qualifier. This causes
XP to run a 5-Phase Chkdsk on the drive. However, it's possible
that in making corrections to the volume Chkdsk may remove
data from the drive. Always have data backed up before turning
a Chkdsk C: /F loose on the drive.
To run a full Chkdsk:
1.) Start, Run (Type) Cmd [Enter]
2.) Chkdsk C: /F
System will respond that the drive cannot be locked, and would
you like to run the Chkdsk at the next reboot - Answer Y
3.) Exit ( Cmd Prompt Window)
4.) Reboot the PC

YankFan ® said:
Evey time I start my computer it wants to run diskcheck on one of my
partitions. Why is it doing that?

Thanks in advance
Click to expand...
I did all this and still it wants to check it after every reboot or start.

--


YankFan ®
<http://yankfan.blogspot.com/>
Support Our Troops:
<http://www.anysoldier.com/index.cfm>
Freedom isn't free. Just ask any soldier...Semper Fidelis
Click to expand...
 
YankFan said:
Yes I did and it still doing the check after reboot.
Click to expand...

Then run a diagnostic on the hard drive. Get the utility from the drive
mftr.'s website. If you don't know the mftr. or can't find the utility
at their site, use Seagate's SeaTools (Desktop version). You will
create a bootable floppy or cd with the file you download. You will
need third-party burning software to create the cd.

If necessary, change the boot order in the BIOS to boot from the optical
drive first, hard drive second. Boot with the utility and do a thorough
test on that drive. If the drive has any physical errors, back up your
data and replace the drive.

If the drive has no physical errors but shows file system problems, back
up your data and format the drive.

Malke
 
Evey time I start my computer it wants to run diskcheck on one of my
partitions. Why is it doing that?

Thanks in advance
Click to expand...

You said, "it wants to", so I'll assume you are not
letting it?

It sounds like maybe there was an improper shutdown.
Try letting it run through the check and perform a
proper shutdown and then see if it still does it.

--

"Verily I say unto you, This generation shall not pass,
till all these things be fulfilled." - Matthew 24:34

Sleep peacefully, God is awake.
 
YankFan said:
R. McCarty said:
A volume (Partition) can either be in one of two states, Clean or
Dirty. Essentially, Dirty means that the drive has inconsistencies
on it. ( Files or Folders have issues ). When the Dirty bit gets set
XP will attempt to run Chkdsk at startup to find and resolve the
inconsistencies on it. What you probably need to do is queue up
a Chkdsk with the /F or /R (Fix or Repair) qualifier. This causes
XP to run a 5-Phase Chkdsk on the drive. However, it's possible
that in making corrections to the volume Chkdsk may remove
data from the drive. Always have data backed up before turning
a Chkdsk C: /F loose on the drive.
To run a full Chkdsk:
1.) Start, Run (Type) Cmd [Enter]
2.) Chkdsk C: /F
System will respond that the drive cannot be locked, and would
you like to run the Chkdsk at the next reboot - Answer Y
3.) Exit ( Cmd Prompt Window)
4.) Reboot the PC

YankFan ® said:
Evey time I start my computer it wants to run diskcheck on one of my
partitions. Why is it doing that?

Thanks in advance
Click to expand...
I did all this and still it wants to check it after every reboot or
start.
Click to expand...

Try running the full chkdsk from the Recovery Console (first "Repair" option
on the XP CD).
Click to expand...
 
YankFan ® said:
Evey time I start my computer it wants to run diskcheck on one of my
partitions. Why is it doing that?

Thanks in advance
Click to expand...

XP will do that if one of the partitions is FAT32 or FAT16 and not NTFS.
Check in Disk Manager to see if one of your disks is not formatted in
something other than NTFS. If that's the situation, then you have the
choice of converting to NTFS. I'd move the files on it to the main
partition first, tho, then move them back after formatting. HTH..JG
 
XP will do that if one of the partitions is FAT32 or FAT16 and not NTFS.
False.

Check in Disk Manager to see if one of your disks is not formatted in
something other than NTFS. If that's the situation, then you have the
choice of converting to NTFS. I'd move the files on it to the main
partition first, tho, then move them back after formatting. HTH..JG
Click to expand...

Absolute nonsense.

Whether the file system is FATxx or NTFS, the circumstances that cause
AutoChk (the automatic check on startup) are identical, namely...

1) A bit is set to indicate file system writes were interrupted

This is the most common cause, and happens after Windows crashes,
resets, fails to shut down properly, or is switched off or reset by
the user. When this happens, files that were being written will be
incomplete, and the next startup detects the relevant status bit and
"fixes" the file system. This does NOT recover data, which is:
- typically damaged by the "fix"
- made to look as if it is no longer corrupted
Also, cues that could be used for manual repair are lost.

Sometimes you will see this even after what appears to be a proper
shutdown. Unless this is (2), (3) or (4), this would most likely be
due to an ATX power off that occurs before the data is writen from the
hard drive's internal cache RAM to the actual platters.

2) A different bit is set to indicate a disk access failed

This indicates impending hard drive failure, and once again the
relevant bit (a different one this time) will cause AutoChk to "fix"
things. This time a full surface scan is done, which takes a long
time. Note that no previous bad exit is required to trigger this form
of AutoChk; any failed disk access at any time during the last Windows
session will cause this, even if you did shut down properly.

If this is the cause, then attempting to convert the file system from
FATxx to NTFS is one of the worst things you can do!

3) You did a ChkDsk /F or /R on a volume that was in use

C: is *always* in use, which means that whenever you try to do a
ChkDsk /F or /R (to "fix" file system, and do that plus a surface
scan, respectively), you will be advised that the system is set to
perform this operation on the next boot. AFAIK, this is done by
setting the relevant bits as per (1) or (2).

4) You have explicitly set ChkDsk to run on startup

This can be ChkDsk in the startup axis, or set as a Task to be run on
startup or on account logon.

See http://cquirke.mvps.org/ntfs.htm

Number 1 myth: "NTFS doesn't suffer data corruption on bad exits" (or
even more absurdly, "NTFS doesn't suffer data corruption").

All that NTFS' transaction rollback does, is revert to the last good
metadata (i.e. discarding any changes that were in progress). The
"user" data (i.e. the actual data within the file's cluster chain) is
not preserved at all, so the outcome is as bleak as for FATxx, except
there are no low-level recovery tools for NTFS.


------------ ----- ---- --- -- - - - -
Click to expand...
The most accurate diagnostic instrument
in medicine is the Retrospectoscope
 
cquirke (MVP Windows shell/user) said:
Absolute nonsense.

Whether the file system is FATxx or NTFS, the circumstances that cause
AutoChk (the automatic check on startup) are identical, namely...

1) A bit is set to indicate file system writes were interrupted

This is the most common cause, and happens after Windows crashes,
resets, fails to shut down properly, or is switched off or reset by
the user. When this happens, files that were being written will be
incomplete, and the next startup detects the relevant status bit and
"fixes" the file system. This does NOT recover data, which is:
- typically damaged by the "fix"
- made to look as if it is no longer corrupted
Also, cues that could be used for manual repair are lost.

Sometimes you will see this even after what appears to be a proper
shutdown. Unless this is (2), (3) or (4), this would most likely be
due to an ATX power off that occurs before the data is writen from the
hard drive's internal cache RAM to the actual platters.

2) A different bit is set to indicate a disk access failed

This indicates impending hard drive failure, and once again the
relevant bit (a different one this time) will cause AutoChk to "fix"
things. This time a full surface scan is done, which takes a long
time. Note that no previous bad exit is required to trigger this form
of AutoChk; any failed disk access at any time during the last Windows
session will cause this, even if you did shut down properly.

If this is the cause, then attempting to convert the file system from
FATxx to NTFS is one of the worst things you can do!

3) You did a ChkDsk /F or /R on a volume that was in use

C: is *always* in use, which means that whenever you try to do a
ChkDsk /F or /R (to "fix" file system, and do that plus a surface
scan, respectively), you will be advised that the system is set to
perform this operation on the next boot. AFAIK, this is done by
setting the relevant bits as per (1) or (2).

4) You have explicitly set ChkDsk to run on startup

This can be ChkDsk in the startup axis, or set as a Task to be run on
startup or on account logon.

See http://cquirke.mvps.org/ntfs.htm

Number 1 myth: "NTFS doesn't suffer data corruption on bad exits" (or
even more absurdly, "NTFS doesn't suffer data corruption").

All that NTFS' transaction rollback does, is revert to the last good
metadata (i.e. discarding any changes that were in progress). The
"user" data (i.e. the actual data within the file's cluster chain) is
not preserved at all, so the outcome is as bleak as for FATxx, except
there are no low-level recovery tools for NTFS.



The most accurate diagnostic instrument
in medicine is the Retrospectoscope
Click to expand...

I stand corrected. I should have said that once when assembling a computer,
XP gave me a message that it was running Chkdsk because of a logical drive
that I had left in FAT 32. Dunno why, but when I formatted it in NTFS the
message stopped. Evidentally that was idiosyncratic and not a
characteristic of XP in general. J
 
Back
Top