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

How to recover accidentaly deleted partition/files?

- - - - -

  • Please log in to reply
56 replies to this topic

#1
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

Hello!

This is my problem and I hope somebody here can help me. HDD is WD20EARS - for data only - not system.OS is XP 32 bit. When I first installed this HDD, I reserved some 8 GB partition(not formatted) and the rest 1.8 TB was used for the files. Today I decided to delete this not formatted partition because I didn't want to see it between the other drive's letters. Obviously this was a big mistake because the second partition also disappeared with all of the files there. At first I tried PartedMagic with TestDisk and it showed start of the main partition at sector 16370235 and end at 3907024064 sector and total 3890653830 sectors. I am not so familiar with partition management so I tried to recover the partition in XP with PartitionWizard. This program showed slightly different sectors for the beginning ant the end of the partition. I think this was my second mistake because after PW finished, it showed ntfs-partition but there was nothing. XP still wasn't able to see the partition so I rebooted the system. Then appeared those blue screen with check disk tool and after the check the partition appeared in XP, but it is empty. Can I really recover the partition or at least most of the files? I now run deep analysis with TestDisk and afther several hours(the next morning here :)) I wil have some results. This is powerful tool and I don't know exactly what to do so I will need help.




How to remove advertisement from MSFN

#2
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

The analisys says - "The harddisk seems too small" - 4497 GB. There are two FAT16 partitions and I don't know where they came from.

Attached Files



#3
Kelsenellenelvian

Kelsenellenelvian

    WPI Guru

  • Developer
  • 8,873 posts
  • Joined 18-September 03
  • OS:Windows 7 x64
  • Country: Country Flag

Wait a 5 terabyte hardrive seems to small?



#4
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

It is actually 2 TB - WD20EARS. Something got wrong with the partitions and maybe also with the XP check disk tool that ran afther one reboot ater I(was thinking) recovered the main partition with PartitionWizard.



#5
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,841 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

The screenshot shows very little.

You should run TESTDISK again with a LOG (and post/attach the LOG, not a screenshot.

Also, you did not provide an EXACT (enough) report of the actions you took.

How EXACTLY (on which OS; with which tool giving which EXACT commands) did you try to delete the first partition?

The issue (more or less) is the following (now).

IF you recreated a NTFS partition starting on the SAME address (or a "near enough" one) you have effectively overwritten the $MFT of the original NTFS partition and you won't be able to recover the "previous" partition contents (but you might be able to recover most of the files in it, with file-oriented recovery software, very likely losing the filenames). :(

IF on the other hand you recreated the new NTFS partition on a DIFFERENT address (or "far enough" one) like it would be if you created just a single partition starting from the beginning of the disk, there is a chance that the new $MFT did not overwrite the previous one and thus it is possible to recover a large part of the filesystem. :)

 

The data "sector 16370235 and end at 3907024064 sector and total 3890653830 sectors" represent a "valid" partition created with the "old" Cylinder boundary standard (possibly through XP or a third party tool, not with Vista :ph34r: or later)

On such a partition the $MFT should start at 786432*8+16370235=22661691

 

First check you should make would be to use a disk viewer/editor and verify that absolute sector 22661691 is the actual start of $MFT .

 

jaclaz



#6
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

I have some LOG, but I don't know if this is enough or I should go further with TestDisk actions. OS is XP 32 bit and I used the standard tool - Disk Management. According to TestDisk the main partition should start at sector 16370235 and end at sector 3907024064. I tried to recover the main partition with PartitionWizard - Partition Recovery Wizard. It showed start at sector 16370298 and end at 3907020601. Does this mean that I should go for file recovery and not partition recovery? I was hoping that if I resize this now looking empty partition to it's correct boundaries...

 

"First check you should make would be to use a disk viewer/editor and verify that absolute sector 22661691 is the actual start of $MFT ." - PartitionWizard shows: Partition type ID: 0x7 Serial Number: 0x1cb6bb8c1f403a0; First Ph sector: 16370298; Last Ph. sector: 3907020601 - Is that you ask for?

 

Should I try to make a copy with Data RescueDD? I have a NAS and I can use one 2 TB HDD that I have there.

Attached Files


Edited by grancharov, 24 November 2013 - 06:12 AM.


#7
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,841 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Actually you should have done the image BEFORE fiddling with the disk, and right now it would (unless you continue fiddling, doing "random" things to that poor little disk ;)) be just loosing some time.

The idea is to first verify by ONLY reading some data on the disk, if it is recoverable (as filesystem).

