SeaTools says the firmware revision is "unknown"; have you tried to find a firmware update for it? I'm not sure if SeaTools has an integrated firmware update utility.

Are you hoping to recover DATA or are you trying to get the drive working again ?

AlaricD wrote on 2020-10-29, 16:18:

SeaTools says the firmware revision is "unknown"; have you tried to find a firmware update for it? I'm not sure if SeaTools has an integrated firmware update utility.

That may just be due to the drive being connected through a USB to SATA converter that SeaTools does not like .

I just want to recover the drive. I don't care about anything on it.

script-fu wrote on 2020-10-29, 16:22:

I just want to recover the drive. I don't care about anything on it.

Having had a closer look at your screenshots, I believe this may well be a hardware failure of the drive .

A SMART diagnostic might be in order . Running the drive through a USB to SATA adapter might be an issue, though, hopefully not an un-surmountable one (some USB to SATA adapters do not pass SMART info).

Try the following programs .
https://www.passmark.com/products/diskcheckup/
https://sourceforge.net/projects/gsmartcontro … 32.exe/download

If Passmark DiskCheckup does not work, try Gsmartcontrol . If Gsmartcontrol does not work , try adding "-d sat" (without the double quotes) in the smartctl parameters field in Options-->Preferences and restarting the program .

Will do darry and i will report back when i get it done. Thank you

Here is the passmark dump

Here is the gsmartcontrol-1.1.3-win32 dump

If you need something more elaborate from those programs lmk.

What does the serial terminal say?

script-fu wrote on 2020-10-29, 17:01:

Here is the gsmartcontrol-1.1.3-win32 dump

If you need something more elaborate from those programs lmk.

Everything looks good to me in that SMART report, except those weird JMicron unsupported things .
I wonder if the USB to SATA adapter that you are using actually supports 48-bit LBA .

Do you have a modern (Windows 7 or higher) PC where you could connect the drive directly to a SATA port and do a drive wipe (at least the first few MegaBytes) with the utility of your choice ?

EDIT : I may be wrong about the 48-bit thing according to https://linux.die.net/man/8/smartctl . You could try to do a drive wipe (zero-fill) over USB .

Smart thing to use gsmartcontrol

No. SMART says read errors and seek errors count is too high, do not do anything to revive this and seagate SSHD is known to die once the NAND IC used up.

Get another hard drive anyway that is not Seagate except for Samsung designed drives under Seagate brand, Hitachi, HGST, Samsung, WD and Toshiba.

Cheers,

I tried again to run seatools but this time from a dos bootable cd i burned. All i get is a flashing cursor on a black background.

So the only thing i have is windows 10 computers. I can install the hard drive into one of them and hook it up just regular sata. I'm not sure what to use tho as the drive is locked.

Hum i tried this way to recover the drive. However diskpart said the hd was write protection. I could never get any further.
https://www.windowscentral.com/how-clean-and- … part-windows-10
https://ccm.net/forum/affich-801310-removing- … -using-diskpart

I do have some old flavors of linux live boot cd's here maybe 6 or 7 different ones. They let you bring the computer up and then you can decide to install linux if you want. Maybe that might help. I also have a older hiren's boot disk. I think all these are from 2011 or so.

pentiumspeed wrote on 2020-10-29, 17:35:

Smart thing to use gsmartcontrol […]
Show full quote

Smart thing to use gsmartcontrol

No. SMART says read errors and seek errors count is too high, do not do anything to revive this and seagate SSHD is known to die once the NAND IC used up.

Get another hard drive anyway that is not Seagate except for Samsung designed drives under Seagate brand, Hitachi, HGST, Samsung, WD and Toshiba.

Cheers,

PentiumSpeed are you saying this is a fake Seagate Firecuda?

darry wrote on 2020-10-29, 17:17:

You could try to do a drive wipe (zero-fill) over USB .

What software would i use darry?

Thanks

script-fu wrote on 2020-10-29, 17:40:

I tried again to run seatools but this time from a dos bootable cd i burned. All i get is a flashing cursor on a black backgroun […]
Show full quote

I tried again to run seatools but this time from a dos bootable cd i burned. All i get is a flashing cursor on a black background.

So the only thing i have is windows 10 computers. I can install the hard drive into one of them and hook it up just regular sata. I'm not sure what to use tho as the drive is locked.

Hum i tried this way to recover the drive. However diskpart said the hd was write protection. I could never get any further.
https://www.windowscentral.com/how-clean-and- … part-windows-10
https://ccm.net/forum/affich-801310-removing- … -using-diskpart

