On 25.09.2013 22:17, Jean-Pierre André wrote: >> # dd if=/dev/mapper/truecrypt1 bs=4096 skip=75092490 count=1 | head -c 4 >> | hexdump >> 0000000 b836 f1e9 > > This is the same value as the one read by ntfsinfo, > this tends to prove ntfsinfo reacted properly on wrong > data.
[...] > Good luck. If you find some useful conclusion, please > share it. I have further evidence to back this up: After completely decrypting the whole volume (removed TrueCrypt entirely, took the night), I can perfectly access everything on the disk from my Linux partition. It seems to me that it's beyond reasonable doubt that TrueCrypt is at fault here. Hopefully that's at least guy for you guys to know if there's someone else in the future with the same problem :-) Thanks again for your support, Best regards, Joe ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ ntfs-3g-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
