Main Area and Open Discussion > General Software Discussion

Truecrypt forced dismount and filesystem corruption

(1/1)

nosh:
I've had problems with the NTFS filesystem of a Truecrypt volume (external HDD) getting corrupted in the past. I've run chkdsk and that fixed it most times. I had to reformat the drive and start from scratch on one occasion (after chkdsk couldn't fix the problem, IIRC - I'm hazy about the details since it was a while back.)

I suspected hardware issues but it struck me it could be the forced dismount I used on the volume. The dismount was initiated through a batch file using the /force switch, so it occured everytime.

I stopped using forced dismount and started using Unlocker to take care of whatever was stopping the volume from dismounting normally.

Today, I tried to dismount the volume and got the usual "truecrypt volume contains files or folders being used by applications or system" message. Unlocker shows there's nothing locking the drive. I installed iobit Unlocker and it doesn't show the drive as locked either. I did a forced dismount, remounted the volume and ran chkdsk. No errors detected, but I'm worried my luck may not last. There seems to be a mismatch between what Truecrypt and the Unlocking utilities are reporting. The Windows Indexing service never runs on my system and I even closed the usual suspects - Everything & Locate32 (both configured to ignore the TC drive), anti-virus (doesn't scan in realtime, in any case).

Is there any way to know which files-in-use/apps Truecrypt has detected? Or should I just go ahead and use a forced dismount as long as Unlocker gives me the all clear?

40hz:


Maybe I'm excessively paranoid, but whenever I have a problem like that with an encrypted volume I just do a quick restart rather than get fancy with switches and forced quits. I'd rather let Windows "do the paperwork" if there's a chance of data corruption when mounting or unmounting storage devices.
 8)

nosh:
Seems like that's the only "clean" solution available.  :up:

Just saw your edit... 4 minute reboot... I AM EXCIIIITE!  :P

40hz:
4 minute reboot? Wow... :tellme: I can run a full integrity check on my Linux filesystem in less time than that.  :-\

nosh:
Haven't actually timed it but it definitely isn't brisk!

Navigation

[0] Message Index