Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Damaged Logical Structure of Seagate 7200.11

- - - - - Seagate 7200.11 damaged logical structure ST31500341AS

  • Please log in to reply
20 replies to this topic

#1
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag

 

Hello everyone
 
using this cable:
Nokia CA-42 DKU-5 USB Cable 3100 5100 6100 6800 7200
http://www.ebay.co.u...984.m1497.l2649
this driver: http://www.citronid...._usb_driver.rar
Windows 7 32bit
 
loopback works, watched and followed the complete guide:
however, if i put the business card in, ctrl + z didnt respond, but it did say connected, so i completed the whole procedure without the business card, last lines were:
 
F3 T>m0,2,2,0,0,0,0,22 Enter
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewrite Retries = 0000
User Partition Format 3% complete, Zone 00, Pass 00, LBA 0002F79B, ErrCode 00000080, Elapsed Time 0 mins 30 secs
User Partition Format Successful - Elapsed Time 0 mins 30 secs Zone re-format was skipped.
F3 T>/2
F3 2>Z
Spin Down Complete
Elapsed Time 3.038 msecs
Turn off power from HDD, shutdown your comp.
 
so i connected the hdd back, but everything was the same for some reason, as i went into my computer, the hdd didnt appear, and in disk management it appeared like this:
20140119_042102aasdas_zps7f23a164.jpg
 
so i try right clicking on the hdd in disk management > assing letter, say g for example, enter, and it halts disk management, left it for hours and it wouldnt resume, sometimes it comes up in my computer as "Local Disk", 
 
i reboot pc, try running "mini tool power data recovery" the real hdd name comes up "3 documents" but when i click on browse, halts again
 
hope someone can help me out

 
 

 

so i connected the hdd back, but everything was the same for some reason, as i went into my computer, the hdd didnt appear, and in disk management it appeared like this:

If it was actually "the same as before" it was NOT either BSY or LBA0.
Check in the BIOS ( NOT in the booted Windows).
Is it seen as having zero capacity? If no see below, if yes it means that the de-bricking was not successful and you shoudl try again.
Is it detected? If yes then your procedure worked and the disk is not anymore belongng to this thread, if it is not detected it means that the de-bricking was not successful and you shoudl try again.
If the disk is NOT LBA0 and NOT BSY, then:
 

hope someone can help me out

Read (attentively) the post just before yours.
Start a NEW thread, you need to recover the partitoning/volume(s).
 
jaclaz

 

 
ok i checked the bios, heres what it looks like: 
ASASFSDGF_zps4e689b96.jpg
 
so from what you say this must be a different issue, i also tried this hdd on ubuntu to see if the drive comes up, but it didnt, and on another windows 7 system, the same as others, just hangs there when you try to enter disk management, if you know about this issue please respond, or if you think i should create a new thread, do you know the name of the problem? any guidance please?

 

 
 

@TomasMascinskas
You have to understand that there are three "levels" when it comes to a disk drive:


  • Real physical level (this is what the BIOS can see and that in your case is OK)
  • Physical level (or RAW device) which is what Disk Management uses to access the device
  • Logical level (what Explorer or other file manager will use ONCE the Disk Manager above will have created a valid logical structure, i.e. partitions/volumes and filesystems on them)
A bricked disk will not be accessed correctly at level #1 above and consequently it won't be available at the other two ones.
An unbricked disk will be accessible at level #1 and at level #2 above but not necessarily at level #3 as, for a number of reasons its logical structure may have been corrupted.
 
