chroot cannot be mounted

[kronn]

updating crouton and the chroot went fine and without errors.

However, when I try to sudo enter-chroot and tail the syslog, I get the following output

chronos@localhost / $ tail -n0 -f /var/log/messages &
[1] 386
chronos@localhost / $ sudo enter-chroot
2015-03-22T13:17:33.606686+01:00 INFO kernel: [ 5550.736360] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,data=ordered
Entering /mnt/stateful_partition/crouton/chroots/trusty...
2015-03-22T13:17:34.169314+01:00 NOTICE dbus[613]: [system] Activating service name='org.freedesktop.login1' (using servicehelper)
2015-03-22T13:17:34.178635+01:00 NOTICE dbus[613]: [system] Activated service 'org.freedesktop.login1' failed: Cannot launch daemon, file not found or permissions invalid
2015-03-22T13:17:34.211696+01:00 INFO kernel: [ 5551.340650] systemd-logind[641]: New seat seat0.
2015-03-22T13:17:34.256679+01:00 INFO kernel: [ 5551.384267] systemd-logind[641]: New session c1 of user root.
2015-03-22T13:17:34.406681+01:00 INFO kernel: [ 5551.534282] systemd-logind[641]: Removed session c1.
2015-03-22T13:17:34.491688+01:00 INFO kernel: [ 5551.620445] systemd-logind[641]: New session c2 of user kronn.
2015-03-22T13:17:44.151688+01:00 INFO kernel: [ 5561.278952] systemd-logind[641]: New session c3 of user root.
2015-03-22T13:17:44.171687+01:00 INFO kernel: [ 5561.299963] systemd-logind[641]: Removed session c3.
2015-03-22T13:17:44.691747+01:00 INFO kernel: [ 5561.822443] systemd-logind[641]: Removed session c2.
2015-03-22T13:17:44.736677+01:00 INFO kernel: [ 5561.864570] systemd-logind[641]: New session c4 of user root.
Unmounting /mnt/stateful_partition/crouton/chroots/trusty...
2015-03-22T13:17:45.610806+01:00 ERR umount.ecryptfs[995]: Failed to find key with sig [37ad567b81947b21]: Required key not available
2015-03-22T13:17:45.610897+01:00 ERR umount.ecryptfs[995]: Failed to find key with sig [dda26d4c4bac4751]: Required key not available

[2]+  Stopped                 sudo enter-chroot
chronos@localhost / $ fg 2
sudo enter-chroot
chronos@localhost / $

I can see the files of the unencrypted chroot in /mnt/stateful_partition/crouton/chroots/trusty, As far as I remember, the chroot was not encrypted. I only have the extra-cli and extension-targets installed.

The only cause I can think of is a power-outage while the chroot was mounted.

How can I recover from this state?

I wouldn't loose any data with this, it's just a little tedious to copy the needed files back into the chroot. Also, I would like to understand problem instead of just recreating the chroot.

[drinkcat]

The only cause I can think of is a power-outage while the chroot was mounted.

It might be that the chroot got corrupted, somehow...

How can I recover from this state?

Start by updating your chroot. If that's not enough, you could reinstall the Ubuntu package that provides systemd-logind (apt-get install --reinstall systemd-services). If that's still not enough, you might be better off creating a new chroot....

[kronn]

I updated it as first step before opening the issue. Painless process, no errors, but also - sadly - no change.

How can I reinstall that Ubuntu-package when I cannot enter the chroot?

[kronn]

Ah, found it:

sudo enter-chroot -x apt-get install --reinstall systemd-services

However, the chroot remains broken. I will recreate it, thanks for your help.