PC-3000 Forum

Hello,

So I have a failed ST4000LM024-2AN17V (2.5"). Drive spins up, sounds like it cant calibrate; sort of a faint clicking but then it recognizes (reads ID; see MODEL, SN, FIRMWARE and even CAPACITY) but then the motor shuts off.

Terminal shows:

Boot 0x80MMD00040001
SpinUp
FAIL Servo Op=0100 Resp=0007
0100 9000 0000 0001 0000 9015 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
ResponseFrame 1AC0 0000 0000 DF00 0000 0000 0000 0000 0EF3 0000 CE00 0000 604C 3696 0005 0100 8552 FFFF 2000 0000 0000 0303 0003 1EBF 0000 C350 0000 0000 0020 2247 001D 0005 0000 Loop=2247Motor startedHeads loaded
FAIL Servo Op=0100 Resp=0007
0100 9000 0000 0001 0000 9015 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
ResponseFrame 1B80 0000 0000 DF00 0000 0000 0000 0000 0EF3 0001 CE00 0000 665B 369C 0005 0100 8552 FFFF 2000 0000 4072 0303 0000 C350 0000 C350 0000 0000 0020 2247 001D 0005 0000 Loop=2247Motor startedHeads loaded

Obviously this drive isnt supported yet.. I can get to tech / diag >T as such no idea what to do.. does anyone know what pins to short to get access to >T or what the issue might be (maybe its just the heads? but its strange that its reading ID and thne powering off).

Any help advice greatly appreciated.

Pretty sure heads are bad with Op=0100 Resp=0007
Be ready for extremely slow reading after changing heads.

FAIL Servo Op error mean that heads can't read Servo labels (the most powerful magnet signal) from the platters surface.
approx 5% cases with such error in terminal has a PCB issue, but usually it's heads/surface problem.
So, need to check this drive inside.

Hi
i have same hard disk try to unlock the terminal but not successfully done may be this hard disk family ( Rugged Family)not support yet.
Please help and what is the Family and how to unlock the terminal of this hard disk.

Filipp_TS wrote:Source of the post FAIL Servo Op error mean that heads can't read Servo labels (the most powerful magnet signal) from the platters surface.
approx 5% cases with such error in terminal has a PCB issue, but usually it's heads/surface problem.
So, need to check this drive inside.

Hi,
I do agree with Filipp Here 007 is a head issue .Filipp Whats a 005 Error ?

Dear Amarbir,

Amarbir[CDR-Labs] wrote:Source of the post Whats a 005 Error ?

This is head issue too

Dmitriy_TS wrote:Source of the post Dear Amarbir,

Amarbir[CDR-Labs] wrote:Source of the post Whats a 005 Error ?

This is head issue too

Dimitry Sir ,
Last week or two i have solved two cases of Rosewood 2TB after heads swaps .Both of them were continuously giving these 005 servo errors and my heads were fluttering but still i got data virtually near 100% in both cases .In my cases 1 or 2 heads work at full 110 mbps transfer speed and others do not work at high speed .So i disable the slow once clone the high speed once and by the time thats done the non working heads start spitting data at low speeds and case is solved in 3 to 4 days .i wonder whats the issue .I am still on ver 6.3.16 for no reason though my TS is active .Is there any improvement in rom parsing to work with heads like logical head map , physical head map and also head adaptive transfers in rosewood series ? .Head adaptive transfer will be so so very nice if it can be implemented sir

Dear Amarbir,

Amarbir[CDR-Labs] wrote:Source of the post Both of them were continuously giving these 005 servo errors and my heads were fluttering but still i got data virtually near 100% in both cases .

Based on our experience, the drives with 005 servo errors were finally crashed in 1-2 hours.

Amarbir[CDR-Labs] wrote:Source of the post Is there any improvement in rom parsing to work with heads like logical head map , physical head map and also head adaptive transfers in rosewood series ? .Head adaptive transfer will be so so very nice if it can be implemented sir

Adaptive transfer and ROM physical head map will be supported in new version.

Dmitriy_TS wrote:Source of the post Dear Amarbir,

Amarbir[CDR-Labs] wrote:Source of the post Both of them were continuously giving these 005 servo errors and my heads were fluttering but still i got data virtually near 100% in both cases .

Based on our experience, the drives with 005 servo errors were finally crashed in 1-2 hours.

Amarbir[CDR-Labs] wrote:Source of the post Is there any improvement in rom parsing to work with heads like logical head map , physical head map and also head adaptive transfers in rosewood series ? .Head adaptive transfer will be so so very nice if it can be implemented sir

Adaptive transfer and ROM physical head map will be supported in new version.

Well,
I do a lot of physical data recovery work ,None on my 005 servo error hdd have crashed till today ,Infact i have used those heads in next drive also .