Page 1 of 1

Full disk encryption problem

Posted: 28. Mar 2014, 13:36
by marconi
I successfully crypted disk using README_CRYPT.TXT, but when I start system I get three error messages.
The encryption work, the only problem are this boring messages. What is wrong?

Code: Select all

/boot/initrd.gz: Loading kernel modules from initrd image:
insmod /lib/modules/3.10.17/kernel/fs/mbcache.ko
[5.181998] mbcache: exports duplicate symbol mb_cache_create (owned by kernel)
modprobe: ERROR: could not insert 'mbcache': Exec format error
insmod /lib/modules/3.10.17/kernel/fs/jbd2/jbd2.ko
[5.226763] jbd2: exports duplicate symbol jbd2__journal_restart (owned by kernel)
modprobe: ERROR: could not insert 'jbd2': Exec format error
insmod /lib/modules/3.10.17/kernel/fs/jbd2/jbd2.ko
[5.268557] jbd2: exports duplicate symbol jbd2_journal_restart (owned by kernel)
modprobe: ERROR: could not insert 'ext4': Exec format error
Unlocking LUKS encrypted device '/dev/sda2' as luks mapped device 'lukssda2':
Enter passphrase for /dev/sda2:

Re: Full disk encryption problem

Posted: 28. Mar 2014, 18:06
by gapan
Are you using the huge kernel?

Re: Full disk encryption problem

Posted: 28. Mar 2014, 20:19
by marconi
gapan wrote:Are you using the huge kernel?
I tried with both vmlinuz and vmlinuz-huge-3.10.17. Has anyone tried to do the full disk encryption with README_CRYPT.TXT on Salix 14.1?

Re: Full disk encryption problem

Posted: 28. Mar 2014, 20:41
by gapan
These are both the same. One is symlinked to the other. The README_CRYPT.TXT instructions assume you are using kernel-generic instead of kernel-huge. If you use kernel-huge, the modules that you're including in the initrd are also part of the kernel binary, hence the messages you get. You cannot load a module if it's already loaded through the kernel itself.

Re: Full disk encryption problem

Posted: 29. Mar 2014, 01:27
by TracyTiger
marconi wrote:Has anyone tried to do the full disk encryption with README_CRYPT.TXT on Salix 14.1?
I just built a Salix64 14.1 system with all disk partitons encrypted except /boot. http://forum.salixos.org/viewtopic.php? ... 528#p33528

I had noncritical errors similar to yours until I figured out that only the huge kernel was available in Salix. I eliminated the errors by removing most of the modules (-m) when building the initrd. In other words ... what gapan wrote.

If you want to experiment some you can copy the generic kernel from Slackware 14.1 into your setup and create your initrd from that.

Re: Full disk encryption problem

Posted: 29. Mar 2014, 08:56
by gapan
TracyTiger wrote:I had noncritical errors similar to yours until I figured out that only the huge kernel was available in Salix.
False statement. kernel-generic can be installed anytime.

Re: Full disk encryption problem

Posted: 29. Mar 2014, 17:47
by TracyTiger
You're correct. Poor choice of words on my part.

I meant that it wasn't on the installation disk I was using. I didn't mean to mislead.

Your post made me realize I moved the kernel the hard way instead of using Salix tools.