If it is not, the free space you have will become useful as target for the "file-oriented" recovery attempt.

 

Ideally you should get "partition wizard", whatever it is, in the dustbin and not even think of using it again (unless told by someone to actually use it).

Last time I checked them there were 3 or 4 programs called "partition wizard", WHICH one have you used?

 

I need to:

  • understand WHAT EXACTLY you did (please describe everything you did, with the most details you can remember)
  • have you perform a couple of tests by reading/copying a few "key" sectors

 

The point is this.

  1. IF you ONLY created a partition entry in the MBR AND did NOT "format" it, then it is possible that the filesystem is recoverable
  2. IF  you - through any means - "formatted" the partition then IF it was a "quick" format, you have lost the filesystem for good BUT file recovery might be possible
  3. IF you - through any means - "formatted" the partition then IF it was a "full" format (as an example as performed by Vista :ph34r: or later) then not only the filesystem is lost forever but also each and every file that was there.

To quickly disambiguate, of the above three actions, #1 is instantaneous, #2 would have taken several seconds/minutes, #3 would have taken hours.

 

Without knowing what EXACTLY you did and under which EXACT OS and with WHICH EXACT tool, I cannot provide you with any meaningful support/advice.

 

You seemingly do not know what is (let alone use it) a disk editor/viewer.

 

Go here:

http://mh-nexus.de/en/hxd/

http://mh-nexus.de/e...php?product=HxD

and get this file:

http://mh-nexus.de/downloads/HxDen.zip

It is the portable English edition of the Nexus HD editor.

Uncompress in a directory.

Run Hxd.exe, it will ask you to create a configuration file in the directory, tell it "OK".

Then Extras->Open Disk Select the disk, you want to choose among the Physical disks, and since it is /dev/sdc in TESTDISK, that disk should be Hard Disk 3 (the numbering is the same that you can see in disk management), LEAVE the tickbox to "read only".

On the top bar there is an "edit box" Sector 0.

Write in it 22661691 and press Enter.

You should be now be on sector 22661691 of the disk.

It should begin with "File0" and around the middle of it you should be able to see "$.M.F.T.".

If you use the little up arrow beside the "Edit box" you can go on later sectors.

Every other sector should begin with "File0", the next one beginning with "File0" should have around the middle "$.M.F.T.m.i.r.r."

If you continue to go ahead, you should find a number of sectors with the "default" hidden fiels of a NTFS filesystem, like $LogFile, $boot, $Quota, etc.

If you continue to go ahead, within a few sectors you should be able to recognize some file/directory names that were on the disk.

If you can find some of them visually, there are good chances that the filesystem can be recovered, if after a few tens sectors there are no such filenames, the $MFT is lost (and your only chance is file based recovery).

 

jaclaz



#8
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

OK - I will try again.

I had 2 partitions - G and H on WD20EARS. The first one was 8 GB and not formatted. I didn't want to see the letter for that partition so I decided to delete it from the Disk Managemen tool in XP. Then the second - ntfs-partition disappeared. I loaded Parted Magic but didn't write nothing to HDD. In the past I managed to recover accidentally lost partition with MiniTool Partition Wizard so I used it again.

Attached File  PartitionWizard2.jpg   109.24KB   2 downloads

Then I ran Wizard - Partition Recovery Wizard - I don't know if this is some kind of formatting... It definitely didn't take hours - I think it is the first or second case.

I didn't perform reading/copying "key" sectors - don't know how.

 

There are only Zeroes on sector 22661691. The symbols begin at sector 138270720.

 

Attached Files

  • Attached File  XhD.jpg   309.36KB   2 downloads


#9
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,841 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Wait a minute.

It is possible that originally you made a (huge) Extended partition and created two logical volumes in it? :unsure:

That would explain how you managed to delete BOTH volumes from XP disk Management, and also the reason why in the posted screenshot of Minitool Partition Wizard the "lost" partition is seen as "logical".

 

What we need to find is the $MFT of the volume that you had as H:.

A "normal" NTFS partition sized above 5 or 6 Gb has it's $MFT on cluster 786432 and the default cluster size for a NTFS partition of that size should be 8 sectors.

So, the $MFT should not be before 786432*8=6291456 sectors starting from the beginning of the volume.

Here the problem seems to be that we don't know for sure where the volume exactly began.

Try the following:

  1. in HxD, go to sector 6291456 of the disk
  2. once there Search->Find "search for=FILE0 Datatype=Text-string Search direction=Forward

It may take a long time for the search to find a hit (if any).

 

