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