Bug#801361: [systemd] attempts to unmount filesystems at end of boot, INCLUDING ROOT

[Ara Keary]

PS, downgrading (under amd64)
 systemd libpam-systemd libsystemd libsystemd:i386
to 226-4 on source and destination systems also solves the rsa/dsa ssh key
logging problem (it works again).
Tell me if any log file is needed

On 9 October 2015 at 12:55, Ara Keary <ara.keary at gmail.com> wrote:

> Hi,
>
> same here: no proper boot after 227-1 → 226-4 systemd update.
>
> /var/log/syslog show attempts to unount EVERY partition ; only the
> unmounting of / fails (fortunately...).
>
> Under amd64 multiarch, downgrading
>  systemd libpam-systemd libsystemd libsystemd:i386
> to 226-4 solves the problem
>
> Before downgrading, solved manually by mounting manually all partitions
> from root console
>  mount -a
> and restarting gdm
>  service gdm restart
>
> Other symptom, if helpful: trying to log with rsa/dsa key fails on every
> machine i can access to.
> Could all this mess be related to a (pam) *system-wise authentification
> problem*?
>
> On fresh testing → unstable 1 day old update: same symptoms. Thus seems
> unrelated to old .conf file problem.
>
> Maintainers: i really truly appreciate ∞ly your work, but do you test
> updates before uploading? ...
>
> Best log decrypting,
>
> Ara
>
> PS Severity should be critical
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151009/41324349/attachment-0002.html>