: SUBSYSTEM=block
E: SYSTEMD_READY=0
E: TAGS=:systemd:
E: USEC_INITIALIZED=40061
/dev/md0p5 and /dev/md0p6 also report SYSTEMD_READY=0
So, the tag isn't being set correctly?
Ali
On 24 September 2012 11:11, Lennart Poettering lenn...@poettering.net wrote:
On Mon, 24.09.12 10:59, Ali Lown
]: Expecting device /dev/md1p5...
The 'conflicting device node' is an interesting message, since I don't
see how it can be conflicting with anything...
Thanks.
Ali
On 22 September 2012 12:43, Ali Lown a...@lown.me.uk wrote:
I waited until the weekend so I could take down the devices briefly
deprecated in the linux world?
On 17 September 2012 13:57, Alexander E. Patrakov patra...@gmail.com wrote:
2012/9/17 Ali Lown a...@lown.me.uk:
I am unable to get systemd to mount a LUKS partition on boot. This
LUKS partition (pdc_bhjchdjgaep5) sits on top of a fakeraid mirror set
(pdc_bhjchdjgae
I am unable to get systemd to mount a LUKS partition on boot. This
LUKS partition (pdc_bhjchdjgaep5) sits on top of a fakeraid mirror set
(pdc_bhjchdjgae) of 2TB disks (sdd,sde).
I am using systemd from scm
(f6c2e28b07a0d24c68f7780fc986ac3619fdcbdb). I have also tried systemd
189, and have the
