Saved Bookmarks
| 1. |
Solve : Hd detected but specifications (manufacturer) misidentified....? |
|
Answer» ....120gb ata 133 hard drive by maxtor is identified in device manager with a different (garbeled but similar) name so when I try to use maxblast to repair the drive so I can scan for viruses etc... maxblast errs out not recognizing the drive. Is this information provided to the system by firmware or by a service sector on the hard drive media? If by firmware I guess the drive is nogood. The drive currently reads as raw unformatted but there is a partition on it.Whee did you get it? Seagate ST3160215ACE 160GB Internal Hard DriveThe above was from a USA seller.Buying another hard drive does not address the problem related to this one.Well, let me put it another way. You can buy a new drive for $50. You can pay a service to recover data from the drive for maybe $200. You can hire a Super Tech to analyze the drive for $35 an hour. If he is really good and has the right tools he might find the problem inside of an hour. But he can not fix it. He will recommend a new drive. Is that what you wanted to know? Without doing laboratory tests, all I can do is say that statistically the possibility of the drive being salvageable with that kind of error is under that 2% because the area where that information is stored is not used except when the system starts up. Errors in sectors on a hard drive are from either wear or a defect in manufacture. If that sector was recoverable, the built in firmware would have made the fix. Now if anybody else on this forum knows exactly how the error happened, please let him speak up know. BTW, have you a log for how long the drive was in use? If it has 5000 hours or more, you got fair service from it. This is not meat to be sarcasm It just comes out that way. Quote from: thundershadow on January 12, 2011, 05:18:14 PM Is this information provided to the system by firmware or by a service sector on the hard drive media? Firmware. You could try swapping out the logic board from an identical model drive into that one, this would allow you to access the data on the drive if the problem is the logic board. Usually the drive showing up with a garbled name indicates either a drive logic board failure, or a defective data cable or (in some cases) an incorrect jumper setting. I've never seen a drive that failed as a result of things like head crashes and failures with the disk/data mechanism report it's name incorrectly; GENERALLY that points to a problem with the logic board. Quote from: Geek-9pm on January 12, 2011, 08:25:04 PM BTW, have you a log for how long the drive was in use? If it has 5000 hours or more, you got fair service from it. Are you serious? what do you do? have a notepad OPEN on your desk with scrawled notes? Quote from: Geek-9pm's drive log Turned on computer and thus drive. Used it for 3 hours; this brings the grand total up to 127 hours of operation.etc... seriously? a "log for how long the drive was in use"? Who keeps that? Quote from: Geek-9pm on January 12, 2011, 05:40:29 PM If the firmware was bad, the drive would not work at all.Absolutely wrong. Firmware can get corruptedand still work properly. Either that or I managed to defy your LAWS of hard drive mechanics because I accidentally corrupted one to the point where it's ID as far as the BIOS was concerned was a rather long garbled string. I distinctly recall the SMILEY faces and how it turned half the EPA logo red when the BIOS listed the HD name. the drive still worked for storing and retrieving data just fine, at half it's original size (for some reason). Thank you BC. I have one drive with over 5000 hours on it and it failed. I never thought about replacing the logic board. I might try that. If it works, I can keep my log book up to date.Thanx for the responses. I`m going to look into the data cable possibility. That cable did get migrated from my primary to my secondary controller while I had replaced that hd. I thought maybe if that were possible it would have reported that it wasn`t an 80 conductor cable while it was attempting to mount the drive but I guess it is possible to miss if it is a intermitten connection. My case is rather small so I`m using a docking bay to double duty my 5.25 expansion slot and maybe that also is SOMETHING to look at.I reseated the hd in my docking bay and replaced the ribbon cable. It seems to have solved the problem. What started the cascade of crap was a loose power connection on the hd. It would cause the tell-tale smashing head sound (clicking). Since I have had trouble with the related hd in the past I didn`t recognize the problem was from the power connector instead. Thanx again for the input. Quote from: thundershadow on January 13, 2011, 11:52:13 PM I reseated the hd in my docking bay and replaced the ribbon cable. It seems to have solved the problem. What started the cascade of crap was a loose power connection on the hd. It would cause the tell-tale smashing head sound (clicking). Since I have had trouble with the related hd in the past I didn`t recognize the problem was from the power connector instead. Thanx again for the input. At least it had a inexpensive solution |
|