Thanks for the idea. I also migrated from HDDs to SSDs. It also seems faster.
1 Like
I have the same TM problem as discussed above, but with slightly different twist: the initial bundle being written is .sparsebundle, which gets populated with about 1MB of files, and then renamed to .sparsebundle. This rename fails with Permission Denied.
Problems here. System was working nicely on 25.10.0. Updated, rebooted, system not accessible via web UI or ssh.
Logged into the console, found multiple problems:
(1) nginx hadnāt started because mime.types is included by the main config but was missing from the system;
(2) SSH had been disabled;
(3) syslog-ng.service isnāt starting - also missing config files, scl.conf is included by the main conf file but isnāt in /etc/syslog-ng or /usr/share/syslog-ng/include;
(4) I canāt sudo or su, critical error āunable to initialise PAMā; same PAM problems if I try to get a shell from the web UI;
(5) No apps containers are running (presumably because they need to switch user and hit the PAM failure);
(6) Also errors during boot relating to set-serial and /etc/init.d/ups-monitor (missing).
It looks like something has removed a load of config files from /etc. Really not good.
How do I back out this update? Is it safe to restore a pre-update snapshot of the boot pool?
Updateā¦
I used rsync to restore all the missing files from /etc. Thatās fixed syslog, pam and a few other issues.
Still canāt start either of my apps; PhotoPrism canāt find /init and Plex fails on service āpermissionsā. I suspect thereās some config been overwritten as well as files missing; might have to try restoring the entire /etc snapshot from pre-upgrade.
Why not just roll back to .0?
I was hoping not to have to go backwards completely, but itās looking like the best route, I have to agree!
Is anyone else experiencing issues with cron jobs or cloud sync tasks not initiating after the 25.10.0.1 update? Jira has been filed, also this thread.
.0 or .1 release means youāre a beta tester; donāt do it on your main, āproductionā, machine.
Reversion is always a possibility, including to 25.04.x (never upgrade pool features right after an update!!!).
5 Likes
After reboot and toggling NetBIOS-NS, the problem has not reoccurred. Iāve even removed the hard mapping of pointing my TrueNAS server name to IP address in my HOSTS file.
So Iāve learned! I should really have downloaded 25.04 originally (this is a new build and Iām new to TN), I guess. The labelling of 25.10 as āstableā and 25.04 as ālegacyā on the download page misled me. Iām used to āstableā meaning āfit for productionā.
The rollback to 25.10.0 didnāt work, recreated all the problems, so perhaps the damage happened slightly earlier than it appeared, though there were no symptoms. Very strange. I think a rebuild is probably called for here.
3 Likes
No issues here with cron jobs on 25.10.0.1. I have five rsync jobs scheduled each week on my Goldeye server, all of which seem to be running fine. I currently have no cloud sync tasks, so I canāt comment on itās status.
I donāt know where along the way this problem crept in, but the owner on the data datasets had changed from apps/apps to root/root. When I changed it back, all the data became accessible again.
Before trying that, I had rolled back to 25.04, and I had the same problem. So this for me wasnāt a 25.10 problem
Well, I donāt know any other company labeling something as a release and itās actually a beta version. Max confusing and frustratingā¦
1 Like
Yeah, iX takes ānever trust a .0 releaseā and turns it up to 11.
5 Likes
well i rely on this
Developer > Early Adopter > General > Mission Critical
so 25.10.0.1 is Early Adopter. thatās basically a beta more or less.
and 25.04.2.6 fangtooth is for general actual use for people donāt want to beta.
if not sure if itās a beta or not, best just bookmark that webpage and rely on that.
7 Likes
Look in consumer law , there is something called āsurprisingā. iXSystems deviates from known mechanics by releasing beta versions as releases, in particular if there is a beta a release candidate and a release of the beta version. I donāt know anyone else releasing betas of betas.
1 Like
Soā¦ double your money back, I guess?
Really, iX have been inconsistentāone would almost say ādishonestāāabout this for years. On the one hand, they aggressively promote their new .0 release as the ānew stable release,ā and tell anyone whoāll listen that they totally ought to upgrade right away. And then when people have problems,[1] itās, āwell, that was only for early adopters, just check our software status page.ā Itās their plausible deniability.
The adoption of update profiles in 25.10 is a welcome change, but the CF that is SMART (and iXā complete lack of transparency about what theyāre really doing any more) makes me not want to update to 25.10 at all.
including the occasional, though thankfully rare, data-destroying bug ā©ļø
6 Likes
Like Arwenās comments from 1 year ago:
Nightly Releases = Crazy Train
Release candidate = Booze Train
Release = Scenic Train with wild life
Release +.1 = Commuter Train
Release +.2 = Sleeper Train
7 Likes
This is perfectly normal for Microsoft: they fired their entire QA team a while ago and now just use Windows users as beta-testers.
3 Likes