[systemd-bugs] [Bug 88483] btrfs raid on plain dmcrypt fails to boot randomly

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=88483

--- Comment #4 from Paolo <palmaway at gmx.it> ---
I changed /etc/fstab to contain the following line:

UUID=ee0726c7-f7d1-4031-8a53-32d384334196   /data   btrfs 
defaults,compress-force=lzo  0 0

as you can see, I also eliminated the "device" mount options, in case those
were the ones creating the problem. Unfortunately, as stated in my first post,
now I get these messages at boot:

- "A start job is running for" /dev/mapper/cryptb and /dev/mapper/cryptc with
no timeout;
- "A start job is running for dev-disk-by/x2uuid-..." with a timeout of 1min
and 30 secs.

The three messages alternate on screen, and when the timeout for the last one
ends, I am able to enter the root password for maintenance.

Please don't ask me why doesn't it work, as that is exactly why I posted a bug
report: there is an expected behavior, but it doesn't happen.

Can you please clarify what do you mean by "the idea is to always use the
UUID"? Do you mean in the crypttab as well? How can I use the UUID's in the
crypttab, since the disks share the same UUID? Can you provide an example?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150301/22669ab6/attachment.html>