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 and a second ago, I filed a bugreport to systemd. It is just sent, so I must wait to receive a bugnumber. In this bugreport, I explained, what I believe, why this is not working correctly. Maybe you might want to take a look. However my thoughts may be wrong. Does it help? Hans -- 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/2893510.DH5TOtLQVj@protheus2
