From their statements so far, I don’t think so.
2 Likes
John,
Here are a few poudriere guides that helped me set it up. I did it specifically because I wanted to run Zabbix, but I wanted it with a postgresql backend rather than mysql, so I had to compile it with those option.
Those should get you pointed in the right direction…
–vr
1 Like
Yeah, that was my question as well. Since there is no upgrade path to a 13.3 train from 13.0, and once on a manual download/install of 13.3, the only available trains are to scale, that this is a one-shot deal, with possible patches for major security vulnerabilities.
But it appears that this is going to be a lone release, barring the odd security vulnerability…Thought that would be easier to announce security patches if there was a train…
But who am I to know the machinations of iX?
We are fully committed to supporting our Enterprise customers who are mostly using 13.0 at this time.
At this stage, we don’t see any major benefits of moving them to 13.3. We do not want to move them to 13.3 if there’s insufficient testing. So for that reason, we’ve decided to patch 13.0 where needed.
At the same time, we are migrating new Enterprise customers to 24.04 and expect to be able to offer any Enterprise customer a reasonably smooth upgrade (1 system reboot). Jails (and VMs) are the major use-case where smooth upgrades are not possible and these are largely used by the community.
1 Like
Thank you both @VulcanRidr and @grahamperrin
I’ve been trying unsuccessfuly to do a manual update of TrueNAS Core from version 13.0-U6.2 to the latest 13.3.
I’ve downloaded TrueNAS-13.3-RELEASE-manual-update.tar, pushed the Apply Update button but it stays like this forever.
Do you guys have any clue how to proceed from here?
Thanks.
Wait?
1 Like
Do you have enough available space on your boot drive?
1 Like
Change from memory device to any other option, better if it’s an SSD. Might help.
Otherwise, you can always save your configuration and do a clean reinstall.
1 Like
You might be correct. I’m sure I’ve waited for at least one hour. I’m going to wait longer and see.
I do, I have 87 GB free in my freenas-boot pool.
I’ve tried that route too, with no luck.
Right, this is what I’m going to do as a last resort.
And before anyone else asks, I verified the SHA256 checksum.
Thanks everybody, I’ll report later today.
1 Like
Hi, have you tried uploading to your pool instead of memory (upload File Temporary Storage Location) ?
It might be some endpoint protection on client (or something else client-side) silently breaking upload. If worst comes to worst you could in principle scp the manual update file to the server and then run freenas-update <path to update file>. This is a hackish way to apply updates, but generally works. First validate shasum, that you’re on the correct server, etc before doing this.
1 Like
I just got back home after 14 hours and there you go, update successful!
Hilariously, waiting was all I needed to do!
Sorry for wasting everybody’s time. Yet, I was glad to realize once more that the community is always ready to help out!
This is interesting, because it unlike the web UI, a CLI command might give you some immediate feedback to assure you that all you need to do is wait!
4 Likes
As the Time Machine fix will not be coming to 13.0U6+ and given the issues with jails. Am I right to assume that I can update the main system to 13.3 and keep my jails as they are?
And secondly, as the update is a manual process since 13.3 is a different beast. Can I move back to 13.0U6 boot environment if needed or will that break things after upgrading to 13.3?
Thanks!
I think strictly depends on what service you are running through your jails.
When i update all jails seems working fine, and then i could upgrade all without issue.
But i have still migrated everything (or almost) on docker with a VM… Imho more stable and a lot better to mantein
1 Like
Almost certainly. Even very-old jails usually work fine, pretty-recent jails should be no problem.
Yes.
(Don’t upgrade ZFS pools if prompted.)
1 Like
Wouldn’t doing so break upgraded jails?
In the past no. But there were some major changes with 13.3 that broke some packages as outlined on the old forum. If you upgrade your system and jails to 13.3 you are stuck on that release.
3 Likes
@Jailer do you mean that it’s historically sometimes been possible to get away with running higher minor versions in jails than the host kernel?
I agree - don’t upgrade jails until you’re confident. It’s fine to run a lower minor version in the jail.
1 Like