My system was working fine until three days back, it started giving me problems....

Configuration is:
P4 1.7GHz
Windows XP Professional
Harddisks 200GB(Primary) and 80GB(Slave) are being used
Mercury Motherboard
Drives Present: C,E,F on Primary and D,G,H on Slave

Whenever i start my computer, it takes a long time and then starts scan disk and asks if it can scan my H drive. I let it continue but then is comes up saying that H is a non win xp drive and that it'll not continue. Then continues to start Windows... Takes a lot of time and then hangs up at the startup screen and then starts after 10 minutes. And then pops a message from the System Tray saying that "Windows was unable to connect to all drives"....

I thought maybe some files were corrupted and so used Acronis True Image and restored an image which was 1 month old... To my utter surprise... The problem still continues... I presume that the problem might be with the power supply cable ot data cable but i'm not sure exactly...

I tried even removing my 80GB Slave Harddisk hoping to solve the problem but it is still prevailing.... I'm desperately behind my computer because all my project files are stored in H drive... Please help me...

Dani AI

Generated

Good points from , and about running disk checks. Since restoring an Acronis image did not stop the symptom, the problem is more likely a hardware/controller issue or Windows is trying to reconnect a drive that no longer exists or is a different device (removable/card reader or mapped network share). The next checks should focus on identifying what “H:” actually refers to, and protecting data before making changes.

First, identify the device behind H: open Disk Management (diskmgmt.msc) and Device Manager (devmgmt.msc) to see whether H is a local partition, a removable/card-reader volume, or a mapped network drive. If Disk Management shows a volume as RAW or “Unknown,” do not initialize it — that will overwrite headers. Copy important files off the disk first (attach the drive to another PC or use a USB/IDE adapter) or use a recovery tool before attempting repairs.

Second, do hardware and BIOS checks: enter BIOS to confirm which drives the motherboard detects at POST. Swap IDE/data and power cables, try the drive on a different IDE channel or another PC, and verify jumper settings if the drive is PATA. Slow or missing device detection points to a failing drive, cable, or controller rather than a Windows-only problem.

Third, rule out mapped-network or startup references: the tray message you quoted often means Windows failed to reconnect a mapped network drive. Check mapped drives in My Computer (Disconnect Network Drive), list active mappings (net use) and review msconfig Startup entries. Also inspect Event Viewer (eventvwr.msc) for disk/controller errors (I/O or NTFS events) to guide diagnosis.

If data on H is critical and the drive shows hardware faults or RAW filesystem, prioritize cloning or professional recovery before further attempts to repair.

Recommended Answers

All 3 Replies

Try scanning all your partitions from the .

You will want to execute the following command for each partition:

chkdsk [drive] /r

For example:

chkdsk c: /r

This will scan all your drives for file system errors or bad sectors. It is possible that, for one reason or another, your partition got corrupted.

I have seen that before, I was able to fix by going to run/cmd

and then run chkdsk from there. It will run then at next boot up, and fixed the problems after it ran.

I have seen that before, I was able to fix by going to run/cmd

and then run chkdsk from there. It will run then at next boot up, and fixed the problems after it ran.

Actually, the chkdsk from Recovery Console is a much more rigirous check than the one run from cmd. Try running chkdsk from Recovery Console

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.