October 6th, 2017, 10:36
October 6th, 2017, 10:50
October 6th, 2017, 11:22
data-medics wrote:It is likely a firmware malfunction, possibly related to the media cache or sector re-allocation functions of the drive.
If the data is as important as you say, you should really get it to someone with professional tools like PC-3000 to properly diagnose it.
October 6th, 2017, 11:33
titokhonan wrote:it´s too expecive for me to travel to another country, and here in Cuba there is no profeccional company to recover the data.[/b]
October 6th, 2017, 11:36
October 6th, 2017, 14:42
October 6th, 2017, 17:56
October 6th, 2017, 17:59
Spildit wrote:Goes without saying ....
DO NOT REGEN TRANSLATOR ON THIS DRIVE WITH 2700.11 COMMANDS POSTED ON THE NET .....
October 6th, 2017, 18:02
mmzhr wrote:Spildit wrote:Goes without saying ....
DO NOT REGEN TRANSLATOR ON THIS DRIVE WITH 2700.11 COMMANDS POSTED ON THE NET .....
yes like as spildit say do not regenrate translator on 720012 series or you end up with partial access problem
say goodby to your data
October 7th, 2017, 10:41
mmzhr wrote:
for fixing this series
just clear smart with
/1N1,,22
and disable background scan with
/TF"BGMS_ENABLE",0,22
October 7th, 2017, 11:10
Masterclass wrote:mmzhr wrote:
for fixing this series
just clear smart with
/1N1,,22
and disable background scan with
/TF"BGMS_ENABLE",0,22
Can someone ban this guy? Such bullshit is no longer funny...
October 8th, 2017, 0:20
mmzhr wrote:
i posting learning topics and want to help others
October 8th, 2017, 7:42
Masterclass wrote:mmzhr wrote:
i posting learning topics and want to help others
Nobody needs your "help" since you cant understand what the problem is.How can you advice something when you know really nothing about HDDs? Your brain still cant understand that when a person needs data - just typing silly commands without its understanding can spoil data.
October 8th, 2017, 8:17
mmzhr wrote:Masterclass wrote:mmzhr wrote:
i posting learning topics and want to help others
Nobody needs your "help" since you cant understand what the problem is.How can you advice something when you know really nothing about HDDs? Your brain still cant understand that when a person needs data - just typing silly commands without its understanding can spoil data.
October 8th, 2017, 14:09
Spildit wrote:OP didn't post any log yet so "understanding" the problem at this stage is impossible. Only "possible" thing to do is "guessing" and that will not help the OP as one needs to know exactly what is wrong in order to "bypass" the problem temporarly to gain access to the data and then when the data is extracted to a safe place and confirmed to be valid and intact the drive should never be used again.
October 8th, 2017, 16:53
Spildit wrote:mmzhr wrote:Spildit wrote:OP didn't post any log yet so "understanding" the problem at this stage is impossible. Only "possible" thing to do is "guessing" and that will not help the OP as one needs to know exactly what is wrong in order to "bypass" the problem temporarly to gain access to the data and then when the data is extracted to a safe place and confirmed to be valid and intact the drive should never be used again.
he dosent log yet but i has before many 31000524as drives that fixed easy
Including the ones with bad heads ? And with bad surface ? Fixed easy with terminal only ?
October 8th, 2017, 18:18
Spildit wrote:How did you fix those drives ? Clearing S.M.A.R.T. ?
October 8th, 2017, 18:57
Spildit wrote:mmzhr wrote:Spildit wrote:How did you fix those drives ? Clearing S.M.A.R.T. ?
no i fixed those drive with commands that send it to you in pm
Commands that you did send to me in PM will only disable background media scan, etc .... I posted those on my forum several YEARS ago ... It will NOT fix drive (like fix bad sectors) it will just facilitate or allow for data to be copied bypassing "pending bug", etc .... Nothing special about those commands and nothing "secret" as they were posted several years ago ...
October 8th, 2017, 19:10
Spildit wrote:mmzhr wrote:Spildit wrote:OP didn't post any log yet so "understanding" the problem at this stage is impossible. Only "possible" thing to do is "guessing" and that will not help the OP as one needs to know exactly what is wrong in order to "bypass" the problem temporarly to gain access to the data and then when the data is extracted to a safe place and confirmed to be valid and intact the drive should never be used again.
he dosent log yet but i has before many 31000524as drives that fixed easy
Including the ones with bad heads ? And with bad surface ? Fixed easy with terminal only ?
October 8th, 2017, 19:20
Spildit wrote:Even if you could cut head on that drive dust inside the drive already damaged all heads and platters.
You can't fix modern seagate because they are junk. Just buy Hitachi.
Powered by phpBB © phpBB Group.