Announcing FreeNAS 9.2.0-RELEASE

Status
Not open for further replies.
J

jkh

Guest
Hi Folks,

After one early BETA and two Release Candidates, it gives us great pleasure to announce the full and final release of FreeNAS 9.2.0!

As implied from the series of pre-releases, this release has benefitted substantially from a great deal of public testing as well as several months of “living on” testing we ourselves have done on a wide variety of hardware. This is, without a doubt, the best release of FreeNAS yet!

Since 9.1.1 was released, we have fixed 268 bugs in the bug tracker, as well as countless others that were found and fixed independently of the bug tracking system.

We have also made a number of enhancements to the UI and generally done our best to bring more polish to the FreeNAS system, both in usability and performance. Those doing benchmarks against 9.1.1 should notice some measurable improvements on any reasonably capable hardware, particularly at higher loads. Those using encryption will be especially pleased at the performance improvements on AESNI capable processors - encryption is now effectively “invisible” given that speeds comparable with non-encrypted pools can easily be achieved.

The documentation has also been updated for 9.2.0, though the source code (see release notes) is still a useful reference for features like the new web API, which comes with several examples in the source tree.

Should you encounter any bugs in this release, or wish to submit enhancement requests, please visit http://bugs.freenas.org and by all means file a bug! We use the bug tracking system quite religiously and screen bugs on a daily basis, so filing a bug report is the best way of making sure that any issues do not get lost! Since no release engineering process is ever truly finished, we are already planning for 9.2.1 and will aim to fix any “fit and finish” bugs we deem appropriate for the next software update.

We also have the FreeNAS forums for general discussion and encourage everyone to use them. Finally, the FreeNAS developers also hang out in the #freenas IRC channel on FreeNode in their copious spare time should you wish to discuss things more in real-time.

We are very proud of this release and the hard work that has gone into it! We are also tremendously grateful to the many people who have taken the time to file bugs, fix bugs and send us pull requests, post helpful comments in the FreeNAS forums, or otherwise be a part of the ever-growing FreeNAS community.

Again, if you didn’t follow the link in the first line, the bits are in http://iso.cdn.freenas.org/9.2.0/RELEASE/ You can also get them via the FreeNAS download page (http://www.freenas.org/download.html) and also sign up for the FreeNAS newsletter at the same time!

Regards,

- The FreeNAS Engineering Team

