Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
September 25th, 2014, 8:22
Hello everyone,
I have WD 3.5" internal HDD for one of the customers,
when I try to make raw recovery, quick disk analyse, or anything else, the PC3000 just keep Software reset over and over
I checked all 4 heads, Models, FW, all seems to be good.
I talked to Acelab TS and he stayed 3h working on it over TeamViewer but no luck.
If anyone interested of taking a look over TeamViewer, Please PM
September 25th, 2014, 8:27
What did the customer say happen?
What is the file system on the drive?
What is the customer expecting to recover from the drive?
Any encryption scheme used?
September 25th, 2014, 8:34
labtech wrote:What did the customer say happen?
What is the file system on the drive?
What is the customer expecting to recover from the drive?
Any encryption scheme used?
the customer told me his PC stopped working suddenly, and the and show that HDD not detected,
it have 1 partition NTFS and have windows 7 on it, and the customers wants the desktop files and folders
there is no encryption
September 25th, 2014, 8:42
Were you able to confirm the same results with any other tool?
September 25th, 2014, 8:47
labtech wrote:Were you able to confirm the same results with any other tool?
I only have PC3000
September 25th, 2014, 8:49
Hello,
is it new case or old?or still you want get support for same?
September 25th, 2014, 8:53
safwan1967 wrote:Hello,
is it new case or old?or still you want get support for same?
it is the same
and i have teamviwer ready, just PM me
September 25th, 2014, 9:07
I am assuming a clone has been created and the logical work is done on the clone and not the "failed" drive correct?
I meant other software tools/logical file extraction tools.
If all check out, my best educated guess is that there may be a translation shift in the data causing software to be confused.
September 25th, 2014, 10:37
H3 has some reading problems, maybe is related to head itself or otherwise could just be 'coincidence' bad sectors only on H3, but it does intermittently read. Also, FS is ExFAT so if client says natively should be NTFS then there are additional problems. Heads 0,1,2 need to be read then adjust reading parameters to read all 'easily read' sectors from H3 then possibly this image will be enough to reach user data inside.
September 25th, 2014, 10:52
hddguy wrote:H3 has some reading problems, maybe is related to head itself or otherwise could just be 'coincidence' bad sectors only on H3, but it does intermittently read. Also, FS is ExFAT so if client says natively should be NTFS then there are additional problems. Heads 0,1,2 need to be read then adjust reading parameters to read all 'easily read' sectors from H3 then possibly this image will be enough to reach user data inside.
I really thank you for your time and help.
how about if I replace all heads (I have new donor drive), or I just start imaging as you instruct ?
September 25th, 2014, 10:54
LostDataSa wrote:hddguy wrote:H3 has some reading problems, maybe is related to head itself or otherwise could just be 'coincidence' bad sectors only on H3, but it does intermittently read. Also, FS is ExFAT so if client says natively should be NTFS then there are additional problems. Heads 0,1,2 need to be read then adjust reading parameters to read all 'easily read' sectors from H3 then possibly this image will be enough to reach user data inside.
I really thank you for your time and help.
how about if I replace all heads (I have new donor drive), or I just start imaging as you instruct ?
while at least 75% of sectors are readable you should image first. In case head change fails or makes no change to condition, you would still have image and can (probably) extract data from it
September 27th, 2014, 3:04
Hello
you got already support from genius.then it is ok..i hope it will work..best of luck
Powered by phpBB © phpBB Group.