I am going to leave this topic and open a new one. But for now, I tested the the pcb with the power on. Tensions were fine (5V in, 3,3 out, etc.). I got 12V in and 14v (to pump). I think the pump tension is too weak. The problem is that I had to unplug the pcb in order to test it (because all the components are on the other side of the board) and I got only a peak to 14V followed zero. Maybe a component is cutting the voltage when it does not detect a closed circuit. And 14V may not be enough to keep the right rpm.
I see I have a lot to learn. In the mean time, I will open a new topic to see if someone has the schematics for this hdd.

Thank you all.

This thread may be of interest to you:
newbie-info-from-and-for-newbies-about-firmware-etc-t6562.html

BTW, if you can hear the heads move, then this would suggest that the drive has spun up to the correct speed.

_________________
A backup a day keeps DR away.

I was reviewing my few posts today. Well, eh, it turns out the busy state was due to FW as all of you who really want to help should know. I understand the purpose of a forum is to share and to help. it does not look like this is the case for some people here. Sometimes, I think the idea is to shutdown all attempts to learn and to do. At least that has been my first impression. For example, I saw a post of someone asking for Salvation training videos and someone else replied saying it was better to watch DIY videos on youtube or something... Wow! That's what I call good advice!

Ok, but I digress... The problem I had was solved with the firmware loading. All Maxtors starting with STM are in fact Maxtor Seagate drives... I guess the drive must have been dropped, as the noise produced was a little louder the usual. Either that, or the FW problem common to certain Barracudas produced from a certain year and such... Well, it worked.

I guess that's it.

Thanks to all who helped.

All our crystal balls were down for maintenance (NOT percussive ). Usually at least a terminal log helps....



Everything happens because of a reason.



Often the 1st impression is not the right one. We live with it...



For how many bugs are in their tools (despite if you master them you can do nice things with !), unfortunately there's a bit of truth in the reply.



So it means that APP or something else (except OVLYs !) was screwed...
AND you didn't use SD tool to upload for example COMPLETE FIRMWARE, right ?



As clearly written on top cover....



If the drive was even SLIGHTLY DROPPED it wouldn't work THAT way.
Maybe it was "a little bit shocked" hence a "small" problem that the drive was able to mend by itself (oh yes !). The rest is pure guessing but very far from reality (if you said that these drives are crap, well, it is 70% true....)



... ah yes, exactly : guess.



You're welcome

Sorry to dig up this topic.
I also need the FW for this model. Can anyone share?
Thanks

_________________
http://www.pclab.com.pt facebook.com/PCLAB.A.T
ACELab partner

@pclab, what FW and ROM revision do you need and for what platform ? (PC3000, SD, other) ? tracks, modules, all ? PM me (have at least 1 dozen different....)

PM sent .
Thanks BlackST

_________________
http://www.pclab.com.pt facebook.com/PCLAB.A.T
ACELab partner

Closer I have (same FW, same ROM), is a 815AS (difference is in cache). This should work.

Please send it to test.
Thanks

_________________
http://www.pclab.com.pt facebook.com/PCLAB.A.T
ACELab partner

Working on it.
Thanks BlackST

_________________
http://www.pclab.com.pt facebook.com/PCLAB.A.T
ACELab partner