Question Seagate external hdd not detecting after I accidently pulled it out when was in Use

[Nvrmndryo]

I was downloading some big files and my pc froze for a while, so I pulled the usb cable of the Seagate external hdd(1tb) and after that usb hdd is not detectable on my pc (win 10).
I tried connecting to my ps4 and its saying usb device file system is corrupted.
I tried to run diskpart in cmd and its showing disk 3(seagate external) as 3950mb size.
I also installed Diskinternals partition recovery tool and its showing unallocated 3.85 gb but my usb hdd is 1tb size.
I have very important data on this hdd, what could be done to save all the data or any way to recover the partition as it was before?

 

[Ralston18]

First thing you must be aware that anything you do could cause further data loss or make potentially recoverable data unrecoverable.

If you happen to have any copies of that important data be sure that those copies (in whole or in part) are safely away from the current host system. You do not want some error of omission or commission causing additional drive problems for working drives.

Second is that it is indeed very likely that the sudden unplugging caused file corruption.

How hard did you pull the USB cable? If quick and sudden maybe you damaged the cable.

Did you try another known working USB cable at any time during troubleshooting?

When connecting to the PS4 perhaps? Or did you use the Seagate's original USB cable?

Seagate Seatools:

https://www.seagate.com/support/downloads/seatools/seatools-win-master/

Learn what you can about the drive.

For file recovery Recuva may be viable.

Reference:

https://www.ccleaner.com/recuva/download

However, hold on any immediate attempts to "fix" the drive and/or recover data.

There may be other ideas and suggestions.

 

[fzabkar]

A capacity of 3.8GB is symptomatic of internal faults, ie bad heads or media. The firmware cannot reach the hidden, reserved System Area on the platters (SA), so it reverts to reporting a bogus capacity stored in the "ROM" on the PCB.

If CrystalDiskInfo cannot read the SMART data (which are stored in the SA), then this would confirm an internal fault.

 

[Nvrmndryo]

First thing you must be aware that anything you do could cause further data loss or make potentially recoverable data unrecoverable.

If you happen to have any copies of that important data be sure that those copies (in whole or in part) are safely away from the current host system. You do not want some error of omission or commission causing additional drive problems for working drives.

Second is that it is indeed very likely that the sudden unplugging caused file corruption.

How hard did you pull the USB cable? If quick and sudden maybe you damaged the cable.

Did you try another known working USB cable at any time during troubleshooting?

When connecting to the PS4 perhaps? Or did you use the Seagate's original USB cable?

Seagate Seatools:

https://www.seagate.com/support/downloads/seatools/seatools-win-master/

Learn what you can about the drive.

For file recovery Recuva may be viable.

Reference:

https://www.ccleaner.com/recuva/download

However, hold on any immediate attempts to "fix" the drive and/or recover data.

There may be other ideas and suggestions.

I did pull quickly but its the normal pull I do like usual.
Its an seagate goflex hdd which has old Mini usb cable, I don't have any other cable lying around so I did not try using different cable.
I used same original cable to connect to ps4.
I tried sea tools, but no help. Ill share the screenshot.
https://www.flickr.com/gp/21429760@N02/Ts0a18
Now i can try recovery but for that hdd needs to be formatted and first detected as a 1tb hdd.
I am waiting for sometime, lets see what other people say about this.

 

[Nvrmndryo]

A capacity of 3.8GB is symptomatic of internal faults, ie bad heads or media. The firmware cannot reach the hidden, reserved System Area on the platters (SA), so it reverts to reporting a bogus capacity stored in the "ROM" on the PCB.

If CrystalDiskInfo cannot read the SMART data (which are stored in the SA), then this would confirm an internal fault.

I am surprised to see that just pulling hdd while in use could cause this! hdd was working fine before.
on crystaldiskinfo its showing 8.4gb!
attaching the screenshot.
https://www.flickr.com/gp/21429760@N02/80Ff79

 

[fzabkar]

These bogus IDs also come from the "ROM" on the PCB:

Model number - ST_M13FQBL​

Serial number - QNR_BFW​

The drive probably had issues with bad sectors. The firmware had already been loaded into the drive's RAM, so you may not have noticed that anything was wrong. When you repowered the drive, it would have had to reload it's firmware from the SA, so the problem would then have manifested itself.

 

[Nvrmndryo]

These bogus IDs also come from the "ROM" on the PCB:

Model number - ST_M13FQBL​

Serial number - QNR_BFW​

The drive probably had issues with bad sectors. The firmware had already been loaded into the drive's RAM, so you may not have noticed that anything was wrong. When you repowered the drive, it would have had to reload it's firmware from the SA, so the problem would then have manifested itself.

So does that mean my hdd is will not work again?
I tried with new cable but its the same.

 

[Nvrmndryo]

I think It's time to say goodbye to the hdd as I don't think it will work again., I removed the external casing and connected internally to my desktop and its still showing the same.
So I think my hdd is damaged without any strong reason.
How hdd can be damaged if someone pulls the cable, what if there is a power cut or some other issue?
Data loss is one thing but permanent damage is not acceptable .
Thanks everyone for the replies.