help~ Maxtor HDD Recovery

[hardsam09]

Hi~~
Problem HDD : Maxtor DiamondMax 22 STM3320614AS 320GB SATA
Problem Description : The HDD spins up a while, then stop and spins a again. I think is the PCB Board Problem.

I got accounting file and database inside, any solution??

[BlackST]

Most probably NOT THE PCB unless you noticed something wrong in it and didn't tell exactly...

[Smart302]

it'Seagate F3 Family 7200.11。 I think the Firmware or head failure

[unknown]

I got accounting file and database inside, any solution??

Yes. Send the drive to a pro.

[poehere]

This is Seagate drive but regard if this is not the typical Seagate drive busy error and you try this solution you will brick your drive. You need to have it looked at by someone to determine exact problem in this drive before trying to repair it with this solution.

[hardsam09]

Most probably NOT THE PCB unless you noticed something wrong in it and didn't tell exactly...

When i connect it to my pc, i can feel it spin a while, then it will stop and spin again. In bios is not detect that drive, windows or dos also~~

[BlackST]

Bingo. SA / Heads. Probability about being PCB : 1 - 2 %

[hardsam09]

So the best way is send back the HDD to Seagate?

[poehere]

If you do not need your data on it yes. RMA the drive and get a new one. Note this is not a DR recovery from Seagate on this drive.

[thomaslindet]

Hi !

I have the same problem on my disk, this is also a 7200.11 Seagate drive, but a Barracuda for me. I asked on the seagate support about this problem : http://forums.seagate.com/t5/Barracuda- ... lse#M20226 and someone told me communicate with the drive via its serial terminal interface to know more about the problem. I'm waiting for the cable to arrive to do it.

I thought that sharing infos would be a good thing, as long I also have data on this drive I wanna recover (almost 900Go in my case, a shame I couldn't backed that up).

Anyway, have you made more "discoveries" on the way to solve the problem since the last answer ?

And let's wish each other good luck

[thomaslindet]

Hey !

The problem is solved for me, I found someone describing the exact same problem as mine, with same disk and same firmware. He solved it using the BSY fix method. So I tried it as a last thing to do before throwing the disk away (I couldn't afford data recovery and couldn't apply for RMA).

I can't tell if this will work with your disk, as long it's not the same model, plus the fact the diagnosis doesn't go in this way.

So I feel lucky it worked, and I hope this can help you, unless you found another solution by yourself.

Regards.

[fzabkar]

The problem is solved for me, I found someone describing the exact same problem as mine, with same disk and same firmware. He solved it using the BSY fix method.

Congratulations, and thanks for the feedback.

[Alexii]

looks like Poehere was wrong.

[jono-ats]

looks like Poehere was wrong.

And if so, so what?

I'm sure that if she had the drive in front of her, and didn't have to rely on a vague problem description, she would have made the correct diagnosis & etc. with little trouble.

Trying to accurately diagnose drives remotely is often a toss of the dice, even for the so-called experts.

I think the fact that she invested time to reach out and help a stranger is commendable.

Jono

[Alexii]

looks like Poehere was wrong.

And if so, so what?

I'm sure that if she had the drive in front of her, and didn't have to rely on a vague problem description, she would have made the correct diagnosis & etc. with little trouble.

Trying to accurately diagnose drives remotely is often a toss of the dice, even for the so-called experts.

I think the fact that she invested time to reach out and help a stranger is commendable.

Jono

Heya Jono. To answer your question - so nothing. Absolutly nothing.

[poehere]

looks like Poehere was wrong.

And if so, so what?

I'm sure that if she had the drive in front of her, and didn't have to rely on a vague problem description, she would have made the correct diagnosis & etc. with little trouble.

Trying to accurately diagnose drives remotely is often a toss of the dice, even for the so-called experts.

I think the fact that she invested time to reach out and help a stranger is commendable.

Jono

Thanks Jono but as you can see it was hardsam09 who I answered. Thomaslindet fixed his drive we still do not know if hardsam09 drive is fixed yet or not.

Hey !

The problem is solved for me, I found someone describing the exact same problem as mine, with same disk and same firmware. He solved it using the BSY fix method. So I tried it as a last thing to do before throwing the disk away (I couldn't afford data recovery and couldn't apply for RMA).

I can't tell if this will work with your disk, as long it's not the same model, plus the fact the diagnosis doesn't go in this way.

So I feel lucky it worked, and I hope this can help you, unless you found another solution by yourself.

Regards.

Who knows now?? This guy fixed his Seagate the other is a Maxtor/Seagate.

[Alexii]

Looks like i need to read more carefully =)