Starting with the OpenMandrivaLx.3.01-PLASMA.x86_64.iso
I updated the live version and installed calamares 3.0.1
> # urpmi.update -a
> # urpmi calamares
I installed OpenMandrivaLx.3.01-PLASMA.x86_64 on /dev/sdc using the Manual Partition option with a luks encrypted swap and root partition, both
partitions having the same password. The /dev/sdc disk has only 2 partitions.
The bootloader is also situated on /dev/sdc.
The new installation boots fine and can be updated to the current situation but the swap partition isn’t opened at boot time although the boot process asks for a LUKS key (only one!) at the start of the boot.
Checking for swap on the running system returns no results:
# cat /proc/swaps
Filename Type Size Used Priority
- I noticed 2 errors scrolling by very quickly during the boot process and
found the following paragraph in the /var/log/boot.log file.
Does this look familiar to one of you?
Maybe for different reasons but I’ve had problems with swap and dual boot. Some of the steps I’ve taken to solve that problems are commented here,
In my case, problems came from bad choices during installation.
Don’t know much about it.
This probably should be a bug report.
A question. Does your Lx 3 system/systems ever use swap? Mine don’t, ever, that I’ve seen. With swappiness set at 10 a Lx 3 system won’t use swap until 90% of RAM is used.
# cat /proc/sys/vm/swappiness
Also check the 4th line of your .png where is starts "See ‘systemctl status …’ try to run that and see what it says and post that here as code also post contents of /etc/fstab as code.
Also google might come up with some interesting information such as this and this.
Helpful hint: Posting the log is great but it is more useful if posted as code (ie. preformatted text icon: < />).
I never checked if my system uses swap, I stumbled on the problem because I saw a boot error passing by. On my installation swappiness also returns the value 10
Here is the output of the systemctl command:
# systemctl status "dev-disk-by\\x2duuid-273349a0\\x2dadf2\\x2d426a\\x2d84e7\\x2dcdd16f9aa251.swap"
● dev-disk-by\x2duuid-273349a0\x2dadf2\x2d426a\x2d84e7\x2dcdd16f9aa251.swap - /dev/disk/by-uuid/273349a0-adf2-426a-84e7-cdd16f9
Loaded: loaded (/etc/fstab; generated; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2017-03-17 21:41:44 CET; 24min left
Process: 4255 ExecActivate=/sbin/swapon -o defaults,noatime /dev/disk/by-uuid/273349a0-adf2-426a-84e7-cdd16f9aa251 (code=exit
Mar 17 21:41:44 kastaar swapon: swapon: /dev/sdb1: read swap header failed
Mar 17 21:41:44 kastaar systemd: Failed to activate swap /dev/disk/by-uuid/273349a0-adf2-426a-84e7-cdd16f9aa251.
lines 1-10/10 (END)
And this is the contents of /etc/fstab:
# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=273349a0-adf2-426a-84e7-cdd16f9aa251 swap swap defaults,noatime 0 0
UUID=f000775c-645a-49c8-8506-06f51ea85497 / ext4 defaults,noatime 0 1
Regardless swap should work. I don’t know what to say or do about this situation so we need developer help. Could you post this issue on the Cooker ML?
At the moment developers seem to be elsewhere, perhaps somewhere in Europe in a Beer Garden.
Edit: Or better yet file a bug report?
On modern machines
swap in not more so mush used but it may help in some case and it is mandatory if you use hibernation of the system.
I don’t know if
swapon can handle directly with encrypted partition.
You may try with
sudo swapon -s and with
sudo swapon -v -o defaults,noatime /dev/disk/by-uuid/273349a0-adf2-426a-84e7-cdd16f9aa251
An usual configuration is to use LVM on LUKS.
Finally imho keep
/home in a different partition with respect
/ is always a good practise.
swapon -s doesn’t give any reply
# swapon -s
The second command produces an error:
# swapon -v -o defaults,noatime /dev/disk/by-uuid/273349a0-adf2-426a-84e7-cdd16f9aa251
swapon: /dev/sdb1: read swap header failed
I now got the time to look deeper in this encryption method and it looks by far not that promising any more.
Do I understand this correctly:
Suppose you have 4 encrypted partitions with a different pass-phrase:
At boot time you have to insert 4 different pass-phrases (in the right order) each time you start-up the system.
This isn’t so convenient.
Your LVM on LUKS solution and Ben79 's link are at first sight far better solutions.
But there is a problem, both solutions are using the mkinitcpio or update-initramfs commands which I can’t locate on the OpenMandriva installation.
Did one of you already test this procedure, know the location of these commands or know alternative commands?
Five times if you encrypt
/boot ;). However there is the possibility to store the password on the disk so you don’t need to insert it each time, or use on time automatic password for swap.
About ‘LVM on LUKS’ you need to insert two time the same password. Actually the problem is Calamares has not support for LVM yet. I opened a discussion and a bug report but the problem is the upstream. So I haven’t tested on Lx3 yet.
I experimented a little bit with Full disk encryption with LUKS (including /boot) as mentioned in Ben79’s link.
I have everything in a pdf but I don’t know how to add it to this post.
Anyway also here calamares is the show stopper. I can mount the newly created volumes as /mnt and /mnt/home. They also show-up in MCC but calamares doesn’t know how to handle them.
Isn’t there a way to bypass calamares and install a new system directly on the mounted directory /mnt?
A monkey can find links with Google. I don’t actually know much about encrypted systems/partitions and have never done it myself. The monkey also found this.
I am starting to play with this now. So far I know if I try to install say OM Lx 3.02 build # 913 and select ‘encrypt’ and ‘ext4’ for / and /home when I go to install Calamares then crashes during partitioning. But then I don’t know what I’m doing… Yet… So it must require more than selecting a check box…
Does anyone have Om Lx 3 installed and working with encryption?
Edit: Full Disclosure: I don’t hardly ever use Google itself rather one or StartPage, IXQuick, or less likely Duck Duck Go blow.
If I remember fine TPG fixed it some time ago.
You may also take a look here but select
Primary instead of
As indicated in the first post of this thread, I have a working encrypted OpenMandrivaLx3 system by following the directions you gave me. My system has all available updates installed, has only two partitions (An encrypted ext4 root partition and an encrypted swap partition which doesn’t work). I created the system around 12 March, it works fine, besides the swap problem.
The sad thing is that I can’t repeat the installation a second time. When I repeat the installation calamares also crashes in my case. I think that the updates released since 12 March are interfering with my calamares environment (Before I can run the latest calamares, I have to update the live system with the latest updates before calamares want to start)