Release Notes for FreeNAS 9.2.0-RELEASE

  • Version 9.2-RELEASE of FreeBSD with performance improvements, bug fixes, and updated software packages. For a complete list see http://www.freebsd.org/releases/9.2R/relnotes.html
  • USB 3.0 support is disabled by default as it currently is not compatible with some hardware, including Haswell (Lynx point) chipsets. To enable USB 3.0 support, create a Tunable named xhci_load, set its value to YES, and reboot the system.
  • The Kernel UMA allocator is now the default for ZFS. This results in higher ZFS performance.
  • ZFS will now alert the administrator for pools that are not 4K-aligned.
  • By default, FreeNAS will treat all disks as 4K sector ("Advanced Format") disks. This is a future-proof setting that allows AF disks to later be used as replacement drives for older, legacy 512 byte sector drives without compromising performance. The administrator can optionally disable this 4K-by-default behavior by setting vfs.zfs.vdev.larger_ashift_minimal to 0 in both sysctl and loader tunables.
  • Avahi (multicast DNS, aka Bonjour) registration of all services, include the web service, means you no longer need to have a head on the box to know its IP address, even for initial configuration, if the system your browser is running on supports mDNS (e.g. a Mac or mDNS-enabled Windows/Unix box). The default address will be freenas.local (or freenas-n.local, where n is the # of freenas.local instances already on the local network). This can be changed by changing the hostname in the FreeNAS system or network configuration screens.
  • The built-in admin user account is no longer used and the Admin Account removed. The first time the FreeNAS graphical interface is accessed, a pop-up menu will prompt for the root password. Subsequent logins to the graphical interface will require this password.
  • FreeNAS no longer sends daily emails when email reporting is enabled unless actual errors or issues of concern have arisen. Simply saying "all is well!" each and every day was causing email fatigue and obscuring actual errors. Those wishing for daily "all is well!" reports can simply add a cron job that does this.
  • The plugin system now offers in-place updates for plugins, also segregating installed plugins from available plugins to make the UI
    less cluttered.
  • A complete REST API has been created for FreeNAS, allowing a FreeNAS instance to be controlled remotely. See examples/api in the FreeNAS source repository (https://github.com/freenas/freenas/tree/master) for some examples of this in action. Complete API docs are available in docs/api.
  • The "Permit Sudo" field has been added to the add and edit screens for Users and Groups. A column in View Groups and View Users now indicates whether or not "Permit Sudo" has been set.
  • HTTP and HTTPS access to the FreeNAS graphical interface are no longer mutually exclusive. The fields "WebGUI HTTP Port" and "WebGUI HTTPS Port" have been added to System Settings -> General.
  • An "Edit" button has been added to the "Hostname" field of SystemInformation to make the hostname easier to change.
  • The results from the latest ZFS scrub now appear in Volume Status.
  • The Add Apple (AFP) Share menu has been simplified and a "Default umask" option has been added.
  • The "Server Name" field has also been removed from AFP; in Netatalk 3, this value is automatically derived from the system hostname.
  • "Enable home directories" and "Home directories" options added to AFP.
  • The AIO options have been removed from CIFS.
  • Fourteen TLS-related fields have been added to the Advanced Mode of FTP.
  • An "IPv4 Address" column has been added to the View Jails screen.
  • A shell button has been added to Jails, making it easy to access the command line of the selected jail.
  • A "Create directory" checkbox has been added to the Add Storage function of a jail so that the user does not have to first access the jail's shell to make sure that the directory already exists. A "Read-Only" checkbox has also been added to this screen.
  • A jails templating system has been added, allowing the quick deployment of new jails from existing templates and the ability to create custom templates. Linux jail support has also been added and installation templates are included for Debian-7.1.0, Gentoo-20130820, Ubuntu-13.04, Centos-6.4, Fedora-19, and Suse-12.3.
  • A link to the online FreeBSD manual pages has been added to Help.
  • Added bxe(4) driver for Broadcom NetXtreme II Ethernet 10Gb PCIe adapter.
  • Added padlock(4) driver which provides cryptographic hardware acceleration for VIA C3, C7 and Eden processors.
  • Improved performance of encrypted ZFS volumes.
  • The iSCSI options have been updated to ensure the GUI constraints match the daemon constraints. In particular the GUI limited the number of sessions and the number of connections to a low value that may need to be increased if there are large numbers of targets or clients or both.
 

benamira

Explorer
Joined
Oct 12, 2011
Messages
61
Thanks!! Great news! Just downloading downloaded and will test testing in a few minutes...
First notice is that in the GUI, left menu, before upgrading and below plugins i could see the plugins installed (Plex media server in my case) and could launch it...
After upgrading, the plugin is installed and seems to be working but in the left menu, there is nothing in plugins.
It is working as expected or should i file a bug??

As i am not an expert the only message i see from the console is
http://192.168.0.200/plugins/plexmediaserver/1/_s/treemenu: HTTP Error 502: Bad Gateway
 

Z300M

Guru
Joined
Sep 9, 2011
Messages
882
awesome, is it better to upgrade or do a clean install?
I just did the GUI upgrade from 9.1.1-RELEASE, and everything seems to be fine.
 

9C1 Newbee

Patron
Joined
Oct 9, 2012
Messages
485
Great push to finish in time for Christmas. Thank you for the present guys! Merry Christmas.
 

benamira

Explorer
Joined
Oct 12, 2011
Messages
61
Thanks!! Great news! Just downloading downloaded and will test testing in a few minutes...
First notice is that in the GUI, left menu, before upgrading and below plugins i could see the plugins installed (Plex media server in my case) and could launch it...
After upgrading, the plugin is installed and seems to be working but in the left menu, there is nothing in plugins.
It is working as expected or should i file a bug??

As i am not an expert the only message i see from the console is
http://192.168.0.200/plugins/plexmediaserver/1/_s/treemenu: HTTP Error 502: Bad Gateway


It's fixed without any action..
 

adrianwi

Guru
Joined
Oct 15, 2013
Messages
1,231
Not sure whether I was being brave or stupid, but I've just upgraded from the GUI and everything worked perfectly!

ownCloud and Plex plugins fine too, so might have a go at upgrading them too (as that was the main reason for upgrading FreeNAS)

Great work people!
 

Sir.Robin

Guru
Joined
Apr 14, 2012
Messages
554
Congratulations to you all on this great achievement!! :)

Also, i must say i was impressed by the short response time after filing a bug :)
 

