dsbahr;1910837 Wrote:
> Hi, I’m a new openSuse user, and I need to use Truecrypt.
>
> I couldn’t find it through Yast, so I have installed the rpm package on
> truecrypts homepage, version 6.1.a.
>
> Everything went smooth, but when I try to mount/dismount a volume,
> truecrypts freezes, and stops working. This happens every time.
>
> I do not get any kind of error messages, and I have no idea of, what
> the problem might be?
>
> The encrypted volumes are in NTFS file format. In Ubuntu this didn’t
> seem to be a problem, is this different in Suse? I use KDE4 in Suse.
>
> Has someone experienced a similar problem, and found a solution for
> this?
>
> Besides that, thumbs up, I’m very impressed with openSUSE so far
>
> - dsbahr
Try contacting truecrypt about this, as it’s likely the problem is on
their end. (Or they can find what in OS is causing it exactly to be
fixed). I believe their unusual license clause prevents opensuse
inclusion, so it wouldn’t hurt to bug them about that too – then
opensuse could ensure compatibility directly
I think the problem is the NTFS-Container!
When i create one container, i have only the possibility to select FAT,
ext2 or ext3. And when i create one in FAT it is possible to use. The
only thing is with my old container in NTFS.
Why i can not select NTFS when creating a container?
The problem is the NTFS-3G DRIVER (v1.5012)!
I update the driver from this repository: ‘Index of
/repositories/home:/anubisg1/openSUSE_11.0’ (http://tinyurl.com/5jo8uu)
to the newest stable version 1.5130 and it works perfekt!
Upgrading to the NTFS-3G rpm in the repository you identified fixed the
problem for me. It is NTFS specific as I also had no problems mounting
from FAT volumes.
When mounting a NTFS truecrypt file, select under the mount options
“Filesystem: Do not mount”
With that the truecrypt file is mounted to /dev/mapper/truecrypt1,
however the filesystem is not mounted.
After that it is possible to mount the NTFS filesystem with
-sudo ntfs-3g /dev/mapper/truecrypt1 /media/truecrypt -o
user,gid=100,fmask=113,dmask=002-
(Before mounting, /media/truecrypt must be created with -sudo mkdir
/media/truecrypt-
it still doesn’t work for me, i mean when trying “do not mount” option
and mounting it by the hand, mount still hangs (if i use only mount
command),
if you use /bin/ntfs-3g or /sbin/mount.ntfs-3g (symlink to
/bin/ntfs-3g) it works, in every ntfs-3g version, but if you make a
symlink from /bin/ntfs-3g to /sbin/mount.ntfs*
Code:
mount /dev/mapper/truecrypt1 /media/truecrypt1 -o rw,noexec,nosuid,nodev,users,noatime,gid=100,fmask=133,dmask=022,locale=pl_PL.UTF-8,debug
unless i add -t ntfs-3g or -t ntfs explicitly or use /sbin/mount.ntfs
symlink
tried it with no mount options, with gvfs* programs killed, with
nepomuk & kerry/beagle shutdown etc , every time the same thing;/ it’s
really annoying, because i don’t want to use console to mount it by hand
using /bin/ntfs-3g or mount with -t flag, that’s why i changed distro to
opensuse, that’s why i’m using GUI cryptographic program like truecrypt!
*otherwise mount will use kernel builtin driver instead of ntfs-3g,
stock ntfs-3g package privides this symlink, but package from
‘repository referred by cocolocko’ (http://tinyurl.com/5jo8uu) don’t,
that’s why it worked for him, ntfs-3g wasn’t used;-)
maniel is right. I didn’t go back and check to see when I posted
previously. ntfs-3g is not being used as he described in the package
from the repository cocolocko referred to. I can reproduce the problem
by creating the symlink from mount.ntfs->mount.ntfs-3g
Additionally, the hal policy is changed in from the default openSUSE
11.1 ntfs-3g policy for auto-mounting ntfs media, when using the repo
referenced above, and may cause trouble. If you’ve gone this path, the
fix is to restore the file
/usr/share/hal/fdi/policy/10osvendor/21-storage-ntfs-3g.fdi from the
openSUSE ntfs-3g package) if you want to keep the newer ntfs-3g driver.
i’ve found a solution, you have to rebuild fuse package with version
changed to 2.7.4 in original opensuse specfile and ntfs-3g with wersion
changed to 1.5130 in also original opensuse specfile [and remove patches
and -Werrors from CFLAGS, otherwise the build will fail]
too bad that i can’t paste the specs here or attach srpms to the post
maniel;1918992 Wrote:
> i’ve found a solution, you have to rebuild fuse package with version
> changed to 2.7.4 in original opensuse specfile and ntfs-3g with wersion
> changed to 1.5130 in also original opensuse specfile [and remove patches
> and -Werrors from CFLAGS, otherwise the build will fail]
> too bad that i can’t paste the specs here or attach srpms to the post
nope, it was false alarm, ntfs-3g package i build doesn’t provide
/sbin/mount.ntfs link so mount used kernel builtin driver, that’s why i
successfully mounted my partition:)
Has someone found a solution which does not imply recompiling any
packages?
I’ve downgraded the ntfs-3g package back to the one from the openSUSE
repository as we found out that the package from the Anubis repo doesn’t
create the /sbin/mount.ntfs symlink which is the only reason why
TrueCrypt is able to mount NTFS containers because it uses the old ntfs
module (which has limited capabilities) in that case.
This combo (TrueCrypt + ntfs-3g) worked perfectly in Kubuntu 8.10.
it looks like it’s stuck on /etc/mtab~*, it’s locked or what? it’s not
the kernel fault IMHO [maybe opensuse patches are messing up?] because
i’m encountering that on 2.6.27.10 kernel too
tried glibc from factory [2.9-4.3, recompiled with my own flags] and
still the same;/
devs! are you tere?!