Hello, I got a new MRT tool and I am still learning and training on some of my old drives.
Imaging drives was quite easy to get and I was able to recover all of them except one. This one don't identify itself. So I was first time opening the Seagate-Tools and try to read some Informations...
Till now I found out:
1) When I wait till the drive become ready (DRD-Light is green) then the drive don't identify and he dont show a serial-number, firmware-version or even the capacity.
2) When I start the F3-Tool directly after powering on the drive it identifies with S/N, Firmware-Version and Capacity correct.
The initial Scan (ATA mode) results with the following:
Code:
Identifying device...
Device identification error!
Getting detailed firmware version...
Failed to get firmware version!
Physical sector size : .............................Failed to get
physical sector size of service area : .............Failed to get
Number of physical heads : .........................Failed to get
Get System module information ...
ID length Description
=========================
Failed to get system module information!
Getting DT information...
ROM:
ID Offset address Length
============================
00 06020100 33792
01 06020000 256
04 04001000 4096
0602BE00 4096
total 8192
05 0006C000 81920
08 10070000 948
0A 060A731C 1024
12 100D4000 104
13 060B1F6C 544
14 060B218C 64
15 00000000 524288
Getting service area size.......
Service area size: : ................................Fail
Getting list of sys files.......
Serial port error!
Unable to get relevant data from DT List!
I also can't get the terminal-connection running - not by selecting Terminal-Mode immideatly and not by switching after the scan to terminal mode. The only thing which I can access at the Moment is the ROM.
It's a
Seagate 7200.11 drive with 250GB (
ST3250310NS) with Firmware
SN04.
What I could do form there on?
Flash a new firmware with the ISO from Seagate?
Fix the firmware in some way with one of the MRT-Options?
Is maybe something with the PCB wrong? (I checked it under a 10x microscope for burnmarks, bad connections of SMDs and other visible damages)
I was also googeling and searching here but only thing I found was:
Quote:
Damn UDMA not always works on NS
It is working now, i did it manually.
... What exact does that mean?