Hi, I’m new to TrueNas and got my server (repurposed an old PC) up and running in October last year. Wanted to host my own photos and stream content. I’m currently on version 25.10.6.
I’m not running any virtual machines or containers. All apps are from TrueNas app repo.
After removing the dataset, I proceeded to “Choose Pool” > “nameofpool” > Clicked choose and received this notification when it reached 60%
Error Name: EINVAL
Error Code: 22
Reason: [err -110]: b"Failed to activate service ‘org.freedesktop.systemd1’: timed out (service_start_timeout=25000ms)"
Error Class: DBusTimedOutError
(The log is pretty long)
Currently stuck and not sure what to do. Tried several times to “Choose pool” but to no avail.
that dbus timeout on org.freedesktop.systemd1 usually means middlewared is wedged after the force delete.
ssh in and check:
sudo systemctl status middlewared docker
sudo journalctl -u middlewared -b --no-pager | tail -100
then restart the stuck bits:
sudo systemctl restart middlewared
sudo systemctl restart docker
wait a minute for the ui to come back, then try Choose Pool again.
if systemctl list-jobs shows stuck jobs, reboot once from the shell with sudo reboot. the pool data should still be fine since you only yanked a dataset.
paste the middlewared tail if Choose Pool still dies at 60%.
Hi, thx for your prompt response. Not sure if I’ve set SSH in the system settings, however, I connected to the server using the truenas_admin credentials and used the shell. (things took awfully long to connect. It’s like the server is in slow-mo mode)
yeah that same dbus timeout on systemctl itself means systemd is wedged, not just middlewared. shell feeling like slow-mo fits that.
dont keep retrying Choose Pool from the ui. if you can still type in that shell try:
sudo reboot -f
if that hangs too, power cycle the box (hold the power button or flip the psu). pool disks should come back fine after a hard reset when dbus is this stuck.
after it boots, before touching apps, run:
sudo systemctl is-system-running
sudo systemctl status middlewared docker
paste those. if is-system-running says running, then try Choose Pool once.
Are you running filebrowser - or filebrowser quantum. If so - before deleting datasets stop those apps first - I have found they tend to lock things open given half a chance.
Thanks and noted on your feedback. Yes, I have filebrowser and it’s been solid so far. Used it remotely 2 days ago. Doesn’t lock up in my system, however, it does have some quirks which can be ironed out.