Am 21.09.2013 23:49, schrieb Canek Peláez Valdés: > OK, so I conducted another experiment, to see if I was able to make > systemd *not* to work with an exotic combination of underlying > storage. I did the following: > > - 4 drives, all of them in RAID5. > - The resulting /dev/md127 was put in a Physical Volume, that in a > Volume Group, and that split into 5 Logical Volumes: > 1. /boot (unnecessary, but why not) > 2. swap > 3. / (root) > 4. /usr > 5. /home > - The /home partition was encrypted, and so was the swap. > > Everything works, but now I did had to do something not intuitive. > > First the intuitive changes from my previous experiment: > > 1. I had to put this in /etc/default/grub: > > GRUB_PRELOAD_MODULES="lvm mdraid1x" > > Basically that's it. The partitions again use labels, so I didn't had > to touch fstab, except for the not intuitive change. > > The problem, that I believe Stefan and Frank hinted, is that the > encrypted swap did not activated properly, sometimes resulting in huge > boot times (in the order of 1 minute). But only if you specify the > swap partition in fstab.
Yes, I reported this issue back then ... but I don't have the encrypted swap in /etc/fstab. I only have: # cat /etc/crypttab swap /dev/disk/by-id/ata-INTEL_SSDSA2M080G2GC_CVPO015404LR080JGN-part5 /dev/urandom swap,cipher=aes-cbc-essiv:sha256,size=256 which gives me a /dev/mapper/swap ... but no activated swap ... I will create a swap-unit now ... S