warri

Guru
Joined
Jun 6, 2011
Messages
1,193
Congratulations and thanks for the early christmas present. Going to upgrade in a few minutes!
 

Z300M

Guru
Joined
Sep 9, 2011
Messages
882
There should be no functional difference. Do whatever makes you happiest. :)
But isn't USB3 disabled by default in 9.2.0? I upgraded from 9.1.1 and found that my USB3 ports still worked OK; wouldn't I have to have reenabled that if I had installed from scratch?

And zpool status suggests that I should upgrade. I already upgraded when I moved to 9.1.1; what would a further upgrade get me?
 

adrianwi

Guru
Joined
Oct 15, 2013
Messages
1,231
Not sure whether I was being brave or stupid, but I've just upgraded from the GUI and everything worked perfectly!

ownCloud and Plex plugins fine too, so might have a go at upgrading them too (as that was the main reason for upgrading FreeNAS)

Great work people!


Plex upgrade not quite as smooth, and whilst it did complete after a few hours and worked after a reboot, it trashed my database which is currently rebuilding. Would have been quicker to delete and re-install!

Holding fire on the ownCloud upgrade :)

Ah, what the hell! Thought I'd give ownCloud a go and after about an hour the upgrade completed. OSX client displayed a XML error and wouldn't connect, but could access via HTTP and everything was OK apart from the users which had been lost. Not a major problem, as I only had 3 so could recreate but might be more of an issue for someone running lots of user accounts. The OSX client now looks like its doing a full re-sync, which is a bit of a pain, but otherwise looks OK.

Won't be trying any upgrades for a few months...
 
J

jkh

Guest
plugin updating is a new feature - sounds like it's still got some teething problems!

We'll check that out. On the flip side, there's nothing says you *have* to upgrade your plugins just because you've updated FreeNAS!
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
Great job! I just upgraded my machine using the GUI upgrade method and it worked flawlessly. My NAS is in the basement and I was able to upgrade it without even being near it. I haven't seen a single problem myself and I've been checking it out for the past hour.

So props off to the iX Systems Team and all the beta testers. I remember iX Systems were rolling out 8.0 and a few of the subsequent versions, rushing it out the door without enough testing and it was a bad time for some folks. With 9.1.0 and definitely 9.2.0 I believe you have the process down and the fact you offered a second release candidate is proof of that.

Merry Christmas and Happy Holidays to All.
 

benamira

Explorer
Joined
Oct 12, 2011
Messages
61
plugin updating is a new feature - sounds like it's still got some teething problems!

We'll check that out. On the flip side, there's nothing says you *have* to upgrade your plugins just because you've updated FreeNAS!


Completely agree!
Upgraded to 9.2 but keep the current version of the plugin (plex media server) is a conservative approach to be sure not to lose the DB and all the config.
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
plugin updating is a new feature - sounds like it's still got some teething problems!

We'll check that out. On the flip side, there's nothing says you *have* to upgrade your plugins just because you've updated FreeNAS!

Yes, but Plex is doing upgrades every week and there's quite a few SERIOUS bugs that are getting fixed in recent builds. So the "need" to upgrade to fix things like subtitles and other things is quite high. I'm running the weekly plexpass builds in linux and religiously upgrade when they are posted.
 

ThreeDee

Guru
Joined
Jun 13, 2013
Messages
700
hopefully the Plex upgrade feature will get ironed out at some point .. other than that minor hiccup .. everything running smooth like glass with the 9.2 release!
 
Status
Not open for further replies.
Top