1

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

« Last post by Fellfrosch on Today at 22:06:44 »

Danke für die Erklärungen. Bin ich ja froh, dass ich als blindes Huhn trotzdem in die richtige Richtung marschiert bin. 

2

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

« Last post by brutor on Today at 22:03:01 »

Confirm that the solution from Fellfrosch is working on my system.

had to implement the change ro ==> rw in the boot command to be able to boot.

Many Thanks for this help !

3

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

« Last post by reddark on Today at 22:00:47 »

so siehts jetzt bei mir aus ...

Code: [Select]

$ systemctl is-enabled tmp.mount
generated

$ systemctl is-active tmp.mount
active

$ systemctl status tmp.mount
● tmp.mount - /tmp
     Loaded: loaded (/etc/fstab; generated)
     Active: active (mounted) since Wed 2024-05-29 21:56:15 CEST; 2min 7s ago
 Invocation: 1391d16a0edc412a9ebc1d67510a78a7
      Where: /tmp
       What: tmpfs
       Docs: man:fstab(5)
             man:systemd-fstab-generator(8)
      Tasks: 0 (limit: 38092)
     Memory: 8.0K (peak: 2.5M)
        CPU: 5ms
     CGroup: /system.slice/tmp.mount

Mai 29 21:56:15 laptop1 systemd[1]: Mounting tmp.mount - /tmp...
Mai 29 21:56:15 laptop1 systemd[1]: Mounted tmp.mount - /tmp.

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

4

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

« Last post by scholle1 on Today at 21:56:57 »

Code: [Select]

touch /etc/systemd/system/tmp.mount

You have overwritten the dead link to /usr/share/.. with this.

Code: [Select]

systemctl unmask tmp.mount

and the command removes file /etc/systemd/system/tmp.mount.
Another way - same result.
Wie sagt man auf englisch: Well done. 

5

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

« Last post by micspabo on Today at 21:32:12 »

Thanks for all the hints. They were very helpful to me.

I did the same two steps as Fellfrosch, but unmasking tmp.mount showed

Code: [Select]

Unit tmp.mount does not exist, proceeding anyway.
Removed '/etc/systemd/system/tmp.mount'.

Nevertheless,- after a reboot

Code: [Select]

# systemctl is-enabled tmp.mount
  enabled

# systemctl is-active tmp.mount
  active

# systemctl status tmp.mount
  Active: active (mounted) since Wed 2024-05-29 21:08:08 CEST; 14min ago
  Siduction systemd[1]: Mounting tmp.mount - Temporary Directory /tmp...
  Siduction systemd[1]: Mounted tmp.mount - Temporary Directory /tmp.

# mount | grep tmpfs | grep /tmp
  tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=16085924k,nr_inodes=1048576,inode64)

@Fellfrosch
  masking a service will make it impossible for the system to sideload
  it, even if an unforseen part of the system still tries to start it.

6

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

« Last post by scholle1 on Today at 21:31:43 »

Can be overridden with:

Bei mir ist /etc/systemd/system/tmp.mount ein toter Link weil /usr/share/systemd/tmp.mount nicht mehr existiert.
Der Link zeigt auf /usr/share und nicht auf /usr/lib , wo tmp.mount tatsächlich ist!

Dazu:
Absichtlich frische Installation siduction.....-kde-amd64-202405152113.iso auf ext4.
In dieser Installation fehlt die "tmp"-Zeile in der fstab.
(Habe die Zeile bei vielen anderen Installationen seit Jahren in der fstab. Benutze meist Btrfs Dateisystem.)
dann DU
systemd von 256~rc2-3 zu 256~rc3-5

Code: [Select]

Vor DU
# journalctl -b | grep "/tmp"
Mai 29 18:06:05 pc2 systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
Mai 29 18:06:05 pc2 systemd[1]: Mounting tmp.mount - Temporary Directory /tmp...
Mai 29 18:06:05 pc2 systemd[1]: Mounted tmp.mount - Temporary Directory /tmp.

Nach DU
# journalctl -b | grep "/tmp"
Mai 29 19:12:54 pc2 systemd[1]: tmp.mount: Failed to open /etc/systemd/system/tmp.mount: No such file or directoryBoot fehlerfrei vor und nach DU.
Also will systemd "tmp.mount" ausführen, aber es ist keine "tmp" Zeile in fstab und nach DU die systemd-Unit "tmp.mount" nicht erreichbar, da der tote Link (s.o.) wie eine Maskierung wirkt. Sieht so aus als wissen sie bei systemd selbst nicht genau was sie da veranstalten.

Nach "rm /etc/systemd/system/tmp.mount" ist die Funktion wieder wie vor dem DU.
Aber
1. Ich hatte vor und nach dem DU kein Bootproblem.
2. Das DU hat die systemd-version 256~rc3-2 und 256~rc3-3 übersprungen. (Von rc2-3 zu rc3-5)

7

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.

8

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??

9

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?

10

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.