Hello people!

Sorry but my cam and english is so bad.. =)

I'm from Brazil.

This HD have a bad component:



1R2
I'm traying to found this component but i dont know his name.

Please somebody can help me?

Inductor

_________________
data recovery service[/b]

Thanx Guy!!!

for now, where in brazil i find this... =(

Are you sure it's bad? If a small piece is just broken off, it's usually still fine. Shorted inductors are difficult to diagnose. Unless if it's open?

What does it measure on a multimeter?

he was acting normal, a little slow, until he's stopped again.
and the only component that I thought was abnormal is that.

I have a multimeter but I dont know how to use in this case, can you help me?

I tried to put him on a computer but before entering in the windows he makes some noises and self shutting down.
it seems that happens in time that he will do some reading, because when i turn on the computer it is recognized and does not make any noise.


lol google tradutor is fine =)

that gone with a bang

You can measure the coil by using the Ohms setting on the meter (The symbol looks like an upside down U). It should read close to .000, maybe as high as .10 If it reads 10 or more, it's almost certainly bad. If it gets hot while the drive is on, it may be shorted, or there may be other bad components nearby. Otherwise, it's likely good, despite looking bad. The coil has a brittle ferrite casing, and it breaks easily. This is usually damaged by improper handling or installation. 99% of the time, it still works fine.

Honestly, if there is any bad component on the PCB, you will be better off replacing the entire PCB. Troubleshooting a PCB is usually difficult, and can't be done by eye (Unless if the damage is obvious). Replacing the PCB isn't easy, as you have to switch the ROM, but it will be much easier than someone who doesn't know Electronics to troubleshoot a board.

If there is actually any important data on this drive, you should seriously send it to a professional.

hummmm, ok's, i'll make tests and reply after..

Thanx a lot for the explanation.

Also, measure WITHOUT power connected to the drive. Measure with no power. Measure without power. I say this multiple times to make sure Google Translator isn't clear.

The drive has OTHER damage beyond the inductor .

Most definitely, but he won't believe it until he finds out for himself

hahaha, ok. I understand by myself.. but at the time of writing I cant do very well..

No, he just.

I believe, but for now, i cant find any PCB for this seagate..

Brazil is champion in Samsungs HDDs.. =(

Does anyone in Brazil do Data Recovery?

Bom Dia!

morning!! =)

Yes, there are some locals, especialists.
However , i have to sent because is not coming here..

News!!

I have meansured de "poor" Inductor and got 0,00 in reading. Other components like resistors and other inductors also gave 0,00. I used 200u scale.

Pictures:

Well, it's likely still good. First, the best way to test an inductor, or any part for that matter, is to test out of circuit. Second, it may only be 3uH or so. On a 200uH scale, it might be within the meter's tolerance to read 0.

If it was my drive, I'd assume the inductor is fine. They rarely go bad, and when they do, it's usually because an associated transistor shorted. If it looks burned, it likely means something else is bad. If I really thought it was bad, I'd measure the output voltage of the associated parts (The inductor is likely part of a power supply circuit). I successfully worked for years in a Lambda factory troubleshooting power supplies without ever using an inductance meter. Bad inductors are often best found by indirect symptoms, not by direct measurement.

You still haven't told us... What makes you think this part is bad? Is it burned? Physically cracked? Did you have a dream?

This drive has other problems... (and with this , they are 2) can't load firmware when starting then it shuts down. And the inductor is fine. The inductor had the top broken, maybe, but it works fine anyway (unless the central core is broken too).
Why not connect terminal then post log to confirm what is REALLY the problem ?