General discussion

XP keeps checking my disk at boot

I keep getting a message the my D: drive needs to be checked everytime I boot. I've let it run to completion as well as running chkdsk manually. No errors are found. Any ideas why this keeps happening on reboot and what I can do to stop it?

I'm running XP pro if that matters. This is not the boot drive. It's an SATA drive which has been working fine for months.

Discussion is locked
Reply to: XP keeps checking my disk at boot
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: XP keeps checking my disk at boot
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
- Collapse -
(NT) (NT) Is it FAT32?
- Collapse -
(NT) (NT) No. NTFS
- Collapse -
Is it over 127GB?

There are some issues only addressed in SP2 that we ran into with >127GB USB 2.0 drives. Your post is a little light on details so I'll comment on one likely item at a time or you can post more details.



- Collapse -

Thanks for your help. I'm running xp pro sp2, current with all security patches, etc. Drive is a 250GB SATA drive. What other details do you need?

- Collapse -
That clears up that one. How about this one.

We've covered just about all the usual and known items except you never shared a complete list of what's in the machine. For instance the above discussion is about a specific board with a known SATA bug. With each post you see a request for all your system info, including operating system, model number, and any other specifics related to the problem.

I don't mind working and trying it from the most likely and seeing what you can supply, but it goes faster with a complete post.



CNET Forums