Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Seagate Barracuda ST1000DM003 not detected by BIOS

August 10th, 2016, 20:37

Hi all,

I've been pouring through the forums and the numerous issues with this model and I'm sorry to say that I have a similar problem.

I'm trying to disable the media cashe but I can't seem to access the console. Ctrl+Z does nothing. I thought the ZZZZZMMMM were a sign of TTL problem but I tested my TTL adapter on another drive and it works just fine (I can bring up the console) so I think it's a problem with the drive/firmware.

I've seen some people post about shorting pins on the PCB to get to the console but that makes me really nervous. Is that really the only way?

Terminal log below:
Code:
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2016.08.10 20:25:54 =~=~=~=~=~=~=~=~=~=~=~=
Boot 0x40M
Spin Up
RECOV Servo Op=0100 Resp=0005
TCC-001D[0x0000631D][0x0000631D]ZZZZMMMMMMMMMMMMMMMZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMddddddW
PreampFaultStatus = 0000YW
PreampFaultStatus = 0000YWMMMMMM
RECOV Servo Op=0155 Resp=0005S
RECOV Servo Op=0055 Resp=0005xxxxZWZWZWZWZWZWZWZWBBWWdd
RECOV Servo Op=0155 Resp=0005[0x00068E5F][0x000690F6][0x00069562][0x000699CE]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001D
RECOV Servo Op=0055 Resp=0005
RECOV Servo Op=0900 Resp=0005
(P) SATA Reset

MCMTFileHandler: EXCEPTION: Failed MCMT read request
(DOS) Table Read FAIL
DOS: MAGIC CONFIG NUMBER MISMATCH
(DOS) Requesting File Save

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
Reconstruction: MCMT Reconstruction Start
  Max number of MC segments 0A61
Nonvolatile MCMT sequence number 0015D1B7
[RSRS] 045E
Starting LBA of RW Request=0000000000038802  Length=00000747
ProcessRWError -Read-   at LBA 0000000000038802  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000038802!

Reconstruction: EXCEPTION: Seg Read Fail: Status = 0000
Reconstruction: EXCEPTION: Error in Header
Reconstruction: EXCEPTION: Error in first Header disc sector
ReadFooters (Backwards): Segment 045E StartLBA 001C4010 Starting Footer LBA 001C4640

   SeqNum 0015D1B8
MC Internal LPC Process
Starting LBA of RW Request=00000000000388C8  Length=00000009
ProcessRWError -Read-   at LBA 00000000000388C8  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 00000000000388C8!

  Footer Status = 0000
Starting LBA of RW Request=00000000000388BF  Length=00000009
ProcessRWError -Read-   at LBA 00000000000388BF  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 00000000000388BF!

  Footer Status = 0000
Starting LBA of RW Request=00000000000388B6  Length=00000009
ProcessRWError -Read-   at LBA 00000000000388B6  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 00000000000388B6!

  Footer Status = 0000
Starting LBA of RW Request=00000000000388AD  Length=00000009
ProcessRWError -Read-   at LBA 00000000000388AD  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 00000000000388AD!

  Footer Status = 0000
Starting LBA of RW Request=00000000000388A4  Length=00000009
ProcessRWError -Read-   at LBA 00000000000388A4  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 00000000000388A4!

  Footer Status = 0000
Starting LBA of RW Request=000000000003889B  Length=00000009
ProcessRWError -Read-   at LBA 000000000003889B  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 000000000003889B!

  Footer Status = 0000
Starting LBA of RW Request=0000000000038892  Length=00000009
ProcessRWError -Read-   at LBA 0000000000038892  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000038892!

  Footer Status = 0000
Starting LBA of RW Request=0000000000038889  Length=00000009
ProcessRWError -Read-   at LBA 0000000000038889  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000038889!

  Footer Status = 0000
Starting LBA of RW Request=0000000000038880  Length=00000009
ProcessRWError -Read-   at LBA 0000000000038880  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000038880!

  Footer Status = 0000
Starting LBA of RW Request=0000000000038877  Length=00000009
ProcessRWError -Read-   at LBA 0000000000038877  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000038877!

  Footer Status = 0000
Starting LBA of RW Request=000000000003886E  Length=00000009
ProcessRWError -Read-   at LBA 000000000003886E  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 000000000003886E!

  Footer Status = 0000
Starting LBA of RW Request=0000000000038865  Length=00000009
ProcessRWError -Read-   at LBA 0000000000038865  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000038865!

  Footer Status = 0000
Starting LBA of RW Request=000000000003885C  Length=00000009
ProcessRWError -Read-   at LBA 000000000003885C  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 000000000003885C!

  Footer Status = 0000
Starting LBA of RW Request=0000000000038853  Length=00000009
ProcessRWError -Read-   at LBA 0000000000038853  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000038853!

  Footer Status = 0000
