Bugzilla – Bug 446020
partitioner doesn't work when encrypted swap is present
Last modified: 2009-12-08 09:48:07 UTC
i can choose a mount point, but then, even though the "File System" parameters say that the device is encrypted, partitioner doesn't ask for a password, the install step fails to mount ("unknown filesystem "LUKS encrypted"") and the installation dies
Please add the YaST log files.
i'm not sure that it's possible, because the installation actually _FAILS_ after this. (if i can somehow retrieve the logs from the linuxrc curses interface, to which it falls back, please tell me how) also, i can provide logs from successful install, but there won't be mentions of the encrypted space, right?
turns out that it is reproducible after installation -> changing summary and component to Yast. steps to reproduce: 1. create and format encrypted swap, close partitioner 2. open partitioner, make a change (i.e. try to set mountpoint for preexisting encrypted volume) 3. close partitioner. result: "mounting /dev/sda5 as swap" in actions window, and an error popup: "system error code is -3003; /sbin/swapon '/dev/sda5': swapon: /dev/sda5: invalid argument" ..obviously, because the correct device is /dev/mapper/cr_sda5 and, as before, when trying to mount the encrypted partition, it won't ask for password, so i guess that it would fail later anyway
Created attachment 252983 [details] yast2 logs
*** This bug has been marked as a duplicate of bug 435244 ***
the issue from bug 435244 seems to be solved for me, however the other one, "system error code is -3003; /sbin/swapon '/dev/sda5': swapon: /dev/sda5: invalid argument" is still there. steps: 1. set up an encrypted swap, without password (in previous versions, this was the way to have random key on each start, the keyfile in /etc/crypttab was set to /dev/urandom. now it's none, so i'm not sure if it works the same. however, the swap is successfully mounted at system start) 2. exit partitioner 3. open partitioner again. the encrypted swap partition has a star next to it (as if its configuration is changed) 4. try to change something, e.g. set up a mountpoint for some partition. 5. when applying changes, the partitioner reports the above mentioned error. 6. no changes are applied => reopening and raising severity matejcik@ws-pool1:~> rpm -q yast2-storage yast2-storage-2.17.60-1.1 matejcik@ws-pool1:~> rpm -q yast2-storage-lib yast2-storage-lib-2.17.60-1.1 y2logs will follow
Created attachment 258329 [details] yast2 logs
The star means that the volume is currently not mounted (as mentioned in the help text).
oh. anyway, the volume -is- mounted at that time, only not as /dev/sda5 but as /dev/mapper/cr_sda5
duplicate *** This bug has been marked as a duplicate of bug 435337 ***