Tachyon booting out of a sudden after some hours

I have a pretty strange behavior: Out of a sudden my Tachyon is rebooting and it seems it does it in a strange way (docker containers shown as active since hours but somehow frozen and needed a restart).

I don’t see that much in the journal, only the following:

Welcome to Ubuntu 20.04.6 LTS (GNU/Linux 5.4.219 aarch64)

* Documentation: https://help.ubuntu.com

* Management: https://landscape.canonical.com

* Support: Ubuntu Pro | Ubuntu

This system has been minimized by removing packages and content that are

not required on a system that users do not log into.

To restore this content, you can run the 'unminimize' command.

Last login: Wed Aug 20 16:39:10 2025 from 192.168.178.121

particle@tachyon-62f23726:~$ journalctl -xe

Failed to search journal ACL: Operation not supported

-- A start job for unit UNIT has begun execution.

--

-- The job identifier is 40.

Aug 21 10:15:07 tachyon-62f23726 dbus-daemon[634450]: [session uid=5005 pid=634450] Successfully activated service 'org.gtk.vfs.Daemon'

Aug 21 10:15:07 tachyon-62f23726 systemd[634408]: Started Virtual filesystem service.

-- Subject: A start job for unit UNIT has finished successfully

-- Defined-By: systemd

-- Support: Enterprise open source support | Ubuntu

--

-- A start job for unit UNIT has finished successfully.

--

-- The job identifier is 40.

Aug 21 10:15:07 tachyon-62f23726 pulseaudio[634417]: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.

Aug 21 10:15:07 tachyon-62f23726 systemd[634408]: Started Sound Service.

-- Subject: A start job for unit UNIT has finished successfully

-- Defined-By: systemd

-- Support: Enterprise open source support | Ubuntu

--

-- A start job for unit UNIT has finished successfully.

--

-- The job identifier is 21.

Aug 21 10:15:07 tachyon-62f23726 systemd[634408]: Reached target Main User Target.

-- Subject: A start job for unit UNIT has finished successfully

-- Defined-By: systemd

-- Support: Enterprise open source support | Ubuntu

--

-- A start job for unit UNIT has finished successfully.

--

-- The job identifier is 5.

Aug 21 10:15:07 tachyon-62f23726 systemd[634408]: Startup finished in 1.301s.

-- Subject: User manager start-up is now complete

-- Defined-By: systemd

-- Support: Enterprise open source support | Ubuntu

--

-- The user manager instance for user 5005 has been started. All services queued

-- for starting have been started. Note that other services might still be starting

-- up or be started at any later time.

--

-- Startup of the manager took 1301784 microseconds.

-- Reboot --

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Reached target Paths.

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Reached target Timers.

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Starting D-Bus User Message Bus Socket.

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Listening on GnuPG network certificate management daemon.

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Listening on GnuPG cryptographic agent (ssh-agent emulation).

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Listening on GnuPG cryptographic agent and passphrase cache.

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Listening on debconf communication socket.

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Listening on Sound System.

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Listening on REST API socket for snapd user session agent.

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Listening on D-Bus User Message Bus Socket.

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Reached target Sockets.

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Reached target Basic System.

Aug 21 10:15:06 tachyon-62f23726 systemd[634408]: Starting Sound Service...

Aug 21 10:15:07 tachyon-62f23726 systemd[634408]: Started D-Bus User Message Bus.

Aug 21 10:15:07 tachyon-62f23726 dbus-daemon[634450]: [session uid=5005 pid=634450] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.1' (uid=5005 >

Aug 21 10:15:07 tachyon-62f23726 systemd[634408]: Starting Virtual filesystem service...

Aug 21 10:15:07 tachyon-62f23726 dbus-daemon[634450]: [session uid=5005 pid=634450] Successfully activated service 'org.gtk.vfs.Daemon'

Aug 21 10:15:07 tachyon-62f23726 systemd[634408]: Started Virtual filesystem service.

Aug 21 10:15:07 tachyon-62f23726 pulseaudio[634417]: module-rescue-stream is obsolete and should no longer be loaded. Please remove it from your configuration.

Aug 21 10:15:07 tachyon-62f23726 systemd[634408]: Started Sound Service.

Aug 21 10:15:07 tachyon-62f23726 systemd[634408]: Reached target Main User Target.

Aug 21 10:15:07 tachyon-62f23726 systemd[634408]: Startup finished in 1.301s.

Now its glowing green and looks like it’s not connecting to the cloud. I can use it, but it looks strange to me.

Also: I had strange effects with bluettooth and tried to reinstall bluez, but installation runs into broken pipe. I am relatively close to go through another fresh setup now, but I had the auto booting issues before as well.

I thought is might be caused by the nvme head (I removed it and installed all locally and use to nvme in a seperate case over usb now, seems to work better. Even with a supported nvme it felt sluggish using the pimoroni). But that doesn’t seem to impact the reboot issues.

Any idea what I should look at?

Just decided to switch to the headless version, thanks to preparation it hasn’t been that much effort to get eveything back running. Will track if I have the same issues again, but atm it’s looking fine and I am connected to the cloud service again as well. All fingers crossed.

I think the Tachyon may be going into idle sleep mode, not actually rebooting. The desktop version defaults to sleep mode enabled but headless does not sleep.

Might have been the case, yes (even if I deactivated sleep mode). I flashed the headless version and haven’t had that issue since a while. Only thing is, bluetooth stops working after some time and without a reboot, I cannot process a power cycle as power off fails.