Alternatively, as it might be faster/better, do the following:

  1. get DMDE from here: http://dmde.com/
  2. extract it to a directory
  3. run dmde
  4. Select the PhysicalDisk 3
  5. click on the button "NTFS search"
  6. leave the scan areas settings "start sector" at 0
  7. change the "end sector" by using the cursor to something around 20 Gb (jolt down the exact sector number)
  8. click on Search
  9. post a screenshot of results (if any)
  10. if no results are found, re-run the search by selecting "Range", this time use as "start sector" what you had before as "end sector" and limit the "end sector" to 40 Gb
  11. if no result repeat up to 60 Gb and then up to 80 Gb (I don't think there can be anything of use beyond this range) 

jaclaz

 

 



#10
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

I mounted this HDD many months ago and I don't remember - I guess it is possible.

From HxD I saw that there are symbols from sector 77453312 to 93916713 and from 138270720 to 3907024064 and also in the first sector.

Attached Files


Edited by grancharov, 24 November 2013 - 10:28 AM.


#11
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,841 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Good. :)

So DMDE found two possible NTFS volumes:

NTFS 0 which has 4412 entries in the $MFT and that supposedly starts at sector 16373760

NTFS 1 which has 5 entries in the $MFT and that supposedly starts at sector 16370298

 

The sector 16373760 corresponds to CHS 1019/55/61 and is correctly "Mb" aligned, as 7995*1048576/512=16373760

The sector 16370298 corresponds to CHS 1019/1/1 (which is the data currently in the MBR) and is correctly "cylinder" aligned.

 

It seems like originally the Disk has been partitioned/formatted under an OS (or with a tool) that aligns to Mb and that (for whatever reason) the tool you used cannot recognize such partitioning scheme and defaulted to a "cylinder aligned" values.

 

If this is the case, if in DMDE you select the NTFS0 volume and press the "Open Volume" button, and in the window that opens you click on the [+] besides "Root", you should be able to see most if not all the files you had before.

If you click on "Metadata" and click on the line that starts with $AttrDef, on the right panel you should see the $MFT entry and it's creation date (see if it "sounds" like the right one for the period when the disk was originally formatted).

If you double click on the $MFT entry in the right top pane, in the lower one you should see the actual LBA of the $MFT and a hex view of it.

See the attached screenshot of an "example" volume.

Does this happen?

What do you find instead?

 

jaclaz

 

 

 

 

Attached Files



#12
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

Yes - when I initially mounted this HDD, I used the tool(Acronis I think) recommended from WD to align the partition from 512 b to 4 k - I use 32 bit OS.

I don't see nothing on NTFS0.

On NTFS1 $Root I see only RECYCLER and System Volume information. In the Metadata I see 14-oct-2010 - the date I bought the HDD.

Attached File  DMDE-ntfs1.jpg   81.85KB   1 downloads

Attached File  DMDE-partitioning.jpg   52.71KB   1 downloads

 

In NTFS1 $MFT I see this:

Attached File  DMDE-ntfs1-mft.jpg   116.12KB   1 downloads


Edited by grancharov, 24 November 2013 - 01:05 PM.


#13
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,841 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

No, there is a misunderstanding.

in this screenshot here:

http://www.msfn.org/...-1385318959.jpg

you must try selecting the "$No Name 02" (which is the one that starts at 16373760) and click "Open Volume".

 

jaclaz



#14
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

Sorry but now I can't upload another screenshot - "You can upload up to Uploading is not allowed of files (Max. single file size: 100MB)" - don't know why.

In $Noname02 I can't see nothing under MetaData and $Root. Instead in $Noname01 I see what I uploaded already.



#15
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,841 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Sorry but now I can't upload another screenshot - "You can upload up to Uploading is not allowed of files (Max. single file size: 100MB)" - don't know why.

In $Noname02 I can't see nothing under MetaData and $Root. Instead in $Noname01 I see what I uploaded already.

Yes, there is a "max size" of the attachments.

You can upload the screenshots to a free hosting service, like -as an example - zshare:

http://www2.zshares.net/

 

If you compare the screenshot you posted:

http://www.msfn.org/...-1385318959.jpg

with this snippet of the DMDE Help:

 

Indicators - volume diagnostic indicators (indicate correspondent structure presence):

  • T – partition table;
  • E – table entry;
  • B – volume boot sector;
  • C – boot sector copy;
  • F – MFT(0) for NTFS or Root for FAT (is being tested on FAT volume opening);
  • f – MFTMirr(0) for NTFS;
  • x – structure is absent or damaged;
  •   – structure is not tested.

