On 12/30/2009 2:09 AM, sieidi wrote:
> Any help for my situation?
>
> My customer had his laptops hard disk with full of customer files and his
> disk space was running off. I cloned the disk to new bigger one, but XP
> didn't show the partition size right. Disk manager showed the size, but
> explorer showed the size that was the one of the earlier hard disk. I told
> customer to run chkdsk /r, but it hadn't any effect for the problem.
>
> But customer needed his laptop and after three weeks he came back and wanted
> to have partition size bigger. So i adjusted size using Gparted -software.
> After the adjustment ntfs was lost from the disk and it told partition was
> raw.
>
> Got files restored using Zero Assumption Recovery -software. They are right
> size files and assosiated with right software. But when i try to open files
> they say that they are corrupted.
>
> If i try to open e.g. doc-file with word 2007, it asks what encoding im
> gonna use and for pdf-files it says the file is corrupted. I have tried to
> run chkdsk /r, but it doesn't have any help for the problem.
>
> Is there any tool to repair corrupted ntfs-files ? Every help for problem is
> high appreciated.
>
> I can get the old files restored from old hard disk, but files changed
> within than three weeks are broken now.
There are a couple of things I would do.
1) Do a raw copy of the new drive that has the 3 weeks worth of new data.
2) Using PartitionMagic or a similar product (I have had a few (not
many) cases of bad luck with GParted and other Linux based partitioners).
3) After you have partition the new drive to its full size then use a
program like Ghost to do a partition to partition copy. Make sure to
have it copy the MBR and tell it not to resize the partition on the new
new drive drive.
4a) Once you've got the customer up and running, look at the raw image
you made and try pulling looking at some of the known files with a
hex-editor and see if there is actual corruption of the file itself or
if the NTFS system simply was reading it wrong. If they look right in
the hex-editor, then save the file to a separate drive and try reading
it on to the customers machine and see if it will read on the customers
machine.
4b) If the hex dump between what is on the old drive and the old drive
do not match then you do probably have corrupted files. At that point if
the data was important enough you could go through them and see if there
is a pattern to the corruption. Note that the files really need to be
important because your talking some serious hours and some serious
modeling to find possible patterns. I had to do that once for a person
who's doctoral thesis got corrupted. It took me about 10 days to find
the pattern and restore that one file (It also tied up two of my
computers doing the modeling).
Sincerely,
C.Joseph Drayton, Ph.D. AS&T
CSD Computer Services
Web site:
http://csdcs.site90.net/
E-mail:
(E-Mail Removed)
Similar Threads
