On Sat, Feb 13, 2016 at 10:49 AM, PeLo L <pelo99@xxxxxxxxxxx> 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.