Your disk is detected correctly in the BIOS :yes:, and as such your disk is NOT "bricked" (anymore) :), BUT evidently the logical structure on it has been damaged :(.
 
Start a NEW thread and we will see if it  is possible to repair/recover the logical structure of the disk or if at least file-based recovery is possible.
 
In more detail, the partitioning of the disk is still OK (your disk management does see a single partition on it) BUT NO valid filesystem is recognised by the Windows and as such a drive letter CANNOT be assigned to it.
 
jaclaz

 




How to remove advertisement from MSFN

#2
jaclaz

jaclaz

    The Finder

  • Developer
  • 15,785 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Good, start by providing a copy of the MBR (first absolute sector of the disk).

A suitable tool (for the not-so-avanced user) is HdHacker:

http://dimio.altervista.org/eng/

under Windows 7 you will probably need to run it as Administrator.

Check which disk number the affected disk has in Disk Management (like Disk 0, Disk 1, etc. Disk n)

In Hdhacker you want to select "Physical Drive (MBR)", n, then "First Sector (MBR)", "Number of continuous sectors to read" = 1

Then press button "Read sector from disk"

Then press button "Save sector to file"

Choose a location and filename and save the file.

Then compress it to a zip archive and either attach the .zip to your next post or upload it *somewhere* and provide a link to it.

 

jaclaz



#3
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag

Good, start by providing a copy of the MBR (first absolute sector of the disk).

A suitable tool (for the not-so-avanced user) is HdHacker:

http://dimio.altervista.org/eng/

under Windows 7 you will probably need to run it as Administrator.

Check which disk number the affected disk has in Disk Management (like Disk 0, Disk 1, etc. Disk n)

In Hdhacker you want to select "Physical Drive (MBR)", n, then "First Sector (MBR)", "Number of continuous sectors to read" = 1

Then press button "Read sector from disk"

Then press button "Save sector to file"

Choose a location and filename and save the file.

Then compress it to a zip archive and either attach the .zip to your next post or upload it *somewhere* and provide a link to it.

 

jaclaz

done:

https://www.dropbox....R_HardDisk0.rar



#4
jaclaz

jaclaz

    The Finder

  • Developer
  • 15,785 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Good, the MBR, as expected, is fine (but is important to check it anyway).There is a single entry in it:

 

Entry Type Boot bCyl bHead bSect eCyl eHead eSec StartSector NumSectors
#0 07 80 0 32 33 1023 254 63 2048 2930272256

which is about a NTFS (or exFAT :unsure:) volume created under Vista :ph34r: or later (beginning on LBA 2048) sized 2,930,272,256 sectors, i.e. 1,500,299,395,072 bytes in size.

Since you cannot access the logicaldrive through an assigned drive letter, you will need to use another approach to get the VBR.

 

Now it would be about the right time to make either a dd-like image of the disk or to make a clone of it.

You will need a 2 Tb disk to make an image or a 1.5 Tb disk to make a clone.

 

Get the free version of DMDE:

http://dmde.com/

and follow the instructions here:

http://www.msfn.org/...-2#entry1061689

 

If you decide to not make the image (either because you feel adventurous or because you don't have the money to procure a new disk), you can skip (at your own risk) to the next step, which is, still using the DMDE and the linked above instructions, to save a copy of first (say) 2100 sectors.

I.e. you need to set the Start sector to 0 and the Number of sector to 2100.

What is actually relevant is just the sector LBA 2048 (which is the PBR or VBR, Partition or Volume Boot Record) but having a bunch more sectors may be useful to see if strange forms of corruption happened.

You also want to make a copy of the very last sector of the partition, i.e. sector 2048+2,930,272,256=2,930,274,304 which is the PBR Mirrror, i.e. it should be an exact copy of sector 2048.

Compress the two resulting files into a zip archive and upload them like you did for the MBR.

 

jaclaz



#5
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag

Good, the MBR, as expected, is fine (but is important to check it anyway).There is a single entry in it:

 

Entry Type Boot bCyl bHead bSect eCyl eHead eSec StartSector NumSectors
#0 07 80 0 32 33 1023 254 63 2048 2930272256

which is about a NTFS (or exFAT :unsure:) volume created under Vista :ph34r: or later (beginning on LBA 2048) sized 2,930,272,256 sectors, i.e. 1,500,299,395,072 bytes in size.

Since you cannot access the logicaldrive through an assigned drive letter, you will need to use another approach to get the VBR.

 

Now it would be about the right time to make either a dd-like image of the disk or to make a clone of it.

You will need a 2 Tb disk to make an image or a 1.5 Tb disk to make a clone.

 

Get the free version of DMDE:

http://dmde.com/

and follow the instructions here:

http://www.msfn.org/...-2#entry1061689

 

If you decide to not make the image (either because you feel adventurous or because you don't have the money to procure a new disk), you can skip (at your own risk) to the next step, which is, still using the DMDE and the linked above instructions, to save a copy of first (say) 2100 sectors.

I.e. you need to set the Start sector to 0 and the Number of sector to 2100.

What is actually relevant is just the sector LBA 2048 (which is the PBR or VBR, Partition or Volume Boot Record) but having a bunch more sectors may be useful to see if strange forms of corruption happened.

You also want to make a copy of the very last sector of the partition, i.e. sector 2048+2,930,272,256=2,930,274,304 which is the PBR Mirrror, i.e. it should be an exact copy of sector 2048.

Compress the two resulting files into a zip archive and upload them like you did for the MBR.

 

jaclaz

 

thank you for being so helpful, but i got an error: 

 

asdasdf_zps0d812525.jpg



#6
jaclaz

jaclaz

    The Finder

  • Developer
  • 15,785 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

 

thank you for being so helpful, but i got an error: 

 

Yep. :(

And that error would explain nicely why the filesystem is not recognized.

A "normal" NTFS volume has it's $MFT starting on LCN 786432 with an 8 sectors/cluster that would make 786432*8+2048=6,293,504, the $MFT plays a vital part in filesystem recognizing and access and for the error you got it seems like that sector is in a damaged/bad area.

 

You can try to see what happens with "ignore all", or decide to "abort".

 

The next attempt is to try making an image of the disk using a more suitable tool for damaged disks, there is a very good one for Linux (that would make the imaging procedure automatic) and also a more manual Windows one:

http://www.datarescu...cue/v3/drdd.htm

 

but then you can try imaging the disk in chunks manually with DMDE, (to get the "advanced" LOG feature in it you need the Professional edition)

 

If you are familiar enough with Linux (and command line) you can use ddrescue using a log.

 

A succinct "theory of operation" when imaging manually in "chunks" is provided here:

http://www.msfn.org/...disk/?p=1059909

 

jaclaz



#7
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag

 

 

thank you for being so helpful, but i got an error: 

 

Yep. :(

And that error would explain nicely why the filesystem is not recognized.

A "normal" NTFS volume has it's $MFT starting on LCN 786432 with an 8 sectors/cluster that would make 786432*8+2048=6,293,504, the $MFT plays a vital part in filesystem recognizing and access and for the error you got it seems like that sector is in a damaged/bad area.

 

You can try to see what happens with "ignore all", or decide to "abort".

 

The next attempt is to try making an image of the disk using a more suitable tool for damaged disks, there is a very good one for Linux (that would make the imaging procedure automatic) and also a more manual Windows one:

http://www.datarescu...cue/v3/drdd.htm

 

but then you can try imaging the disk in chunks manually with DMDE, (to get the "advanced" LOG feature in it you need the Professional edition)

 

If you are familiar enough with Linux (and command line) you can use ddrescue using a log.

 

A succinct "theory of operation" when imaging manually in "chunks" is provided here:

http://www.msfn.org/...disk/?p=1059909

 

jaclaz

 

 

 

i used abort all, after a good while it finished, then i done as instructed and went to back up to a file, but its been on 0% for like 4 hours:

 

asfsdrfhsdtjh_zps3cb2e1ce.jpg



#8
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag

16 hours later, still same



#9
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag

tried drdd, got errors:

sdfhfdgndfgn_zps1ab31f06.jpg



#10
jaclaz

jaclaz

    The Finder

  • Developer
  • 15,785 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

It seems like you are having several "bad areas".

As said your best option next is ddrescue under Linux, using a Log:

http://www.gnu.org/s...cue_manual.html

Usually it can recover as much as it is possible.

What are the temperatures of that disk drive?

It is a good idea to "keep it cool" (like by putting it under the airflow of a fan) when doing intentsive i/o (like imaging/cloning).

 

jaclaz



#11
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag

im not sure what the temperature is im afraid

also, i never used linux before, which version do i need please?

will this be fine?

http://www.pendrivel...ator/#more-3034

sorry i just know nothing about linux, once again, thank you so much

and also, in this process, are we backing up the image of the harddrive which is the recovery itself, or is this a precaution for the next step in getting the HDD to actually be assingable?



#12
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag

ok im confused, apparently ubuntu is linux itself? can i use ubuntu to use ddrescue



#13
jaclaz

jaclaz

    The Finder

  • Developer
  • 15,785 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Ubuntu is one (among many) available Linux distributions.

Unlike what happens in the MS world, Linux is Open Source and (largely free as in free beer, besides being free as in freedom).

Basically everyone can "assemble" a Linux distribution (or "distro") which may be "universal" or "very specific" (either in the sense of running only on a given hardware or of being "focused" on a specific subset of computing tasks).

In practice there are only a couple handfuls of "main" distro's, and Ubuntu is one of them.

There are more "flavours" or "spin-offs" or "remixes" of Ubuntu as stars in the sky (plus the infinite number of other distro's), it is very confusing for a new user.

Ubuntu is a "fully featured distro" (please read, though I will be soon flamed for this :ph34r:, as "a nice but senselessly huge amount of of bloatware, a large part of which being bells and whistle")  for your uses smaller/simpler distro's will probably be more suited.

You want a "Live CD" distro, i.e. something that is not installed anywhere but that runs directly from a CD or USB stick.

Possible candidates:

http://www.sysresccd...scueCd_Homepage (still largish)

http://puppylinux.org/ (as small as it can be)

http://trinityhome.org/ (what I would probably use if I were you)

 

 

This article should be of use:

http://techmuck.blog...u-ddrescue.html

as well as this thread:

http://www.murga-lin...pic.php?t=71026

 

 

I think you will need anyway some assistance from a friend a bit more familiar than you with the Linux environment, as a few "naming" conventions" and commands are different from DOS or more generally Windows command prompt.

 

There is nothing overly complex in the use of such tools, but there is a concrete risks for the newbie (no offence whatever intended :)) to "confuse" disks/drives/devices, with consequent potentially catastrophic resuts.

 

In any case ideally you should first try the procedure with another (working) possibly smallish hard disk (or a USB stick), just to get the hang of it.

The mentioned:

http://www.pendrivel...ator/#more-3034

should do if you wish to use a USB stick (instead of "burned" CD), check if the distro you choose is supported by the tool, most are.

 

About temperatures, the rule of the thumb is that if it's "warm" i.e. you can hold your hand touching it's cover more than a few seconds and feel it "warm" (i.e. it is around 40° Celsius or less) it is fine, if you feel it "like hot" (i.e. it is around 50° Celsius) is still within the norm, if it feels "very hot", it is "very hot" ;) and probably needs some added ventilation/cooling.

 

The general idea is to copy as much data as possible to a new disk (or disk image).

If you make an image of a perfectly working disk (or a "clone" of the disk on another one) the result will be identical to the source.

When a "failing" or "partially failed" disk is the source the result will be "similar", i.e. it will be identical for corresponding "good sectors" and will have "holes" for the bad ones (actually sectors containing 00's).

The image (or clone) being on a fully working hard disk allows to performa actions that would be impossible to do on the failing/partially failed disk, such as filesystem reconstruction and/or file recovery.

 

In theory, one should make a second image (from the first one) and attempt recovery on this last one, as this allows to attempt different techniques (including some that while recovering something make something else unrecoverable) as a "way back" is available any time.

But it depends on the amount of data that the ddrescue actually manages to copy and from a number of other factors (if only a small part of the disk is imaged without errors or if anyway "key parts" of the filesystem are still missing there is no sense in attempting filesystem recovery and all you can do is attempt file based recovery which is read only, so this second image is not needed).

 

jaclaz



#14
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag

once again thank you, the ubuntu i have, is installed via dual boot running along side windows 7 ultimate 32 bit

ubuntu is:

Ubuntu 13.10
32 bit
 
can you tell me how to install/download on ubuntu, extremely noob with it, thank you
 
and i understand now what you mean by imaging the drive now


#15
jaclaz

jaclaz

    The Finder

  • Developer
  • 15,785 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

 

once again thank you, the ubuntu i have, is installed via dual boot running along side windows 7 ultimate 32 bit

ubuntu is:

Ubuntu 13.10
32 bit
 
can you tell me how to install/download on ubuntu, extremely noob with it, thank you
 
and i understand now what you mean by imaging the drive now

 

ddrescue is likely already there, or if not, read here:

https://help.ubuntu....ty/DataRecovery

Sometimes the good :) Linux guys have a peculiar way to make things more complex by misnaning or confusing things by giving to different things the same name, etc. :w00t: or - some other times - by giving so many options to do something that it makes reaching the goal more difficult.

The above page has a link to another page where 5 or 6 different methods to install ddrescue (which is astutely called gddrescue as package, whilst the ddrescue package actually delivers dd_rescue :ph34r:) but the easiest would be to use apt-get as in:

http://www.forensics...g/wiki/Ddrescue

http://www.forensics...bian_and_Ubuntu



sudo apt-get install gddrescue

jaclaz


Edited by jaclaz, 07 February 2014 - 07:09 AM.


#16
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag

ok i been going crazy here, looked up lots of youtube videos, read up about the linux, ubuntu, gddrescue, i found my hdd in "applications" "disks", found out terminal, some coding there, i foudn the correct commands needed, and eventually i found that i dont have gddrescue, or ddrescue, and that i cannot install them, i tried various ways, running firefox and clicking on the links in https://help.ubuntu....ty/DataRecovery, using the code: sudo apt-get install gddrescue, which didnt work, neither did ddrescue, however its not an internet connectivity as the update code worked in the terminal and so it did with install another app too, so i will try to find a usb bootable download with the gddrescue already installed, so far im hopeful, and once again thank you so much for everything

 

i found this: http://ubuntu-rescue...ix.org/node/119  but when i double click on it in ubuntu it says "the package is of bad quality", should i "ignore and install"?

 

ok now im getting somewhere, installed it, running the ddrescue command, it gets to 1179mb rescued, then 1 error, and after around 5 minutes, it says errsize 1499GB, which is very worrying, now its in the:

"Splitting error areas..." state, ill leave that overnight

 

FYI, the code im running is:

sudo ddrescue -r 3 /dev/sde /media/ubuntu/EMPTY /media/ubuntu/1C41-D695/log.txt

 

update, its been around 8 hours, and it seems the ipos: and opos:, went from position 0, all the way to the end 1500gb, and circulated many times now, and the rescued it still 1179,b, and errsize 1499gb, total errors is 1

 

also when i was in disks app in ubuntu the broken hdd came up with 669 bad sectors if that helps

 

but i find it hard to believe 1499GB is the error rate, since there are so many more sectors than 669, thats no where near 99% of the sectors, i didnt do nothing damaging to the hdd, it just randomly stopped working one day, i was trying to cut and paste files from the hdd but it just halted that one day, no physical damage, logical thats my fault, no viruses, so weird

 

 

update:

i interupted the process since there were was no progress for 8 hours with ctrl + c, back at the prompt, i attempted:

 
sudo ddrescue -n /dev/sde /media/ubuntu/EMPTY /media/ubuntu/1C41-D695/log.txt
sudo ddrescue -r 3 /dev/sde /media/ubuntu/EMPTY /media/ubuntu/1C41-D695/log.txt  OLD COMMAND
 
so that the splitting is skipped (as that was the code given throughout the 8 hours
 
it finished already with the new code, being the rescued state at 1179mb and errsize at 1499gb
 
 
 
now im lost, i dont know what to do, so i will wait for your input

Edited by TomasMascinskas, 13 February 2014 - 09:39 AM.


#17
jaclaz

jaclaz

    The Finder

  • Developer
  • 15,785 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

now im lost, i dont know what to do, so i will wait for your input

Unfortunately I have none :(.
We have seemingly exhusted the things that can be done DIY.
Now there are three possibilities:

  1. the hard disk is botched beyond any possible repair/recovery.
  2. the hard disk may be repaired by professionals with hardware/software tools (like replacing SA's - whatever they are - fixing translation tables and what not)
  3. the hard disk may be repaired by professionals with hardware intervention (like replacing heads, swapping platters, etc.

#1 above means end of game, #2 means probably US $ 300 to 500, #2 likely means US $800 to 1200.

 

jaclaz



#18
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag
could you please explain to me why it would say 99% error, what are your guesses that it could be, im assuming maybe it just comes across a bad sector that it cant read and gets stuck on it rather than labelling it as bad and moving onto the next
 
also i think i thought of a few faults that couldve been mine, the hdd i was recovering to name had a space in it, and the log file was being written to a 100mb usb stick that filled up and ran out of space, so i renamed the spare functional hdd to simply "backup", which is 2tb, and i will write the log file to the backup hdd this time too (couldnt before due to that hdd having a space in the file name
 
but theres a problem now, for some reason the broken hdd wont appear using ubuntu terminal with sudo fdisk -l, and it wont appear in ubuntu, disks, app, but the hdd still is functioning correctly physically, initializes, spins, headers move, etc, and in windows, the usual, freezes in disk management
 
ok odd, tried a different port, now its recognised, even though i tried that sata port just a while ago
 
so im back in the terminal and gddrescue, trying the command again, but now its just 1 error, with the errsize being 1500GB, how on earth is that all an error, its definately not all bad no way, could you please explain to me what i need to do about this, i cannot find anything about this wherever im searching, i found, try reversing, try "--try-again", --no-split, its all 1500gb error size still
 
 
 
i would much rather learn how to fix hdd's myself, even if it means learning to rewrite table, i could even pay you to teach me if you are willing to
 
if not, could you answer the above question, and if all doesnt work out
 
could you recommend me a data recovery company in UNITED KINGDOM, LONDON, that is very professional, know what they are doing, i would know the location where my hdd is being kept at, and what is being done to it, because ive read up so many bad things about data recovery services, some just receive the drive, and bin it, and say that the drive is dead, some companies dont even exist, there PCWORLD and they have apparently "data recovery labs" but even they have terrible reviews, i am so lost, if i knew a professional and reliable company with real reviews, and legitamate professionals that actually do their job, a physical store which you can deliver your drive to, i would pay for the recovery

Edited by TomasMascinskas, 24 February 2014 - 08:55 PM.


#19
jaclaz

jaclaz

    The Finder

  • Developer
  • 15,785 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

i would much rather learn how to fix hdd's myself, even if it means learning to rewrite table, i could even pay you to teach me if you are willing to

Uh-oh, logical flaw detected :w00t:.
You are assuming that I actually know how to fix a hdd in a situation like yours, which may or may not (it is not :() accurate.
Point is that to get to the "next" step one needs a little tool that sells for several thousands bucks (and that needs proper training), and to go to the "further" step one needs, beside the above some even more specific tools and quite a bit of experience.
And of course there are no guarantees of any kind that a recovery is possible at all, not even with these tools (and knowledge).
 

if not, could you answer the above question, and if all doesnt work out
 
could you recommend me a data recovery company in UNITED KINGDOM, LONDON, that is very professional, know what they are doing, i would know the location where my hdd is being kept at, and what is being done to it, because ive read up so many bad things about data recovery services, some just receive the drive, and bin it, and say that the drive is dead, some companies dont even exist, there PCWORLD and they have apparently "data recovery labs" but even they have terrible reviews, i am so lost, if i knew a professional and reliable company with real reviews, and legitamate professionals that actually do their job, a physical store which you can deliver your drive to, i would pay for the recovery

I cannot help you on this, you can try asking over at hddguru, that forum's members (besides a few casual passers by) are mainly professionals (usually with a very bad character, extremely unwilling to help and often disturbed by the questions of newbies, but that obviously know where their towel is) and you may make contact with one of them working in London. (and yes you are IMHO correct about the fact that there are seemingly a large number of buffoons that advertise on the internet for services they cannot provide reliably).

jaclaz

#20
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag

 

i would much rather learn how to fix hdd's myself, even if it means learning to rewrite table, i could even pay you to teach me if you are willing to

Uh-oh, logical flaw detected :w00t:.
You are assuming that I actually know how to fix a hdd in a situation like yours, which may or may not (it is not :() accurate.
Point is that to get to the "next" step one needs a little tool that sells for several thousands bucks (and that needs proper training), and to go to the "further" step one needs, beside the above some even more specific tools and quite a bit of experience.
And of course there are no guarantees of any kind that a recovery is possible at all, not even with these tools (and knowledge).
 

if not, could you answer the above question, and if all doesnt work out
 
could you recommend me a data recovery company in UNITED KINGDOM, LONDON, that is very professional, know what they are doing, i would know the location where my hdd is being kept at, and what is being done to it, because ive read up so many bad things about data recovery services, some just receive the drive, and bin it, and say that the drive is dead, some companies dont even exist, there PCWORLD and they have apparently "data recovery labs" but even they have terrible reviews, i am so lost, if i knew a professional and reliable company with real reviews, and legitamate professionals that actually do their job, a physical store which you can deliver your drive to, i would pay for the recovery

I cannot help you on this, you can try asking over at hddguru, that forum's members (besides a few casual passers by) are mainly professionals (usually with a very bad character, extremely unwilling to help and often disturbed by the questions of newbies, but that obviously know where their towel is) and you may make contact with one of them working in London. (and yes you are IMHO correct about the fact that there are seemingly a large number of buffoons that advertise on the internet for services they cannot provide reliably).

jaclaz

 

awright thanks again, so back to gddrescue, do you have any idea why its stating that there is only 1 error and that error is 1500gb large?



#21
TomasMascinskas

TomasMascinskas

    Newbie

  • Member
  • 18 posts
  • Joined 07-April 13
  • OS:none specified
  • Country: Country Flag
Hey everyone, thought id mention that i finally went through with the data recovery with PCImage, i actually went in person from london to peterborough to physically hand delivery the dead hdd and a fresh new hdd to the shop, took ages to get there but when i did everything was simple and easy, simply handed in the drive, they already knew of me coz of the email communications, had an overall summary of the problems of the hdd and the process of the recovery.
 
the turn around recovery was incredible...next day they identified the problem, i confirmed with the fix, and day after it was all recovered on my spare hdd, instead of picking it up in person they first cloned the hdd to a backup, and put another clone on my new fresh hdd and sent it back to me (this way if the package was lost they still had a clone, which i couldnt do as i didnt know how to fix the problem myself)
 
Here were the problems found:
 
1.       Media degradation (bad sectors), possibly caused by the contamination, but also possibly the initial underlying issue in the first place.
 
2.       Firmware module corruption, in particular the translator. Almost certainly caused by improper use of an “internet fix” which does not take into account entries in the NRG
 
3.       Quite possibly some file system damage, the extent of which is unknown as of yet.
 
 
 
 
So for anyone on this forum wondering...go ahead with PCImage, thumbs up from me






Also tagged with one or more of these keywords: Seagate 7200.11, damaged logical structure, ST31500341AS

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users