M3 not responding HX-M401TCB/G

[DarkZeros]

Hi, I recently had a problem with my HDD, and it is so weird that I need some guidelines if possible.
The drive is a Samsung/Maxtor M3. Manufacture by Seagate. Model HX-M401TCB/G.

Normally I am used to drives slowly failling over time.
But this time it started going slow, really slow, no clicking sounds, just slow and died in 5minutes. Up to the point drive was not even opening. I disconected and connected it again multiple times, in multiple USB 3 conectors (it is a single conector USB3 drive). No luck.

Sympthomp:
- LED is off (it used to be on, even when idle)
- Detected by PC, but as BAD DRIVE.
- Imposible to reinitialize with any tool.
- GB size is wrong, detected as 0b or 2190GB.
- HDD Disc spins normally when pluged, but doesnt do any sound when given read/write commands.

I am thinking the board is dead.
I was triying to look for Seagate Firmware to reflash it but no luck.

I have lots of data in the drive, while I do have a copy, it is really scattered in thousands of CDs (It is a 4TB drive). So It can take me days of job to rebuild it to the previus state.

Any guidance?
Do you think is possible to recover? I am thinking that after repairing the board the data should be fine.

Thanks!

[jermy]

If there "ISN'T" unusual noise coming from the HDD, a terminal log would be a good start

[northwind]

Wow, a 4TB 2.5" Samsung drive (it's not a Seagate).

I agree with Jermy, get a terminal output, assuming it doesn't make any weird sound.
If it does, better start putting those CDs with your backups together

[pcimage]

It is a Seagate drive, rebranded as Samsung and in a Samsung box.

I've got one right here, a ST4000LM016 drive

Looks like a typical Seagate "Freeplay" drive.

If the drive is spinning then it's 99.99% likely NOT anything to do with PCB.

Should be an inexpensive recovery AT THIS STAGE, if it's not tampered with!

[northwind]

Aha, so Seagate, Rebranded as Samsung and in a Maxtor/Samsung case?
My bad! Never seen one.
Still, terminal should be in order.

[pcimage]

Aha, so Seagate, Rebranded as Samsung and in a Maxtor/Samsung case?
My bad! Never seen one.
Still, terminal should be in order.

That's rightl! I've only ever had one in.

And yes, a terminal output may well give some clues as to what is going on!

[DarkZeros]

What do you mean by terminal?

I can handle myself with ubuntu and bash, but is anything special I need to do? Some tool to launch and get the log?
GParted?

Thanks

[northwind]

Search this forum for 'seagate terminal' and 'TTL' and you'll get your answers.

However, if data is important, I STRONGLY suggest you consult Sean @ pcimage.co.uk

[MindMergepk]

Search this forum for 'seagate terminal' and 'TTL' and you'll get your answers.

However, if data is important, I STRONGLY suggest you consult Sean @ pcimage.co.uk

+1

Sean is highly recommended

[fzabkar]

How to connect a terminal cable on a Samsung drive ?
http://www.hddoracle.com/viewtopic.php?f=116&t=189

[DarkZeros]

I haven't connected yet the cable I am thinking to buy the tools to do the connection.
But a technician analized it, aparently the firmware/trasnlation tables are dead the rest of the disc is ok (mechanically).

He said that a firmware has to be reflashed. However, it is not posible to find the original one in Seagate website. And he said the firmware in this chip is signed so there is nothing to do.

Is this a proper veredict? Will I be able to find more by connecting the TTL?
Is it even possible to get the firmware from another drive and then flash it?

If I can't do it cheaply I will just say byebye and start doing all my collection again...

Any help is welcome!

[fzabkar]

How to connect the TTL Adaptor to a Seagate drive :
http://www.hddoracle.com/viewtopic.php?f=6&t=193

[rogfanther]

First you need to decide if you want the data to the point of paying for it. If you send it to pcimage now, it should not cost that much. But after the drives passes for a couple of people´s hands, costs of recovery ( if still possible ) can go up fast.

If you rule out sending the drive to someone, then follow the links , get the TTL log and post it here.

[DarkZeros]

Hi Guys, After some time, managed to get a TTL device. And.... I got this:

Boot 0x80M
Low Current Spin
RECOV Servo Op=0095 Resp=0005[LBA=0x00000001]
DSC
SIM Error 2042 LBA 0000000000011274 FD FC35B028
RW Error 00000080
(DOS Table) Worst Count: 00001194 At SU: 002BAC31
Intel 6G->3G
Send Status: COMRESET seen
CSpd= 3Gbps
Set Transfer Mode selected
PIO selected
Set Transfer Mode selected
Ultra DMA selected
ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

Unrecoverable Read Verify Error Reported

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

Unrecoverable Read Verify Error Reported

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

Unrecoverable Read Verify Error Reported

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

Unrecoverable Read Verify Error Reported

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

Unrecoverable Read Verify Error Reported

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

Unrecoverable Read Verify Error Reported

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

Unrecoverable Read Verify Error Reported

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

Unrecoverable Read Verify Error Reported

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

Unrecoverable Read Verify Error Reported

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

Unrecoverable Read Verify Error Reported

DSC
ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A1

TCC:0018

Any help?
Seems that boot sector is wrong.... so.... firmware is in that sector not on a FLASH mem on board?

[DarkZeros]

Oh and one more thing, even though most commands seem to work, every time I input something wrong the response is "Diagnostic Port Locked".

I am unsure if this means I can't run that command, or is inexistant.

In case it is locked somehow, any possibility to unlock it?

More data from the disc:

Code:

Prod Desc: M10TDP SATA KarnakPlus.HDA.Kona,4K,MDW_520KTPI,SMR,3Gpre,DFW,10CH,1N2,128MB
Package Version: M0A0A03B3.SDMA.MB000G.
Serial #: W800CZWB
Changelist: 00926500
Model #: ST4000LM016-1N2170
ID: 101
Default factory config: SD&D
Active config: SD&D


And trying to clear SMART data, (was empty anyway) makes the HDD stop responding to comands and spam this meassage every minute or so:

Code:

F3 T>/1
F3 1>N1

LED:0x0000000BD FAddr:0x00008004

LED:0x0000000BD FAddr:0x00008004

...

[data-medics]

It's a SED drive with encrypted firmware. I'm afraid that for this model no one that I know of has a way to unlock the terminal yet (at least not for this model). I managed to recover one that was a media cache issue before, but I'm not sure if my technique would work in your case and it would require a tool like PC-3000 to even attempt it.

It may even be a bad read/write head. Hard to tell from that output.

[DarkZeros]

Ok, I give up. Ill send it for warranty....

- SED can't be unlocked.
- Even if I can, I would need to find a new firmware to flash, this one seems dead and unreadable, and is hard to find.
- If the firmware is dead something else is wrong in the drive, data is not corrupted by itself, and it started by being very slow but accessible, so I am prone to think something terrible was going on before the firmware was damaged.

Thanks anyway!