[systemd-bugs] [Bug 88483] btrfs raid on plain dmcrypt fails to boot randomly
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Nov 12 13:46:44 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=88483
--- Comment #11 from dutch109 at gmail.com ---
I am hit by this bug too (Arch Linux with Linux 4.4 & systemd 231).
None of the workarounds I found here and elsewhere did work, I tried:
* explicitely require all devices in /etc/fstab with device=xxx,device=yyy
* setting filesystem to noauto,x-systemd.automount in /etc/fstab and noauto in
/etc/crypttab (it did work until a recent update)
* adding btrfs in MODULES array in /etc/mkinitcpio.conf
I finally "fixed" it by setting the filesystem to noauto in /etc/fstab (so they
are NOT mounted by systemd at boot), and creating a simple service that mounts
the missing partitions later.
/etc/systemd/system/late-mount.service :
[Unit]
Description=Mount directories that systemd fail to mount
[Service]
ExecStart=/etc/systemd/system/late-mount
[Install]
WantedBy=multi-user.target
/etc/systemd/system/late-mount:
#!/bin/bash -e
mount /xxx
mount /xxx/yyy
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-bugs/attachments/20161112/0cbb0303/attachment.html>
More information about the systemd-bugs
mailing list