Raspi os Bulleye se cuelga al rato

[jomaiz]

¿Sabéis si hay problemas con Bulleye? Tengo una RPI 4 como servidor de archivos y al rato de encenderla, esté ociosa o no, se queda frita, no responde. Lo curioso es que el led de ethernet está parpadeando sin parar.

¿Cómo puedo instalar la versión anterior? no la encuentro en su web.

[egrueda]

¿Sabéis si hay problemas con Bulleye?

No, no hay ningún problema con bullseye.
Tendrás que investigar qué le está pasando exactamente a tu instalación: qué se muestra por pantalla, que dice el syslog, etc
¿No tendría más sentido pensar que le pasa algo a tu raspi, en lugar de pensar que el sistema operativo esté mal?

¿Cómo puedo instalar la versión anterior? no la encuentro en su web.

No creo que esa sea la solución, de hecho es exactamente lo contrario.
Aun así tienes aquí todas las versiones:
https://downloads.raspberrypi.org/raspbian/images/

[futbolin]

A mi Bulleye no ha hecho más que darme problemas, estoy trabajando con la última versión que tenía '2021-05-07-raspios-buster-armhf-lite'

[egrueda]

A mi Bulleye no ha hecho más que darme problemas

¿Podrías ser más explícito? ¿qué problemas te ha dado exactamente y con qué?

[futbolin]

En cuanto pueda vuelvo a hacer pruebas con la versión, que no lo recuerdo, pero probé varias veces a utilizarla y siempre me daba algún problema. Ayer por ejemplo al encenderla llegaba un punto en que dejaba de tener imagen en la pantalla, pensé que sería el cable o la alimentación y probe a cambiarlos y nada.. al final cambié por la imagen que tenía y me funcionó a la primera.

[jomaiz]

Me encanta la informática, es escribir en un foro pidiendo ayuda y no volver a pasar

Si vuelve a ocurrir intentaré recopilar información para pediros socorro.

[egrueda]

Me encanta la informática, es escribir en un foro pidiendo ayuda y no volver a pasar

Es un hecho científico demostrado

[jomaiz]

Ha vuelto a ocurrir por suerte o por desgracia. He estado revisando el syslog y estas son las líneas que me llaman la atención:

- Mensajes puntuales de baja tensión, ¿cómo puede ser si tengo el cargador original de la RPI 4?
raspberrypi kernel: [475136.384395] Under-voltage detected! (0x00050005)
raspberrypi kernel: [475142.624510] Voltage normalised (0x00000000)

- Otros errores que no sé si hay que tener en cuenta:
raspberrypi kernel: [477507.627036] rpi_firmware_get_throttled: 2 callbacks suppressed
raspberrypi udisksd[459]: Failed to load the 'mdraid' libblockdev plugin
raspberrypi udisksd[459]: Failed to load the 'crypto' libblockdev plugin
raspberrypi lightdm[538]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
raspberrypi pipewire[730]: could not set nice-level to -11: Permission denied
raspberrypi pipewire[730]: could not make thread realtime: Permission denied
raspberrypi dhcpcd[423]: eth0: carrier acquired
raspberrypi dhcpcd[423]: unknown option: raspberry
raspberrypi systemd[781]: gpgconf: error al ejecutar '/usr/lib/gnupg/scdaemon': probablemente no está instalado

[egrueda]

Las líneas de "Under-voltage detected" son importantes, esos picos pueden generar funcionamientos imprevistos que producen efectos en cadena.
Mira a ver si ha sido algo puntual o si se repite: "grep -i voltage /var/log/syslog"

Respecto a los otros fallos:
- lso fallos de pipewire y gpgconf no deberían afectar a la estabilidad del equipo
- dhcpcd dice que hay un parámetro incorrecto en la configuración. Extrae más información con "systemctl status dhcpcd"

Mi recomendación:
- revisa el tema de la alimentación a ver si es recurrente
- instala un sistema de monitorización para ver gráficos cuando deja de responder, es decir, para poder ver qué hacía la máquina en ese momento, cpu y memoria sobre todo. Para eso tienes rpi-monitor (apartado statistics) o Monitorix