I do have some old flavors of linux live boot cd's here maybe 6 or 7 different ones. They let you bring the computer up and then you can decide to install linux if you want. Maybe that might help. I also have a older hiren's boot disk. I think all these are from 2011 or so.

Hmm, diskpart not working is not a good sign, AFAIK .

When I hit weird scenarios, my go-to solution is booting into Linux using a bootable USB drive or LiveCD (Ubuntu, for example ) with only the "bad" drive connected to a SATA port (avoids accidentally working on wrong drive) and AHCI disabled (switched to legacy or compatibility) in BIOS as some older AHCI implementations have freezing bugs at boot when a drive with weird data is connected .

Once booted to a root command line (sudo -i to become root), run

a) (to list detected drives, usually /dev/sda , /dev/sdb , etc)

1fdisk -l 

b) You can run

1hdparm -i /dev/sdx

to identify the drive, replacing sdx with the actual devices listed after running a)

c) Once you have identified the "bad" drive" , you can run

1dd if=/dev/zero of=/dev/sdx bs=512 count=100000

replacing sdx with the actual drive to overwrite the first 50MB or so with zeros .

No. I did not say fake. Just that Seagate had quality issues and I was careful not to use them if I have any back then and still is for me. I had to be careful with choosing one that is reliable would weary anyone trying to find Seagate hard drive models that are known reliable.

PS: Seagate bought Samsung's hard drive line long ago. Also Samsung drives are very good and is not influenced by Seagate design team.

Been in computing for more than 30 years.

Back in the day, I had one of Seagate hard drive given to me dead was around 80MB half height 3.5", The chips fell off the circuit board, yet looked soldered correctly but poor solder bond between copper pads and the solder. Then when I opened up, the rare earth magnets were dipped in paint to prevent corrosion burst open, swelled up and spewed powder that killed the platters. Rare earth magnets corrodes rapidly if exposed for this reason in later drives were nickel plated instead.

Cheers,

darry wrote on 2020-10-29, 18:03:

Hmm, diskpart not working is not a good sign, AFAIK . […]
Show full quote

Hmm, diskpart not working is not a good sign, AFAIK .

When I hit weird scenarios, my go-to solution is booting into Linux using a bootable USB drive or LiveCD (Ubuntu, for example ) with only the "bad" drive connected to a SATA port (avoids accidentally working on wrong drive) and AHCI disabled (switched to legacy or compatibility) in BIOS as some older AHCI implementations have freezing bugs at boot when a drive with weird data is connected .

Once booted to a root command line (sudo -i to become root), run

a) (to list detected drives, usually /dev/sda , /dev/sdb , etc)

Copy code to clipboard

1fdisk -l 

b) You can run

Copy code to clipboard

1hdparm -i /dev/sdx

to identify the drive, replacing sdx with the actual devices listed after running a)

c) Once you have identified the "bad" drive" , you can run

Copy code to clipboard

1dd if=/dev/zero of=/dev/sdx bs=512 count=100000

replacing sdx with the actual drive to overwrite the first 50MB or so with zeros .

Okay i will give this a shot. I'm not sure if i can get around the blinking cursor tho. I haven't so far. I will report back and thank you all for your time.

_Best

pentiumspeed wrote on 2020-10-29, 18:18:

No. I did not say fake. Just that Seagate had quality issues and I was careful not to use them if I have any back then and still is for me. I had to be careful with choosing one that is reliable would weary anyone trying to find reliable Seagate hard drive.

Been in computing for more than 30 years.

Cheers,

Ahhh it's a seagate thing i understand.

Yep the computer wont boot at all with the hard drive plugged in as master. It also wont let the computer boot when plugged in USB. However you can see the drive over USB in windows 10 with all those programs. I have multiple USB devices that plug up to sata as well right down to an old USB/Firewire dual toaster.

The only way to save this drive will need to be thru USB me thinks.

script-fu wrote on 2020-10-29, 18:34:

Yep the computer wont boot at all with the hard drive plugged in as master. It also wont let the computer boot when plugged in USB. However you can see the drive over USB in windows 10 with all those programs. I have multiple USB devices that plug up to sata as well right down to an old USB/Firewire dual toaster.

The only way to save this drive will need to be thru USB me thinks.

You can boot the computer into Linux without the drive connected and then, once it's booted, connected the "bad" drive over USB .

You should still be able to follow the steps for wiping, unless something is physically wrong with the drive .