Posts by Guenter66

Wenn ich das wüsste. Wo sehe ich das? (und schon mal sorry für die Frage)

Quote from hyle

Quote from Guenter66

Nur der Desktop erscheint nicht mehr, sonder die Konsole.

Soll das so sein?

Nein, war vorher anders

Da stehen zwei Einträge drin:

proc /proc proc defaults 0 0
PARTUUID=7990eabb-01 /boot/firmware vfat defaults 0 2
PARTUUID=7990eabb-02 / ext4 defaults,noatime,nofail 0 1

systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

multi-user.target @2min 3.962s
└─iobroker.service @2min 3.961s
└─network.target @1min 58.684s
└─NetworkManager.service @1min 58.399s +284ms
└─dbus.service @1min 58.004s +369ms
└─basic.target @1min 57.980s
└─sockets.target @1min 57.980s
└─triggerhappy.socket @1min 57.979s
└─sysinit.target @1min 57.970s
└─systemd-timesyncd.service @1min 57.877s +92ms
└─systemd-tmpfiles-setup.service @1min 57.809s +64ms
└─local-fs.target @1min 57.788s
└─run-user-1000.mount @2min 3.966s
└─local-fs-pre.target @1min 23.502s
└─systemd-tmpfiles-setup-dev.service @1min 23.427s +75ms
└─systemd-sysusers.service @1min 23.299s +112ms
└─systemd-remount-fs.service @1min 23.197s +97ms
└─systemd-journald.socket @1min 23.165s
└─-.mount @1min 23.147s
└─-.slice @1min 23.147s

systemd-analyze time
Startup finished in 1.740s (kernel) + 2min 4.584s (userspace) = 2min 6.325s
multi-user.target reached after 2min 3.962s in userspace.

