|In my experiences with IDE hard drives that have failed, about a dozen or more, there has never been one that had data on it that was worth the effort of trying to replace the pc board, or removing the disk(s) inside the drive and installing it(them) in another drive, so I have not tried that myself.|
I was not aware that exactly the same model can have a pc board that won't even fit. I have only participated in RMAing one drive for a friend, a Maxtor 80gb, and the refurbished replacement drive was absolutely identical to the drive that failed. We chose the option of having them send a replacement drive to my friend first, then sending back the failed drive within a specified short time period, so I was able to compare the drives.
I don't know for sure, of course, but I would think even if the pc board is different, a drive of the same capacity made about the same time would have the data organized on the disk(s) the same way (interleave, the width and spacing of the tracks, how physical secors relate to logical sectors, etc.), so I would think, if nothing else, removing the disk(s) and installing them in the replacement drive should work.
Of the failed drives I have dealt with........
Only one failed because it would no longer spin.
Only one made an oddball noise while failing, other than thrashing - the above mentioned Maxtor 80gb drive - like a high pitched buzzer - occaisionally at first, then more often within a short time (a couple of days) , and then the drive wouldn't work at all.
Some of them made thrashing noises a short time after having been started up - the drive moving the arms/heads randomly - after they had been on long enough for things to warm up.
I found most of them had one or more IC chips on their pc board that got a lot hotter than they should have - if I placed my fingertip on them while the drive was running they were hot enough I could not keep my fingertip on them without feeling I would be burning my finger, wheras on a drive that works fine they never get that hot.
I had some success with some of them when I removed the drive from where it was mounted and positioned it so I could blow a lot of air directly at it's pc board with a household fan. The drive would work okay for a longer time after having been started up after having cooled to room temp until the chip(s) on the pc board got too hot . But - after a short time, that no longer was of any help.
Obviously when the pc board on the drive malfunctions the data on the disk(s) inside the drive is likely to get messed up.
I would think that if the pc board is replaced with a compatible one, or if the disk(s) is(are) transferred to another drive that is compatible with the way the data on the disk(s) is(are) organized, one should be able to repair at least some of the damage done to the data, and be able to recover at least some of it intact.
However, whether the specific data you wanted to retrieve can be recovered is rather random.
"No, the drive does not show up in disk management..."
"...the drive does show up in the BIOS. But it ONLY shows up in the BIOS (besides linux)."
"Gparted is what I was using and the drive did not show up under where all the drives are listed..."
"Ok, fdisk says that it cannot find the partition table and mbr
for the disk..."
"....tells me that the partition table for the drive I am trying to fix is missing."
"159 SMART Error SMART Error S elf M onitoring, A nalysis, and R eporting T echnology (SMART) Error returned during SMART Status/Self Test Command. S Elf M onitoring, A nalysis, and R eporting T ECHNOLOGY (SMART) Error returned during SMART Status / Self Test Command. The drive is defective. The drive is defective. Replace. Replace."
You can't get user data off the drive until at least the partition table(s) have been repaired, if not both the mbr and the partition table(s). FAT32 partitioning has two partition tables, NTFS has one (the MFT; Master File Table).
It is probably a huge waste of time to try to repair the partition table(s) before replacing the pc board on the drive or transferring the disk(s) in the drive to another drive.
I think it's extremely unlikely this 20gb drive has a software drive overlay on it. That would only have been needed if the mboard it was installed on was relatively old, say, older than the mid 90's, and it's bios wouldn't recognize a drive larger than 8gb because of bugs in the bios code.
" Ever since I plugged the drive in xp, it started asking me for some scsi driver, though when I go through driver installation, it says cannot install hardware.'
Did the mboard you have it hooked up to have a SATA controller as well?
If yes, had you installed the drivers for it previously? They're not built into XP.
If not, whatever is wrong with the pc board may be causing the board to be wrongly detected as a SCSI controller, and/or the IDE drive to be wrongly detected as a SCSI drive.
2000 and XP have a lot of built in support for detecting and automatically installing the drivers for SCSI controllers, but some you have to install the drivers for.
Windows has had built in support for SCSI controllers for a long time, and for controllers it doesn't have drivers for the SCSI drivers can be installed and then use that built in support.
When 2000 and XP were first released, there was no such thing as SATA drive controllers. The drivers for SATA drive controllers are written to use the existing SCSI support already built into Windows, so when SATA controller drivers have been installed, when you look in Device Manager you see at least one entry for a SCSI controller, and you may not find anything at all about SATA in Device Manager unless the label for the controller specified in it's *.inf file to be shown in Device Manager has the text SATA in it.