41

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

« Last post by michaa7 on Yesterday at 16:45:34 »

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?

42

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

« Last post by dibl on Yesterday at 16:45:11 »

...

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]

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]

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]

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

43

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

« Last post by Fellfrosch on Yesterday at 16:43:13 »

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.

44

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

« Last post by hendrikL on Yesterday at 16:33:51 »

@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]

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


45

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

« Last post by reddark on Yesterday at 16:29:32 »

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 

46

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

« Last post by Fellfrosch on Yesterday at 16:27:35 »

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

47

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

« Last post by towo on Yesterday at 16:22:35 »

Und auch eine Neuinstallation mit dem Testiso von heute hat diesen fstab-Eintrag und bootet problemlos.

And also a new installation with the testiso from today has this fstab entry and boots without problems.

48

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

« Last post by hendrikL on Yesterday at 16:19:32 »

Code: [Select]

~$ 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=385C-E2B7                              /boot/efi   vfat    umask=0077          0 2
UUID=009a5764-2ac7-41d0-9a9f-f80285bfb34e   /           ext4    noatime             0 1
tmpfs                                       /tmp        tmpfs   noatime,mode=1777   0 0
UUID=6134a4d8-1a1b-46e2-99da-4263c146ef57   /ablage     ext4    noatime             0 1
UUID=41a8bbb8-076c-49bf-9e0e-e05102319636   /speicher   ext4    defaults,noatime    0 1

hhl@hhl-2:~$ LANG=C apt policy systemd
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
        500 https://incoming.debian.org/debian-buildd buildd-unstable/main amd64 Packages
        100 /var/lib/dpkg/status
     256~rc3-2 500
        500 https://deb.debian.org/debian testing/main amd64 Packages
No problem so far!

49

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

« Last post by hendrikL on Yesterday at 16:17:02 »

Und noch einmal. wenn ihr wieder ein funktionierendes system habt, schaut, wo der Fehler liegen kann.
Z. B. falscher fstab Eintrag, oder hat sich etwas an der cmd-line, boot Zeile geändert, schaut nach, denn ansonsten werdet ihr ewig diesen Fehler mit Euch schleppen, dmesg, journalctl, irgendwelche Fehlermeldung, andere Auffälligkeiten.
systemd reagiert da nur auf etwas!

----------------------------------------------

And once again, if you have a functioning system again, see where the error may lie.
For example, wrong fstab entry, or has something changed in the cmd-line, boot line, check, because otherwise you will carry this error with you forever, dmesg, journalctl, any error message, other anomalies.
systemd only reacts to something!

50

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

« Last post by unklarer on Yesterday at 16:13:05 »

Kann jemand von den betroffenen Systemen hier seine fstab auf diesen Eintrag überprüfen?

Code: [Select]

tmpfs                                       /tmp        tmpfs   noatime,mode=1777   0 0

Und, wenn sie ihn haben, ihn auskommentieren, neu starten, um zu sehen, ob der Fehler verschwunden ist?

Ich habe keinen solchen Eintrag in meinen fstabs.

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

I don't have such an entry in my fstab's.