1

Upgrade Warnings / Re: system failed to start due to systemd upgrade!

« Last post by Fellfrosch on Today at 20:32:02 »

Dear diary. This is the last entry for today.   
I did

Code: [Select]

touch /etc/systemd/system/tmp.mountNow tmp.mount wasn't listed as bad anymore, but as masked. I unmasked it via

Code: [Select]

systemctl unmask tmp.mountAfter that I rebooted, with still deactivated line in fstab.
Result:
tmp is now mounted as tmpfs like it should. So for now I'm at least satisfied.

@devil or anybody else who has more knowledge then me. As I have already written, I'm no expert regarding systemd. Have You some hints for me?
Why is touching an already existing file changing things?
What does masking do? I thought masking means hiding a process. But it seems that I'm wrong with this assumption.

2

Upgrade Warnings / Re: system failed to start due to systemd upgrade!

« Last post by reddark on Today at 20:23:36 »

The changelog for systemd 256~rc3-3 says:  Make /tmp/ a tmpfs by default. Restore the upstream default and make /tmp/ a tmpfs.
Can be overridden with:
 

Code: [Select]

touch /etc/systemd/system/tmp.mountor:

Code: [Select]

systemctl mask tmp.mount
So it seems, it's not a bug, but a feature, that was badly communicated. Can someone test this on bare metal please, I can't free any hardware right now.

bedeutet tmpfs in der fstab wieder aktivieren und dann diese befehle ausführen??

3

Upgrade Warnings / Re: system failed to start due to systemd upgrade!

« Last post by Fellfrosch on Today at 20:12:21 »

There is something fishy.

I rolled back with timeshift. Disabled the fstab entry. Enabled the tmp.mount unit via

Code: [Select]

systemctl enable tmp.mount rebooted. Everything looks good. tmp is mounted as tmpfs.
Now I did the update to 256~rc3-5
Reboot. tmp isn't mounted anymore as tmpfs.

Code: [Select]

systemctl list-unit-files | grep bad
tmp.mount                                                                 bad             enabled
So what does that mean, that the unit is in a bad state. How do I get more infos on what systemd dislikes?

4

Upgrade Warnings / Re: system failed to start due to systemd upgrade!

« Last post by dibl on Today at 20:05:46 »

...
Can be overridden with:
...

LOL -- yes, AFTER YOU HAVE BOOTED YOUR BORKED SYSTEM!

Ha ha ha --- the joke is on us!   

Thanks, @devil -- mystery solved.

5

Upgrade Warnings / Re: system failed to start due to systemd upgrade!

« Last post by devil on Today at 18:54:32 »

The changelog for systemd 256~rc3-3 says:  Make /tmp/ a tmpfs by default. Restore the upstream default and make /tmp/ a tmpfs.
Can be overridden with:
 

Code: [Select]

touch /etc/systemd/system/tmp.mountor:

Code: [Select]

systemctl mask tmp.mount
So it seems, it's not a bug, but a feature, that was badly communicated. Can someone test this on bare metal please, I can't free any hardware right now.

6

Upgrade Warnings / Re: system failed to start due to systemd upgrade!

« Last post by dibl on Today at 18:54:05 »

...
Kann es sein, dass der Eintrag in der fstab sich mit der systemd Unit ins Gehege kommt?

EN: Is it possible that the tmpfs entry in fstab is in conflict with the systemd unit tmp.mount?

Apparently so.

However, here is a good running system that was fully upgraded as of last Sunday (26 MAY) and as you see, it has both the tmpfs entry in fstab, and the tmp.mount unit, with no problem booting to X.

Code: [Select]

System:
  Host: dibl-MOW Kernel: 6.8.10-1-siduction-amd64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 5.27.11 Distro: siduction 22.1.2 Masters_of_War -
    kde - (202303151559)
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X299-E GAMING v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 1401
    date: 05/21/2018
CPU:
  Info: quad core Intel Core i7-7740X [MT MCP] speed (MHz): avg: 800
    min/max: 800/4500
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nouveau v: kernel
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 24.1.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau
    resolution: 1: 1920x1200~60Hz 2: 1920x1080~60Hz
  API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 24.0.8-1 renderer: NV136
Network:
  Device-1: Intel Ethernet I219-V driver: e1000e
Drives:
  Local Storage: total: 4.1 TiB used: 748.76 GiB (17.8%)
Info:
  Memory: total: 32 GiB available: 31.27 GiB used: 1.95 GiB (6.2%)
  Processes: 276 Uptime: 3h 25m Shell: Bash inxi: 3.3.34

