On 2014-10-08 18:13 +0200, Hans wrote:
> Am Mittwoch, 8. Oktober 2014, 17:49:47 schrieb Sven Joachim:
> Hi Sven,
>
>> journalctl -u systemd-remount-fs.service
>
> Please look here:
>
> protheus2:~# journalctl -u systemd-remount-fs.service
> -- Logs begin at Mi 2014-10-08 16:57:15 CEST, end at Mi 2014-10-08 18:07:33
> CEST. --
> Okt 08 16:57:18 protheus2 systemd-remount-fs[707]: mount: /usr not mounted or
> bad option
> Okt 08 16:57:18 protheus2 systemd-remount-fs[707]: /bin/mount for /usr exited
> with exit status 32.
> Okt 08 16:57:18 protheus2 systemd[1]: systemd-remount-fs.service: main
> process
> exited, code=exited, status=1/FAILURE
> Okt 08 16:57:18 protheus2 systemd[1]: Failed to start Remount Root and Kernel
> File Systems.
> Okt 08 16:57:18 protheus2 systemd[1]: Unit systemd-remount-fs.service entered
> failed state.
> protheus2:~#
>
>
> I believe, the problem occurs because of my encrypted filesystem
No, it seems to be because of the separate /usr filesystem. Basically,
systemd expects /usr to be mounted by the initramfs which is implemented
by initramfs-tools in unstable, but not in testing.
> and a second ago, I filed a bugreport to systemd. It is just sent, so
> I must wait to receive a bugnumber.
Should be merged with #742048[1] probably.
Cheers,
Sven
1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742048
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87siiywm3n....@turtle.gmx.de
