[arch-general] Error message with full disk encryption

Carsten Mattner carstenmattner at gmail.com
Sat Feb 13 21:12:50 UTC 2016

On Sat, Feb 13, 2016 at 4:51 PM, Yaro Kasear <yaro at marupa.net> wrote:
> On Sat, 2016-02-13 at 13:47 +0100, Carsten Mattner wrote:
>> On Sat, Feb 13, 2016 at 10:49 AM, PeLo L <pelo99 at outlook.com> wrote:
>> >
>> > Hi,
>> >
>> >
>> > I've followed the arch wiki and deployed a full disk encrypted
>> > install.
>> > Everything works fine and am able to boot properly into the
>> > install.
>> > While trying to shutdown my system, systemd displays an error
>> > which says "systemd: stopped (with error)  /dev/mapper/crypt-boot".
>> > 'crypt-boot' is the device mapper name for the encrypted boot
>> > partition. Could someone explain this. Do I need to be concerned
>> > of any data loss in the boot partition?
>> I've seen this on old and newly installed root-luks systems myself.
>> Here it's always dm1 and I'm not sure if it's luks-root or luks-swap,
>> but it looks like a bug in systemd or one of the units because this
>> appeared sometime in the last 6 months or less.
> I have also seen this issue come up on my system. It doesn't seem to
> affect anything except causing a slightly longer shutdown time. Still,
> would be good to see this fixed.

There's also some message bus errors on shutdown that are intermittent,
but even though it may sounds stupid, I've grown to ignore systemd
shutdown and startup issues for the most part, because they happen
occasionally and sometimes they don't. Nothing to write home about,
just growing pains or Kinderkrankheiten as they say in Germany :).

More information about the arch-general mailing list