• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Crazy WD problems and dvd burner question

Phosphers

n00b
Joined
Feb 7, 2003
Messages
53
Last week we had several power outages, afterwords windows flipped out about my WD drive. Not an outright falure but it only reads at 200k/sec now and pegs the CPU load to 100%. Only this drive is affected. Won't pass scandisk :(.
Also, it seems my dvd burner is stuck on ata33. I somehow lost my boot sumary screen so I can't tell if setting the PIO mode affects anything.
 
For the hard drive, it's probably toast. Take it as a lesson in the value of quality power protection like line conditioners/in line battery backups. To make sure, run WD's diagnostic tools and follow their RMA procedure if the drive is still under warranty.

As for the DVD Burner, ATA33 should be fine - 8X is less than 12MB/sec, 16X fits under 24MB/sec (I can't remember the exact values, but IIRC 8X is something just over 10,000KB/sec). Both of these figures are well within the 33MB/sec of ATA-33.
 
DougLite said:
For the hard drive, it's probably toast. Take it as a lesson in the value of quality power protection like line conditioners/in line battery backups. To make sure, run WD's diagnostic tools and follow their RMA procedure if the drive is still under warranty.
Running the diagnostics is a great idea, but sometimes the diagnostic utility does not label a "poor performing" drive as defective. This happened to me very recently where my system was reading from the drive at 2MB/s. Ran v5.04c of the diagnostics (took well over 3 hours for a 250GB drive) and the drive passed all tests successfully. Then I ran v4.xx and it labeled the drive as defective. I ended up submitting the RMA with an attached screenshot of the HDTach numbers and WD created an RMA.

Anyway, I am not discounting this advice. It should always be the first step in troubleshooting supposed HDD failures by running the diagnostics. Unfortunately the diagnostics are not 100% conclusive.
 
Back
Top