system failed to start due to systemd upgrade!

[Fellfrosch]

@hendrikL
Verstehn ich Dich richtig, dass bei Dir nach der Korrektur Deiner mysteriösen fstab Zeile Du nun mit den neusten systemd Versionen problemlos booten kannst?

[reddark]

hmm, als ich vorhin mit 256~rc3-5 den mc starten wollte, wurde mir gemeldet, das mc keine tmp anlegen kann ... fiel mir nur so auf .. keine ahnung obs hilft 

[hendrikL]

@hendrikL
Verstehe ich Dich richtig, dass bei Dir nach der Korrektur Deiner mysteriösen fstab Zeile Du nun mit den neusten systemd Versionen problemlos booten kannst?

So ist es, ja!

Code Select Expand


:~$ inxi -Sa
System:
  Host: hhl-2 Kernel: 6.9.2-1-siduction-amd64 arch: x86_64 bits: 64
    compiler: gcc v: 13.2.0 clocksource: tsc avail: hpet,acpi_pm
    parameters: initrd=\3c3ddd603b3346d4ac5cc56721efbd2d\6.9.2-1-siduction-amd64\initrd.img-6.9.2-1-siduction-amd64
    root=UUID=009a5764-2ac7-41d0-9a9f-f80285bfb34e ro quiet splash
    systemd.machine_id=3c3ddd603b3346d4ac5cc56721efbd2d
  Desktop: KDE Plasma v: 5.27.11 tk: Qt v: 5.15.13 info: frameworks
    v: 5.115.0 wm: kwin_wayland vt: 2 dm: SDDM Distro: siduction 22.1.2
    Masters_of_War - kde - (202303151559) base: Debian GNU/Linux trixie/sid


[Fellfrosch]

Ich hab jetzt mal trotzdem den Hinweis von @unklarer ausprobiert
Siehe da die Kiste bootet. Ich probier nu mal mit der Zeile ein bisserl rum. Werde berichten.

[dibl]

...

Can anyone here, from the affected systems, check their fstab for this entry?
--
And, if they have it, comment it out, reboot to see if the error is gone?

YES!

I have this ancient museum item:

Code Select Expand

System:
  Host: don-presario Kernel: 6.8.10-1-siduction-amd64 arch: x86_64 bits: 64
  Desktop: LXQt v: 1.4.0 Distro: siduction 2023.1.1 giants - lxqt -
    (202309091910)
Machine:
  Type: Laptop System: Hewlett-Packard product: Presario CQ56 Notebook PC
    v: 058D100002242810010620100 serial: <superuser required>
  Mobo: Hewlett-Packard model: 1604 v: 88.17 serial: <superuser required>
    BIOS: Hewlett-Packard v: F.18 date: 04/18/2011
Battery:
  ID-1: BAT0 charge: 37.3 Wh (89.0%) condition: 41.9/41.9 Wh (100.0%)
CPU:
  Info: single core AMD V140 [UP] speed (MHz): 2300 min/max: 800/2300
Graphics:
  Device-1: AMD RS880M [Mobility Radeon HD 4225/4250] driver: radeon v: kernel
  Display: x11 server: X.Org v: 21.1.11 driver: X: loaded: radeon
    unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon
    resolution: 1366x768~60Hz
  API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 24.0.8-1 renderer: AMD
    RS880 (DRM 2.50.0 / 6.8.10-1-siduction-amd64 LLVM 17.0.6)
Network:
  Device-1: Qualcomm Atheros AR9285 Wireless Network Adapter driver: ath9k
  Device-2: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169
Drives:
  Local Storage: total: 111.79 GiB used: 9.6 GiB (8.6%)
Info:
  Memory: total: 8 GiB note: est. available: 7.52 GiB used: 2.32 GiB (30.8%)
  Processes: 199 Uptime: 5m Shell: Bash inxi: 3.3.34
 
I broke it Monday before I read this forum. Using the rw on boot line, and booting to run level 3, I have updated it through this morning. (I have 4 KDE/Plasma systems that were saved by the first post here.)
 

Code Select Expand

systemd:
  Installed: 256~rc3-5
  Candidate: 256~rc3-5
  Version table:
*** 256~rc3-5 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
 
 

Code Select Expand

# /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=7A0D-BB1C                            /boot/efi      vfat    umask=0077 0 2
UUID=4f510b39-82f2-4622-90e0-5863d0403099 /boot          ext2    defaults,noatime 0 2
UUID=3cadef2d-6a86-4d4d-b02d-2a32a875d226 /              ext4    defaults,noatime,commit=120 0 1
UUID=1fcaa3bd-cbb0-4efa-9b21-9c23e7e05a8d /home          ext4    defaults,noatime,commit=120 0 2
# tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0


I am posting from this LXQt desktop -- it boots to the GUI with the tmpfs line commented out.

