FAQ: Updating from 9.3 to 9.10

[dlavigne]

This FAQ originally appeared at wiki.freenas.org.

What has changed in 9.10 vs 9.3?

In a nutshell, the underlying OS and a lot of "ports" used to implement various services. See the Release Notes for the 9.10-RELEASE as well as the ChangeLog files for all of the various Software Updates released for 9.10 to paint a complete picture.

I upgraded to 9.10 and my LACP (lagg) interface stopped working. It worked great in 9.3! HELP!

LACP links actually only "sort of" worked in FreeBSD 9 - they would misbehave in odd and difficult to diagnose ways when one of the physical links failed. In FreeBSD 10 (and hence 9.10), Active LACP is now enforced so that there is a proper heartbeat and the robustness of the link can be assured. Re-configure your switch for Active LACP and your lagg will work again.


Will my 9.3 jails continue to work under 9.10?

Yes and no. If you have a 9.3 jail used by a plugin or other application that you don't plan to change in any way (you just want it to continue to work), then yes, it will keep working just fine. If you are trying to use FreeBSD tools like the ports and packages collection (or any of the various upgrade helpers for them) then NO. Those tools inspect the currently running OS version and will immediately detect a mis-match and get angry. If you want to do any "manual jail management" then you need a 9.10 jail.


How do I create a 9.10 jail?

Due to the way that templates are cached over the lifetime of a FreeNAS install (an architectural design flaw it is too late to fix now), you will need a fresh (totally empty) jail root in order to trigger the download and installation of a FreeBSD 10 jail environment (template).


I upgraded to 9.10 and my self-signed SSL certificates that I created earlier (on FreeNAS) no longer work. Help?

See comments in https://bugs.freenas.org/issues/14977 - easiest to just re-issue the certs in 9.10 due to the fact that 9.3 had some bugs in its cert generation logic (non-security compromising ones, but the tightened cert checks in 9.10 catch them nonetheless).


After upgrading last night, I found myself unable to access the FreeNAS GUI (in HTTPS only mode). How do I get my GUI access back?

For a rebootless http workaround please do the following:

1. SSH into your system.
2. Make a backup of your system database (for safety): cp /data/freenas-v1.db /data/freenas-v1.db.bak.
3. Manually set the GUI's protocol to 'http' in the database: sqlite3 /data/freenas-v1.db "UPDATE system_settings SET stg_guiprotocol = 'http';".
4. Ensure that the above step went through successfully by printing the value of stg_guiprotocol from the database: sqlite3 /data/freenas-v1.db "select stg_guiprotocol from system_settings;".
5. Regenerate nginx config file and then restart nginx and django: service ix-nginx onestart && service nginx restart && service django restart.

I'm having authentication issues with SMB and AD / LDAP / ... after upgrading - Why?

TLSv1 has finally been deprecated as insecure. Try switching to TLSv1.2.