|
From: SourceForge.net <no...@so...> - 2005-03-18 20:11:15
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3055536 By: gkmohan win-full.img is generated using ntfsclone --rescue -o win-full.img /dev/hda3 win-special.img is generated using ntfsclone --rescue -so win-special.img /dev/hda3 --- strings -td ntfs-bad-blocks.img /mnt/freestore/winxp.img | grep BadClusteR --- strings gives up without trying complaining large sizes [root@localhost root]# strings -td /mnt/freestore/win-full.img strings: Warning: could not locate '/mnt/freestore/win-full.img'. reason: Value too large for defined data type [root@localhost root]# strings -td /mnt/freestore/win-special.img strings: Warning: could not locate '/mnt/freestore/win-special.img'. reason: Value too large for defined data type But I did just grep [root@localhost root]# grep BadClusteR /mnt/freestore/win-special.img [root@localhost root]# grep BadClusteR /mnt/freestore/win-full.img grep: memory exhausted that is (according to grep manual), win-special.img does not have BadClusteR strings. I will try to find out a way search the file win-full.img --- Please explain in more details/examples what you mean. There are several sizes. --- here are the stats one /mnt/windows (df -B1 /mnt/windows) Filesystem 1B-blocks Used Available Use% Mounted on /dev/hda3 6168956928 3183087616 2985869312 52% /mnt/windows here are the reserved sizes (ls -l /mnt/freestore/*.img) -rwx------ 1 root root 6168957440 Mar 17 22:50 /mnt/freestore/win-full.img* -rwx------ 1 root root 3183839628 Mar 17 21:08 /mnt/freestore/win-special.img* here are the actual sizes (du -B1 /mnt/freestore/*.img) 3186274304 /mnt/freestore/win-full.img 3186958336 /mnt/freestore/win-special.img As specified in the ntfsclone manual, I can mount win-full.img but not win-special.img --- > To check that everything went right I mounted the image file as a > loopback device mount /mnt/freestore/winxp.img /mnt/loop -t ntfs -o > loop=/dev/loop0 and then did a diff with the mounted ntfs partition > diff -r /mnt/loop /mnt/windows which reveals that I cannot access > /mnt/loop/WINDOWS directory. I get an I/O error when I try to access > this directory. Do you have any idea of what could have gone wrong? So it seems the kernel couldn't read the data there. If Windows can see that directory then this is a kernel bug/feature again. --- I need to be more specific here. I can access mnt/windows/WINDOWS but not /mnt/loop/WINDOWS. That is the kernel can read the WINDOWS directory on the mounted ntfs partition but not from the image win-full.img mounted from a loopback device on /mnt/loop. --- > I also have another question. What happens to the bad sectors portion > of the data when the image used for restore? The unreadable content of the disk having bad sectors is filled by 0x02 (this will change to a readable character) and a "BadClusteR" signature is written at the start of these sectors. --- Sorry for being dumb here but what happens during restore to a partition with no bad sectors. Will BadSectoR signature still be restored? ______________________________________________________________________ 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 |
