siamak5561
Data Recovery Novice
Posts: 66
Joined: Mon Jul 16, 2018 7:17 pm

Seagate ST1000DM003 Detect problem

Mon Apr 08, 2019 11:45 am

Hi
Normally cant get F3 with this drive, so with Virtual start function in MRT I get F3 , but almost all terminal command not work like :

F3 T>i4,1,22

Overlay PartNum: 02191019
CFW PartNum: 04191054
Overlay CompileDate: 20130219
CFW CompileDate: 20130419

OverlayCompatibilityCheck failed

Unable to load Diag Cmd Processor Overlay


F3 T>
ASCII Diag mode

F3 T>/T

F3 T>m0,6,3,,,,,22

Overlay PartNum: 02191019
CFW PartNum: 04191054
Overlay CompileDate: 20130219
CFW CompileDate: 20130419

OverlayCompatibilityCheck failed

Unable to load Diag Cmd Processor Overlay

F3 T>
ASCII Diag mode

F3 T>/T

F3 T>F,,22

Overlay PartNum: 02191019
CFW PartNum: 04191054
Overlay CompileDate: 20130219
CFW CompileDate: 20130419

OverlayCompatibilityCheck failed

Unable to load Diag Cmd Processor Overlay

F3 T>


Just /1N1 work, So any suggestion?
A Beginner in Data Recovery with MRT Ultra

User avatar
Jared
Forum Admin
Posts: 3663
Joined: Mon Jan 12, 2015 12:32 pm
Location: Providence, RI
Contact: Website Facebook Twitter Skype YouTube Google+

Seagate ST1000DM003 Detect problem

Mon Apr 08, 2019 12:30 pm

siamak5561 wrote:F3 T>m0,6,3,,,,,22


Why on earth did you do this? That was the wrong move, and probably just nuked all hope of recovery. M commands are only to be used in specific cases and only when you actually know what you're doing with the command. It's not some magical fix all command you should just toss in there.

In all likelihood, your original problem was just a reallocation or media cache issue that would take five minutes for a pro to fix. Now you can only hope that the drive didn't even begin to run that command.

The time to ask for help is BEFORE YOU DESTROY THE DRIVE COMPLETELY!!!

siamak5561
Data Recovery Novice
Posts: 66
Joined: Mon Jul 16, 2018 7:17 pm

Seagate ST1000DM003 Detect problem

Mon Apr 08, 2019 1:39 pm

Jared wrote:
siamak5561 wrote:F3 T>m0,6,3,,,,,22


Why on earth did you do this? That was the wrong move, and probably just nuked all hope of recovery. M commands are only to be used in specific cases and only when you actually know what you're doing with the command. It's not some magical fix all command you should just toss in there.

In all likelihood, your original problem was just a reallocation or media cache issue that would take five minutes for a pro to fix. Now you can only hope that the drive didn't even begin to run that command.

The time to ask for help is BEFORE YOU DESTROY THE DRIVE COMPLETELY!!!


Yes i Know about M commands, but Data not important, just want to repair drive.
A Beginner in Data Recovery with MRT Ultra

hdd00
Data Recovery Noob
Posts: 47
Joined: Fri Apr 10, 2015 4:37 am

Seagate ST1000DM003 Detect problem

Tue Apr 09, 2019 12:03 am

There is a incompatibility between the overlays as you can see. Either the Rom is not original or you loaded an incompatible 3D module (virtual start) to the drive.
If the Rom is original, try to load other 3D modules versions to the drive.

siamak5561
Data Recovery Novice
Posts: 66
Joined: Mon Jul 16, 2018 7:17 pm

Seagate ST1000DM003 Detect problem

Tue Apr 09, 2019 12:18 pm

hdd00 wrote:There is a incompatibility between the overlays as you can see. Either the Rom is not original or you loaded an incompatible 3D module (virtual start) to the drive.
If the Rom is original, try to load other 3D modules versions to the drive.


i test several other 3d modules but with them i didnt even get F3 . I even replace pcb but nothing changed.

this is when normally start drive


Off Topic
Boot 0x40M
Spin Up
RECOV Servo Op=0100 Resp=0005
Trans.

Spin Up
SpinOK
TCC:001C

(P) SATA Reset
A Beginner in Data Recovery with MRT Ultra

User avatar
Jared
Forum Admin
Posts: 3663
Joined: Mon Jan 12, 2015 12:32 pm
Location: Providence, RI
Contact: Website Facebook Twitter Skype YouTube Google+

Seagate ST1000DM003 Detect problem

Tue Apr 09, 2019 2:29 pm

That looks like a pretty normal start up to me. Are you sure it isn't just getting stuck busy?

If you can get to this:
siamak5561 wrote:Source of the post (P) SATA Reset


Then most the firmware is loaded. You've probably just got to patch up system file 93 to get the drive working. Then you can refurb using the normal methods of a bad sector drive.

siamak5561
Data Recovery Novice
Posts: 66
Joined: Mon Jul 16, 2018 7:17 pm

Seagate ST1000DM003 Detect problem

Wed Apr 10, 2019 2:02 am

Jared wrote:That looks like a pretty normal start up to me. Are you sure it isn't just getting stuck busy?

If you can get to this:
siamak5561 wrote:Source of the post (P) SATA Reset


Then most the firmware is loaded. You've probably just got to patch up system file 93 to get the drive working. Then you can refurb using the normal methods of a bad sector drive.


But I dont access to sys files, nor terminal, any other way to get sys files?
A Beginner in Data Recovery with MRT Ultra

User avatar
Jared
Forum Admin
Posts: 3663
Joined: Mon Jan 12, 2015 12:32 pm
Location: Providence, RI
Contact: Website Facebook Twitter Skype YouTube Google+

Seagate ST1000DM003 Detect problem

Wed Apr 10, 2019 12:38 pm

Contact me on Skype, I can remotely connect in and show you.

siamak5561
Data Recovery Novice
Posts: 66
Joined: Mon Jul 16, 2018 7:17 pm

Seagate ST1000DM003 Detect problem

Sun Apr 14, 2019 1:06 pm

Jared wrote:Contact me on Skype, I can remotely connect in and show you.


So, I manage to get F3, how to patch sys file 93?
A Beginner in Data Recovery with MRT Ultra

Return to “Seagate Data Recovery”

Who is online

Users browsing this forum: No registered users and 0 guests