Red color indicates errors in the partitioning.

 

and based on your previous screenshot here:

http://www.msfn.org/...-1385309565.jpg

 you will see how everything confirms that the "good" voume is the one starting on 16373760, it is possible that you (or DMDE) are doing *something* that currently prevents the correct parsing of that volume data.

Maybe you should try closing and restarting DMDE, then do a new scan, starting from fresh.

When you get to this screenshot:

http://www.msfn.org/...-1385309565.jpg

if you select the "NTFS0" it should open the "right" data.

It is possible that something has been modified by your previous attempts with partition wizard or by the built-in Windows tools, but I doubt it, in any case there is "enough" to attempt a filesystem based recovery.

(i.e. it is worth the time to make a dd-like copy of the disk as is)

In DMDE re-open the Physical disk, then go to "Tools"-> Copy Sectors, click on Partition button, on the dialog that opens click on the PhysicalDisk listing and click OK (this will auto-compile the fields Start Sector and End Sector in the "Source" part of the dialog), choose in the "Target" part a file.

Be VERY careful to choose a drive with enough space!

The resulting file will be a 1:1 copy of the disk, so it will be 2 Tb in size!

Consider that it will take several hours to make the copy and if - for whatever reasons - either the source or the target disk tend to heat up, it would be a good idea to add something to keep them cool, like a small fan.

 

 

jaclaz



#16
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

My last screenshot definitely wasn't 100 MB - it was 154 kB. I resized it to 89 kB but I received the same error. No matter anyway...

In the first post I wrote that when I tried to recover the lost partition with Partition Wizard, after that I rebooted and then in the corresponding step of the starting process XP ran its tool for disk checking. I didn't stopped it and maybe this made the situation worse.

I use the free version of DMDE - is this a problem? Maybe it is better to use dadarescuedd?

The destination will be 2 TB "green" HDD in D-Link DNS-345. It won't be a problem that it runs under linux(file system) - right?



#17
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,841 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

NO, the upload limit (maximum global size for attachments on MSFN.ORG forum) is much lower expecially - I believe - for new members, if you sum all the screenshots and logs you posted, you have probably reached it.

 

It does matter that you find a way to produce that screenshot, as I need to know the actual LBA of the "real", "good" $MFT (the one found for the volume that starts @16373760) and have to know what actually it is found when using that $MFT.

 

From what I could gather till now, partition Wizard simply recreated a partition with a slightly different situation.

It is possible that CHKDSK made some "damage", but I doubt it (and it shoudl have been an extremely "short" run of CHKDSK) :unsure:

 

In the meantime I thought a bit about WHAT caused the issue, and (morally only :w00t:) I have good news :).

