|
From: SourceForge.net <no...@so...> - 2005-03-20 19:36:12
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3057671 By: szaka > 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) Unless somebody tells or figures out, I'll check after about two weeks why the NTFS driver can read dying sectors but not badblocks and ntfsclone. > Please let me know when you include the option --retries=<number>. It would take about 0.5-1 hour but currently I'm too sick to do any productive thing. Next chance will be about after two weeks. > 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. This is how it is done already. > I have no clue here but would not using ntfs driver simplify life a > lot? Is ntfsclone designed to be a stand-alone program? Ntfsclone makes an _exact_ backup, at bit level. Currently the NTFS driver doesn't support getting all the needed information, also the Linux kernel has a lot of limitations to export exotic things to user space. > 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>` Simpler: 1) run `ntfsclone -o <image> <device>` if you get the 'read_all: I/O error' 2) run `ntfsclone --rescue --retries=<number> -o <image> <device> then you could run 3) run `chkdsk /f /r <drive:>` and retry to make a better backup 4) run `ntfsclone --rescue --retries=<number> -o <image> <device> The reason to postpone chkdsk /r is that sometimes it kills the disk entirely (the disk stops working at all) so you won't have any chance anymore to save your data. Similarly, running badblocks on a dying disk first may kill the disk and no chance to save the data later on. > 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. Right, this is guaranteed. Any error would mean a bug somewhere or one has bad sectors and used the ntfsclone --rescue option. ______________________________________________________________________ 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 |
