• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

HELP ME :( ! My second hard disk is weird...

AlbertHK

Junior Member
I have my 2 hard disks connected to my system via a Promise Ultra 133TX2 card. they are both 70 gig Western Digital Drives and I am running WinXP. For some reason every time I start up. Windows wants to run CheckDisk (chkdisk) on drive D:, and when I lef chkdsk run, it wont even perform the check for consistency, it just stays at 0 Percent Completed. And when I'm in windows, i can read and view files perfectly fine located on that drive [D:], but now i can't seem to transfer/save ANYTHING to it anymore, and When I attempt to my system locks up like an opossum. My computer needs a doctor....Has anyone had this problem? Any ideas? I'M STUMPED AND NEED HELP!

ALSO-during startup my hard drive(s) will spin back down and stuff

 
Sounds like one or more of hte drives is physically failing. When WinXP auto-runs CHKDSK at startup, but the progress-bar stays at zero "forever", that means that it is doing the more-intensive "surface-scan", instead of simply checking the filesystem for consistency. This is triggered by the OS setting one of the filesystem's "fail bits" indicating some sort of physical/device-level problem.

These same sorts of problems can cause then entire OS to freeze, for as much as several minutes at a time, when attempting to access the HD.

I would download the "Western Digital Data Lifeguard" diagnostics bootable floppy (on a different system, possibly), and then boot your system with that to test the drive.

You should probably also do some isolation-testing too, disconnect one of the drives completely from the system (don't forget to set the WD drive to the "single" jumper setting, not "master" - jumper removed, usually), and then use WD DLGDIAG disk to test each one individually.

This will help isolate whether or not both are showing failure symptoms, or just one, even those both may appear to fail if they were connected onto the same shared IDE channel.

Second, spin-up problems at boot, can be caused by bad power or IDE cables/loose connections, drive firmware/hardware issues, or lack of adequate power/poorly-regulated power (failing/under-powered PSU). That's one other reason to test each drive individually, if both test ok singly, then it could be an overall power issue, or a cable issue.

Heat/vibration/abuse are not good things for HDs either, if the HDs aren't kept properly cooled, WD ones have been known to "lose" sectors, and similar system freezes, first intermitten, and then chronic, and then loaded to a crash/Bsod, are aften symptoms of an overheating drive.

OTOH, if the system, after being powered-off and cooled-down for some time, freezes every time, when accessing specific files/directories, then there is likely to be a bad spot on the disk or it is otherwise failing.

IDE HDs spinning back down during bootup, are often due to power or cabling problems, or the HD is failing internal self-tests that it does during booting/spin-up,and shuts down for safety.

Btw, I'm not familiar with 70GB WD IDE HDs, are those 10K RPM Raptors, by any chance? Those need active cooling, for certain. I'm going to assume that they are just standard 80GB IDE HDs, who format out to something like 73GB, I think. My WD 80GB JB drive shows as 74GB physical capacity.

 
Originally posted by: AlbertHK
Larry you rock. Its fixed 🙂

Care to give any insight on what exactly was the problem? Also, what specifically fixed the problem. It might be helpful for anyone experiencing the same problems...

I also like to learn what people do that ends up working. 😉
 
I ran the Western Digital Diagnostic tool and it found nothing wrong with the drive. and nothing was wrong with my SCSI card either, so i crawled inside the case to find that the power cable to my HD after testing wasnt supplying enough power. turns out my whole PSU was pretty dead from the get go, so I swapped it for a 500 watt and everything is dandy now 🙂
 
Back
Top