I am not sure of the history of the pending bug, but this Seagate looks like it has the earlier version without the pending error and fix (unless you know different). The PC3000 manual says it could be adaptive data failure. The explanation on switching off heads is also a little confusing and it seems you cannot switch off head 0. The manual says it could also be head contamination from a poor lubrication layer. If so, whats the best method for cleaning heads?

I have tested all heads via the terminal and they all seem okay. I tried the T>T4 command but it does not accept it. Is this heads or is there anything else I can try?

T>/2
2>s444,0,22
2>U
2>H0
Head 0
2>H1
Head 1
2>H2
Head 2
2>H3
Head 3
2>H4
Head 4
2>Interface task reset
4096k x 16 buffer detected
TONKA - 1_Disk M-27 03-30-05 11:42
Head Mask FFFF - Switch to full int.
Spin Ready
3.06 10-07-05 15:20
(P)PATA Reset
Master

T>T4
Command Inactive - No VALID Cert Code Detected
T>Interface task reset
4096k x 16 buffer detected
TONKA - 1_Disk M-27 03-30-05 11:42
Head Mask FFFF - Switch to full int.
Spin Ready
3.06 10-07-05 15:20
(P)PATA Reset
Master
(S)PATA Reset
Master
AT Er 00 Nwt Er 43 RiskAccess ReadSector EC=db02 at 3133845.43.0018

CE Log EC=43 Rtype=25 OV=0 STStatus0
SCAN Error
AT Er 00 Nwt Er 43 RdWr 0e9a2.05.0432
ATA St 50 Er 00 Op c8 e, 0000903,00 00 03
Niwot: 00000903 ff 00000903.0.0c0 8000 2dee 07fb 0000

CE Log EC=43 Rtype=24 OV=0 STStatus0
AT Er 00 Nwt Er 43 RdWr 0e9a3.05.028d
ATA St 50 Er 00 Op c8 e, 0000903,00 00 03
Niwot: 00000903 ff 00000903.0.0c0 8000 2dee 07fb 0000

CE Log EC=43 Rtype=24 OV=0 STStatus0
AT Er 00 Nwt Er 43 RdWr 0e9a3.05.0300
ATA St 50 Er 00 Op c8 e, 0000903,00 00 03
Niwot: 00000903 ff 00000903.0.0c0 8000 2dee 07fb 0000

CE Log EC=43 Rtype=26 OV=0 STStatus0
Not handled software path:
AT Er 00 Nwt Er 00 RdWr ffffffff.01.008c
ATA St 50 Er 00 Op c8 e, 0000903,00 00 03
Niwot: 00000903 ff 00000903.0.0c0 8000 2dee 07fb 0000

CE Log EC=43 Rtype=24 OV=0 STStatus0

_________________
HDD, SSD, Flash and RAID Data Recovery
Founder of The Data Recovery Professionals Group

Further to this, I did get the full T4 head test to work. They all reported passed eg.

Testing head 0...
DAC value = FDBA
Biasing with current 0025mA
DAC value = FCA2
Biasing with current 0050mA
DAC value = FB8A
Biasing with current 0075mA
DAC value = FA72
Biasing with current 0100mA
DAC value = F95A
Biasing with current 0125mA
DAC value = F842
Biasing with current 0150mA
DAC value = F72A
Biasing with current 0175mA
DAC value = F612
Biasing with current 0200mA
DAC value = FDBA
Passed Max OD Bias Current = 0200mA. Limit = 0100mA

_________________
HDD, SSD, Flash and RAID Data Recovery
Founder of The Data Recovery Professionals Group

According to the terminal log, drive should either be detectable in BIOS or get ready, but hang when you try to ID it. It looks like there are at least surface defects or one of the heads is unable to read.

In current condition you should be able to read the data using Data Extractor, no major problems should appear. Or more information from you is necessary.

If something goes wrong, there could be a PCB problem, e.g. broken contacts or damaged interface. In that case you need to replace the PCB, if you can't ID the drive.

Or data isn't important and you're looking to repair the drive?
Switching heads off is applicable only when you need to repair the drive.

_________________
• Remote RAID, NAS, SAN, VMware, DVR (CCTV), flash and tape recovery. Data recovery support.

Thanks Dmitri. The drive is imaging on DE. While I could not build a head map of the drive, it does appear that at least on head is failing. We go through stages of grabbing lots of data, then a really slow portion which I presume is the failing head. We have about 75% of the drive imaged now. It just takes a long time... Thanks for the help.

_________________
HDD, SSD, Flash and RAID Data Recovery
Founder of The Data Recovery Professionals Group