On Wed, 08 Oct 2014 18:41:00 +0200 Sven Joachim sent:
> > 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 i
On Wed, 08 Oct 2014 18:13:09 +0200 Hans sent:
> 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,
> >
> > 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.
>
Just to make it
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 2
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
On 2014-10-08 17:14 +0200, Hans wrote:
> Tha last error I could associate to the drive, but I am stuck, how to fix
> this.
>
> I get:
>
> protheus2:~# systemctl --failed list-units
> UNIT LOAD ACTIVE SUBDESCRIPTION
> ● systemd-remount-fs.service loaded failed failed
Hi Jonathan,
> Look; don't guess. You've discovered with systemctl list-units
> --failed which units have failed. Now use systemctl status on each of
> those units, which will give you when it was started, what was
> started, how it stopped (with exit code and signal status), and (if
> you do th
Hans Ullrich:
> However, everything is working well, as far as I see.
> Maybe it is, because I am using encrypted filesystems? Or because of using a
> SSD-drive?
Look; don't guess. You've discovered with systemctl list-units
--failed which units have failed. Now use systemctl status on each of
Hi Michael, hi Sven!
Yes, you are right, I have indeed errors.
systemctl --failed
UNIT LOAD ACTIVE SUBDESCRIPTION
● speech-dispatcher.serviceloaded failed failed LSB: Speech Dispatcher
● systemd-modules-load.service loaded failed failed Load Kernel Modules
● sy
Am 07.10.2014 um 20:02 schrieb Sven Joachim:
> On 2014-10-07 18:15 +0200, Hans wrote:
>
>> Hi folks,
>>
>> after the last update (debian/jessie), I get a lot of LSB related messages
>> and
>> other stufff at boot.
>
> I presume you are using systemd? There is a new behavior in version
> 215,
On 2014-10-07 18:15 +0200, Hans wrote:
> Hi folks,
>
> after the last update (debian/jessie), I get a lot of LSB related messages
> and
> other stufff at boot.
I presume you are using systemd? There is a new behavior in version
215, as soon as a unit fails to start systemd enters verbose mode
Hi folks,
after the last update (debian/jessie), I get a lot of LSB related messages and
other stufff at boot.
It is a little bit annoying. Can I suppress these?
I gave the option "quiet" in the grub commandline already.
Additionally I discovered a new message, telling me, it is checking some
12 matches
Mail list logo
