Working with a Seagate ST1000DM003 from an Apple iMac.

Spins up fine, no out of the ordinary noises. Does not show up in bios or in OS (Windows, OS X, Ubuntu). Actually briefly showed up in OS X but dropped out within seconds.

It causes exceedingly long post and boot when connected.

No errors to speak of in F3 UART. Can spin up and down without issue. Head resistance checks out.

NRG is empty.

SMART will not clear. When i run the command it does nothing at all, and on power cycle the table is not cleared. I have not attempted to clear the G list at this point.

Ive only really used readonly commands on it at this point, but everything works exactly as i would expect. That is to say, it acts like a functional drive.

Any thoughts on the best course of action at this point? Happy to provide any logs requested.

Thank You

Given the model, it's most likely the media cache or auto-reallocation functions. You'll need to modify system file 93 to disable these features and stabilize the drive.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company

I appreciate it. Thank You

I am doing this over UART.

I have what i believe to be file 93 read from the drive -
Is there a process for editing the hex to achieve disabling the settings question, or is this purely in the realm of PC-3000 and other systems?

What does a typical file 93 contain?

File is attached

Thank You

File 93

I helpful member has modified my file for me (looks like changing the first byte to 00, everything else is the same, for reference). Im not able to write this file back to the drive over UART, it just times out.

Any thoughts?

That doesn't seem right at all. The modification is much more than just zeroing out the first two bytes.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company

Here, try this:

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company

Also, when you write it back try doing it right after a power cycle. Power it on, then immediately try writing the file before it has time to get stuck busy.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company

Disregard that single byte change statement. Had a bad case of the Dum Dums and compared the wrong files.

No such luck. It tries to send the file (no bits transfer) and then after 60 seconds it times out and says " no response from remote system"

To clarify i am using a bus pirate to facilitate the UART connection, and Hyperterminal to send and receive the files, using YModem.

Using this as a reference http://www.hddoracle.com/viewtopic.php? ... e5853836e7

r093 works great
w093 times out

Is there a better way?

Im not sure if it is actually going into a busy state. Is there a way to determine this?

Ye, but not worth spending for one time job

I dont know if this is against forum etiquette or not, but I'm going to open this up for bids if anyone wants to give it a try. Just message me privately.

It is extremely likely that this is firmware/logical issue. I have no reason to suspect physical damage / bad or weak heads or anything real difficult.

I really just need it to be stable, i can do the actual data extraction here.

My thought is if someone wants to make a few bucks for probably a few minutes of machine time i am all ears.

Heads might not write because they are weak.

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