Bug 9657

Summary:	Cannot mount a file container with Truecrypt: "Failed to set up a loop device"
Product:	Mageia	Reporter:	Stéphane Couturier <mageia>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	chmielu1_a, davidwhodgins
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Stéphane Couturier 2013-04-08 08:01:18 CEST

Description of problem:
When trying to use Truecrypt 7.1a on Cauldron, I cannot manage to mount a file container. The error message is "Failed to set up a loop device:" followed by the path of the file I am trying to mount.

Version-Release number of selected component (if applicable):
Truecrypt 7.1a, cauldron updated with latest packages

How reproducible:
Every time, even with a newly created file container.
Mounting a crypted partition works fine.
I never had this message with Mageia2.

Steps to Reproduce:
1. start truecrypt (as root, or making the user has proper permissions) 
2. select a file container
3. click mount => error message

A possible fix was discussed for another distribution: https://bbs.archlinux.org/viewtopic.php?id=136879
It seems related to "modprobe" but I don't understand what the workaround is, and I wonder if this is related to a change between Mageia2 and Cauldron.

Thank you,

Reproducible: 

Steps to Reproduce:

Comment 1 Stéphane Couturier 2013-04-08 08:07:59 CEST

I confirm the workaround:

1. open console and log in as root
2. enter "modprobe loop"
=> File container can now be mounted.

Any side effect to this command?
Can it be added as a defaut when booting Mageia?

Thanks,

Comment 2 Marcin Ch 2013-04-08 18:15:07 CEST

I added loop to modprobe.conf (/sbin/modprobe loop):
$ cat /etc/modprobe.conf |grep loop
install scsi_hostadapter /sbin/modprobe sata_nv; /sbin/modprobe pata_amd; /sbin/modprobe loop; /bin/true
$
You can try:
echo "loop" > /etc/modprobe.preload.d/loop

CC: (none) => chmielu1_a

Comment 3 Stéphane Couturier 2013-04-18 13:17:05 CEST

Hi, I added the loop as indicated. It actually worked only after a few reboots, but it is now working fine everytime, thanks for the tip.

Comment 4 Manuel Hiebel 2013-04-19 18:54:30 CEST

have we this package in our repositories ? if not I really don't see what we can do..

Comment 5 Dave Hodgins 2013-04-21 02:07:54 CEST

I think all we need is udev rule(s) that
recognize truecrypt devices, and ensures
the modprobe loop is done.

I'll try to take a look at writing some
in the next few days.

CC: (none) => davidwhodgins

Comment 6 Dave Hodgins 2013-04-22 00:30:11 CEST

Forget the idea of using udev rules. Unlike luks encrypted devices,
truecrypt volumes do not contain anything detected by udev, that can
be used to identify a truecrypt encrypted device.

Other then recommending
echo "loop" > /etc/modprobe.preload.d/loop.conf
for anyone using truecrypt, I don't see anything else we can do.

Anyone object to closing this bug as invalid, since it's for a
product that is not supported by Mageia?

Comment 7 Stéphane Couturier 2013-04-23 16:41:09 CEST

Hi, I don't mind that it is closed.
Out of curiosity, would Truecrypt be the only tool that would benefit from adding loop to modprobe.conf in the offical distribution file? I'll have a look at Mageia2 files just to see how it was.
Thank you all for your help.

Comment 8 Dave Hodgins 2013-04-23 20:32:11 CEST

Closing as invalid, since it involves software not provided by Mageia.

Status: NEW => RESOLVED
Resolution: (none) => INVALID