st3000dm001 wont pick up in bios firmware issue?

[professor_jonny]

I have a st3000dm001 drive and one day the computer started locking up accessing device manager and the hdd.

After a reboot the hdd would not pickup in bios.

The hdd spins up and makes the correct noises from the actuator like it is working it is not clicking and then spinning down or any thing like that.

is likely the problem an issue with the firmware or something more sinister?

from memory this drive had a firmware update ages ago to a new version.

I could fix this with just a ttl logic interface hooked up to the drive? of note there is nothing real important on the drive just a few years of downloading torrents so I'm keen to try to attempt a minor repair, so I can dump the data onto another drive as I have since read up these drive are failure prone.

I have read about the smart table causing a fault and errors in the glist? causing the drive to halt could this be my problem?

I'm guessing I need to plug in an interface and look to see what is wrong, is there an error report function or something can find out what the issue is?

firmware cc4c is written on the sticker on the lid.

[jermy]

Let's see the terminal log

[lcoughey]

It is not uncommon for this model of drive to have at least one head that is failing to read, too. If you value your data at all, it is best to seek the assistance of a data recovery professional who has the right tools and experience to handle these drives. If you try DIY methods without proper diagnosis, you will probably make things worse.

[hpw333]

it's better to post terminal log here

[professor_jonny]

ok so this is what I got in the log on boot up it looks like the mcmt pri is corrupt.

Code:

Boot 0x40M
Spin Up
TCC-001C[0x00026F7C][0x000273E8][0x00027854]
Trans.

Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001C
(P) SATA Reset

MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MCMainPOR: EXCEPTION: MCMT PRI copy corrupt
MCMainPOR:  MCMT SEC copy valid
Reconstruction: MCMT Reconstruction Start
  Max number of MC segments 0A61
Nonvolatile MCMT sequence number 0000DEA1
[RSRS] 05BA
ProcessRWError -Read-   at LBA 000000000004A7C2  Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 000000000004A7C2!

Reconstruction: Completed 1:
[MCMTWS]
Rst 0x40M
MC Internal LPC Process
Spin Up
TCC-001C
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

I found this that says it is fixable

http://www.dolphindatalab.com/seagate-f ... rfffffffe/

from what I gather I have to sort the read pins to gain terminal access but can I fix from terminal ?

[professor_jonny]

I'm guessing this means there is bad sectors in the sa?

[professor_jonny]

I managed to get into terminal and I believe this is the basic info

Code:

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

F3 T>V1
User Slip Defect List
                         log log   log     phys   phys
        LBA    span   cumm   cyl  hd  sctr zn   cyl   sctr     SFI      PBA
           0      0      0     0  0     0   0      0     0        9            0

Head 0: entries      1        slips        0
Head 1: entries      0        slips        0
Head 2: entries      0        slips        0
Head 3: entries      0        slips        0
Head 4: entries      0        slips        0
Head 5: entries      0        slips        0
  Total Entries      1  Total Slips        0

F3 T>


F3 7>X

Head 00Resistance 0159
Head 01 Resistance 0164
Head 02 Resistance 0114
Head 03 Resistance 0143
Head 04 Resistance 011B
Head 05 Resistance 0166

F3 7>

[professor_jonny]

I ran a non destructive test for defects and rebuilt the g-p and slip lists and now the drive pops up in windows and is accessible from diskmgmt.msc

what would be best now method to recover data I'm guessing ddrescue and create an image?

The partition table seems to be corrupt but on a scan with test disk shows files and folders present on the drive.

[Martin]

I ran a non destructive test for defects and rebuilt the g-p and slip lists

What comands were been used for that? Very interesting

[professor_jonny]

I believe these were the console commands I used

Code:

m0,2,1,,,,,22 To rebuilt slip list(V1)
m0,2,2,,,,,22 To rebuilt g list(V2)
m0,2,3,,,,,22 To rebuilt P list(V3)

as well as the N1 command to clear the smart data.

[labtech]

How long did rebuilding the p-list take?

[professor_jonny]

it seemed to take less than 1 min each on all three options it nagged a few errors during the functions then after a reboot of the drive it all come back working.

I was thinking all those options should of taken hours I was kind of stumped

[labtech]

I don't specialize in "drive repair", but I don't think in this case that command is actually "rebuilding the p-list".
Either way, if the intention is to recover files, then rebuilding those lists is not the solution.

[professor_jonny]

I rebuilt those files in an attempt to recover the firmware brick after doing a bit of reading of the terminal commands for the F3 series,
This seemed to work the drive is now accessible from within windows and it seemed to fix the initial mcmt corruption as the drive was stuck in a led fault and was inaccessible via terminal or the sata interface before hand.

At least from now on I can image the disk and get back some of what is on the drive, it is only a whole lot of torrent files I don't really care if I loose the data on there but it would be nice to recover it.

if it did re generate the sectors there may be a few corrupt files on the hdd with the wrong sectors mid data when I image it back off but it does not really matter as it is all video files.

I'm very happy for now, realistically I was expecting to just find out what the issue was and if it was going to cost heaps to repair or just a simple fix.

I'm guessing there is a defect in the SA area and this has masked the error or cleared the error pending relocation so the drive now does not attempt to recover it every time at first boot, really I have no idea.

It is some what working now so I'm more than happy with the outcome.

[hpw333]

I rebuilt those files in an attempt to recover the firmware brick after doing a bit of reading of the terminal commands for the F3 series,
This seemed to work the drive is now accessible from within windows and it seemed to fix the initial mcmt corruption as the drive was stuck in a led fault and was inaccessible via terminal or the sata interface before hand.

At least from now on I can image the disk and get back some of what is on the drive, it is only a whole lot of torrent files I don't really care if I loose the data on there but it would be nice to recover it.

if it did re generate the sectors there may be a few corrupt files on the hdd with the wrong sectors mid data when I image it back off but it does not really matter as it is all video files.

I'm very happy for now, realistically I was expecting to just find out what the issue was and if it was going to cost heaps to repair or just a simple fix.

I'm guessing there is a defect in the SA area and this has masked the error or cleared the error pending relocation so the drive now does not attempt to recover it every time at first boot, really I have no idea.

It is some what working now so I'm more than happy with the outcome.

Recover HDD by this way is very Wrong
and apply M command is not best for this problem
and cause many prb for your data
even your plist is not corrupted , why you need to build it ?
same question for Glist ?

did you know what the meaning of MCMT Problem ?
this problem is famous in F3 and solving is easy
try now to scan HDD With VCR And Check All Sector is good , or you have bad sector there ?

[professor_jonny]

There is a few bad sectors on the drive that popped up when imaging the drive nothing major.

I managed to get all files off the drive as there are video files a bad sector here and there is not going to cause much of an issue.

I don't think the m0 functions actually worked as they threw error's saying sector head failure and had to reboot drive after each attempt.

I think the clear smart function is the only one that actually worked.

I believe mcmt is the media cache I believe I disabled that using the F command.