I need some more diagnostics to track down the issue. Please download
the latest utils
(http://exfat.googlecode.com/files/exfat-utils-0.9.5.tar.gz), untar
them:
tar xf exfat-utils-0.9.5.tar.gz
cd exfat-utils-0.9.5
apply the attached patch:
patch -p0 < ~/Downloads/invcldiag.patch
compile the utils (you'll need scons and libfuse-dev):
scons
run exfatfsck against the failing volume (it works with FS in
read-only mode, so it cannot damage your data):
sudo fsck/exfatfsck /dev/sdd1
and send me the full output it produces.
Thanks in advance.
--
Andrew Nayenko <res...@gmail.com>
The EOD entry (entry with 0 in the type field) is missing in the root
directory. Looks like Windows checks directory's size field to
determine the end of the directory, meanwhile fuse-exfat uses EOD
entry for this purpose. This is why your disk is readable under
Windows but not under Linux.
Anyway, the absence of EOD is a problem. Most probably it's caused by
the bug in mkfs.exfat 0.9.4 (which was fixed in 0.9.5). So, the most
straightforward way to fix you issue is to recreate the filesystem
using latest mkfs.exfat (currently 0.9.5) or Windows' format.exe.
--
Andrew Nayenko <res...@gmail.com>