Seagate woes....2TB LP

[Nick_CT]

Hello all,

I have a ST2000DL001 with me that I'm having trouble with. When powered up in PC3K and I launch the F3 utility it goes BSY. It's not reporting serial, model, size...nothing. Everything sounds good and normal with the drive.

Terminal is giving me a constant stream of the following:

LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0

Firmware is CC41.

Any ideas guys?

[zebong]

is the drive clicking ?

[Nick_CT]

No, it sounds perfectly normal and no clicking, exactly the same as another identical, working drive that I have here.
When connected to PC3K and powered up, it shows DRD and DSC as normal. But as soon as I launch the F3 util it goes BSY.

Rst 0x20M
RW: Disc Ctlr Initialization Completed.
(P) SATA Reset

LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0
etc...

[hamidbid]

test normal solution

[Nick_CT]

Firstly, thanks to Zebong for some recommendations he provided yestertday on something to try with this drive.

I couldn't get terminal access yesterday, but managed to do so today and ran N1, and after clearing SMART the drive is working again 100%

[hddguy]

Those LP cases can be tricky

good job

[Coenwolf]

Having same problem here with ST2000DL001 and clearing SMART seems to bring it on line but only for a short time. Are there any other suggestions I can try?

[rms610]

Hi nick
I have same your problem,please guide me

[Nick_CT]

Research how to connect to a Seagate drive via terminal and then you can find the command to clear SMART.

But...you can kill a drive with a wrong terminal command. And if the problem is something else then you can make the problem worse.

DIY is always risky.

[apcsllc]

Firstly, thanks to Zebong for some recommendations he provided yestertday on something to try with this drive.

I couldn't get terminal access yesterday, but managed to do so today and ran N1, and after clearing SMART the drive is working again 100%
------------------------------------------------------------------
can you elaborate please???

i have same issue however the drive is giving me info relating to the partitions SEE BELOW

What do I do next???

<0><0><0>
Boot 0x40M
Spin Up[0x000246DF]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
MediaPartition:

Host LBA Length Disc LBA Length Start Cyl Head
Media Partition 00000000 0099A2A0 00000000 00133454 00000000 00000000
MC 00000000 00989788 00000000 001312F1 00000000 00000000
MSP 009916B8 00000CB8 001322D7 00000197 00000215 00000005
User Partition 0099A2A0 00133454 0000020A 00000005

MCMainPOR: EXCEPTION: SIM aborted prior to MCMT read
MCMainPOR: EXCEPTION: POR Failed General
MCMainPOR: Feature Disabled...

MSP MainPOR:
MSP Init Metadata
Buf Bytes/VBM 00000210 DBA Base 40000000
Metadata size in bytes 0040
Num Segments 0065
Logical Sector Alignment 00000000
MSP Reconstruction
Rst 0x40M
MC Internal LPC Process
Spin Up
LED:000000BD FAddr:000058B3

[jignesh]

Hello all,

I have a ST2000DL001 with me that I'm having trouble with. When powered up in PC3K and I launch the F3 utility it goes BSY. It's not reporting serial, model, size...nothing. Everything sounds good and normal with the drive.

Terminal is giving me a constant stream of the following:

LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0

Firmware is CC41.

Any ideas guys?

Dear Bro NickCT
Wromm This Is My Brownie Cake
Yooo I Want To Eat It.
Bro NickCt When U Come Online Just Add Me On My Skypee Messenger My Skypee ID Is : jignesh.pankhania@hotmail.com
I Have Fixed Many Of This HDD.
Just Few Day Ago I Have Fixed It This One Drive.

Here Is My Drive Pic.
I Have Hebiit To Write Party Name On The Clean Place With Marker So I Have Removed That My Clint Info With Pictur Editor.
When Case I Solved And I Have To Give Back This Drive I Have Erase That Info With Eraser.
Sorry For My Bad English.

