01-22-2009 12:22 PM
I'm troubleshooting a problem with my backups producing 'delayed write failed' error messages in Windows XP. I use EMC Retrospect Express 7.x and noticed my backups would begin to fail once it started working with data that was on my ST3250410AS. I did a little research and found that this problem could happen if the wrong driver was installed for my hard disk, which is a secondary storage drive. When Windows XP finds the drive, it recognizes it as a ST3250410AS, but once it is installed, Device Manager lists it with the generic entry of "Disk drive". Since this seems to be an incorrect driver problem, what's the easiest way to get it to detect properly? I've tried removing it from Safe Mode and having it redetected with the same results. My system board is an ASUS P5K-E.
Your help is appreciated.
Solved! Go to Solution.
01-22-2009 12:29 PM
i think your board has an intel chipset. these and nforce controllers seem to be the worst. try turning off ncq and write caching
in your device manager or ideally find a controller that isnt intel/nforce. i use a sil3132 based controller.
01-22-2009 12:38 PM
actually you might have a seperate controller built in, my gigabyte 965p-ds3 has 4 sata on the intel chipset and 2 on a seperate
gigabyte controller the intel are orange and the gigabyte are purple.
01-24-2009 12:23 PM
Actually, it's the P35 chipset. All of my other drives have been detected properly. It's only the Seagate drive that shows up as 'Disk drive' in Device Manager. ????
01-24-2009 10:09 PM
"ST3250410AS detected as "Disk drive" in Windows XP"
id be more worried if it wasnt.
Honestly, try a different controller.
01-25-2009 11:45 PM - edited 01-30-2009 10:54 AM
I've been using boards that incorporate Intel-based chipset for years without problems. In fact, I don't really trust anything else. My Western Digital drive is not experiencing the same problem and is correctly identified by Windows XP.
Thanks for your feedback. Has anyone else experienced this problem? Any input from other users would be greatly appreciated.
UPDATE 1/30/09: I ended up resolving this by removing the drive in Safe Mode and removing its entries in the registry, allowing me to redetect it upon reboot. However, the backup issue was corrected by disabling compression during the backup. It appears it was trying to compress very large AVI files on the drive, which kept it from completing the backup properly. I still feel unsure about the time it took to complete the backup (specifically with the Seagate drive), so there still may be an issue with it. For now, everything appears to be O.K.