ST3000DM001 after head replacement

Moderator: Nick_TS


drmilos
New user
Posts: 51
Joined: 11.05.13
Reputation: 1 / (14)

ST3000DM001 after head replacement

Postby drmilos » 18.01.14, 09:10

I have ST3000DM001 (FW: CC9C, Site: TK, Date: 12283) with failed head stack (knocking sound, stops spinning, no access).

I have found what I consider an ideal donor (4 chars in S/N, near date, identical site and FW).

After head replacement the drive starts knocking (actually more scratching then knocking), then I hear some whirring, then some more scratching and knocking and it keeps spinning and stays busy.

Here is the terminal output:

Boot 0x40M
Spin Up
RECOV Servo Op=0100 Resp=0005[0x000065B4][0x00006A20][0x00006E8C]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
RECOV Servo Op=0600 Resp=0005
RECOV Servo Op=015B Resp=0005
RECOV Servo Op=005B Resp=0005
MCMainPOR: EXCEPTION: SIM aborted prior to MCMT read
MCMainPOR: EXCEPTION: POR Failed General
MCMainPOR: Feature Disabled...
RECOV Servo Op=016B Resp=0005
RECOV Servo Op=005B Resp=0005 PASS
RECOV Servo Op=016B Resp=0005
RECOV Servo Op=006B Resp=0005
RECOV Servo Op=016B Resp=0005S22(01)[0000000000087BD2]v00000008qv00000008qv00000008qv00000008qv00000008qv00000008qv00000008qv00000008qv00000008qv00000008q
Starting LBA of RW Request=0000000000087BC6 Length=00000188
ProcessRWError -Write- at LBA 0000000000087BD2 Sense Code=C4090081
RECOV Servo Op=056B Resp=0005
RECOV Servo Op=046B Resp=0005
RECOV Servo Op=036B Resp=0005[000000002BB5424F]v00000028qv00000028qv00000028qv00000028qv00000028qv
WaitForReadChannelDone: timeout. SOBReadBufferStatus = 0002
WaitForReadChannelDone: timeout. SOBReadBufferStatus = 0002
WaitForReadChannelDone: timeout. SOBReadBufferStatus = 0002
WaitForReadChannelDone: timeout. SOBReadBufferStatus = 0002
WaitForReadChannelDone: timeout. SOBReadBufferStatus = 0002
WaitForReadChannelDone: timeout. SOBReadBufferStatus = 0002
WaitForReadChannelDone: timeout. SOBReadBufferStatus = 0002
WaitForReadChannelDone: timeout. SOBReadBufferStatus = 0002

The last Wait.. line repeats every few minutes.

Donor head has not been damaged in the exercise (returned to donor and tested, works OK). Patient head in donor drive show the same symptoms as in patient so I believe it's really dead.

Is there anything I can try or I should cut my losses and let this one go? Any suggestion much appreciated.


NSRGroup
Newbie
Posts: 34
Joined: 24.04.13
Reputation: 0 / (4)

Re: ST3000DM001 after head replacement

Postby NSRGroup » 19.01.14, 10:01

what 's that donor hdd details?
is the same date code or near?


AJ2008
Posts: 1410
Joined: 25.11.08
Reputation: 12 / (116)

Re: ST3000DM001 after head replacement

Postby AJ2008 » 20.01.14, 11:14

NSRGroup wrote:what 's that donor hdd details?
is the same date code or near?


Date code seems to have no importance, more importantly is Site Code...


NSRGroup
Newbie
Posts: 34
Joined: 24.04.13
Reputation: 0 / (4)

Re: ST3000DM001 after head replacement

Postby NSRGroup » 20.01.14, 16:21

some times for my experience near date code is better or needed


drmilos
New user
Posts: 51
Joined: 11.05.13
Reputation: 1 / (14)

Re: ST3000DM001 after head replacement

Postby drmilos » 21.01.14, 07:02

Donor date code is 12262, patient 12283, other parameters are identical (model, site, F/W and first 4 characters in S/N).


AJ2008
Posts: 1410
Joined: 25.11.08
Reputation: 12 / (116)

Re: ST3000DM001 after head replacement

Postby AJ2008 » 21.01.14, 11:01

drmilos wrote:model, site, F/W and first 4 characters in S/N.


This is my criteria also (except I match only first 3 values of SN).

If it seems like is scratching you can try to import adaptives from donor ROM to patient ROM, maybe some aspect of this controls flying height for example, other option is to place heads back to donor and if donor is bad now then probably some surface errors at patient have damaged donor heads.


drmilos
New user
Posts: 51
Joined: 11.05.13
Reputation: 1 / (14)

Re: ST3000DM001 after head replacement

Postby drmilos » 24.01.14, 07:03

I have tried, along with head transplant:

- Importing adaptives from donor ROM to patient ROM;

- Swapping both top and bottom magnets;

- Swapping head screws;

- Swapping PCB;

- and combinations of the above

Same result, no joy, exactly the same behaviour as described in the original post.

The most interesting part is that donor head is not destroyed. When I return original head to donor, it shows some reluctance and few scratching noises, but still gets ready and Ids, I can read sectors in the utility. This is after at least 4 swaps to and fro and lots of audible scratching in the patient.

I am no smarter after this exercise except that ideal donor may not be so ideal.


NSRGroup
Newbie
Posts: 34
Joined: 24.04.13
Reputation: 0 / (4)

Re: ST3000DM001 after head replacement

Postby NSRGroup » 24.01.14, 09:39

if we can doing hot swap for F3 architecture then you testing hot swap method?


Return to “Archive”

Who is online

Users browsing this forum: No registered users and 15 guests