[jomaiz]

Las líneas de "Under-voltage detected" son importantes, esos picos pueden generar funcionamientos imprevistos que producen efectos en cadena.
Mira a ver si ha sido algo puntual o si se repite: "grep -i voltage /var/log/syslog"

Parece que no es puntual, las siguientes líneas son sólo de hoy y de ayer.

Dec 1 00:02:35 raspberrypi kernel: [473066.747418] Under-voltage detected! (0x00050005)
Dec 1 00:02:42 raspberrypi kernel: [473072.987523] Voltage normalised (0x00000000)
Dec 1 00:37:05 raspberrypi kernel: [475136.384395] Under-voltage detected! (0x00050005)
Dec 1 00:37:11 raspberrypi kernel: [475142.624510] Voltage normalised (0x00000000)
Dec 1 00:37:30 raspberrypi kernel: [475161.344859] Under-voltage detected! (0x00050005)
Dec 1 00:37:34 raspberrypi kernel: [475165.504924] Voltage normalised (0x00000000)
Dec 1 00:37:49 raspberrypi kernel: [475180.065188] Under-voltage detected! (0x00050005)
Dec 1 00:37:53 raspberrypi kernel: [475184.225327] Voltage normalised (0x00000000)
Dec 1 01:16:30 raspberrypi kernel: [477501.386928] Under-voltage detected! (0x00050005)
Dec 1 01:16:36 raspberrypi kernel: [477507.627045] Voltage normalised (0x00000000)
Dec 1 01:46:39 raspberrypi kernel: [479311.019427] Under-voltage detected! (0x00050005)
Dec 1 01:46:44 raspberrypi kernel: [479315.179491] Voltage normalised (0x00000000)
Dec 1 01:56:01 raspberrypi kernel: [479872.629147] Under-voltage detected! (0x00050005)
Dec 1 01:56:07 raspberrypi kernel: [479878.869213] Voltage normalised (0x00000000)
Dec 1 01:56:49 raspberrypi kernel: [479920.469940] Under-voltage detected! (0x00050005)
Dec 1 01:56:53 raspberrypi kernel: [479924.630055] Voltage normalised (0x00000000)
Dec 1 01:59:15 raspberrypi kernel: [480066.072557] Under-voltage detected! (0x00050005)
Dec 1 01:59:25 raspberrypi kernel: [480076.472682] Voltage normalised (0x00000000)
Dec 1 05:43:03 raspberrypi kernel: [493494.792145] Under-voltage detected! (0x00050005)
Dec 1 05:43:07 raspberrypi kernel: [493498.952210] Voltage normalised (0x00000000)
Dec 1 05:45:12 raspberrypi kernel: [493623.754436] Under-voltage detected! (0x00050005)
Dec 1 05:45:20 raspberrypi kernel: [493632.074558] Voltage normalised (0x00000000)
Dec 1 07:51:38 raspberrypi kernel: [501209.649904] Under-voltage detected! (0x00050005)
Dec 1 07:51:44 raspberrypi kernel: [501215.890009] Voltage normalised (0x00000000)
Dec 1 15:28:49 raspberrypi kernel: [528641.179488] Under-voltage detected! (0x00050005)
Dec 1 15:28:55 raspberrypi kernel: [528647.419651] Voltage normalised (0x00000000)
Dec 1 15:40:55 raspberrypi kernel: [529367.112392] Under-voltage detected! (0x00050005)
Dec 1 15:40:59 raspberrypi kernel: [529371.272451] Voltage normalised (0x00000000)
Dec 1 16:00:55 raspberrypi kernel: [530567.293792] Under-voltage detected! (0x00050005)
Dec 1 16:00:59 raspberrypi kernel: [530571.453867] Voltage normalised (0x00000000)
Dec 1 16:19:30 raspberrypi kernel: [531682.193644] Under-voltage detected! (0x00050005)
Dec 1 16:19:38 raspberrypi kernel: [531690.513760] Voltage normalised (0x00000000)
Dec 1 16:29:47 raspberrypi kernel: [532299.964608] Under-voltage detected! (0x00050005)
Dec 1 16:29:58 raspberrypi kernel: [532310.364781] Voltage normalised (0x00000000)
Dec 1 21:19:19 raspberrypi kernel: [ 717.356004] Under-voltage detected! (0x00050005)
Dec 1 21:19:23 raspberrypi kernel: [ 721.516003] Voltage normalised (0x00000000)
Dec 1 21:30:41 raspberrypi kernel: [ 1399.603384] Under-voltage detected! (0x00050005)
Dec 1 21:30:45 raspberrypi kernel: [ 1403.763403] Voltage normalised (0x00000000)