don@dibl-MOW:~$ sudo apt policy systemd
systemd:
  Installed: 256~rc3-2
  Candidate: 256~rc3-5
  Version table:
     256~rc3-5 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
 *** 256~rc3-2 100
        100 /var/lib/dpkg/status

don@dibl-MOW:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=F765-9806                            /boot/efi      vfat    umask=0077                                     0 2
UUID=f1bd917e-47c9-43dd-bed8-b9ccdc518968 /boot          ext2    defaults,noatime                               0 2
UUID=9cdc98b4-ebed-478d-9d14-0ebfb4613543 /              ext4    defaults,noatime,errors=remount-ro,commit=120  0 1
UUID=b7eb0948-83b6-4a2a-8724-12e258a0c5fb /home              ext4        defaults,relatime,errors=remount-ro,commit=120 0 2
UUID=44ee6177-c0e3-47e7-aee7-6c4a74c63c4d /mnt/DATA          btrfs       noatime,compress=lzo,space_cache=v2            0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777                     0 0

don@dibl-MOW:~$ cat /usr/lib/systemd/system/tmp.mount
#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Temporary Directory /tmp
Documentation=https://systemd.io/TEMPORARY_DIRECTORIES
Documentation=man:file-hierarchy(7)
Documentation=https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
ConditionPathIsSymbolicLink=!/tmp
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target
After=swap.target

[Mount]
What=tmpfs
Where=/tmp
Type=tmpfs
Options=mode=1777,strictatime,nosuid,nodev,size=50%%,nr_inodes=1m

[Install]
WantedBy=local-fs.target
I have 3 more systems configured like this one, a desktop and 2 laptops, and they all run error-free.

So, this "conflict" is a new feature of the updated systemd, I guess.

7

Upgrade Warnings / Re: system failed to start due to systemd upgrade!

« Last post by hendrikL on Today at 18:47:46 »

@Fellfrosch
existiert  /usr/lib/systemd/system/tmp.mount?
Klar, wer lesen kann, ist im Vorteil!

Vielleicht systemd neu installieren, mit allem Drum und Dran, apt install --reinstall systemd systemd-<foo> usw.!?

8

Upgrade Warnings / Re: system failed to start due to systemd upgrade!

« Last post by Fellfrosch on Today at 18:41:59 »

Unfortunately I think just commenting out the line in fstab means /tmp is not mounted as a tmpfs anymore, but is a simple directory under root.

@hendrikL showed, that it should be listed with the mount command. On my system it isn't listed. The systemd unit isn't active on my system as well and I'm on top not able to activate it:

Code: [Select]

systemctl enable tmp.mount
Failed to enable unit: Unit tmp.mount does not exist
But systemd was always and will probably stay for some time longer an enigma to me.

I fear I'm helpless on this.

9

Upgrade Warnings / Re: system failed to start due to systemd upgrade!

« Last post by reddark on Today at 18:37:18 »

so, hab tmpfs auskommentiert und ein neues upgrade drüber laufen lassen.
computer läuft 

die datei /usr/lib/systemd/system/tmp.mount war vorher nicht vorhanden, nun ist sie es:

Code: [Select]

$ cat /usr/lib/systemd/system/tmp.mount
#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Temporary Directory /tmp
Documentation=https://systemd.io/TEMPORARY_DIRECTORIES
Documentation=man:file-hierarchy(7)
Documentation=https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
ConditionPathIsSymbolicLink=!/tmp
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target
After=swap.target

[Mount]
What=tmpfs
Where=/tmp
Type=tmpfs
Options=mode=1777,strictatime,nosuid,nodev,size=50%%,nr_inodes=1m


10

Upgrade Warnings / Re: system failed to start due to systemd upgrade!

« Last post by micspabo on Today at 18:12:36 »

First of all,- I just had to comment out the line from /etc/fstab

Code: [Select]

tmpfs   /tmp   tmpfs   defaults,noatime,mode=1777   0   0
and I am able to boot normally with ro again. There is no downgrade of systemd neccessary for me.

Code: [Select]

# cat file /usr/lib/systemd/system/tmp.mount

#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Temporary Directory /tmp
Documentation=https://systemd.io/TEMPORARY_DIRECTORIES
Documentation=man:file-hierarchy(7)
Documentation=https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
ConditionPathIsSymbolicLink=!/tmp
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target
After=swap.target

[Mount]
What=tmpfs
Where=/tmp
Type=tmpfs
Options=mode=1777,strictatime,nosuid,nodev,size=50%%,nr_inodes=1m


Code: [Select]

# ls -ld /tmp
drwxrwxrwt 1 root root 2,3K 29. Mai 17:59 /tmp

  I am up and running again. Hope someone is able to explain what's the culprit in this case.