LED:000000CC Faddr:00249EFS

got this disk 7200.11 ST3500820AS f/w -LC11 ,
disk gives terminal - LED:000000CC Faddr:00249EFS
However if pcb removed and tried ctrl+Z but nothing comes on terminal.
can someone give a hint please?

In a twist to tale hard disk given LED error when pcb is connected but when PCB is removed disk does not come on terminal , guru's pls. help

most likely either you are doing something wrong, or Terminal has been locked. Can it be unlocked, yes it can! Will someone tell you how to do it? I think not. Have fun tinkering :mrgreen:

I do not agree
Other disks can be accessed in terminal , even this disk shows error when pcb is connected. I think terminal is not locked this could be some unknown firmware defect
Re: LED:000000CC Faddr:00249EFS is differenrt than usual code - LED:0000000CC Faddr:0024A051

learner wrote:Other disks can be accessed in terminal

but we are talking about this disk, not about other disks, or are we not?
Anyways, your sitting infront of the drive, so you should know best :mrgreen:

I have no done anything with the drive , may be before I got disk ,customer has tried DIY and that could be the reason. I want to know what could be the reason pcb disconnected fromhda is not coming in terminal ,any suggestion friends?

learner wrote:I have no done anything with the drive , may be before I got disk ,customer has tried DIY and that could be the reason. I want to know what could be the reason pcb disconnected fromhda is not coming in terminal ,any suggestion friends?

Sometimes they do that

yes I'm gonna find out reason behind it.
>> ESD induced damage while improper handling of PCB
>> Eprom corruption
these could be possible reasons , we are trying different pcb by replacing adaptive paramerterts

Not that I read all of your thread. Its not the usual sd15 firmware and that error is not specific to a SD15 brick either. You need to do more investigating...

learner wrote:yes I'm gonna find out reason behind it.
>> ESD induced damage while improper handling of PCB
>> Eprom corruption
these could be possible reasons , we are trying different pcb by replacing adaptive paramerterts

No, I mean sometimes this is normal behavior, depending on the model and fw revision

I have performed the "normal" methods on LC11 500GB Seagate, and there where some minor differences.

Try it with just blocking spindle connection to.

You may have to "fiddle" with it for a little to get to T>, but I have gotten it.

Zero Alpha wrote:Not that I read all of your thread. Its not the usual sd15 firmware and that error is not specific to a SD15 brick either. You need to do more investigating...

This disk has firmware defect from seagate side.I confimed it on seagate website in serial no. check. May be original crash was because of this ,customers DIY has worsen the situation. as said by Russwinters I will fiddle with it and report.

Try checking the UDMA F3 Seagate book. Look in back this might help you out on this one. Sorry that is if you have the UDMA

Depending on what DIY done, there are many things to check and fix and maybe data is garbled...

I doubt this has anything to do with customers DIY. It's an common issue, if you have not run into this before then it's because you have not done enough recoveries on this series. I can think of at least two ways to resolve this issue.