por aquí sé que la RPI estuvo muerta

Dec 2 10:01:55 raspberrypi kernel: [ 2364.834331] Under-voltage detected! (0x00050005)
Dec 2 10:02:02 raspberrypi kernel: [ 2371.072438] Voltage normalised (0x00000000)
Dec 2 10:29:55 raspberrypi kernel: [ 638.882357] Under-voltage detected! (0x00050005)
Dec 2 10:30:01 raspberrypi kernel: [ 645.132193] Voltage normalised (0x00000000)

¿Me compro otro cargador original?

[egrueda]

¿Qué tienes conectado a la raspi para que teng esos picos? discos externos? hats?

[jomaiz]

¿Qué tienes conectado a la raspi para que teng esos picos? discos externos? hats?

tengo un dock con 2 discos duros de 5400. El dock tiene su propia alimentación y lo normal es que el sistema esté siempre ocioso.

¿Ves algo incorrecto?

[egrueda]

No, no veo nada raro. Y entiendo que antes tenías el mismo hardware y no se colgaba...
¿Estás usando el cargador "oficial" de 3A?

Por otro lado, ¿puedes compartir el syslog donde esté el último cuelgue? Para ver las líneas antes de la incidencia, a ver qué está diciendo

[jomaiz]

entiendo que antes tenías el mismo hardware y no se colgaba...

Exactamente el mismo hardware, tan "sólo" cambia buster por bulleye.

¿Estás usando el cargador "oficial" de 3A?

Sí, me compré el cargador oficial porque era consciente de los problemas que dan los otros.

¿puedes compartir el syslog donde esté el último cuelgue?

Se acaba de pillar y por mi parte estaba completamente ociosa. Ha debido fallar entre las 10:37:20 y las 11:44:49

