Metspitzer wrote:
I have a friend who is too lazy to post his own problems. He bought a
high capacity drive. The drive started running chkdsk at reboot. He
got a replacement from Seagate. The second drive is also running
chkdsk at startup.

Since this happened on two brand new drives, I told him that getting a
new controller card may help.

He has been still writing to the drives while waiting on the
controller card.

Does chkdsk fix errors, or just mark sectors as bad? Anyone else
think a controller will fix his problem?

CHKDSK can stay in a loop, running at each startup of the system.
There is a "dirty" flag, which can be set, to indicate the file
system needs to be checked. And sometimes, the flag doesn't get
cleared after CHKDSK runs. Maybe your problem is something like
that.

fsutil dirty query C:

http://technet.microsoft.com/en-us/l.../bb490641.aspx

The flag can be queried or it can be set (to request a CHKDSK),
but it cannot be cleared with that command. And the location
of the flag is not documented on purpose, so people cannot bypass
it. It is only supposed to be cleared, when CHKDSK is happy.

You can try booting the Recovery Console using the WinXP disc,
and do a chkdsk from there. Perhaps that might clear the flag.

The options available in chkdsk, vary depending on where you
run it from. The options in Recovery Console are different than
the ones elsewhere. These are a couple links from my bookmarks.
The second one is pretty easy to read.

http://support.microsoft.com/kb/314835/EN-US/#/

http://www.answers.com/topic/chkdsk-1

Paul