Hi Simon, [email protected] wrote: > Hi Jean-Pierre, > > I have good news! > I was able to repair the image and access the data! >
Great news. I saw your previous email with more errors, but I did not get time to analyze the details. > The program I wrote was able to do the lion share of the work. > A few errors needed manual fixing because the scan() / check() functions need > 10 successive error free blocks for resync and some areas had multiple errors > within a 10 block area. > > And in case you need it for someone else, here is the source code of the > program: > http://www.sbsw.net/ntfsclone-check.cpp > I have downloaded it, I will consider integrating it as an option in ntfsclone to check the consistency of an image. > For me the case is closed, do you need any further information regarding the > problem? > For me, the issue still is to identify whether there is a bug in ntfsclone or if the image got somewhat corrupted for another reason. Did you initially compress the image ? If you could decompress it, the corruption probably occurred earlier than compression, otherwise you would not be able to decompress. > To me these errors look a bit as if the variable, that holds the code to write > in ntfsclone, doesn't get initialized all the time for code 0x1 blocks, > because most of the time ntfsclone just wrote a 0x0 were a 0x1 would belong. > This looks like a bug in ntfsclone, though such error pattern has not been reported so far. If this error pattern is caused by a bad ntfsclone, the good news is that an auto-repair can be built. > But in a few cases there were other values (0xC8) there. But this is just a > wild guess. And of course the image was created with the old version of > ntfsclone that was shipped with the openSuSE 12.1 x64 DVD. Maybe it is > already gone in the newest version.... > Can you be more precise about the ntfsclone version used to build the image ? ("ntfsclone -h" will display it) There has been a major port in 2010 from a dead project, and some code cleaning was done at the time. > I could now try to create a new ntfsclone-image from the raw-image and see if > the errors persist?! > Yes, please, try to create an image again with the original version, and if you got a corrupted image, try again with a recent version. Regards Jean-Pierre ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ ntfs-3g-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
