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

So what happened to this HD?

McCarthy

Platinum Member
IBM 60GXP started developing bad sectors.
Took it out to send off for RMA.
Put it back in last night just to double check that I'd grabbed everything good off it. Back in as Master on it's channel alongside the Maxtor it'd been sharing the channel with previously (a CDrom was master in the time the IBM drive was out).

Anyway, there's the leadup to the story. Put the drive back in, booted, it detected fine, W2K starts...starts SLOW, gets to the desktop and hangs. Finally hit reset and let it try again. Same thing. Pull the drives out, setup the IBM as single, take the Maxtor out, reboot. Starts up ok, but the IBM shows only jibberish for the folder names in Explorer.

No biggie, was just double checking before the RMA.

Take it out, put the Maxtor and the CDrom back in. Boot up, look in Explorer a little later and the Maxtor is all jibberish as well. Somehow the FAT on this drive was hosed completely. Norton Disk Doctor wouldn't fix anything, (mistakenly) let Scandisk run and it converted a few loose fragments to those useless CHK files - 1gig of CHKs off a 75% full 40gig drive. So now after having run Scandisk I figure I've ruined my shot at recovering the drive, but I'm still curious - What Happened?

Anyone have any ideas? The IBM was working before, just had developed some bad sectors. Nothing like this though. And how would it have managed to corrupt the Maxtor? I'm drawing a blank, thought maybe just by coincidence I'd broken a wire in the cable or something, but can't find any damage there.

--Mc
 
Yup, up to date. Drive came out of this same system and hasn't been exposed elsewhere, so if there was a virus the virus would have had access to the Maxtor all the time the IBM has been out. Reasonable idea, but can't see that would be it in this instance. Then again can't see what it is either. Most frustrating, but I checked for virus updates anyway just for good measure after your reply. Turns out the autoupdate had already grabbed the latest and autoprotect is still on.

--Mc
 
Have you checked your mobo? Bad cable? Bad IDE controller? Because of the gibberish, I was thinking it was a virus but I've seen wacky IDE controllers corrupt hardrives.
 
Back
Top