Starting LBA of RW Request=000000000003884A  Length=00000009
ProcessRWError -Read-   at LBA 000000000003884A  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 000000000003884A!

  Footer Status = 0000
Starting LBA of RW Request=0000000000038841  Length=00000009
ProcessRWError -Read-   at LBA 0000000000038841  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000038841!

  Footer Status = 0000
Starting LBA of RW Request=0000000000038838  Length=00000009
ProcessRWError -Read-   at LBA 0000000000038838  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000038838!

  Footer Status = 0000
Starting LBA of RW Request=000000000003882F  Length=00000009
ProcessRWError -Read-   at LBA 000000000003882F  Sense Code=C3160080
InitiateMarkPendingReallocateRequest for disc_lba: 000000000003882F!

  Footer Status = 0000
Starting LBA of RW Request=0000000000038826  Length=00000009
ProcessRWError -Read-   at LBA 0000000000038826  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000038826!

  Footer Status = 0000
Starting LBA of RW Request=000000000003881D  Length=00000009
ProcessRWError -Read-   at LBA 000000000003881D  Sense Code=C3160080
InitiateMarkPendingReallocateRequest for disc_lba: 000000000003881D!

  Footer Status = 0000
Starting LBA of RW Request=0000000000038814  Length=00000009
ProcessRWError -Read-   at LBA 0000000000038814  Sense Code=43110081
InitiateMarkPendingReallocateRequest for disc_lba: 0000000000038814!

  Footer Status = 0000
Starting LBA of RW Request=000000000003880B  Length=00000009
ProcessRWError -Read-   at LBA 000000000003880B  Sense Code=C3160080
InitiateMarkPendingReallocateRequest for disc_lba: 000000000003880B!

  Footer Status = 0000
Reconstruction: EXCEPTION: Error in Header and ALL Footers.
Continuing after error
Reconstruction: Completed 0: HeadPtr was unwritten
[MCMTWS]
Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001E
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
LED:00000047 FAddr:FFFFFFFE
Attachments
log.txt
(7.99 KiB) Downloaded 997 times

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 11th, 2016, 11:43

There is other way if you have special tools and software. If not - only shorting read channel.

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 11th, 2016, 21:16

What other tools and software do I need?

When should I short the read channel?

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 11th, 2016, 21:43

Using short read channel as keywords in the search function of the forum:
search.php?keywords=short+the+read+channel&terms=all&author=&sc=1&sf=all&sk=t&sd=d&sr=posts&st=0&ch=300&t=0&submit=Search

Plenty of info.

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 12th, 2016, 13:08

can you need shorting points
Please see the picture under link. try red pins first, and if they not work, try yellow pair
short-point.jpg

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 13th, 2016, 7:51

labtech wrote:Using short read channel as keywords in the search function of the forum:
search.php?keywords=short+the+read+channel&terms=all&author=&sc=1&sf=all&sk=t&sd=d&sr=posts&st=0&ch=300&t=0&submit=Search

Plenty of info.


I have searched but there is so much conflicting information.

For example this post by gps31 says "Short immediately after Second SPIN UP message and before (P) SATA Reset"

But this post by saltwater says "You have to short HSA read channel pins after (P) SATA Reset and hold 5-10 secs."

Which is it?

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 13th, 2016, 20:25

Right before, but sometimes is tricky. The timing has to be right. Finding and practicing with another drive should help.

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 17th, 2016, 14:30

OK, I finally got to the terminal by shorting the red pair after second "Spin Up" and holding until "No HOST FIS"

^L output:
Grenada Luxor 2.1 RAP22 - GR Hda DH, DETCR, 4K Zest
Product FamilyId: 58, MemberId: 06
HDA SN: W1D07NB5, RPM: 7199, Wedges: 188, Heads: 2, OrigHeads: A, Lbas: 00000EA468E0, PreampType: B2 13
PCBA SN: 0000M215F8EG, Controller: LUXORL_2_1( 202)(FF-FF-FF-FF), Channel: ITERATIVE, PowerAsic: MCKINLEY DESKTOP LITE Rev 15, BufferBytes: 4000000
Package Version: GR753B.CCD4.BN01BC.CC4H , Package P/N: 100708662, Package Global ID: 00188399,
Package Build Date: 05/22/2012, Package Build Time: 11:39:28, Package CFW Version: GR75.CCD4.00455097.00188399,
Package SFW1 Version: B3A9, Package SFW2 Version: ----, Package SFW3 Version: ----, Package SFW4 Version: ----
Controller FW Rev: 05221139, CustomerRel: CC4H, Changelist: 00455097, ProdType: GR75.CCD4, Date: 05/22/2012, Time: 113928, UserId: 00188399
Servo FW Rev: B3A9
RAP FW Implementation Key: 16, Format Rev: 0002, Contents Rev: 5F 02 00 00
Features:
- Quadradic Equation AFH enabled
- VBAR with adjustable zone boundaries enabled
- Volume Based Sparing enabled
- IOEDC enabled
- IOECC enabled
- DERP Read Retries enabled v. 3.8.00.0000000000001FF7
- LTTC-UDR2 enabled


