Package: systemd
Version: 232-25+deb9u1
Severity: important
Laptop was connected to a Thunderbolt dock, lid closed, using desktop
monitor and keyboard, everything connected through the dock. It is a
laptop with encrypted LVM and swap on LVM.
Laptop's thunderbolt cable was bumped very slightly w
Package: systemd
Version: 215-8
Severity: serious
I have a server with many LVM logical volumes on top of the same RAID1
md device on two spindles.
At boot, fsck appeared to be starting on many of the LVs simultaneously.
There was a horrendous sound of disk head movement from the server.
This
Package: systemd
Version: 215-8
Severity: important
Immediately after upgrade from wheezy, the system booted up and
displayed the emergency mode prompt but also started running fsck.
There are many filesystems and the emergency mode prompt/greeting was
scrolled away by the fsck output.
When fsc
Package: systemd
Version: 215-17+deb8u1
Severity: important
This has been happening on a system that was upgraded from wheezy to jessie
Sometimes systemd starts the network and then tries to start things that
depend on the network (e.g. ntpdate, NFS client mounts) before DHCP has
obtained a lease
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/07/15 13:58, Michael Biebl wrote:
> Am 04.07.2015 um 11:38 schrieb Daniel Pocock:
>> Package: systemd Version: 215-17+deb8u1 Severity: important
>>
>> This has been happening on a system that was upgraded fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/07/15 14:29, Michael Biebl wrote:
> Am 04.07.2015 um 14:22 schrieb Daniel Pocock:
>>
>>
>> On 04/07/15 13:58, Michael Biebl wrote:
>>> Am 04.07.2015 um 11:38 schrieb Daniel Pocock:
>>>> Packag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/07/15 21:10, Michael Biebl wrote:
> Hi,
>
> Am 04.07.2015 um 18:08 schrieb Daniel Pocock:
>> On 04/07/15 14:29, Michael Biebl wrote:
>
>>> (*) As a side note: you might want to consider enabling
>>> sys
Package: systemd
Version: 215-17+deb8u4
Severity: important
If the init script in /etc/init.d is a symlink to a script on another
filesystem such as /opt then systemd silently ignores it
It doesn't get started at boot
Using a command like
systemctl start foo
gives no output, no error, but d
Severity: important
Package: systemd
Version: 215-17+deb8u2
Since upgrading to jessie/systemd, one particular system frequently
stops in the single-user mode password prompt during booting.
Looking at the journalctl output, I usually find that some mount has
failed with a line like this:
/dev/m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/07/16 02:36, Michael Biebl wrote:
> Control: tags -1 + moreinfo
>
> Hi Daniel
>
> Am 01.07.2016 um 10:35 schrieb Daniel Pocock:
>> Severity: important Package: systemd Version: 215-17+deb8u2
>>
>> Since
Control: tags -1 - moreinfo
I've observed this problem again today
Looking more closely, I noticed that it started to fsck the mount just
before it tried to mount it. It didn't appear to wait for fsck to finish:
Dec 03 10:51:37 systemd[1]: Started File System Check on
/dev/mapper/vg00-foo_ho
I also reported the issue upstream:
https://github.com/systemd/systemd/issues/4812
and noticed somebody else reported a similar bug upstream for Btrfs:
https://github.com/systemd/systemd/issues/927
___
Pkg-systemd-maintainers mailing list
Pkg-syste
On 15/12/16 00:29, Michael Biebl wrote:
> Am 07.12.2016 um 17:36 schrieb Daniel Pocock:
>> I've observed this problem again today
>>
>> Looking more closely, I noticed that it started to fsck the mount
>> just before it tried to mount it. It didn't
Package: systemd
Version: 215-17+deb8u5
When my system is booting, I see the following:
systemd[1]: var.mount: Directory /var to mount over is not empty,
mounting anyway.
-- Subject: Mount point is not empty
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd
On 15/12/16 11:37, Michael Biebl wrote:
> Am 15.12.2016 um 07:31 schrieb Daniel Pocock:
>
>> Please look more closely ... 3 lines after that it says the fsck has
>> "Started" and then it gives another line about "cgroup is empty"
>>
>> Could that j
The systemd package from jessie-backports was installed, same problem
The whole system has been updated to stretch, the problem persists with
the systemd 230-7 package
As discussed in the upstream bug report, I've tested wrapping the mount
call with a script that uses strace, it shows that the m
I've posted the details below in the upstream bug report on Github as well.
This may be applicable to jessie users who have btrfs-tools v3.17-1.1
and/or manually created the /lib/udev/rules.d/99-btrfs.rules file
As a potentially workaround/solution, users can upgrade to btrfs-progs
v4.7.3-1 from
While researching the issue, I also came across this blog[1] about
ensuring btrfs scan completes before mounts
Does that already happen by default in the latest versions of systemd on
Debian?
https://blogs.gentoo.org/remi/2014/12/05/gentoo-btrfs-arrays-and-systemd-a-public-service-announcement
Package: systemd
Version: 232-8
Severity: important
The box is running stretch, updated from jessie yesterday.
When the box shuts down, it unmounts all the filesystems.
When it gets to /var there is a warning: Failed unmounting /var
I wrote a little wrapper script to put in place of /bin/umou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/01/17 07:05, Michael Biebl wrote:
> Am 14.01.2017 um 15:49 schrieb Daniel Pocock:
>
>> I've removed the file 99-btrfs.rules now and put the system in a
>> reboot loop for about 45 minutes, it rebooted about 18 time
I've tried upgrading two systems from jessie to stretch
The first one didn't experience this issue, the second one did. Both
systems had been upgraded through several versions of Debian over many
years, they had not been clean installs of jessie.
I've tried
dpkg --purge sysvinit
apt-get
I tried:
dpkg -i --force-breaks /var/cache/apt/archives/systemd_232-15_amd64.deb
and then got the upgrade proceeded successfully with:
apt-get -f install
apt-get dist-upgrade
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lis
On 16/02/17 12:42, Felipe Sateler wrote:
> On Thu, Feb 16, 2017 at 8:42 AM, Daniel Pocock wrote:
>> I tried:
>>
>> dpkg -i --force-breaks /var/cache/apt/archives/systemd_232-15_amd64.deb
> What breaks did dpkg tell you it had t
On 06/01/17 15:24, Michael Biebl wrote:
> Am 06.01.2017 um 15:12 schrieb Daniel Pocock:
>> root-fs/var/lib/systemd/random-seed
>
>
>> root-fs/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
>
>> root-fs/var/run/avahi-daemon
>> root-fs/var/run
24 matches
Mail list logo
