| 1 |
On Fri, Sep 20, 2013 at 11:17 AM, Stefan G. Weichinger <lists@×××××.at> wrote: |
| 2 |
> |
| 3 |
> I haven't yet worked through all your suggestions/descriptions. |
| 4 |
> |
| 5 |
> Edited USE-flags and dracut-modules, worked around bug |
| 6 |
> |
| 7 |
> https://bugs.gentoo.org/show_bug.cgi?id=485202 |
| 8 |
> |
| 9 |
> and rebuilt kernel and initrd. |
| 10 |
> |
| 11 |
> Didn't activate LVs ... |
| 12 |
> |
| 13 |
> Now I edited fstab: |
| 14 |
> |
| 15 |
> I had the option "systemd.automount" enabled, like in |
| 16 |
> |
| 17 |
> /dev/mapper/VG03-media /mnt/media ext4 |
| 18 |
> noatime,user_xattr,comment=systemd.automount 0 2 |
| 19 |
> |
| 20 |
> The/my idea behind that: the boot-process should not need to wait for |
| 21 |
> the LVs activated/fscked/mounted ... and my root-fs and /home are both |
| 22 |
> on the SSD anyway (not LVM-based). |
| 23 |
> |
| 24 |
> I removed that option and after the next boot the LVs were activated and |
| 25 |
> mounted (though the booting was a bit slower, as expected). |
| 26 |
> |
| 27 |
> OK. I send this message now and test another few reboots. |
| 28 |
|
| 29 |
Forgot to mention it: I also enabled mdadm.service. |
| 30 |
|
| 31 |
Regards. |
| 32 |
-- |
| 33 |
Canek Peláez Valdés |
| 34 |
Posgrado en Ciencia e Ingeniería de la Computación |
| 35 |
Universidad Nacional Autónoma de México |
Archives