August 25th, 2018, 12:56
August 25th, 2018, 17:09
August 26th, 2018, 3:34
August 29th, 2018, 17:07
fzabkar wrote:Can you retrieve a terminal log? You will need a USB-TTL serial adapter.
August 29th, 2018, 17:20
August 30th, 2018, 21:15
mr_spokk wrote:Clone the drive with DD Rescue, after that don't use the Seagate anymore...
September 1st, 2018, 7:56
fzabkar wrote:Can you retrieve a terminal log? You will need a USB-TTL serial adapter.
September 1st, 2018, 10:04
Num Flgs normlzd worst raw
5 0033 3 3 00000000000F87
September 1st, 2018, 15:43
September 11th, 2018, 18:30
maximus wrote:First, since I have not seen any mention of how important the data is, if it is important enough to pay for recovery, then seek a data recovery professional.
The data isn't going to sink a business or anything, but it would be nice to retrieve pictures. I'm willing to try retrieve it knowing there's a risk.Num Flgs normlzd worst raw
5 0033 3 3 00000000000F87
Smart ID 5 is reallocated sectors, the value is 0xF87 which is 3975 sectors that have been reallocated, indicating a failing disk. There is no "fixing" this disk. There may be some terminal commands that could help get the drive more stable for recovery, but not fix it. But if you do the wrong commands you can kill it and loose your data forever.
I think I had this drive spinning in my system for the last two years every time I powered up. (I stupidly didn't remove the power cable, but did remove the SATA cable) I don't think I had a head crash. (no scraping or clicking) If I'm going to lose data, I may already have lost it.
The response from fzabkar lays out commands to turn off background stuff. Is that what you were recommending?
If you can still get it to be recognized, try HDDSuperClone instead of ddrescue. HDDSuperClone can detect when the drive goes offline (ddrescue cannot always detect this), which it sounds like yours is doing. It will stop when that happens, at which point you would power cycle the drive to (hopefully) get it to come back online, and then continue the recovery. If it is just a bad spot, you should be able to get through it with a few power cycles. If it is a bad head, you will not be so lucky.
September 11th, 2018, 18:38
fzabkar wrote:At level T, issue the following commands:F"READ_SPARING_ENABLED",0,22
F"WRITE_SPARING_ENABLED",0,22
F"OFFLINE_SPARING_ENABLED",0,22
F"DAR_ENABLED",0,22
F"DISABLE_IDLE_ACTIVITY",1,22
F"BGMS_DISABLE_DATA_REFRESH",1,22
F"ABORT_PREFETCH",1,22
F"READ_LOOKAHEAD_DISABLED_ON_POWER_UP",1,22
F"READ_CACHING_DISABLED_ON_POWER_UP",1,22
F"MediaCacheControl",00,22
These commands should disable certain features, thereby making your drive more stable for recovery purposes.
Please see this warning:
http://www.hddoracle.com/viewtopic.php? ... =80#p15109
September 12th, 2018, 0:40
fzabkar wrote:At level T, issue the following commands:F"READ_SPARING_ENABLED",0,22
F"WRITE_SPARING_ENABLED",0,22
F"OFFLINE_SPARING_ENABLED",0,22
F"DAR_ENABLED",0,22
F"DISABLE_IDLE_ACTIVITY",1,22
F"BGMS_DISABLE_DATA_REFRESH",1,22
F"ABORT_PREFETCH",1,22
F"READ_LOOKAHEAD_DISABLED_ON_POWER_UP",1,22
F"READ_CACHING_DISABLED_ON_POWER_UP",1,22
F"MediaCacheControl",00,22
These commands should disable certain features, thereby making your drive more stable for recovery purposes.
Please see this warning:
http://www.hddoracle.com/viewtopic.php? ... =80#p15109
September 12th, 2018, 17:25
The message, when I attempt to run HDDSuperClone on Ubuntu is: hddsuperclone: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
September 12th, 2018, 23:13
maximus wrote:The message, when I attempt to run HDDSuperClone on Ubuntu is: hddsuperclone: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
Well crap, I started working on some USB communications in the program, which I would say is causing that issue. What version of Ubuntu are you using? I will fix that in the next release.
For now you should be able to use HDDSuperClone version 1.99.3.beta, that was before I started the USB coding. On the site in the download page, expand the OLD VERSIONS to get it.
September 13th, 2018, 15:05
September 14th, 2018, 16:23
September 14th, 2018, 17:32
September 15th, 2018, 12:55
fzabkar wrote:ISTR one thread where a user reported that he couldn't get the settings to stick. Otherwise I haven't heard of any other problems.
AIUI, these settings are written to sys file 93h in the System Area (SA) on the platters. That's how the professional tools do it.
Some reading for you ...
Read and Write F3 Arch Sys files with HyperTerminal :
http://www.hddoracle.com/viewtopic.php?f=83&t=1455
Seagate F3 Arch - Patching the 093 sysfile :
http://www.hddoracle.com/viewtopic.php?f=59&t=1842
Bypass InitiateMarkPendingReallocateRequest on F3 Arch :
http://www.hddoracle.com/viewtopic.php?f=83&t=557
To see the default settings, just type F at level T.
As for the "dangers", once your data are recovered, your drive should be taken out of service. Therefore any dangers are moot.
Powered by phpBB © phpBB Group.