It was not strictly your fault (nor the fault of the tools you used), it was one of the lesser known SERIOUS glitches with XP (actually with it's Disk Manager), see here:

http://reboot.pro/to...itioning-issue/

basically the XP disk manager CANNOT deal with disks containing logical volumes NOT aligned to cylinders and whenever you do *anything* on such a disk, even something as trifling as changing the active status of a Primary partition, it attempts to re-calculate/re-check the whole partitioning setup, fails and plainly deletes any and all logical volumes inside extended.

 

The issues (if any) with that NAS are the following:

  • the filesystem of the partition on which you create the huge file must be capable of making such a big file (this means either NTFS or Ext2/3/4, I am not familiar with that hardware but - if by any chance the filesystem is FAT32 it won't work :ph34r:) and you need to have anyway 2,000,398,934,016 free space on the volume on which you make the file, if the actual disk in the NAS is 2Tb in size, I doubt you will have that amount of space actually free in the filesystem
  • transferring 2 Tb over the network might be very slow (normally such dd copies are made to disks directly connected to the machine)

I am not aware of a limitation in the free edition of DMDE about the imaging, but you can use datarescuedd as well as *any* tool capable of making a dd-like copy of the disk.

 

BEFORE you make the "huge copy" I would like to have a look at:

some 100 sectors starting from sector 0:

dsfo \\.\PhysicalDriven 0 51200 C:\myfirst100.bin

some 300 sectors starting from sector 16370098 <- these include also the beginning of the "bad" $MFT which is @16370322

dsfo \\.\PhysicalDriven 8381490176 153600 C:\mybadpart300.bin

some 300 sectors starting from sector 16373560

dsfo \\.\PhysicalDriven 8383262720 153600 C:\mygoodpart300.bin

some 300 sectors starting from sector (the whatever sector the "good $MFT" is)

dsfo \\.\PhysicalDriven ???????? 153600 C:\mygood$MFT300.bin

(in the screenshot you posted http://www.msfn.org/...-1385319889.jpg which is about the "bad" $MFT, the meaningful LBA address is the one in the top left of the right bottom pane, in GREEN LBA:16370322, I need the corresponding one for the "good" $MFT)

 

The n  in the above is the "usual" disk number.

You can get the dsfo.exe as part of the DSFOK toolkit:

http://members.ozema...eezip/freeware/

extract it in a directory like C:\dsfok, then open a command prompt and navigate to it and then enter the command lines above.

If you have issues with command line tools, say so BEFORE attempting using them incorrectly.

As an alternative you can use the DMDE or the DatarescueDD to create the needed "partial" .bin files.

Once you have created them, do compress them all into a .zip archive, upload to a free hosting site and post a link to the file.

Ask for clarifications if you have doubts.

 

jaclaz

 



#18
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

You at first wrote that 2 TB HDD will be enough and now - won't be enough? I already was thinking about buying a 4 TB HDD to put it into last free slot in the NAS. I know that more than 2 TB won't work with XP, but right now I can't exchange XP with 7...

 I think the file system for my NAS is ext3 or ext4. Because of the low network speed(I use a cheap router) I agree that it maybe would be better to mount this HDD in the PC. But then I will have to format and align(or reversely) it. So if only the speed will be the problem here, and not the space - I will copy through the LAN.

I'm not very comfortable with command line tools. Would you tell me how exactly to get those 100 sectors with DMDE?

 

$Noname02 $MFT - LBA 16373784


Edited by grancharov, 25 November 2013 - 01:25 PM.


#19
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,841 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

A 2 Tb hard disk would be enough if you do a "clone" (i.e. you can write directly to a disk or \\.\Physicaldrive).
A 2 Tb hard disk would NOT be enough if you do an "image" (i.e. a file written on an existing filesystem) as the filesystem structures will occupy a part of the 2 Tb.
If you can use Explorer, if you select the volume and Right click->Properties you need to have at least 2,000,398,934,016 bytes in "Free Space":

Spoiler

the above example most likely belongs to a 2Tb disk partitioned under XP that has a few hidden sectors at the beginning and some unused space at the end, since also your currently failed disk has some unused space at the end, you could do with (3,907,024,064+1)*512=2,000,396,321,280 to image/clone the WHOLE disk.

BUT it would be also "enough" if you save separately (in two distinct files) only the sectors from 0 to 100 and the sectors from 16,370,000 (rounded) to 3,907,024,064, which would make (3,907,024,064+1-16,370,000)*512=1,992,014,881,280 which should fit in a filesystem on a 2 Tb disk.

 
With DMDE, after having opened the PhysicalDrive, go to Tools->Copy Sectors

  • myfirst100.bin:
    Input in "Source" Start sector=0 Number of sectors=100
    In "Destination" click File button and then Save to myfirst100.bin
  • mybadpart300.bin:
    Input in "Source" Start sector=16370098 Number of sectors=300
    In "Destination" click File button and then Save to mybadpart300.bin
  • mygoodpart300.bin:
    Input in "Source" Start sector=16373560 Number of sectors=300
    In "Destination" click File button and then Save to mygoodpart300.bin
  • mygood$MFT300.bin:
    Input in "Source" Start sector=????????  Number of sectors=300 <- the ???????? stand for the LBA that I still miss
    In "Destination" click File button and then Save mygood$MFT300.bin

jaclaz



#20
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

http://www2.zshares.net/7rjdwmauz1zz - this is from Noname02.



#21
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,841 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Ok, all data seems (if not "right") understandable.

I am still curious about the exact procedure that was originally used to create the filesystem.

The $MFT is on cluster #3, which is VERY unusual (default is as said 786432), most probably this is the single issue that "throws off" TESTDISK.

 

The data seems like entirely recoverable. :thumbup

The point is whether once you will have made a simple corrections to the MBR and possibly checked the Bootsector mirror (or replace it) it will be possible only through DMDE (in which case you will need to buy a license for the full version, since the Free one only allows for recovery of single items) or the small manual repairs will be enough to run TESTDISK and get the files or (better) it will be possible to run successfully CHKDSK.

 

If you have found a suitable way to make the image (always better safe than sorry) all seems like fine and dandy.  :)

 

The plan is to have the image created, do a few changes/correction on the disk and let CHKDSK fix the rest, if it works (it seemingly worked nicely on the partially rebuilt filesystem I tried :yes:), good, if it doesn't, we restore the image and try again with DMDE. 

 

In the meantime I will rebuild another partial filesystem from scratch and see what TESTDISK can do with it.

 

jaclaz

 

P.S.: you might want to remove/delete the last file you uploaded to zshare


Edited by jaclaz, 26 November 2013 - 05:42 AM.


#22
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

Thank You for the assistance!

I have a couple of questions. At first about DMDE: there is "Express" and "Home" version. Is the "Express" enough for my case? I think that the differences between these versions aren't important to me.

The next one is more general - I'm not sure what would be better(faster, safer...smarter :)):

- to free one HDD in my NAS and to make the image there

- to free this HDD and move it in my main PC - and because I use 32 bit OS I will have to reformat and align it

- to mount this HDD and also the damaged HDD in my secondary PC, where I recently installed Win7

or to buy a new - 4 TB HDD and mount it in the NAS?

 

The problem is that my main PC has only one free SATA port and old OS, and my secondary PC has a case(CM Elite 360), that doesn't support more than 3 HDD's by default and there are already 2(I could connect another 2 but the cooling can be a problem).



#23
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,841 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

I am not much familiar with the licensing options of DMDE, but both Home and Express would do (if needed) in your case:

http://dmde.com/editions.html

the difference is support period (that you probably - or hopefully - won't need at all) and number of hardware changes per year (that again you should not need at all).

This is "personal use only", right? :unsure:

 

There is no need to "realign" anything (connected to using a 32 bit OS), maybe if the NAS uses Ext2/3/4 there is a need to re-format as NTFS (there are Ext2/3 drivers for Windows XP, but cannot say if they are reliable with this mass of data/size of file/transfer).

 

You can mount a HD "temporarily" alright, I mean you open the side of the case, put the harddisk on a piece of cardboard beside the case or on top of it and have the cables get out of the case. As long as you don't have kids or pets at loose in the house ;) there would be no issues.

 

It is some time since I image such a huge hard disk, but it should be (at top SATA 2 speed) something like 150 Mb/s top speed, but on average more like 100 Mb/s, i.e. you have around 2 Tb=2,000 Gb=2,000,000 Mb divided by 100, 2,000,000/100=20,000 seconds/3600=5,55 hours,  likely it will take something between 5 and 8 hours.

 

A "normal" 100 Mbps local Lan will have at the most 12.5 Mb/s of transfer, more probably 10 Mb/s, i.e. it will take approximately ten times!

Think at all the things that may go wrong (power outage/blackout as an example) over 5 days 24h. :ph34r:

 

jaclaz



#24
grancharov

grancharov

    Newbie

  • Member
  • 37 posts
  • Joined 23-November 13
  • OS:Windows 7 x64
  • Country: Country Flag

I read that the so called advanced format HDD is optimized for Vista and newer OS and under XP it needs to be "aligned" with special tool... I think (but not sure) that without the "align"-procedure I will have lower performance. Anyway, I will cope with this task.

 

OK, most likely I will move one HDD from NAS to the main PC. I will write again when I'm ready - probably in Thursday or Friday. Thank you again!



#25
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,841 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Yep :), but you see, everything is "relative". :w00t:

 

Having a partition aligned to 64K as a multiple of 4096 bytes (the common cluster size in NTFS) is an advantage where the BUS (i.e. SATA2 or later) is faster than the actual hard disk.

BTW this alignment favours only some types of data access, compare with:

http://reboot.pro/to...-issue/?p=85960

and it applies (mainly) to NTFS (as NTFS is "inherently" aligned to cluster size), it won't work (unless some further measures are taken) to FAT/FAT32, see:

http://www.msfn.org/...n-its-clusters/

http://reboot.pro/to...-under-windows/

http://reboot.pro/to...-memory-drives/

 

It may also apply to EXT2/3/4 :unsure:, but the point is that if the bus is slower than the device (such as it would be in a NAS) there won't likely be any positive effect.

 

What people sometimes forget is that only relatively recently actually hard disks were capable of saturating a SATA1 (or ATA6, i.e. IDE133) bus speeds.

 

A SATA2 bus outperforms *any* harddisk, the new frontier (SSD's) are faster and do *need* SATA3, but when you put in it a slowish intermediate (such as USB2 or Ethernet connection) the performance of the bus is so inferior to that of the device that it makes little sense to optimize the device.

 

jaclaz






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users