I buggered my drive up. I guess I powered it up and shut it down to many times in a short space of time. I was trying to get my computer to work as it crashed and well...

Now my 2TB drive will not reconise at all. It worked fine and was not the cause of my computer crashing. My man handling massed it up.

Drive not damaged or shocked. I think it is some kind of firmware issue due to the resets.

The drive contains Movies Series and so on. Nothing that can be pulled of backups, but there are some that I havent backed up and will be a pain to get again.

I also want to see if this drive can be repaired to work again. I had no problems with it at all until I abused it...

Drive has failed inside PC.
Nothing was written to the drive when it failed
Failed when being powered on and off.
Drive has not been opened.
When powered on, it performs all the calibration sounds like normal. No strange sounds or such.
Only been powered 4 times.
I believe firmware is corrupted, busy, or locked.

No terminal info, sorry. I cant get the adapter pins in and I don't want to mess with that, like I did with my last drive.

Anyone able to see if they can bring life to this. Please let me know.

Shane

Any good DR companies in the UK that you recommend in the UK that can perhaps spin this drive up and get it working for a good fee? I would like to get this drive back in working order.

Thanks

I got terminal to work and the drive goes into F3 T>

What does this mean?

Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
Retry delay
MCMainPOR: Start:
User Data Base 009AAAB0
MCInitialize: Start: Host VBM Size (Bytes): 00000210 Metadata VBM Size (Bytes) :
ClearMC: Start Full Starting LBA 000174A8, Count 00989AE0.
ClearMC: Completed, Last LBA 00009A0F88
MCInitialize: MC Cleared
MCInitialize: MCTBufferPtr->Header.MCTStateFlags = 0000000A
MCInitialize: MCTBufferPtr->Header.MCStateFlagsDisc = 00000001
MCInitialize: MCStateFlags = 00000001

Set MCMT Version Current
[MCMTWS] Tail/Head 0000 0000
MCInitialize: Init complete:
MCMainPOR: MCTStateFlags 00000022 MCStateFlags 00000040 Tms 00000000 00000000 00006644 PASS
No HOST FIS-ReadyStatusFlags 0002A1A1

So, I've been doing more stuff in terminal, getting info mainly.

The V1 list loads and I think the translator is loading. Not sure on this. I get 1 entry on it.
V2 List brings back 8 entries
V4 has no entires
V10 Has a mountain of entries.
V40 has nothing
N5 returns smart info. So looks like that is okay.

Not sure where to go from here. I don't want to use any of the ***m0,2,2,,,,,22*** commands if the translator is okay and its not needed.

Any recommendations to get drive online again, otherwise it will be scrapped.

Drive still loads in its original above state in terminal.

Shane

PcImage in Peterborough, ask for Sean.

_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
http://www.rescue-it.se

V1 should have lots of entries... so it is probably not loaded

_________________
Adatmentés - Data recovery

Damn. Look like I need to rebuild it. From what I understand I also have to take the P and G list into consideration otherwise I might get partial access?

I'll post the list entries once I hook the drive to the terminal again.

I have a feeling the drive was writing something when I powered it off too suddenly and it corrupted a firmware somewhere. But I could be totally wrong.

Shane

The translator is not loaded and that's why you get the NOHOST message on your terminal.
It is my understanding that the data on this drive is not valuable, thus you can proceed with m0 command to get the drive working again.

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

From what I can understand m0,6,2,,,,,22 command is commonly used and the safest to rebuild the translator?

I see that the other commands in this post. So I would like to know the best one to use without bricking the drive and still keep user data if possible. https://www.data-medics.com/forum/seaga ... me|61-1224

Then again, would this command be better, (m0,2,1,,,,,22 ( To rebuilt slip list, V1 )) to rebuild the list if it only had one entry and it should have more?

My other post is not posting... Umm, it was this. what exactly does (m0,6,2,,,,,22) command do? Would it be better if I use this as its the most commonly used command.

Shane

I ran the command it seems to have done the trick, the drive is back up and running and I am able to view all the three partitions. But I just noticed that some of the files in the first partition are damaged, so I think something caused bad sectors at the beginning of the drive. The other sectors are okay, so I will grab what I don't have and investigate the drive somemore.

Here is the terminal log: -

Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
Retry delay
MCMainPOR: Start:
User Data Base 009AAAB0
MCInitialize: Start: Host VBM Size (Bytes): 00000210 Metadata VBM Size (Bytes) :
ClearMC: Start Full Starting LBA 000174A8, Count 00989AE0.
ClearMC: Completed, Last LBA 00009A0F88
MCInitialize: MC Cleared
MCInitialize: MCTBufferPtr->Header.MCTStateFlags = 0000000A
MCInitialize: MCTBufferPtr->Header.MCStateFlagsDisc = 00000001
MCInitialize: MCStateFlags = 00000001

Set MCMT Version Current
[MCMTWS] Tail/Head 0000 0000
MCInitialize: Init complete:
MCMainPOR: MCTStateFlags 00000022 MCStateFlags 00000040 Tms 00000000 00000000 0000663B PASS
No HOST FIS-ReadyStatusFlags 0002A1A1
ASCII Diag mode

F3 T>V4
Reassigned Sectors List Enabled
Entries: 0000, Alts: 0000, Removed: 002D,
Pending: 0000 Host Pending: 0000
Idx LBA PBA LLLCHS of LBA Wdg PLPCHS of PBA SFI Hours Msecs Status BBM Mask

F3 T>V40
Nonresident GList 0 entries returned
Total entries available: 0
PBA Len Flags Phy Cyl Hd PhySctr SFI

F3 T>m0,6,2,,,,,22
Max Wr Retries = 08, Max Rd Retries = 32, Max Iterations = 3A, Max Certify Rewrite Retries = 001B

(DOS) File Save

(DOS) File Save

Update Capacity and Save
Update HPA Cap and Save
User Partition Format Successful - Elapsed Time 0 mins 00 secs

F3 T>
Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
(P) SATA Reset

That V1 list is BIG!

It means that you(or somebody) tried to recalculate translator and the drive is currently finishing it by clearing the MC
And it is very possible that the drive cannot write and killed the translator, showing you the error now.

Find out if heads can write, change them if they can't and fix SA

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.