He all,
I’ve been using Truenas SCALE since a long while with only two apps installed : NextCloud and mini dlna. All was running quite well since a long time as well. But, don’t know why, few days ago I lost my apps and got an issue with the error message here above (title).
Does somebody have an idea for solving my Truenas trouble ?
Thanks a lot in advance.
I’m on Truenas SCALE Goldeye 25.04.2.6, trying this afternoon to update it to 25.10.2.1, in case of
Did you make any networking changes recently? Often error messages like this are a result of broken network settings.
I’ve had this fault on every boot for some time, fixed by unsetting the pool and setting it again.
No never that made changes
Hi fayelund,
Sorry for my newbie question :), unsetting then setting the pool means detach/attach my main volume ?
no he means on the apps page top right corner click on configuration → unset pool. This will stop the docker service completely. After a few seconds you can re-set the pool, which should restart the docker service
Ah yes ! Sure. Thanks. I’m going to check
It succeed ! Thanks a lot to you guys. Hope it will remain stable, will see.
Sorry, should have written better. In apps →configuration, unset your pool, and set it again to the same pool as before.
And @LarsR beat me to it 
Ah ok. I think this is a bug that can happen when apps data is on slower storage and isn’t ready the first time the system tries to start docker. There was a fix put in at a later point that should resolve this but I forget exactly when that came in–possibly 25.10.X.
Hey, I just had the same topic after updating to 26.0.0-BETA.1
Unset, eating a few moments and then choosing the sam pool was the solution !
Thank you very much!!!
I experience this still on 25.10.3, so definitely not fixed. I also need to restart netdata to fix it, and middleware to fix ssh, after every reboot. I have suspicion that my LACP links comes up too late or something like that.
Looks like there’s one related fix going into 26-BETA.2 but it’s more focused on IPv6 so I’m not positive it’s the same issue. @Fayelund, are you using DHCP or static IPs?
Static IP, placed directly on the lagg group
Hmm. It may be a few different causes resulting in the same error message. I’d suggest filing a bug ticket with a debug and being specific in it about your suspicions with the networking set up.
Hmmm. I tried everything suggested in other threads:
Your mileage may vary. Not sure what the root issue is, but it’s smooth sailing on the BETA now.
That sounds right from the tickets I’ve seen. 2 should be fixed for BETA.2, 3 is the one I’m less sure about based on the current fix.
I tried that when the fault started, NAS-139097, got closed stating you didn’t have time to Investigate. Will try to file a new one.
Ticket created: NAS-140772