Yours Friend
Jignesh Pankhania

[apcsllc]

Hello all,

I have a ST2000DL001 with me that I'm having trouble with. When powered up in PC3K and I launch the F3 utility it goes BSY. It's not reporting serial, model, size...nothing. Everything sounds good and normal with the drive.

Terminal is giving me a constant stream of the following:

LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0
LED:000000BD FAddr:000074C0

Firmware is CC41.

Any ideas guys?

Dear Bro NickCT
Wromm This Is My Brownie Cake
Yooo I Want To Eat It.
Bro NickCt When U Come Online Just Add Me On My Skypee Messenger My Skypee ID Is : jignesh.pankhania@hotmail.com
I Have Fixed Many Of This HDD.
Just Few Day Ago I Have Fixed It This One Drive.

Here Is My Drive Pic.
I Have Hebiit To Write Party Name On The Clean Place With Marker So I Have Removed That My Clint Info With Pictur Editor.
When Case I Solved And I Have To Give Back This Drive I Have Erase That Info With Eraser.
Sorry For My Bad English.

Yours Friend
Jignesh Pankhania

Jignesh I have a drive that i was unable to get any communication from the other day, after removing pcb and placing card stock on the head i was able to get this :

<0><0><0>
Boot 0x40M
Spin Up[0x000246DF]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
MediaPartition:

Host LBA Length Disc LBA Length Start Cyl Head
Media Partition 00000000 0099A2A0 00000000 00133454 00000000 00000000
MC 00000000 00989788 00000000 001312F1 00000000 00000000
MSP 009916B8 00000CB8 001322D7 00000197 00000215 00000005
User Partition 0099A2A0 00133454 0000020A 00000005

MCMainPOR: EXCEPTION: SIM aborted prior to MCMT read
MCMainPOR: EXCEPTION: POR Failed General
MCMainPOR: Feature Disabled...

MSP MainPOR:
MSP Init Metadata
Buf Bytes/VBM 00000210 DBA Base 40000000
Metadata size in bytes 0040
Num Segments 0065
Logical Sector Alignment 00000000
MSP Reconstruction
Rst 0x40M
MC Internal LPC Process
Spin Up
LED:000000BD FAddr:000058B3


Im not sure what to do now can you help??

Drive spins but not recognized in bios

[labtech]

See if can get prompt in terminal and send command CTRL+X. Then post output here.

[apcsllc]

i cant get prompt

this is all i get when i apply power to the drive when connected to terminal ctrl+z doesnt do anything

<0>
Boot 0x40M
Spin Up[0x000246DF]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
MediaPartition:

Host LBA Length Disc LBA Length Start Cyl Head
Media Partition 00000000 0099A2A0 00000000 00133454 00000000 00000000
MC 00000000 00989788 00000000 001312F1 00000000 00000000
MSP 009916B8 00000CB8 001322D7 00000197 00000215 00000005
User Partition 0099A2A0 00133454 0000020A 00000005

MCMainPOR: EXCEPTION: SIM aborted prior to MCMT read
MCMainPOR: EXCEPTION: POR Failed General
MCMainPOR: Feature Disabled...

MSP MainPOR:
MSP Init Metadata
Buf Bytes/VBM 00000210 DBA Base 40000000
Metadata size in bytes 0040
Num Segments 0065
Logical Sector Alignment 00000000
MSP Reconstruction
Rst 0x40M
MC Internal LPC Process
Spin Up
LED:000000BD FAddr:000058B3

[labtech]

You may not like this, but here it goes...

Solely based on your reply, this seems to be more complex than I believe you can handle.

