ST3000DM001 - 9YN166 Drive not detect, Spin Up, 11Click's

[pikus_09]

Hello everyone, I'm writing about this because today happened to me just such a situation with my drive, after a week of trouble-free operation . I'm writing about this because today happened to me just such a situation with my drive, after a week of trouble-free operation. After connecting the power drive spin up being accompanied by a 11 clicks and drive spin down.
What's more, I noticed that the MCU is terribly hot you can not keep your finger on it.
Clean the contacts of the head, the engine did not help the effect is still the same.
LOG terminal:


Boot 0x40M
Spin Up
FAIL Servo Op=0100 Resp=0007
ResponseFrame EB00 0055 03B4 2FC0 0008 0000 0000 0000 0F3E 0000 0000 0000 0000
0000 0000 0000 13E9 70C4 FFFF 2000 DC0C 0000 0000 3F0F 0000 3F0F 0000 2247 0000
0020 001E 0007 0010
FAIL Servo Op=0100 Resp=0003
ResponseFrame E500 0058 03B4 2FC0 0008 0000 0000 0000 0F3E 0000 0000 0000 0000
0000 0000 0000 13E9 70C4 FFFF 2000 DC0C 0000 0000 3F0F 0000 3F0F 0000 007F 0000
0020 001E 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E500 0058 03B4 2FC0 0008 0000 0000 0000 0F3E 0000 0000 0000 0000
0000 0000 0000 13E9 70C4 FFFF 2000 DC0C 0000 0000 3F0F 0000 3F0F 0000 007F 0000
0020 001E 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E440 0058 03B4 2FC0 0008 0000 0000 0000 0F3E 0000 0000 0000 0000
0000 0000 0000 13E9 70C4 FFFF 2000 DC0C 0000 0000 3F0F 0000 3F0F 0000 007F 0000
0020 001E 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E400 0058 03B4 2FC0 0008 0000 0000 0000 0F3E 0000 0000 0000 0000
0000 0000 0000 13E9 70C4 FFFF 2000 DC0C 0000 0000 3F0F 0000 3F0F 0000 007F 0000
0020 001E 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E3C0 0058 03B4 2FC0 0008 0000 0000 0000 0F3E 0000 0000 0000 0000
0000 0000 0000 13E9 70C4 FFFF 2000 DC0C 0000 0000 3F0F 0000 3F0F 0000 007F 0000
0020 001E 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E3C0 0058 03B4 2F80 0008 0000 0000 0000 0F4C 0000 0000 0000 0000
0000 0000 0000 13E9 70C4 FFFF 2000 DC0C 0000 0000 3F0F 0000 3F0F 0000 007F 0000
0020 001E 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E380 0058 03B4 3000 0008 0000 0000 0000 0F30 0000 0000 0000 0000
0000 0000 0000 13E9 70C4 FFFF 2000 DC0C 0000 0000 3F0F 0000 3F0F 0000 007F 0000
0020 001E 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E340 0058 03B4 3000 0008 0000 0000 0000 0F30 0000 0000 0000 0000
0000 0000 0000 13E9 70C4 FFFF 2000 DC0C 0000 0000 3F0F 0000 3F0F 0000 007F 0000
0020 001E 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E340 0058 03B4 2F80 0008 0000 0000 0000 0F4C 0000 0000 0000 0000
0000 0000 0000 13E9 70C4 FFFF 2000 DC0C 0000 0000 3F0F 0000 3F0F 0000 007F 0000
0020 001E 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E300 0058 03B4 2FC0 0008 0000 0000 0000 0F3E 0000 0000 0000 0000
0000 0000 0000 13E9 70C4 FFFF 2000 DC0C 0000 0000 3F0F 0000 3F0F 0000 007F 0000
0020 001E 0004 0000

I question whether the problem indicates a faulty MCU (stress is terribly hot, even when the circuit board is unscrewed from the disk) Does heads are damaged? Come on, I think it's strange that after a week of action were damaged.


Sorry for my english.

[fzabkar]

I would measure the Vcore and Vio voltages, but try to save the contents of the flash memory IC if you can.

http://www.users.on.net/~fzabkar/HDD/ST ... 1_regs.jpg

[hhddrec]

i think your problem is relarive to fw or heads
wath tools and skills do you have?

[pikus_09]

Ok, I can save the contents of Flash ROM, and even make a copy of 25F40 (I have a SPI flash programmer) I have also STcomPlus, terminal, I do not have PC3000 unfortunately too expensive for me, and I know that pirates are not helping,
The disk had changed the firmware from CC4B on CC4H.
voltages:

(PCB is borrowed from the Internet, but it is the same as the ones in the attached picture.)


ps. ROM dump add on Thursday because tomorrow I'm out of range.

[fzabkar]

Those voltages are OK.

Vcore = 0.9V
Vio = 1.8V

I believe there is a second Vcore supply at the uppermost coil immediately to the right of the motor terminals. It should be around 1V.