[michaa7]

DE:
Ich bin verwirrt. Auch mein system hat nach dem heutigen problemlosen d-u systemd-256~rc3-5 (rc3-3 und rc-4 wurden nie intalliert!) installiert, aber *keinen*
tmpfs  /tmp  Eintrag in der /etc/fstab.

Weiß hier jemand unter welchen Bedingungen diese Zeile zugefügt wird/werden muß?


EN:
I am confused. After todays d-u I have systemd-256~rc3-5 (rc3-3 und rc-4 were never installed!) , no problem, but also no tmpfs /tmp  entry in /etc/fstab.

Anyone has a clue under which circumstances this new entry has to be created and when, as in my case, it's apparently not needed?

[hendrikL]

@Michaa7
Ich finde es auch sehr seltsam, ich habe ein funktionierendes System mit jenem fstab Eintrag und auch ohne jenem!

------

I also find it very strange, I have a working system with that fstab entry and also without it!

[Fellfrosch]

Hmmmm ich hab nu mal den tempfs Eintrag auf nofail gesetzt. damit bootet (wie erwartet) die Kiste.
Dann hab ich mir über mount anzeigen lassen, was eingehängt wurde. Kein tmpfs auf /tmp.
Dennoch hab ich ein /tmp Verzeichnis und da schreibt systemd auch rein:

Code Select Expand

/tmp$ ls -l |grep systemd
drwx------ 3 root     root     4096 29. Mai 16:54 systemd-private-3402ea97344d41d7bc30c9a45cccf11b-bluetooth.service-OPJW41
drwx------ 3 root     root     4096 29. Mai 16:54 systemd-private-3402ea97344d41d7bc30c9a45cccf11b-colord.service-BcmfKt
drwx------ 3 root     root     4096 29. Mai 16:54 systemd-private-3402ea97344d41d7bc30c9a45cccf11b-exim4.service-0PYjNp
drwx------ 3 root     root     4096 29. Mai 16:54 systemd-private-3402ea97344d41d7bc30c9a45cccf11b-haveged.service-9nagIM
drwx------ 3 root     root     4096 29. Mai 16:54 systemd-private-3402ea97344d41d7bc30c9a45cccf11b-iwd.service-OdHx7K
drwx------ 3 root     root     4096 29. Mai 16:54 systemd-private-3402ea97344d41d7bc30c9a45cccf11b-ModemManager.service-6fcrlH
drwx------ 3 root     root     4096 29. Mai 16:54 systemd-private-3402ea97344d41d7bc30c9a45cccf11b-polkit.service-NuiM3Y
drwx------ 3 root     root     4096 29. Mai 16:54 systemd-private-3402ea97344d41d7bc30c9a45cccf11b-switcheroo-control.service-Ic7Byc
drwx------ 3 root     root     4096 29. Mai 16:54 systemd-private-3402ea97344d41d7bc30c9a45cccf11b-systemd-logind.service-KpsMLg
drwx------ 3 root     root     4096 29. Mai 16:54 systemd-private-3402ea97344d41d7bc30c9a45cccf11b-systemd-timesyncd.service-NnMQgo
drwx------ 3 root     root     4096 29. Mai 16:54 systemd-private-3402ea97344d41d7bc30c9a45cccf11b-upower.service-fPyl4r


Ich fürchte das übersteigt meine Linux-Fähigkeiten/Kenntnisse

[bevo]

dank @reddark bin ich jetzt wenigstens wieder auf rc3-2.
fstab Eintrag  ist " tmpfs                                       /tmp        tmpfs   noatime,mode=1777   0 0 "

Mal sehen wie  es morgen weiter geht

Danke an alle die hier helfen!

bevo

[Fellfrosch]

@hendrikL
Kannst Du mal schauen, ob bei Dir 

Code Select Expand

/usr/lib/systemd/system/tmp.mount
vorhanden ist und was da drin steht. Bei mir steht da Folgendes:

Code Select Expand

#  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
Kann es sein, dass der Eintrag in der fstab sich mit der systemd Unit ins Gehege kommt?

[hendrikL]

Code Select Expand


:~$ 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


Zu Deiner Frage, das Ganze übersteigt langsam meine Linux-Kenntnisse.

Starte ich mit jenem Eintrag und grepe bei mount danach, erscheint

Code Select Expand


$ mount | grep tmpfs | grep /tmp
tmpfs on /tmp type tmpfs (rw,noatime,inode64)

und ohne diesen Eintrag

Code Select Expand


mount | grep tmpfs | grep /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,nr_inodes=1048576,inode64


[micspabo]

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

Code Select Expand


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 Expand


# 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 Expand


# 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.

[reddark]

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 Expand

$ 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


[Fellfrosch]

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 Expand

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.

[hendrikL]

@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.!?