I believe the drive has at least one issue, specifically with the firmware. There can be other issues as well.
With regard to the firmware part, I think that if you discover on your own what issue may be (well by using somebody's guidance here based on the terminal output presented), then I am 99% sure you will not be to resolve the problem on your own, because of knowledge and the tools to implement the possible solution.

If the data is important I recommend sending to a specialized reputable DR professional.

[apcsllc]

You may not like this, but here it goes...

Solely based on your reply, this seems to be more complex than I believe you can handle.

I believe the drive has at least one issue, specifically with the firmware. There can be other issues as well.
With regard to the firmware part, I think that if you discover on your own what issue may be (well by using somebody's guidance here based on the terminal output presented), then I am 99% sure you will not be to resolve the problem on your own, because of knowledge and the tools to implement the possible solution.

If the data is important I recommend sending to a specialized reputable DR professional.

Well I appreciate your concern, however it wasn't even giving me this much response two days ago. I got it to this point where I believe someone who really understands how firmware and HD communicate can diagnose the problem and provide an adequate solution. I am fully capable of carrying out directions as well as I actually do have a brain and am able to learn very quickly. I own a computer repair shop and am pretty good with figuring things out.

If you or someone who can interpret this is willing to help (and if they know what they are REALLY doing) then I'm interested in the help. That's why I'm here. It looked like someone in this thread was already successful with the exact same issue i have.

You may not like this but here it goes.... It sounds like you may not be sure of yourself. Which I can respect letting someone know that, but i hardly think its fair to judge whether i am capable of carrying out and following directions while receiving help from someone more experienced than I am pertaining to a specific skill set or repair. Or rather you said "then I am 99% sure you will not be to resolve the problem on your own". So obviously if I am here asking for help with this specific issue I am not trying to do this on my own.

Thanks....

[hddguy]

You may not like this, but here it goes...

Solely based on your reply, this seems to be more complex than I believe you can handle.

I believe the drive has at least one issue, specifically with the firmware. There can be other issues as well.
With regard to the firmware part, I think that if you discover on your own what issue may be (well by using somebody's guidance here based on the terminal output presented), then I am 99% sure you will not be to resolve the problem on your own, because of knowledge and the tools to implement the possible solution.

If the data is important I recommend sending to a specialized reputable DR professional.

Well I appreciate your concern, however it wasn't even giving me this much response two days ago. I got it to this point where I believe someone who really understands how firmware and HD communicate can diagnose the problem and provide an adequate solution. I am fully capable of carrying out directions as well as I actually do have a brain and am able to learn very quickly. I own a computer repair shop and am pretty good with figuring things out.

If you or someone who can interpret this is willing to help (and if they know what they are REALLY doing) then I'm interested in the help. That's why I'm here. It looked like someone in this thread was already successful with the exact same issue i have.

You may not like this but here it goes.... It sounds like you may not be sure of yourself. Which I can respect letting someone know that, but i hardly think its fair to judge whether i am capable of carrying out and following directions while receiving help from someone more experienced than I am pertaining to a specific skill set or repair. Or rather you said "then I am 99% sure you will not be to resolve the problem on your own". So obviously if I am here asking for help with this specific issue I am not trying to do this on my own.

Thanks....

To put it bluntly, labtech is right, this is beyond you.

Maybe you have some impression that it can be solved with simple fix, but actually this isnt the case. You also need to gain access to specific areas within the service area which is not accessible without specialist hardware like PC3000, which I am assuming you dont have?

Knowledge of the solution is only part of the problem. If you knew solution, you probably still could not apply it...

[apcsllc]

I don't even think i can respond to this in any other way but: thank you so much for being so helpful here on this forum! You guys are awesome!

[labtech]

Sorry for striking a nerve cord, just trying to prevent you from wasting your time without being successful and potentially causing more damage in the DIY recvoery attempts. BTW, if this is a customer's data, may want to consider what I recommended earlier.

But since you insist, the least you could do is find out how to short the read channel so you can get terminal prompt. That, you can find out on your own. The CTRL+X and post output here.

[labtech]

One more suggestion: practice terminal access to see if can even get prompt on another healthy drive model, as working directly on the failed drive is a bad idea.