[systemd-devel] Cryptsetup on FakeRAID fails with timeout
ali at lown.me.uk
Mon Sep 24 04:22:36 PDT 2012
FW back onto the mailing list:
As the devices report ATM (after a manual mounting following systemd failure):
/dev/md0p5 and /dev/md0p6 also report SYSTEMD_READY=0
So, the tag isn't being set correctly?
On 24 September 2012 11:11, Lennart Poettering <lennart at poettering.net> wrote:
> On Mon, 24.09.12 10:59, Ali Lown (ali at lown.me.uk) wrote:
>> As described in OP, I am running
>> f6c2e28b07a0d24c68f7780fc986ac3619fdcbdb, so I am running with
>> I confirmed that the line added in 44b exists in
> Hmm, please try to debug this by checking for the systemd tag and the
> SYSTEMD_READY field for the md device. systemd will pick up block
> devices only if the tag is set and the field is 1. Use "udevadm info
> /dev/md0" (or suchlike) for this.
> Lennart Poettering - Red Hat, Inc.
More information about the systemd-devel