There is an additional 12-pin chip to the left of the preamp contacts, but I don't know what it does. It might be worth measuring the voltages on its adjacent capacitors.

[pikus_09]

Hey Franc,

I attach measured all the voltages on the PCB disk:

any ideas?

[Jano952]

Check 5 and -5 V going to preamp. PCB probably needs to be placed on HDD.

Attachments

[pikus_09]

Ok, well I checked if there is 5V and -5V, and so is 5V however it can not -5V, what is more in line -5V have a short to ground, which leads to Smooth. Bad Smooth!?

[fzabkar]

The -5V supply uses an Inverting Buck-Boost topology. This means that one end of the coil is connected to ground.

Tutorial - Linear and Switchmode Regulators used in HDDs:
http://www.alexsoft.org/viewtopic.php?f=59&t=231&p=596

The PWM control for the -5V supply comes from the motor controller. However, the MCU enables or disables this supply by way of a command to the motor controller, at least in some designs. It could be that this supply is turned off after the MCU fails to detect the preamp, in which case it would need to be measured when the PCB is attached to the HDA.

That said, if the -5V output at the HDA contacts is shorted to ground, then this would indicate a PCB fault, or a bad preamp if the board is attached to the HDA.

The Vio and two Vcore voltages are OK. I don't know what to make of the other IC, though.

I can't suggest any reason for the high temperature of the MCU, but it might be worth trying another board and transferring the serial flash memory. If it weren't for this observation, I would have bet on an internal fault. That may still be the case.

[pikus_09]

Ok, you're right Frank -5V appears only when a signal by MCU and PCB must be plugged into the heads, I measured it again and by this time had come to -4,8V (-5V) there is no short circuit on the preamplifier, ie the problem is rather in firmware than heads. I can not read the contents of ROM LE25FS020, do not read it at all my programmer.

[fzabkar]

I can not read the contents of ROM LE25FS020, do not read it at all my programmer.

Be very careful. This is a 1.8V chip. You must not damage it.

[pikus_09]

Yes, I know, but re-soldering the bone does not change the situation..

[fzabkar]

FWIW, I notice that some boards use EN25S20 chips (or EN25S40). Perhaps you could select this chip type.

http://transonics.com/images/file/pdf/eon/EN25S20.pdf

[pikus_09]

Ok, but i can try read the contents of the bones on the Eon EN25SXXX, but still it was unreadable, the had in mind its very low supply voltage. Something I feel that it is this bone is damaged and its contents.

[fzabkar]

If the ROM were damaged or corrupt, then the drive wouldn't spin.

[pikus_09]

Ok, you may be right, but it can be so that part responsible for starting the engine is intact, and the rest as adaptives, heads and settings may already be damaged or corrupted. I tried to read this ROM to no avail, it does not detect either the E25F40, or on other types of IC's.

[fzabkar]

The ROM's components are checksummed. I'm not a data recovery professional, but your terminal log would suggest that the drive cannot read the embedded servo information. AISI, that could be due to a media or head fault, or a fault in the read channel section of the MCU.

BTW, did you try reading this chip in-circuit, or did you desolder it?

[pikus_09]

The ROM's components are checksummed. I'm not a data recovery professional, but your terminal log would suggest that the drive cannot read the embedded servo information. AISI, that could be due to a media or head fault, or a fault in the read channel section of the MCU.

BTW, did you try reading this chip in-circuit, or did you desolder it?

You know frank, the problem is not just me because I like reading topics that different users have the same problem that, for example after 3 days of work barracuda refused to obey them, and also suggest that the heads landed within 3days?
What's more, in my case barracuda broke down both after 8 days, SMART was OK, no 05, C5, C6.

I try to read the contents of the ROM, it always de-soldered IC with PCB, never vice versa.
btw. And also I have a suspicion that a change in the firmware of CC4B on CC4H hurt this disk.

Sorry for my English.

[pikus_09]

The ROM's components are checksummed. I'm not a data recovery professional, but your terminal log would suggest that the drive cannot read the embedded servo information. AISI, that could be due to a media or head fault, or a fault in the read channel section of the MCU.

BTW, did you try reading this chip in-circuit, or did you desolder it?

You know frank, the problem is not just me because I like reading topics that different users have the same problem that, for example after 3 days of work barracuda refused to obey them, and also suggest that the heads landed within 3days?
What's more, in my case barracuda broke down both after 8 days, SMART was OK, no 05, C5, C6.

I try to read the contents of the ROM, it always de-soldered IC with PCB, never vice versa.
btw. And also I have a suspicion that a change in the firmware of CC4B on CC4H hurt this disk.

Sorry for my English.

Any Ideas!?

[Jano952]

It is really weird that you cant read Flash... Does your programmer support 1,8V devices ? What about HOLD pin, did you connect it to 1,8V ? Can you read at least signature ?