• 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.

someone knowlegdeable about HD's PLEASE HELP!

jhp612

Member
Hi,

I currently own 2 60 GXP IBM drives and they have failed on me about 5 times now ( In about 5 months) I called IBM and they tol dme to use the drive fitness test utility and each time they resulted in error code 0x70 or 0x77. I erased the drive using thi sutility formatted ect and then it happened again. The next time i called IBM tech suppot they told me that it wasnt a IBM problem but a problem with windows and its cache writting. they referred me to :

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q281672


I was wondering if this made sense of if you guys thought it was jus another one of the GXP drives that went bad and for which IBM is now in a lawsuit for. I canRMA the drives for like 36 buxks (shipping ect). Is it really a windows problem? if so i should just wait unti microsoft releases a path and save myself 36 bucks. please helP!!! ANYBODY!!!
 
What OS are you running? And what do you mean exactly by 'they have failed on me about 5 times now'.
Bill
 
I am running XP. What i mean by failed 5 times is that they will suddenly stop woking and make a strange sound. I can boot from a floppy drive and then use the IBM drive fitness utility and then use the erase disk (goes through and eaces sector by sector). then it will work, until the cycle starts over again.
 
Ok, I wasnt sure if it appeared the OS was getting corrupted or the drives where actually acting 'weird'. From the symptoms you post, I don't see how the article IBM refered you to could apply, the symptoms of that are corrupted os files (the registry hives for example). I don't see how that issue could in anyway cause a drive that would stop working and 'just click' until a test program was run, sounds to me that something else is definately going on with those drives.
Bill
 
Back
Top