Dec 2 10:37:10 raspberrypi systemd[1]: Mounted /discos/datos.
Dec 2 10:37:11 raspberrypi dhcpcd[409]: eth0: using static address 192.168.1.2/24
Dec 2 10:37:11 raspberrypi avahi-daemon[331]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Dec 2 10:37:11 raspberrypi dhcpcd[409]: eth0: adding route to 192.168.1.0/24
Dec 2 10:37:11 raspberrypi avahi-daemon[331]: New relevant interface eth0.IPv4 for mDNS.
Dec 2 10:37:11 raspberrypi dhcpcd[409]: eth0: adding default route via 192.168.1.1
Dec 2 10:37:11 raspberrypi avahi-daemon[331]: Registering new address record for 192.168.1.2 on eth0.IPv4.
Dec 2 10:37:11 raspberrypi dbus-daemon[782]: [session uid=1000 pid=782] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.11' (uid=1000 pid=891 comm="pcmanfm --desktop --profile LXDE-pi ")
Dec 2 10:37:11 raspberrypi systemd[759]: Starting Virtual filesystem service - disk device monitor...
Dec 2 10:37:11 raspberrypi dbus-daemon[782]: [session uid=1000 pid=782] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Dec 2 10:37:11 raspberrypi systemd[759]: Started Virtual filesystem service - disk device monitor.
Dec 2 10:37:11 raspberrypi dbus-daemon[782]: [session uid=1000 pid=782] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.11' (uid=1000 pid=891 comm="pcmanfm --desktop --profile LXDE-pi ")
Dec 2 10:37:11 raspberrypi systemd[759]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Dec 2 10:37:11 raspberrypi dbus-daemon[782]: [session uid=1000 pid=782] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Dec 2 10:37:11 raspberrypi systemd[759]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Dec 2 10:37:11 raspberrypi dbus-daemon[782]: [session uid=1000 pid=782] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.11' (uid=1000 pid=891 comm="pcmanfm --desktop --profile LXDE-pi ")
Dec 2 10:37:11 raspberrypi systemd[759]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Dec 2 10:37:11 raspberrypi dbus-daemon[782]: [session uid=1000 pid=782] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Dec 2 10:37:11 raspberrypi systemd[759]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Dec 2 10:37:11 raspberrypi dbus-daemon[782]: [session uid=1000 pid=782] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.11' (uid=1000 pid=891 comm="pcmanfm --desktop --profile LXDE-pi ")
Dec 2 10:37:11 raspberrypi systemd[759]: Starting Virtual filesystem service - digital camera monitor...
Dec 2 10:37:11 raspberrypi dbus-daemon[782]: [session uid=1000 pid=782] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Dec 2 10:37:11 raspberrypi systemd[759]: Started Virtual filesystem service - digital camera monitor.
Dec 2 10:37:11 raspberrypi dbus-daemon[782]: [session uid=1000 pid=782] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.11' (uid=1000 pid=891 comm="pcmanfm --desktop --profile LXDE-pi ")
Dec 2 10:37:11 raspberrypi systemd[759]: Starting Virtual filesystem service - Apple File Conduit monitor...
Dec 2 10:37:11 raspberrypi dbus-daemon[782]: [session uid=1000 pid=782] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Dec 2 10:37:11 raspberrypi systemd[759]: Started Virtual filesystem service - Apple File Conduit monitor.
Dec 2 10:37:12 raspberrypi dbus-daemon[335]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.94' (uid=1000 pid=887 comm="lxpanel --profile LXDE-pi ")
Dec 2 10:37:12 raspberrypi systemd[1]: Starting PackageKit Daemon...
Dec 2 10:37:12 raspberrypi PackageKit: daemon start
Dec 2 10:37:13 raspberrypi dbus-daemon[335]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Dec 2 10:37:13 raspberrypi systemd[1]: Started PackageKit Daemon.
Dec 2 10:37:14 raspberrypi systemd[1]: Started Samba NMB Daemon.
Dec 2 10:37:14 raspberrypi systemd[1]: Starting Samba SMB Daemon...
Dec 2 10:37:14 raspberrypi systemd[1]: Started Samba SMB Daemon.
Dec 2 10:37:14 raspberrypi systemd[1]: Reached target Multi-User System.
Dec 2 10:37:14 raspberrypi systemd[1]: Reached target Graphical Interface.
Dec 2 10:37:14 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes...
Dec 2 10:37:14 raspberrypi systemd[1]: systemd-rfkill.service: Succeeded.
Dec 2 10:37:14 raspberrypi systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Dec 2 10:37:14 raspberrypi systemd[1]: Finished Update UTMP about System Runlevel Changes.
Dec 2 10:37:15 raspberrypi PackageKit: refresh-cache transaction /25_aecddcbb from uid 1000 finished with success after 2360ms
Dec 2 10:37:19 raspberrypi dhcpcd[409]: eth0: no IPv6 Routers available
Dec 2 10:37:20 raspberrypi PackageKit: get-updates transaction /26_adedaadd from uid 1000 finished with success after 4870ms
Dec 2 11:44:49 raspberrypi systemd-timesyncd[287]: Initial synchronization to time server 194.58.203.148:123 (2.debian.pool.ntp.org).
Dec 2 11:44:49 raspberrypi systemd[1]: Starting Clean php session files...
Dec 2 11:44:50 raspberrypi systemd[1]: phpsessionclean.service: Succeeded.
Dec 2 11:44:50 raspberrypi systemd[1]: Finished Clean php session files.
Dec 2 11:44:56 raspberrypi CRON[1360]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Dec 2 11:44:56 raspberrypi systemd[1]: Started Session 6 of user pi.
Dec 2 11:44:58 raspberrypi systemd[1]: systemd-fsckd.service: Succeeded.
Dec 2 11:44:58 raspberrypi systemd[1]: systemd-hostnamed.service: Succeeded.
Dec 2 11:45:01 raspberrypi CRON[1387]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Dec 2 11:45:18 raspberrypi systemd[1]: Started Session 9 of user pi.
Dec 2 11:45:37 raspberrypi systemd[1]: Started Session 10 of user pi.
Dec 2 11:45:43 raspberrypi systemd[1]: dev-sdb1.device: Job dev-sdb1.device/start timed out.
Dec 2 11:45:43 raspberrypi systemd[1]: Timed out waiting for device /dev/sdb1.
Dec 2 11:45:43 raspberrypi systemd[1]: Dependency failed for /discos/auxiliar.
Dec 2 11:45:43 raspberrypi systemd[1]: discos-auxiliar.mount: Job discos-auxiliar.mount/start failed with result 'dependency'.
Dec 2 11:45:43 raspberrypi systemd[1]: Dependency failed for File System Check on /dev/sdb1.
Dec 2 11:45:43 raspberrypi systemd[1]: systemd-fsck@dev-sdb1.service: Job systemd-fsck@dev-sdb1.service/start failed with result 'dependency'.
Dec 2 11:45:43 raspberrypi systemd[1]: Startup finished in 2.418s (kernel) + 1min 31.334s (userspace) = 1min 33.752s.
Dec 2 11:45:43 raspberrypi systemd[1]: dev-sdb1.device: Job dev-sdb1.device/start failed with result 'timeout'.

