Seagate DM Headswap Experiences

[Jared]

As we all seem to be having difficulties head swapping these, I though it'd be nice to have a thread to share our DM head swap experiences. Here's mine from today:

Patient
ST30000DM001
PN: 9YN166-570
FW CC9F
Date: 13044
Site: TK
Serial: Z1F0Y...

Donor
ST30000DM001
PN: 9YN166-570
FW: CC9E
Date: 12433
Site: TK
Serial: Z1F0K...

As you can see, I matched model, site, PN, and first four of serial. The drive initially ID'd showed correct capacity and allowed sector access. Resources were backed up and imaging started. A few heads actually read relatively quickly, others were slow but steady with only a few bad sectors. After about 10 minutes, drive hit a bad sector, began clicking and failed to ID after power cycling it. :x :x :x Now it just clicks and spins down. But at least I know the heads were compatible, and I didn't kill them in the swap.

 

[jol]

thanks, but 10min of 3000GB is ? (almost none)

 

[Jared]

Agreed, the recovery is still a total loss at this point. We'll see how the next head swap goes.

But I'll still take it working for ten minutes over not working at all and wondering if the heads weren't compatable, got damaged in the clean room, etc.

 

[jol]

you were able to write 2 ? or just read (or didn't try to write) ?

 

[LarrySabo]

Do the donor heads still work in the donor? Weird that it worked for a while but never again after having failed on bad sectors, almost as if damaged by bad media.

This is a great topic, BTW, if we get input on what works and what doesn't.

 

[lcoughey]

I just had a 3TB DM come in that was already attempted by Ontrack that I was unable to recover as well. I posted a pictured of the client heads here.

 

[LarrySabo]

Ow, ow, ow. Hurts my eyes!

Here's one that was worked on by "a friend who works in the government and does data recovery."

 

[jol]

oh
my
god

 

[lcoughey]

Ow, ow, ow. Hurts my eyes!

Here's one that was worked on by "a friend who works in the government and does data recovery."

That isn't data recovery...that is data destruction by someone who shouldn't be doing data recovery...assuming that they did the damage and not someone else.

 

[Jared]

Looks like he left some DNA on that one Larry. :lol: