Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=3057628
By: gkmohan
Thanks for the lesson on bad blocks.
Yes, when I ran chkdsk /r there were 5 stages.
You are correct, today I ran it with --rescue
[root@localhost root]# ntfsclone --rescue -O /mnt/freestore/win-full.img /dev/hda3
and it gives out errors "WARNING: Couldn't read a cluster,
data is lost" but finishes to create an image, ofcourse without
these clusters. This image has the same properties as the
image created before chkdsk /r was run. (i.e, I still can't
access some of the data e.g., /mnt/loop/WINDOWS)
Please let me know when you include the option
--retries=<number>. Alternatively on a very bad disk with a lot
of bad sectors, to save time, you could only retry those
sectors where windows claims to have data. Then one needs
to first create a table of data sector numbers based on the
directory structure. Tedious.
I have no clue here but would not using ntfs driver simplify life a lot? Is
ntfsclone designed to be a stand-alone program?
To summarize for future references (szaka please make amends as necessary)
To clone an ntfs partition
1) run `badblocks <device>` to check for bad blocks.
If there are bad blocks this will dump some numbers to stdout
If there are bad blocks
2) run `chkdsk /f /r <drive:>` (ofcourse in windows)
3) run `ntfsclone --rescue --retries=<number> -o <image> <device>
otherwise
2) run `ntfsclone -o <image> <device>`
Optionally I strongly suggest (if your kernel supports ntfs read)
o `mkdir /mnt/loop`
o `mount <image> /mnt/loop -t ntfs -o loop`
o if windows is not mounted mount it (say, /mnt/windows')
o `diff -r /mnt/loop /mnt/windows`
If all goes well you should not see any errors on the last command.
______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=44084
|