[egrueda]

Se acaba de pillar y por mi parte estaba completamente ociosa. Ha debido fallar entre las 10:37:20 y las 11:44:49

¿Pero vuelve a la vida o has tenido que reiniciar?

[jomaiz]

Se acaba de pillar y por mi parte estaba completamente ociosa. Ha debido fallar entre las 10:37:20 y las 11:44:49

¿Pero vuelve a la vida o has tenido que reiniciar?

Me toca reiniciar. No responde ni por ssh, VNC ni funciona el ratón ni el teclado.

[jomaiz]

Otro ejemplo de cuelgue

Dec 2 12:17:53 raspberrypi avahi-daemon[342]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Dec 2 12:17:53 raspberrypi avahi-daemon[342]: New relevant interface eth0.IPv4 for mDNS.
Dec 2 12:17:53 raspberrypi avahi-daemon[342]: Registering new address record for 192.168.1.2 on eth0.IPv4.
Dec 2 12:17:53 raspberrypi dhcpcd[426]: eth0: adding route to 192.168.1.0/24
Dec 2 12:17:53 raspberrypi dhcpcd[426]: eth0: adding default route via 192.168.1.1
Dec 2 12:17:54 raspberrypi dbus-daemon[773]: [session uid=1000 pid=773] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.10' (uid=1000 pid=921 comm="pcmanfm --desktop --profile LXDE-pi ")
Dec 2 12:17:54 raspberrypi systemd[750]: Starting Virtual filesystem service - disk device monitor...
Dec 2 12:17:54 raspberrypi dbus-daemon[773]: [session uid=1000 pid=773] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Dec 2 12:17:54 raspberrypi systemd[750]: Started Virtual filesystem service - disk device monitor.
Dec 2 12:17:54 raspberrypi dbus-daemon[773]: [session uid=1000 pid=773] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.10' (uid=1000 pid=921 comm="pcmanfm --desktop --profile LXDE-pi ")
Dec 2 12:17:54 raspberrypi systemd[750]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Dec 2 12:17:54 raspberrypi dbus-daemon[773]: [session uid=1000 pid=773] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Dec 2 12:17:54 raspberrypi systemd[750]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Dec 2 12:17:54 raspberrypi dbus-daemon[773]: [session uid=1000 pid=773] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.10' (uid=1000 pid=921 comm="pcmanfm --desktop --profile LXDE-pi ")
Dec 2 12:17:54 raspberrypi systemd[750]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Dec 2 12:17:54 raspberrypi dbus-daemon[773]: [session uid=1000 pid=773] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Dec 2 12:17:54 raspberrypi systemd[750]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Dec 2 12:17:54 raspberrypi dbus-daemon[773]: [session uid=1000 pid=773] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.10' (uid=1000 pid=921 comm="pcmanfm --desktop --profile LXDE-pi ")
Dec 2 12:17:54 raspberrypi systemd[750]: Starting Virtual filesystem service - digital camera monitor...
Dec 2 12:17:54 raspberrypi dbus-daemon[773]: [session uid=1000 pid=773] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Dec 2 12:17:54 raspberrypi systemd[750]: Started Virtual filesystem service - digital camera monitor.
Dec 2 12:17:54 raspberrypi dbus-daemon[773]: [session uid=1000 pid=773] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.10' (uid=1000 pid=921 comm="pcmanfm --desktop --profile LXDE-pi ")
Dec 2 12:17:54 raspberrypi systemd[750]: Starting Virtual filesystem service - Apple File Conduit monitor...
Dec 2 12:17:54 raspberrypi dbus-daemon[773]: [session uid=1000 pid=773] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Dec 2 12:17:54 raspberrypi systemd[750]: Started Virtual filesystem service - Apple File Conduit monitor.
Dec 2 12:17:55 raspberrypi dbus-daemon[344]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.96' (uid=1000 pid=920 comm="lxpanel --profile LXDE-pi ")
Dec 2 12:17:55 raspberrypi systemd[1]: Starting PackageKit Daemon...
Dec 2 12:17:55 raspberrypi PackageKit: daemon start
Dec 2 12:17:55 raspberrypi dbus-daemon[344]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Dec 2 12:17:55 raspberrypi systemd[1]: Started PackageKit Daemon.
Dec 2 12:17:56 raspberrypi systemd[1]: Started Samba NMB Daemon.
Dec 2 12:17:56 raspberrypi systemd[1]: Starting Samba SMB Daemon...
Dec 2 12:17:56 raspberrypi systemd[1]: systemd-rfkill.service: Succeeded.
Dec 2 12:17:57 raspberrypi systemd[1]: Started Samba SMB Daemon.
Dec 2 12:17:57 raspberrypi systemd[1]: Reached target Multi-User System.
Dec 2 12:17:57 raspberrypi systemd[1]: Reached target Graphical Interface.
Dec 2 12:17:57 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes...
Dec 2 12:17:57 raspberrypi systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Dec 2 12:17:57 raspberrypi systemd[1]: Finished Update UTMP about System Runlevel Changes.
Dec 2 12:17:58 raspberrypi packagekitd[1165]: Release file for http://archive.raspberrypi.org/debian/d ... /InRelease is not valid yet (invalid for another 37min 49s). Updates for this repository will not be applied.
Dec 2 12:17:58 raspberrypi PackageKit: refresh-cache transaction /36_bdbeabed from uid 1000 finished with failed after 2458ms
Dec 2 12:18:01 raspberrypi CRON[1296]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Dec 2 12:18:02 raspberrypi dhcpcd[426]: eth0: no IPv6 Routers available
Dec 2 12:18:13 raspberrypi systemd[1]: systemd-fsckd.service: Succeeded.

aquí se queda frita unas cuantas horas hasta que me doy cuenta

Dec 2 21:12:18 raspberrypi systemd-timesyncd[314]: Initial synchronization to time server 217.243.166.213:123 (2.debian.pool.ntp.org).
Dec 2 21:12:18 raspberrypi systemd[1]: Starting Clean php session files...
Dec 2 21:12:19 raspberrypi systemd[1]: phpsessionclean.service: Succeeded.
Dec 2 21:12:19 raspberrypi systemd[1]: Finished Clean php session files.
Dec 2 21:12:20 raspberrypi CRON[1369]: (pi) CMD (~/duckdns/duck.sh >/dev/null 2>&1)
Dec 2 21:12:27 raspberrypi systemd[1]: systemd-hostnamed.service: Succeeded.
Dec 2 21:12:34 raspberrypi systemd[1]: Started Session 9 of user pi.

[jomaiz]

Finalmente compre otro cargador y todo resuelto. Muchas gracias por vuestro tiempo.