Description of problem: Truecrypt and other pprograms can't bind a loop device with kernel 3.12.5-100. Failuremessage: "Failed to set up a loop device" If the current nsa incidents, this is a fatal flaw and should be considered a security problem. Kernels prior to 3.12. are working properly. Version-Release number of selected component (if applicable): 3.12.5 How reproducible: Steps to Reproduce: 1. create a truecryptcontainer via truecrypt command or UI 2. try to mount it i.e. in the shell: truecrypt -p <password> -t -k "" --protect-hidden=no -m "nokernelcrypto" /root/truecryptfile.tc /mountpoint it does not matter if its tried via UI or shell. It always the same message. # modprobe loop does not help and won't help, as the old kernel 3.11.10 does not have the module loaded at all and can mount the device. The changes are thereby made inside the kernel. Actual results: a not helping error message: "Failed to set up a loop device" Expected results: a working mount Additional info:
*** This bug has been marked as a duplicate of bug 1019440 ***
Different release, same problem with kernel 3.12 These two lines seem to fix it: echo "options loop max_loop=8" > /etc/modprobe.d/eightloop.conf echo "loop" > /etc/modules-load.d/loop.conf reboot