I think the heads are OK (I had swapped them from a donor):
F3 7>X

Head 00 Resistance 0172
Head 01 Resistance 014C


I tried to recover media cache:
F3 A>R0,10000
F3 A>R10000,10000
F3 A>R20000,10000
F3 A>R30000,10000
F3 A>R40000,10000
F3 A>R50000,10000
F3 A>R60000,10000
F3 A>R70000,10000
F3 A>R80000,85a1

F3 2>P0000,0000

F3 A>W0,10000
F3 A>W10000,10000
F3 A>W20000,10000
F3 A>W30000,10000
F3 A>W40000,10000
F3 A>W50000,10000
F3 A>W60000,10000
F3 A>W70000,10000
F3 A>W80000,85a1


I set these ConGen flags:
F3 T>F"RWRecoveryFlags",00,22
F3 T>F"BGMSFlags",00,22
F3 T>F"PerformanceFlags",043C,22
F3 T>F,,22


I disabled media cache:
F3 T>F"MediaCacheControl",00


The drive still does not ID. Any ideas?

I think this might mean the Service Area (SA) is damaged. Is it possible to re-write/repair over the serial (TTL) port?

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 17th, 2016, 17:18

https://forum.hddguru.com/viewtopic.php ... 68#p237068

fzabkar wrote:Read and Write F3 Arch Sys files with HyperTerminal :
http://www.hddoracle.com/viewtopic.php? ... 1455#p7475

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 17th, 2016, 17:37

jermy wrote:https://forum.hddguru.com/viewtopic.php?f=1&t=33949&p=237068#p237068

fzabkar wrote:Read and Write F3 Arch Sys files with HyperTerminal :
http://www.hddoracle.com/viewtopic.php? ... 1455#p7475


Yes I can already read sys files/modules just fine from it. I don't know what to change to repair it.

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 17th, 2016, 22:10

Head 0 is a bit higher in value. If it still works, it is likely plagued with bad sectors, hence why why the drive is unstable.

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 18th, 2016, 8:53

labtech wrote:Head 0 is a bit higher in value. If it still works, it is likely plagued with bad sectors, hence why why the drive is unstable.


So, what's my course of action for data recovery?

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 18th, 2016, 18:29

Professional help. Seen a drive in similar condition just like yours few hours ago, same model, head 2 is weak. Need advanced tools to properly do the job and maximize data recovery chances.

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 19th, 2016, 0:49

labtech wrote:Head 0 is a bit higher in value. If it still works, it is likely plagued with bad sectors, hence why why the drive is unstable.

Does the drive maintain a record of its original head resistances, maybe in a manufacturing log?

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 19th, 2016, 4:06

Sense Code=43110081 - UNC error

Either caused by bad heads / sectors, but because there are so many of these errors in terminal i would say heads are bad.
These drive deteriorate very quickly in this state so i would stop powering the drive until it has had a head swap.

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 19th, 2016, 7:09

fzabkar wrote:
labtech wrote:Head 0 is a bit higher in value. If it still works, it is likely plagued with bad sectors, hence why why the drive is unstable.

Does the drive maintain a record of its original head resistances, maybe in a manufacturing log?

Not that I know of. But I usually keep notes of changes in head read ability as its performance deteriorates and check before and after. Sometimes, it does show a "worse" reading after.

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 20th, 2016, 2:08

labtech wrote:Professional help. Seen a drive in similar condition just like yours few hours ago, same model, head 2 is weak. Need advanced tools to properly do the job and maximize data recovery chances.


I can appreciate that "professional help" is certainly better. Being a "hands-on" and technically-minded person, I would rather solve the problem myself and learn on the way as well. Who knows, maybe I can eventually become a "professional".

I had already sent this drive to DataTech Labs who wanted $1700. That's a little too much IMO for the data on this drive. Nevertheless, I'd like to make my own efforts.

Which "advanced tools" do I need? PC-3000 seems like a glorified TTL with built-in SATA controller. The packaged software (and knowledge contained therein) is obviously key.

What can "advanced tools" provide that I can't with a little bit of knowledge?

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 20th, 2016, 17:51

Mainly, ability to handle ATA commands automatically based on scripts to optimize imaging parameters in a manner of maximizing chances of success.

Subsequently, ability to image select areas through head mapping, along with critical files through object mapping and so on.

Re: Seagate Barracuda ST1000DM003 not detected by BIOS

August 22nd, 2016, 13:34

If you have a little bit of knowledge you still need good tools. PC3000 is must have for pro. If you have ability to write software you can write something similar.
Post a reply