upgrading from 9.3 to 9.10, when?

[nojohnny101]

here is my setup:

fractal node 804
asrock c226m ws
Intel G3258 @ 3.2ghz
2 x 8gb RAM ECC Kingston
6 x 3tb NAS Seagate
Season 550w 80Plus GOLD

When is it safe to upgrade? my machine is primarily used just for plex and storage of uncommonly used files that are accessed maybe once per week. I have about 3-4 users that are semi-active (connecting a couple of times per week).

I just got a warning this morning that the 9.3 STABLE train is now in maintenance mode. My question:

When do people decided it is time to upgrade? I have always had the mantra of "don't fix it if it ain't broke" but at some point the transition needs to be made in order to keep up on security and bug fixes. How much longer until 9.3 is no longer developed?

I haven't been with Freenas that long so I am not familiar with how long pervious versions are maintained when new versions are released.

Would appreciate thoughts or previous experiences.

 

[m0nkey_]

I'm holding off upgrading to 9.10 for the time being. 9.3.1 is very stable and won't be going away for at least a year. I'm waiting until the next couple of updates in 9.10 before upgrading.

 

[cyberjock]

I'm holding off upgrading to 9.10 for the time being. 9.3.1 is very stable and won't be going away for at least a year. I'm waiting until the next couple of updates in 9.10 before upgrading.

People keep asking me this question.

On my Mini (only use iSCSI and NFS) I upgraded to 9.10. I regularly test new builds that aren't public yet, etc and since I only use iSCSI and NFS (and the fact that I can rollback easily if an update doesn't work for me) I always update when a new version comes out.

My main system, I'm a but more conservative. It uses lots of stuff, all the protocols, jails, etc so I'm still 0n 9.3.1 there. I will probably upgrade to 9.10 in July-ish on this system unless I feel that things will be fine. For me, with all the problems with jails I'm not ready to try to upgrade just yet. ;)

If my main system was being built, I'd just go with 9.10 right now. But since 9.3.1 is what it's used for quite a while, I'll stick with what works... for now. :)

 

[Mlovelace]

I don't run jails or plugins on my systems so I upgraded to 9.10 and I've had no issues so far.

 

[eye3]

I'm holding off upgrading to 9.10 for the time being. 9.3.1 is very stable and won't be going away for at least a year.

I'm waiting until the next couple of updates in 9.10 before upgrading.

If we are still running 9.3 how can we find out when an update is made for 9.10? Is there a URL that lists the updates?

Thanks.

 

[Jailer]

For me, with all the problems with jails I'm not ready to try to upgrade just yet. ;)

Same here. I'll wait until the jail issues are worked out and everything seems ok before I upgrade.

 

[cyberjock]

So I just talked to a developer.. he says that if you have a jail running from a version prior to 9.10 it should still "just work". It'll have the old user environment, but that's not a big deal unless your potentially exposing the jail to the internet directly.

 

[Jailer]

Except that there have been several reported incidents of jails not functioning correctly after the update to 9.10. Most seem to revolve around DHCP issues and I use static IP's for all of mine but I'll still wait until the dust settles a bit. ;)

 

[lvanhelden]

On my Mini (only use iSCSI and NFS) I upgraded to 9.10. I regularly test new builds that aren't public yet, etc and since I only use iSCSI and NFS (and the fact that I can rollback easily if an update doesn't work for me) I always update when a new version comes out.

I just tried upgrading my Mini from 9.3 to 9.10 and networking stopped (...which sucks on a NAS), so I rolled back to 9.3. I think I'll try it again in a couple of weeks, as I am not yet comfortable enough with it to troubleshoot yet. For now I am googleing to see if I find others with this predicament and see if there is an easy solution out there.

 

[nightshade00013]

I upgraded my 9.3 to 9.10 as well as my sister system in Hayward, CA and have had ZERO issues with the jails. Couple standard jails as well as one plugin jail on each system. No network issues at all. So far it seems to just work for me.

 

[Sakuru]

According to cyberjock, 9.3.1 actually won't be supported for much longer: https://forums.freenas.org/index.ph...de-or-should-i-not-upgrade.42677/#post-277812

 

[nojohnny101]

thanks for the discussion.

i think i'm going to hold off on upgrading for a couple of months, which will hopefully be enough time for any nasty bugs to get worked out. seeming as there are no major bugs that are impacting me in 9.3.1 it doesn't hurt to stay on that for a while even if it is "unsupported" soon.

 

[nightshade00013]

No it shouldn't hurt to wait. Some people are still floating around on pre 9.3 versions and doing fine but for support it becomes a pain when someone needs help and they are using a feature that has been deprecated or a version that does not have a feature that is useful for fixing a problem. It's the same idea behind the cell carriers controlling the release of a cell OS, if they have to support it they don't want to deal with people who are running oddball versions.

 

[dasunsrule32]

I've attempted to upgrade on three different occasions now. I'm setup with a lagg and when it boots up in 9.10, it spews mdns errors. If I setup the lagg again, same issue. I've not had luck yet moving to 9.10. :-(

Sent from my Nexus 6P using Tapatalk

 

[nojohnny101]

@dasunsrule32 is it affecting your freenas server behavior? It seems to be a common bug that does not affect operation, see here:
https://forums.freenas.org/index.ph...nternal-errors-help-please.42494/#post-279193

 

[dasunsrule32]

@dasunsrule32 is it affecting your freenas server behavior? It seems to be a common bug that does not affect operation, see here:
https://forums.freenas.org/index.ph...nternal-errors-help-please.42494/#post-279193

Yes, the server never gets on the network. Can't ping, perform DNS lookups, etc. Dead in the water, have to roll back to 9.3.x every time.

It's running on an IBM x3650 x2, I believe that is the correct server model. Will have to verify tomorrow.

Sent from my Nexus 6P using Tapatalk

 

[sef]

That's not due to mdns, mdns is complaining because of the lack of network.

 

[dasunsrule32]

That's not due to mdns, mdns is complaining because of the lack of network.

I understand that. It worked fine in 9.3.1, but upgrading, even with the sadness config, is a fat failure.

Even if I reset the nic's and setup the lagg again, it still fails.

Sent from my Nexus 6P using Tapatalk

 

[nightshade00013]

But it works without lagg enabled? If so leave it off, it's a nice feature to have but my guess is this is home use or small office. Is this for failover or aggregation? If you are aggregating does the switch have proper support for it?

You have given us very sparse info on your system but from what I can tell they should be Broadcom NIC's, it could simply be an incompatibility with FreeBSD 10 driver and lagg support. From a quick search it seems that this would be the case and getting lagg to work has been hit or miss a lot over the years with Broadcom chips.

 

[dasunsrule32]

But it works without lagg enabled? If so leave it off, it's a nice feature to have but my guess is this is home use or small office. Is this for failover or aggregation? If you are aggregating does the switch have proper support for it?

You have given us very sparse info on your system but from what I can tell they should be Broadcom NIC's, it could simply be an incompatibility with FreeBSD 10 driver and lagg support. From a quick search it seems that this would be the case and getting lagg to work has been hit or miss a lot over the years with Broadcom chips.

It worked perfectly in 9.3. What a regression going to freebsd 10 :-\

Anyway, I'll play around with it later some more. It's a actually a dev box at my school for testing Citrix changes, etc before prod.

Sent from my Nexus 6P using Tapatalk