December 8th, 2016, 15:09
December 8th, 2016, 22:50
December 9th, 2016, 2:54
jermy wrote:Most likely taking care on sysfile 93 + hardware imaging will do
December 9th, 2016, 3:02
December 9th, 2016, 8:43
fzabkar wrote:Type "F" at level T and post the output.
December 9th, 2016, 14:09
December 10th, 2016, 0:24
December 10th, 2016, 6:49
prasadsv wrote:Head 00 Resistance 00D7
Head 01 Resistance 0160
Head 02 Resistance 0119
December 10th, 2016, 11:27
Martin wrote:prasadsv wrote:Head 00 Resistance 00D7
Head 01 Resistance 0160
Head 02 Resistance 0119
Apparently, head 0 is not completely ok. I prefer to check it by testing sysfile 181 before any attempts to fix SA.
December 10th, 2016, 15:29
Martin wrote:prasadsv wrote:Head 00 Resistance 00D7
Head 01 Resistance 0160
Head 02 Resistance 0119
Apparently, head 0 is not completely ok. I prefer to check it by testing sysfile 181 before any attempts to fix SA.
December 11th, 2016, 2:07
prasadsv wrote:Martin wrote:prasadsv wrote:Head 00 Resistance 00D7
Head 01 Resistance 0160
Head 02 Resistance 0119
Apparently, head 0 is not completely ok. I prefer to check it by testing sysfile 181 before any attempts to fix SA.
with what command?
December 11th, 2016, 7:10
Martin wrote:prasadsv wrote:Martin wrote:prasadsv wrote:Head 00 Resistance 00D7
Head 01 Resistance 0160
Head 02 Resistance 0119
Apparently, head 0 is not completely ok. I prefer to check it by testing sysfile 181 before any attempts to fix SA.
with what command?
Just RW test. What kind of tool do you use?
December 11th, 2016, 7:30
Spildit wrote:fzabkar wrote:Sorry, I think that should have been ...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
+
F3 T>F"RWRecoveryFlags",00,22
F3 T>F"BGMSFlags",00,22
F3 T>F"PerformanceFlags",043C,22
F3 T>F"MediaCacheControl",00,22
December 11th, 2016, 17:41
Spildit wrote:Post terminal LOG.
Are you willing to pay something for the recovery ?
December 11th, 2016, 17:59
prasadsv wrote:Spildit wrote:Post terminal LOG.
Are you willing to pay something for the recovery ?
hdd SENT TO U?
December 13th, 2016, 18:21
Spildit wrote:And of course plug the drive to TTL on the computer that you will send Teamviewer ID.
December 13th, 2016, 18:27
Spildit wrote:prasadsv wrote:Spildit wrote:And of course plug the drive to TTL on the computer that you will send Teamviewer ID.
Today I open the drive I have seen heads bended up. It has only one head on each arm
Did you replace them ? Can you image the drive now ?
I told you .... if you were to continue you would mess up the drive for sure....
December 13th, 2016, 18:40
March 24th, 2017, 17:03
Spildit wrote:prasadsv wrote:Can I use heads from bad sector drives?
If you are sure that the "Bad sectors" are not caused the inability of the head to read .... And if you are sure that the heads were not damaged by the bad sectors .....
I would start by using a proper drive that you are sure to be working fine and not some junk drives to save costs ....
But at this point your client is already screwed i guess .... Starting to think that it was a BAD idea to advice you in the first place.
If you couldn't do the recovery you should have told your client to send the drive to another place or to outsource it yourself.
It's no longer safe to proceed any further.
Powered by phpBB © phpBB Group.