dmesg | tail -n 5
[ 124.739233] macb 1f00100000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 160.983771] warning: `iwconfig' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[ 162.543354] Bluetooth: RFCOMM TTY layer initialized
[ 162.543367] Bluetooth: RFCOMM socket layer initialized
[ 162.543375] Bluetooth: RFCOMM ver 1.11

systemctl status NetworkManager-wait-online.service
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/lib/systemd/system/NetworkManager-wait-online.service; enabled; preset: enabled)
Active: active (exited) since Tue 2025-05-06 15:11:27 CEST; 1h 13min ago
Docs: man:nm-online(1)
Process: 721 ExecStart=/usr/bin/nm-online -s -q (code=exited, status=0/SUCCESS)
Main PID: 721 (code=exited, status=0/SUCCESS)
CPU: 33ms

May 06 15:11:22 raspberrypi systemd[1]: Starting NetworkManager-wait-online.service - Network Manager Wait Online...
May 06 15:11:27 raspberrypi systemd[1]: Finished NetworkManager-wait-online.service - Network Manager Wait Online.

systemctl cat NetworkManager-wait-online.service
# /lib/systemd/system/NetworkManager-wait-online.service
[Unit]
Description=Network Manager Wait Online
Documentation=man:nm-online(1)
Requires=NetworkManager.service
After=NetworkManager.service
Before=network-online.target

[Service]
# `nm-online -s` waits until the point when NetworkManager logs
# "startup complete". That is when startup actions are settled and
# devices and profiles reached a conclusive activated or deactivated
# state. It depends on which profiles are configured to autoconnect and
# also depends on profile settings like ipv4.may-fail/ipv6.may-fail,
# which affect when a profile is considered fully activated.
# Check NetworkManager logs to find out why wait-online takes a certain
# time.

Type=oneshot
ExecStart=/usr/bin/nm-online -s -q
RemainAfterExit=yes

# Set $NM_ONLINE_TIMEOUT variable for timeout in seconds.
# Edit with `systemctl edit NetworkManager-wait-online`.
#
# Note, this timeout should commonly not be reached. If your boot
# gets delayed too long, then the solution is usually not to decrease
# the timeout, but to fix your setup so that the connected state
# gets reached earlier.
Environment=NM_ONLINE_TIMEOUT=60

[Install]
WantedBy=network-online.target

Hab das nun gemacht:

sudo service influxdb stop
sudo apt remove influxdb
sudo apt remove influxdb-client
sudo apt remove influxdb2
sudo apt autoclean && sudo apt autoremove

sudo rm -rf /var/lib/influxdb/
sudo rm -rf /var/log/influxdb/
sudo rm -rf /etc/influxdb/
sudo rm -rf ~/.influxdbv2/configs

Und influx ist weg. Der Pi5 läuft auch durch, aber braucht immer noch lange.
Zumindest die Minuten sind weg

systemd-analyze blame
34.356s dev-mmcblk0p2.device
34.041s systemd-journal-flush.service
33.879s systemd-udevd.service
5.224s NetworkManager-wait-online.service
1.021s e2scrub_reap.service
585ms user@1000.service
456ms ModemManager.service
407ms avahi-daemon.service
407ms cups.service
387ms polkit.service
378ms systemd-logind.service
369ms dbus.service
357ms rpi-eeprom-update.service
344ms influxdb.service
284ms NetworkManager.service
241ms dphys-swapfile.service
213ms bluetooth.service
209ms keyboard-setup.service
201ms rp1-test.service
175ms ssh.service
173ms systemd-udev-trigger.service
167ms glamor-test.service
162ms sshswitch.service
160ms systemd-fsck@dev-disk-by\x2dpartuuid-7990eabb\x2d01.service
132ms wpa_supplicant.service

Das kommt raus:

sudo systemctl status influxdb.service
● influxdb.service - InfluxDB is an open-source, distributed, time series database
Loaded: loaded (/lib/systemd/system/influxdb.service; enabled; preset: enabled)
Active: active (running) since Tue 2025-05-06 14:07:07 CEST; 41min ago
Docs: https://docs.influxdata.com/influxdb/
Process: 638 ExecStart=/usr/lib/influxdb/scripts/influxd-systemd-start.sh (code=exited, status=0/SUCCESS)
Main PID: 665 (influxd)
Tasks: 28 (limit: 9559)
CPU: 42.348s
CGroup: /system.slice/influxdb.service
├─ 665 /usr/bin/influxd
├─ 944 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
├─ 945 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
├─ 980 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
└─1010 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session

May 06 14:07:07 raspberrypi influxd-systemd-start.sh[665]: ts=2025-05-06T12:07:07.001613Z lvl=info msg=Listening log_id=0wLNdlFW000 service=tcp-listener transport=http a>
May 06 14:07:07 raspberrypi influxd-systemd-start.sh[638]: InfluxDB started
May 06 14:07:07 raspberrypi systemd[1]: Started influxdb.service - InfluxDB is an open-source, distributed, time series database.
May 06 14:09:27 raspberrypi influxd-systemd-start.sh[665]: ts=2025-05-06T12:09:07.031907Z lvl=error msg="Unable to write gathered points" log_id=0wLNdlFW000 service=scra>
May 06 14:09:27 raspberrypi influxd-systemd-start.sh[665]: ts=2025-05-06T12:09:17.017195Z lvl=error msg="Unable to write gathered points" log_id=0wLNdlFW000 service=scra>
May 06 14:09:27 raspberrypi influxd-systemd-start.sh[665]: ts=2025-05-06T12:09:27.015284Z lvl=error msg="Unable to write gathered points" log_id=0wLNdlFW000 service=scra>
May 06 14:37:06 raspberrypi influxd-systemd-start.sh[665]: ts=2025-05-06T12:37:06.965688Z lvl=info msg="Retention policy deletion check (start)" log_id=0wLNdlFW000 servi>
May 06 14:37:06 raspberrypi influxd-systemd-start.sh[665]: ts=2025-05-06T12:37:06.965738Z lvl=info msg="Pruning shard groups after retention check (start)" log_id=0wLNdl>
May 06 14:37:06 raspberrypi influxd-systemd-start.sh[665]: ts=2025-05-06T12:37:06.965835Z lvl=info msg="Pruning shard groups after retention check (end)" log_id=0wLNdlFW>
May 06 14:37:06 raspberrypi influxd-systemd-start.sh[665]: ts=2025-05-06T12:37:06.965850Z lvl=info msg="Retention policy deletion check (end)" log_id=0wLNdlFW000 service>
lines 1-25/25 (END)

Habe dann

sudo systemctl disable influxdb.service
Removed "/etc/systemd/system/multi-user.target.wants/influxdb.service".
Removed "/etc/systemd/system/influxd.service".

Dann reboot aber da hat sich nicht viel geändert.

systemd-analyze blame zeigt immer noch influxdb
4min 14.534s influxdb.service
1min 39.854s dev-mmcblk0p2.device
1min 15.578s e2scrub_reap.service
1min 112ms NetworkManager-wait-online.service
33.149s rtkit-daemon.service
9.251s rpc-statd-notify.service
9.181s console-setup.service
9.178s plymouth-read-write.service
1.322s cups.service
1.174s plymouth-quit-wait.service
1.174s plymouth-quit.service

Und sudo systemctl status influxdb.service zeigt wieder
● influxdb.service - InfluxDB is an open-source, distributed, time series database
Loaded: loaded (/lib/systemd/system/influxdb.service; disabled; preset: enabled)
Active: active (running) since Tue 2025-05-06 14:59:50 CEST; 3min 36s ago
Docs: https://docs.influxdata.com/influxdb/
Process: 624 ExecStart=/usr/lib/influxdb/scripts/influxd-systemd-start.sh (code=exited, status=0/SUCCESS)
Main PID: 654 (influxd)
Tasks: 27 (limit: 9559)
CPU: 10.228s

Habe versucht influxdb zu deinstallieren

gunter@raspberrypi:~ $ sudo apt remove influxdb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'influxdb' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

War also nicht installiert. Komisch.

Danach habe ich den Rat von der InfluxDB Seite angenommen, und die beiden

InfluxDB Einträge in /etc/apt/sources.list.d gelöscht.
Hat aber keine Veränderung gebracht.

Beim Neustart habe ich dann aber eine Meldung gesehen, die sehr schnell weg war:

journalctl -xb
May 06 13:59:08 raspberrypi kernel: Booting Linux on physical CPU 0x0000000000 >
May 06 13:59:08 raspberrypi kernel: Linux version 6.12.25+rpt-rpi-2712 (serge@r>
May 06 13:59:08 raspberrypi kernel: KASLR enabled
May 06 13:59:08 raspberrypi kernel: random: crng init done
May 06 13:59:08 raspberrypi kernel: Machine model: Raspberry Pi 5 Model B Rev 1>
May 06 13:59:08 raspberrypi kernel: efi: UEFI not found.
May 06 13:59:08 raspberrypi kernel: Reserved memory: created CMA memory pool at>
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: initialized node linux,cm>
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x000000003a000000..0x000>
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x0000000000000000..0x000>
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x000000003fd165c0..0x000>
May 06 13:59:08 raspberrypi kernel: NUMA: Faking a node at [mem 0x0000000000000>
May 06 13:59:08 raspberrypi kernel: NODE_DATA(0) allocated [mem 0x1ffb9c300-0x1>
May 06 13:59:08 raspberrypi kernel: Zone ranges:
May 06 13:59:08 raspberrypi kernel: DMA [mem 0x0000000000000000-0x000000>
May 06 13:59:08 raspberrypi kernel: DMA32 empty
May 06 13:59:08 raspberrypi kernel: Normal [mem 0x0000000100000000-0x000000>
May 06 13:59:08 raspberrypi kernel: Movable zone start for each node
May 06 13:59:08 raspberrypi kernel: Early memory node ranges
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000000000000-0x00000>
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000000080000-0x00000>
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000040000000-0x00000>
May 06 13:59:08 raspberrypi kernel: Initmem setup node 0 [mem 0x000000000000000>
May 06 13:59:08 raspberrypi kernel: Booting Linux on physical CPU 0x0000000000 [0x414fd0b1]
May 06 13:59:08 raspberrypi kernel: Linux version 6.12.25+rpt-rpi-2712 (serge@raspberrypi.com) (aarch64-linux-gnu-gcc-12 (Debian 12.2.0>
May 06 13:59:08 raspberrypi kernel: KASLR enabled
May 06 13:59:08 raspberrypi kernel: random: crng init done
May 06 13:59:08 raspberrypi kernel: Machine model: Raspberry Pi 5 Model B Rev 1.0
May 06 13:59:08 raspberrypi kernel: efi: UEFI not found.
May 06 13:59:08 raspberrypi kernel: Reserved memory: created CMA memory pool at 0x000000003a000000, size 64 MiB
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x000000003a000000..0x000000003dffffff (65536 KiB) map reusable linux,cma
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x0000000000000000..0x000000000007ffff (512 KiB) nomap non-reusable atf@0
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x000000003fd165c0..0x000000003fd165f7 (0 KiB) nomap non-reusable nvram@0
May 06 13:59:08 raspberrypi kernel: NUMA: Faking a node at [mem 0x0000000000000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: NODE_DATA(0) allocated [mem 0x1ffb9c300-0x1ffb9f0ff]
May 06 13:59:08 raspberrypi kernel: Zone ranges:
May 06 13:59:08 raspberrypi kernel: DMA [mem 0x0000000000000000-0x00000000ffffffff]
May 06 13:59:08 raspberrypi kernel: DMA32 empty
May 06 13:59:08 raspberrypi kernel: Normal [mem 0x0000000100000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: Movable zone start for each node
May 06 13:59:08 raspberrypi kernel: Early memory node ranges
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000000000000-0x000000000007ffff]
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000000080000-0x000000003f7fffff]
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000040000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: Initmem setup node 0 [mem 0x0000000000000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: Booting Linux on physical CPU 0x0000000000 [0x414fd0b1]
May 06 13:59:08 raspberrypi kernel: Linux version 6.12.25+rpt-rpi-2712 (serge@raspberrypi.com) (aarch64-linux-gnu-gcc-12 (Debian 12.2.0>
May 06 13:59:08 raspberrypi kernel: KASLR enabled
May 06 13:59:08 raspberrypi kernel: random: crng init done
May 06 13:59:08 raspberrypi kernel: Machine model: Raspberry Pi 5 Model B Rev 1.0
May 06 13:59:08 raspberrypi kernel: efi: UEFI not found.
May 06 13:59:08 raspberrypi kernel: Reserved memory: created CMA memory pool at 0x000000003a000000, size 64 MiB
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x000000003a000000..0x000000003dffffff (65536 KiB) map reusable linux,cma
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x0000000000000000..0x000000000007ffff (512 KiB) nomap non-reusable atf@0
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x000000003fd165c0..0x000000003fd165f7 (0 KiB) nomap non-reusable nvram@0
May 06 13:59:08 raspberrypi kernel: NUMA: Faking a node at [mem 0x0000000000000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: NODE_DATA(0) allocated [mem 0x1ffb9c300-0x1ffb9f0ff]
May 06 13:59:08 raspberrypi kernel: Zone ranges:
May 06 13:59:08 raspberrypi kernel: DMA [mem 0x0000000000000000-0x00000000ffffffff]
May 06 13:59:08 raspberrypi kernel: DMA32 empty
May 06 13:59:08 raspberrypi kernel: Normal [mem 0x0000000100000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: Movable zone start for each node
May 06 13:59:08 raspberrypi kernel: Early memory node ranges
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000000000000-0x000000000007ffff]
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000000080000-0x000000003f7fffff]
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000040000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: Initmem setup node 0 [mem 0x0000000000000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: On node 0, zone DMA: 512 pages in unavailable ranges
May 06 13:59:08 raspberrypi kernel: psci: probing for conduit method from DT.
May 06 13:59:08 raspberrypi kernel: psci: PSCIv1.1 detected in firmware.
May 06 13:59:08 raspberrypi kernel: psci: Using standard PSCI v0.2 function IDs
May 06 13:59:08 raspberrypi kernel: psci: MIGRATE_INFO_TYPE not supported.
May 06 13:59:08 raspberrypi kernel: psci: SMC Calling Convention v1.2
May 06 13:59:08 raspberrypi kernel: percpu: Embedded 15 pages/cpu s193368 r8192 d44200 u245760
May 06 13:59:08 raspberrypi kernel: pcpu-alloc: s193368 r8192 d44200 u245760 alloc=15*16384
May 06 13:59:08 raspberrypi kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
May 06 13:59:08 raspberrypi kernel: Detected PIPT I-cache on CPU0
May 06 13:59:08 raspberrypi kernel: CPU features: detected: Virtualization Host Extensions
May 06 13:59:08 raspberrypi kernel: CPU features: detected: Spectre-v4
May 06 13:59:08 raspberrypi kernel: CPU features: detected: Spectre-BHB
May 06 13:59:08 raspberrypi kernel: CPU features: kernel page table isolation forced ON by KASLR
May 06 13:59:08 raspberrypi kernel: CPU features: detected: Kernel page table isolation (KPTI)
May 06 13:59:08 raspberrypi kernel: CPU features: detected: SSBS not fully self-synchronizing
May 06 13:59:08 raspberrypi kernel: alternatives: applying boot alternatives
May 06 13:59:08 raspberrypi kernel: Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=mem>
May 06 13:59:08 raspberrypi kernel: cgroup: Disabling memory control group subsystem
May 06 13:59:08 raspberrypi kernel: mempolicy: NUMA default policy overridden to 'interleave:0'
May 06 13:59:08 raspberrypi kernel: Booting Linux on physical CPU 0x0000000000 [0x414fd0b1]
May 06 13:59:08 raspberrypi kernel: Linux version 6.12.25+rpt-rpi-2712 (serge@raspberrypi.com) (aarch64-linux-gnu-gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils >
May 06 13:59:08 raspberrypi kernel: KASLR enabled
May 06 13:59:08 raspberrypi kernel: random: crng init done
May 06 13:59:08 raspberrypi kernel: Machine model: Raspberry Pi 5 Model B Rev 1.0
May 06 13:59:08 raspberrypi kernel: efi: UEFI not found.
May 06 13:59:08 raspberrypi kernel: Reserved memory: created CMA memory pool at 0x000000003a000000, size 64 MiB
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x000000003a000000..0x000000003dffffff (65536 KiB) map reusable linux,cma
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x0000000000000000..0x000000000007ffff (512 KiB) nomap non-reusable atf@0
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x000000003fd165c0..0x000000003fd165f7 (0 KiB) nomap non-reusable nvram@0
May 06 13:59:08 raspberrypi kernel: NUMA: Faking a node at [mem 0x0000000000000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: NODE_DATA(0) allocated [mem 0x1ffb9c300-0x1ffb9f0ff]
May 06 13:59:08 raspberrypi kernel: Zone ranges:
May 06 13:59:08 raspberrypi kernel: DMA [mem 0x0000000000000000-0x00000000ffffffff]
May 06 13:59:08 raspberrypi kernel: DMA32 empty
May 06 13:59:08 raspberrypi kernel: Normal [mem 0x0000000100000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: Movable zone start for each node
May 06 13:59:08 raspberrypi kernel: Early memory node ranges
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000000000000-0x000000000007ffff]
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000000080000-0x000000003f7fffff]
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000040000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: Initmem setup node 0 [mem 0x0000000000000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: On node 0, zone DMA: 512 pages in unavailable ranges
May 06 13:59:08 raspberrypi kernel: psci: probing for conduit method from DT.
May 06 13:59:08 raspberrypi kernel: psci: PSCIv1.1 detected in firmware.
May 06 13:59:08 raspberrypi kernel: psci: Using standard PSCI v0.2 function IDs
May 06 13:59:08 raspberrypi kernel: psci: MIGRATE_INFO_TYPE not supported.
May 06 13:59:08 raspberrypi kernel: psci: SMC Calling Convention v1.2
May 06 13:59:08 raspberrypi kernel: percpu: Embedded 15 pages/cpu s193368 r8192 d44200 u245760
May 06 13:59:08 raspberrypi kernel: pcpu-alloc: s193368 r8192 d44200 u245760 alloc=15*16384
May 06 13:59:08 raspberrypi kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
May 06 13:59:08 raspberrypi kernel: Detected PIPT I-cache on CPU0
May 06 13:59:08 raspberrypi kernel: CPU features: detected: Virtualization Host Extensions
May 06 13:59:08 raspberrypi kernel: CPU features: detected: Spectre-v4
May 06 13:59:08 raspberrypi kernel: CPU features: detected: Spectre-BHB
May 06 13:59:08 raspberrypi kernel: CPU features: kernel page table isolation forced ON by KASLR
May 06 13:59:08 raspberrypi kernel: CPU features: detected: Kernel page table isolation (KPTI)
May 06 13:59:08 raspberrypi kernel: CPU features: detected: SSBS not fully self-synchronizing
May 06 13:59:08 raspberrypi kernel: alternatives: applying boot alternatives
May 06 13:59:08 raspberrypi kernel: Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave smsc95>
May 06 13:59:08 raspberrypi kernel: cgroup: Disabling memory control group subsystem
May 06 13:59:08 raspberrypi kernel: mempolicy: NUMA default policy overridden to 'interleave:0'
May 06 13:59:08 raspberrypi kernel: Unknown kernel command line parameters "splash", will be passed to user space.
May 06 13:59:08 raspberrypi kernel: Dentry cache hash table entries: 1048576 (order: 9, 8388608 bytes, linear)
May 06 13:59:08 raspberrypi kernel: Inode-cache hash table entries: 524288 (order: 8, 4194304 bytes, linear)
May 06 13:59:08 raspberrypi kernel: Fallback order for Node 0: 0
May 06 13:59:08 raspberrypi kernel: Built 1 zonelists, mobility grouping on. Total pages: 523776
May 06 13:59:08 raspberrypi kernel: Policy zone: Normal
May 06 13:59:08 raspberrypi kernel: Booting Linux on physical CPU 0x0000000000 [0x414fd0b1]
May 06 13:59:08 raspberrypi kernel: Linux version 6.12.25+rpt-rpi-2712 (serge@raspberrypi.com) (aarch64-linux-gnu-gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils >
May 06 13:59:08 raspberrypi kernel: KASLR enabled
May 06 13:59:08 raspberrypi kernel: random: crng init done
May 06 13:59:08 raspberrypi kernel: Machine model: Raspberry Pi 5 Model B Rev 1.0
May 06 13:59:08 raspberrypi kernel: efi: UEFI not found.
May 06 13:59:08 raspberrypi kernel: Reserved memory: created CMA memory pool at 0x000000003a000000, size 64 MiB
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x000000003a000000..0x000000003dffffff (65536 KiB) map reusable linux,cma
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x0000000000000000..0x000000000007ffff (512 KiB) nomap non-reusable atf@0
May 06 13:59:08 raspberrypi kernel: OF: reserved mem: 0x000000003fd165c0..0x000000003fd165f7 (0 KiB) nomap non-reusable nvram@0
May 06 13:59:08 raspberrypi kernel: NUMA: Faking a node at [mem 0x0000000000000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: NODE_DATA(0) allocated [mem 0x1ffb9c300-0x1ffb9f0ff]
May 06 13:59:08 raspberrypi kernel: Zone ranges:
May 06 13:59:08 raspberrypi kernel: DMA [mem 0x0000000000000000-0x00000000ffffffff]
May 06 13:59:08 raspberrypi kernel: DMA32 empty
May 06 13:59:08 raspberrypi kernel: Normal [mem 0x0000000100000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: Movable zone start for each node
May 06 13:59:08 raspberrypi kernel: Early memory node ranges
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000000000000-0x000000000007ffff]
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000000080000-0x000000003f7fffff]
May 06 13:59:08 raspberrypi kernel: node 0: [mem 0x0000000040000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: Initmem setup node 0 [mem 0x0000000000000000-0x00000001ffffffff]
May 06 13:59:08 raspberrypi kernel: On node 0, zone DMA: 512 pages in unavailable ranges
May 06 13:59:08 raspberrypi kernel: psci: probing for conduit method from DT.
May 06 13:59:08 raspberrypi kernel: psci: PSCIv1.1 detected in firmware.
May 06 13:59:08 raspberrypi kernel: psci: Using standard PSCI v0.2 function IDs
May 06 13:59:08 raspberrypi kernel: psci: MIGRATE_INFO_TYPE not supported.
May 06 13:59:08 raspberrypi kernel: psci: SMC Calling Convention v1.2
May 06 13:59:08 raspberrypi kernel: percpu: Embedded 15 pages/cpu s193368 r8192 d44200 u245760
May 06 13:59:08 raspberrypi kernel: pcpu-alloc: s193368 r8192 d44200 u245760 alloc=15*16384
May 06 13:59:08 raspberrypi kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
May 06 13:59:08 raspberrypi kernel: Detected PIPT I-cache on CPU0
May 06 13:59:08 raspberrypi kernel: CPU features: detected: Virtualization Host Extensions
May 06 13:59:08 raspberrypi kernel: CPU features: detected: Spectre-v4
May 06 13:59:08 raspberrypi kernel: CPU features: detected: Spectre-BHB
May 06 13:59:08 raspberrypi kernel: CPU features: kernel page table isolation forced ON by KASLR
May 06 13:59:08 raspberrypi kernel: CPU features: detected: Kernel page table isolation (KPTI)
May 06 13:59:08 raspberrypi kernel: CPU features: detected: SSBS not fully self-synchronizing
May 06 13:59:08 raspberrypi kernel: alternatives: applying boot alternatives
May 06 13:59:08 raspberrypi kernel: Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave smsc95>
May 06 13:59:08 raspberrypi kernel: cgroup: Disabling memory control group subsystem
May 06 13:59:08 raspberrypi kernel: mempolicy: NUMA default policy overridden to 'interleave:0'
May 06 13:59:08 raspberrypi kernel: Unknown kernel command line parameters "splash", will be passed to user space.
May 06 13:59:08 raspberrypi kernel: Dentry cache hash table entries: 1048576 (order: 9, 8388608 bytes, linear)
May 06 13:59:08 raspberrypi kernel: Inode-cache hash table entries: 524288 (order: 8, 4194304 bytes, linear)
May 06 13:59:08 raspberrypi kernel: Fallback order for Node 0: 0
May 06 13:59:08 raspberrypi kernel: Built 1 zonelists, mobility grouping on. Total pages: 523776
May 06 13:59:08 raspberrypi kernel: Policy zone: Normal
May 06 13:59:08 raspberrypi kernel: mem auto-init: stack:all(zero), heap alloc:off, heap free:off
May 06 13:59:08 raspberrypi kernel: software IO TLB: area num 4.
May 06 13:59:08 raspberrypi kernel: software IO TLB: mapped [mem 0x00000000fbffc000-0x00000000ffffc000] (64MB)
May 06 13:59:08 raspberrypi kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
May 06 13:59:08 raspberrypi kernel: ftrace: allocating 44908 entries in 44 pages

systemd-analyze blame zeigt aber leider immer noch den ImfluxDB Service
5min 37.757s influxdb.service
1min 47.150s NetworkManager-wait-online.service
1min 40.625s dev-mmcblk0p2.device
1min 8.179s cups.service
1min 8.044s plymouth-quit-wait.service
1min 7.594s polkit.service
1min 7.530s avahi-daemon.service
1min 7.512s dbus.service
1min 7.499s rpi-eeprom-update.service
1min 7.469s systemd-logind.service
1min 7.458s ssh.service
1min 7.125s e2scrub_reap.service
42.435s user@1000.service
33.953s dphys-swapfile.service
33.809s rp1-test.service
33.523s glamor-test.service
33.502s sshswitch.service
20.025s plymouth-quit.service
10.151s rpc-statd-notify.service
10.073s console-setup.service
10.070s plymouth-read-write.service
796ms ModemManager.service
360ms NetworkManager.service
255ms wpa_supplicant.service
230ms colord.service
164ms systemd-fsck@dev-disk-by\x2dpartuuid-7990eabb\x2d01.service
120ms keyboard-setup.service
103ms systemd-sysusers.service

systemd-analyze time:
Startup finished in 1.723s (kernel) + 2min 54.786s (userspace) = 2min 56.510s
multi-user.target reached after 11min 17.587s in userspace.

systemd-analyze blame
6min 55.811s influxdb.service
2min 54.473s dev-mmcblk0p2.device
1min 24.009s rpc-statd-notify.service
1min 23.894s plymouth-read-write.service
1min 23.884s console-setup.service
1min 15.602s NetworkManager-wait-online.service
1min 7.700s rpi-eeprom-update.service
1min 7.574s polkit.service
1min 7.506s avahi-daemon.service
1min 7.490s dbus.service
1min 7.471s ssh.service
1min 7.453s systemd-logind.service
1min 7.241s e2scrub_reap.service
33.928s rp1-test.service
33.868s dphys-swapfile.service
33.732s glamor-test.service
33.512s sshswitch.service
33.328s systemd-tmpfiles-setup.service
33.204s systemd-binfmt.service
1.099s man-db.service
786ms ModemManager.service
739ms apt-daily.service
671ms apt-daily-upgrade.service
662ms user@1000.service
380ms NetworkManager.service
283ms wpa_supplicant.service
220ms colord.service
208ms logrotate.service
187ms dpkg-db-backup.service
123ms systemd-fsck@dev-disk-by\x2dpartuuid-7990eabb\x2d01.service
116ms systemd-sysusers.service
108ms keyboard-setup.service
108ms triggerhappy.service
94ms systemd-udev-trigger.service
84ms plymouth-start.service
68ms systemd-tmpfiles-setup-dev.service
67ms plymouth-quit-wait.service
66ms plymouth-quit.service
59ms systemd-random-seed.service
52ms systemd-remount-fs.service
49ms systemd-tmpfiles-clean.service
44ms systemd-journald.service
42ms fake-hwclock.service
41ms user-runtime-dir@1000.service
38ms systemd-timesyncd.service
37ms systemd-modules-load.service
34ms systemd-sysctl.service
30ms systemd-udevd.service
29ms dev-mqueue.mount
28ms sys-kernel-debug.mount
27ms sys-kernel-tracing.mount
24ms kmod-static-nodes.service
22ms systemd-user-sessions.service

Hallo!

Mein Pi-5 macht nach Update "sudo apt update" gefolgt von "sudo apt full-upgrade" Probleme.
Er lief ohne Probleme vorher, nun braucht er ewig um zu starten. Nach dem Start läuft aber alles wieder
fast normal. Nur der Desktop erscheint nicht mehr, sonder die Konsole.

htop zeigt dann auch keine "Überlastung"

Beim starten erscheint zunächst dieses hier:

Nach Enter kommt dann

Eine Weile später ist er dann im Netz unter der alten IP und startet auch den ioBroker ganz normal.

Das ganze dauert so um die 5 - 8 Minuten.

Das Gute: er läuft ja dann ohne Probleme.

Wenn nicht schon Jemand von euch eine Lösung weiß, wie oder wo kann ich sehen, was den Bootvorgang so verlangsamt bzw. was Schuld hat an dem Verhalten.
Was für weitere Informationen braucht ihr damit ihr den Überblick habt? Und wo bekomme ich die her?

Ich sage schon einmal vielen Dank!!!

Gruß

Günter

EDIT: Hier der Inhalt des history.log:
Start-Date: 2025-05-05 11:59:51
Commandline: apt full-upgrade
Requested-By: gunter (1000)
Install: linux-headers-6.12.25+rpt-rpi-v8:arm64 (1:6.12.25-1+rpt1, automatic), wfplug-power:arm64 (0.3, automatic), wfplug-cputemp:arm64 (0.14, automatic), lib>
Upgrade: labwc:arm64 (0.7.4-1+rpt1, 0.8.1-1+rpt4), chromium-sandbox:arm64 (1:130.0.6723.116-1~deb12u1+rpt1, 1:135.0.7049.84-1~deb12u1+rpt2), libglx-mesa0:arm64>
Remove: lxinput:arm64 (0.3.5-1+rpt26), lxplug-ptbatt:arm64 (0.22)
End-Date: 2025-05-05 12:03:49