Kay,
Thanks. That rule appears to have fixed it for me.
> The current rules always marked all MD partitions as inactive, which
> does not sound right. We are not even sure if the partitions would
> ever get a change event later.
The partitions correctly mount at boot-time now. The luks partition
On Mon, Sep 24, 2012 at 2:32 PM, Lennart Poettering
wrote:
> On Mon, 24.09.12 12:22, Ali Lown (a...@lown.me.uk) wrote:
>> /dev/md0p1:
>> P: /devices/virtual/block/md0/md0p1
>> E: DEVTYPE=partition
>> E: SUBSYSTEM=block
>> E: SYSTEMD_READY=0
>> E: TAGS=:systemd:
>> /dev/md0p5 and /dev/md0p6 also
On Mon, 24.09.12 12:22, Ali Lown (a...@lown.me.uk) wrote:
> FW back onto the mailing list:
>
> As the devices report ATM (after a manual mounting following systemd failure):
>
> /dev/md0:
> P: /devices/virtual/block/md0
> N: md0
> L: 100
> S: disk/by-id/md-uuid-ee87365a:bf0826c6:0825cc4b:d1c49ec
FW back onto the mailing list:
As the devices report ATM (after a manual mounting following systemd failure):
/dev/md0:
P: /devices/virtual/block/md0
N: md0
L: 100
S: disk/by-id/md-uuid-ee87365a:bf0826c6:0825cc4b:d1c49ecb
E: DEVLINKS=/dev/disk/by-id/md-uuid-ee87365a:bf0826c6:0825cc4b:d1c49ecb
E:
On Mon, Sep 24, 2012 at 11:54:17AM +0200, Lennart Poettering wrote:
> On Sun, 23.09.12 18:20, Ali Lown (a...@lown.me.uk) wrote:
>
> >
> > I responded too early, mdadm has caused its own set of problems:
> >
> > - During the boot process, the mdXpX.device don't get marked as active
> > automatica
On Sun, 23.09.12 18:20, Ali Lown (a...@lown.me.uk) wrote:
>
> I responded too early, mdadm has caused its own set of problems:
>
> - During the boot process, the mdXpX.device don't get marked as active
> automatically causing X.mount based on those devices to fail.
> Once I get to the emergency
I responded too early, mdadm has caused its own set of problems:
- During the boot process, the mdXpX.device don't get marked as active
automatically causing X.mount based on those devices to fail.
Once I get to the emergency shell, simply calling 'systemctl
daemon-reload' reloads the mdXpX.device
I waited until the weekend so I could take down the devices briefly.
After converting to use md instead, I can confirm that systemd is
working fine with automounting the luks partition and correctly asking
for a passphrase.
The migration I used was:
dmraid -an #disable dmraid devices
mdadm --creat
2012/9/17 Ali Lown :
> 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).
Disclaimer: what I am proposing below is not a solution, just a workaround.
Now that a norm
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 sam
10 matches
Mail list logo
