Upgrade Notes
=============
- Before upgrade you must always backup your configuration file, your
system disk and all your data (if possible).
- DO NOT use firmware upgrade if your installed FreeNAS revision is lower
than 0.7(4975). Firmware upgrade from any version < 0.7(4975) is not
recommended. The safest way to upgrade from any version < 0.7(4975),
to 0.7.1, is to boot the LiveCD and use the upgrade options.
- WARNING: If you try to do a firmware upgrade from a version < 0.7(4975),
the process might fail with Broken Pipe or Mount / Umount related errors.
Testing shows these symptoms occur frequently. If you encounter any of
them during an attempted, unrecommended upgrade the only solution is to
re-install from scratch, this will delete all data on the OS disk.
Downgrade Notes
===============
- Downgrading from 0.7.1 to any version less than 0.7(5001) is not
recommended.
- If you try downgrade to a version < 0.7(5001), the partitions may break
or be corrupted leaving the system unusable and possibly destroying data
stored on the OS drive.
Other Notes
===========
- The addition of new software makes the OS almost 1MB bigger.
FreeNAS 0.7.2 Sabanda
Sunday, 17 October 2010 build 5462
Majors changes:
*
Upgrade to FreeBSD 7.3-p3.
*
Upgrade unison to 2.32.52.
*
Upgrade bsnmp-ucd to 0.3.2.
*
Upgrade e2fsprogs to 1.41.12.
*
Upgrade smartmontools to 5.40.
*
Upgrade php5 to 5.2.14.
*
Upgrade transmission to 2.10.
*
Upgrade samba to 3.5.5.
*
Increase image size to 72MB, mfsroot to 180MB.
*
Increase default install size embedded to 120MB, full to 380MB.
*
Increase default swap size to 256MB.
*
Ireasnce memory disk for firmware upgrade to 128MB.
*
Create 4KB aligned data partition on the boot disk.
*
Upgrade arcconf to 6.40.18530.
*
Upgrade cdialog to 1.1.20100428.
*
Set kern.hz=100 when running on virtual machine and kern.hz>100.
*
Add virtual machine guest support (open-vm-tools/vbox-additions).
*
Upgrade inadyn-mt to 02.18.36.
*
Upgrade bash to 4.1.007.
*
Upgrade istgt to 20100707.
*
Upgrade msmtp to 1.4.20.
*
Upgrade nano to 2.2.4.
*
Upgrade gzip to 1.4.
*
Upgrade tftp-hpa to 5.0.
*
Introduce iSCSI boot/install feature (isboot 0.1.3).
*
Upgrade 3ware driver to 9.5.3.
*
Upgrade proftpd to 1.3.3b.
*
Upgrade lighttpd to 1.4.28.
Minors changes:
*
Add Czech and Slovak translations.
*
Add multiple CPUs usage.
*
Add AIO WebGUI for CIFS/SMB service.
*
Remove /var/tmp symbolic link.
*
Support Advanced Format 4KB sector. (UFS/GPT data partition only)
*
Set fsck enable by default at Disks|Mount Point|Add.
*
Set kern.geom.debugflags when formating.
*
Modify Tuning values.
*
Add ability to disable File Manager.
*
Make three backups of configuration when writing new one.
*
Add amdtemp module. (FR 2992462)
*
Add ability to probe on-die digital thermal sensor.
*
Enable disk quotas of kernel option.
*
Remove a useless partition.
*
Add ability to mount 'a' partition on MBR/UFS.
*
Add variables to change upload directory of lighttpd.
*
Disable fsck on MBR/UFS mount point due to 4KB alignment. You need
re-enable it after upgrading.
*
Add wireless firmware modules.
*
Add logical block length for iSCSI target.
*
Add ability to disable/enable for iSCSI target.
*
Add unused extents to the list in iSCSI target edit mode.
*
Add kernel module directory (/boot/modules).
*
Set Large read/write by default (Services|CIFS/SMB|Settings).
*
Add crypto accelerator driver (hifn, safe, ubsec).
*
Move upload directory to /var/tmp/ftmp from /ftmp.
*
Change iSCSI initial parameter.
*
Add new parameter of istgt 20100522.
*
Add minimum set of zfskerntune feature.
*
Add Hyper-V reboot issue patch.
*
Add ZFS pool with 4KB sector support.
*
Add ZFS cache and log device support.
*
Improve parameters for Samba 3.5.x.
*
Improve Active Directory support.
Bug fixes:
*
Fix wrong validation when WINS is enabled.
*
Fix missing /var/tmp in full installation.
*
Fix upload fail when firmware upgrade.
*
Fix AIO checkbox is not disabled if samba is disabled.
*
Fix fail to update index.php if some value is undefined.
*
Fix control of Ctrl+Alt+Del if console menu is disabled (BR 2976816).
*
Fix the document link on Services|Rsync|Server|Settings (BR 2997828).
*
Fix fail to connect SSH if ActiveDirectory is enabled (BR 2821715, 2898371).
*
Fix UPS support for Megatec USB UPSs fails (BR 3079159).
Permanent restrictions:
*
It is not possible to format a SoftRAID disk with MSDOS FAT16/32.
*
It is not possible to encrypt a disk partition, only complete disks are supported.
*
Enable 'polling' on interfaces used by a LAGG interface will make it inoperable.
Known bugs:
*
If DHCP for IPv4 is used, the IPv6 statically configured DNS server will be
overriden by the IPv4 DNS server.
NEED TESTING:
*
IPv6: auto mode
*
All services using IPv6 address (NFS, FTP, etc…)
*
Netatalk VFS Samba module (automatically enabled when Netatalk starts) crashes
samba when accessing to share
*
Need to write an online-test procedure
Help needed:
*
Need help for adding LDAP authentication feature:
Main services can be easily authenticated using PAM-LDAP, but is harder for Samba.
Release Notes for FreeNAS 8.0 Release Candidate 2
---------------------------------------------------
Release Candidate 2 contains fixes for issues that were encountered in RC1. It
does not contain the list of new functionality that was scheduled for RC2, but
it contains enough fixes that it was a significant improvement over RC1.
FreeNAS 8 should be installed to a USB stick or Compact Flash device. It
requires a device of at least 1 GB in size. In a departure from FreeNAS 0.7
releases, the OS drive can not be used as a component for a volume, nor can
it be partitioned for sharing.
New in this RC:
GUI Firmware upgrades are supported, but do to a bug in the interaction between
FreeBSD, lighttpd, and python they work intermittantly. There is a work-around
which wasn't implemented in time for RC2. The procedure involves running
commands from the CLI shell.
# mount -uw /
# echo 'server.network-backend = "writev"' >> \
/usr/local/etc/lighttpd/lighttpd.conf
# mount -r /
# /usr/local/etc/rc.d/lighttpd restart
The upgrade procedure takes advantage of nanobsd by writing the OS to the
"inactive" slice. If you are running off slice 1 the firmawre will be written
to slice 2, and vice versa. The boot label is automatically updated, but
during the initial boot the slice can be choosen manually, allowing for an
easy reversal of an undesirable upgrade.
To use the GUI upgrade feature, first configure a storage volume. This is
used for temporary storage space of the image. The temporary location is
selected from system -> settings -> temporary directory. Once that is
configured, select the Firmware Update tab. Browse to the firmware on your
machine and choose it. Currently there are two firmwares available:
http://sourceforge.net/projects/freenas/files/FreeNAS-8/FreeNAS-8.0-RC2-i386.xz/download SHA256 ff31a6e69244d264e1f5e2a395e36aa308256ebfce708112ae22adbd2de2e083
http://sourceforge.net/projects/freenas/files/FreeNAS-8/FreeNAS-8.0-RC2-amd64.xz/download SHA256 29a131e11e4df9ae1a15d45bbd157ca672acc707d3eb98ae71a56ba175e1093d
Enter the correct SHA256 hash, and upload the firmware. It will report success
on completion, go ahead and reboot the FreeNAS box at that point and it will
boot off the new firmware.
Upgrading via the install iso is still supported, simply boot off the new ISO
and select your boot device from the menu. If you are upgrading from a
snapshot older than RC1 this is the only supported upgrade method.
The bugs in the FTP configuration are sorted out. The GUI will now
generate valid configurations or refuse to save invalid values with an
appropriate error message.
The system now will send email about LSI RAID controller events if the email
service is properly configured.
Configuration bugs in the AFP service have been squashed, although there are
still mixed reports concerning AFP.
Errata:
Volumes created with previous snapshots, betas, or builds from the sourceforge
repo contained a bug in their GPT labeling scheme. This labelling can result
in reduced performance when the underlying device is a hardware RAID 5 or 6
array. It is recommended that if the underlying storage device is a hardware
RAID controller using RAID 5/6/50/60 that volumes be deleted and recreated.
The iSCSI service can generate broken configs for some scenarios. These will
get fixed as feedback is received, as the number of initiators and their various
configurations creates a large matrix of possibilities. The initiators that are
fairly well tested are the MS Software initiator, the VMware ESXi 4.x initiator,
and the FreeBSD initiator.
Link Aggregations, also know as LACP/LAGG/interface bonding, require a reboot
to take effect. This is not enforced by the GUI or by the CLI. Furthermore
there is no way to create a Link Aggregation from the CLI, so the initial setup
is at best non-intuitive. From the CLI you can configure a physical interface
so that the web GUI can be accessed, then from the web GUI a Link Aggregation
can be created, then the physical interface can be deleted, the box rebooted,
and then from the CLI the link aggregation can be selected for configuration.
Once it is configured the box should be rebooted a final time.
Replacing failed drives in arrays isn't possible through the GUI, and due
to the drives being GPT labeled replacing them via the CLI isn't easy either,
nor is the replacement procedure documented at this moment. While the
documentation will be available very shortly, the real solution will be via
the GUI.
The GUI is still HTTP only. That will be rectified shortly, but for the
moment accessing the GUI over a hostile network (such as the internet) is
not a good idea.
Some Mac users are reporting substandard CIFS write speeds. The exact
conditions for this are unknown.
UPGRADES FROM FREENAS 0.7x ARE STILL UNSUPPORTED
The system has no way to import configuration settings from 0.7 versions
of FreeNAS, nor is there any sort of volume importer yet that will preserve
data on existing volumes. Attempting to upgrade from 0.7 will result in the
loss of your configuration, your data, or quite likely, both.
IMPORTING EXISTING STORAGE VOLUMES IS UNSUPPORTED
We will get that working very shortly, for now, don't feed disks with data
you care about to FreeNAS 8
Usability of this Release Candidate:
At this point the feature set of FreeNAS 8 is complete enough to perform file
sharing tasks via NFS or Samba, using local users, AD, or LDAP, as well as
allowing the system to operate as an iSCSI target. The base technology of
FreeBSD, ZFS, Samba, and NFS is very stable and very well tested. While there
isn't an upgrade path from other storage solutions, including previous FreeNAS
0.7 releases, the system is suitable for new deployments provided the
featureset is a good match for the requirements.
A note about versions:
There's been a huge jump in version numbers. The intention is to have the
version number reflect the base version of FreeBSD used. This RC is based
on FreeBSD 8.2, but this version of FreeNAS is called 8.0 as there are future
plans to add functionality that will get the versions caught up. Once
FreeNAS 8.2 is out, a suffix will be added, such as 8.2.1, 8.2.2, etc.
A note about filesystem technologies:
While this system does support UFS based volumes, such as gmirror, gstripe,
graid3, the primary focus is on ZFS. Many of the features are provided via
ZFS datasets, such as the ability to share subsets of volumes via CIFS.
This delta is likely to increase over time, the compelling reasons to use
ZFS are likely to increase as well. It is highly recommended to use ZFS
for new volumes, even if the underlying device is a volume exported by a
hardware RAID controller.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 System
Information to make the hostname easier to change.
The results from the latest ZFS scrub now appear in Volume Status.
Netatalk has been updated to version 3.1.0. See
http://netatalk.sourceforge.net/3.1/ReleaseNotes3.1.0.html for a list of
changes in this release. There are also a number of changes made to AFP
sharing as a result:
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.Release Notes for FreeNAS 9.2.1.1-RELEASE
Samba (SMB/CIFS support) upgraded to version 4.1.4, with select key fixes cherry-picked from 4.1.5. This version adds support for SMB3, the ability for FreeNAS to be a Windows Domain Controller, and advanced features like server-side copy support in Windows 2012 and later, along with multiple years worth of improvements over the version of Samba that shipped in 9.2.0. Samba4 also enables SMB protocol version 3. Previous versions of FreeNAS limited samba to SMB2 because of random crashes that would occur using SMB3. We also fixed a number of Samba issues specific to FreeNAS in 9.2.1.1 – see the fixed bug list for details.
A system dataset (.system) is now created in a user-configurable pool, the default being the first pool found. This can be changed in System->Settings->Advanced, the .system dataset being created as needed. This dataset becamse necessary for storing persistent Samba permissions, and is also being leveraged for other purposes, like collecting core files (which otherwise might overflow the limited system partition space) and storing system log files. It will be used for additional purposes as FreeNAS evolves.
A panic that occurred with VIMAGE jails has been fixed.
A bad bug with jail templates that caused them to be gratuitously downloaded has been fixed. See the fixed bugs query above for details.
Release Notes for FreeNAS 9.2.1-RELEASE (since 9.2.1.1 is just a bug fix release for 9.2.1):
Added the LSI 12G SAS driver as a module to the build. This can be enabled by adding a tunable for mpslsi3_load with a value of YES. This driver is still under development and not yet committed to FreeBSD. It is provided for beta testing only. For production use please consider using a 6G SAS adapter, such as the LSI 9207.
Fixed a bug with netatalk that prevented share browsing from working in the finder on OSX. Also enabled options for fuller-fidelity AFP copies with Mac OS ACLs (ACEs) now stored as ZFS ACLs. Remove the non functional share password field from AFP shares.
Switched from Avahi to mDNSResponder for Zeroconf network configuration, improving the Mac share browsing experience.
Added additional Web API functionality for manipulating ZFS snapshots.
Added IPMI network configuration support for machines with that capability (enabled by setting ipmi_load tunable to YES).
Brought back the FreeNAS 8.x volume manager as a “Manual Setup” option. This volume manager allows manual vdev building and offers no seat belts. Unless you know exactly what you are doing and why you are doing it, using the standard volume manager is highly recommended by the development team!
Made some changes to reporting graphs that segregates reports by type, one type per tab. Add graphs that show individual disk activity.
Fixed a bug that prevented building an encrypted volume using multipath devices.
Update django (used by the WebUI) to 1.6 and dojo to 1.9.2
Add the following ZFS features: enabled_txg hole_birth, extensible_dataset, bookmarks
Add trafshow to the image. This utility gives a CLI view of connections and usage to the FreeNAS box.
Fix kernel module load for fuse. This is needed for importing NTFS volumes.
Add the ability to use a keytab for AD joins. This eliminates the need to use the AD Administrator account to join FreeNAS to AD, closing a long standing issue of needing the AD Admin password in the FreeNAS configuration database.
Updated the LSI 6 Gbps HBA driver (mps) to version 16. Please update the firmware of any mps HBAs to phase 16.This point release for 9.2.1 fixes even more issues found in 9.2.1.1 in CIFS, NFS locking, the new .system dataset, ACLs, migration during upgrades, serial consoles, and a few smaller things. All bugs fixed in 9.2.1.2-RELEASE can be found here (https://bugs.freenas.org/projects/freenas/issues?query_id=39).
From a high level, these are the most significant changes:
Samba (SMB/CIFS support) upgraded to version 4.1.5
Linux Jails now work with UFS
NFS lockd now starts properly at boot time
Serial console misconfiguration is now harder to do.
Logging to .system dataset is now optional. If you have an old syslog dataset (which is how this was formerly done), you are strongly encouraged to transition to the new .system/syslog dataset by enabling that option in System->Settings->Advanced and simply deleting your old syslog dataset.
Bug fixes:
Add a sysctl which already exists, results in GUI traceback
SMB causes CPU to climb up to 100% after 9.2.1.2 update
CIFS - turning on "Enable home directories" prevents smbd4.conf from being created
Update to samba 4.1.6
FreeNAS can't detect disks attached to Marvell 88SX5041 sata ports
pyflakes output
homedirectory path always put in to smb4.conf
AD and LDAP services need manual reconfiguration after an upgrade
Prevent edit of volumes in 'Volume Status'
serial console menu - not working anymore
AFP Share fixed and Work, but now Time Machine option broken
FTP fails to start when syslog dataset is added
Unable to install plugins - libedit.so.7 not found, required by sh
smb4.conf not found
Samba Issues causing High CPUHigh level features:
Samba (SMB/CIFS support) upgraded to version 4.1.6
Netatalk (AFP support) upgraded to version 3.1.1
ZFS replication status is now provided in ZFS Replication UI
The bug preventing FTP from starting when logging to system dataset has been fixed.
Bug fixes:
Replication bailing out fails to send email notifications
Cronjob kinit: krb5_get_kdc_cred: Matching credential not found
replication feedback
Most of the Tripp Lite UPS driver entries are malformed...
CIFS - turning on "Enable home directories" prevents smbd4.conf from being created
Update to samba 4.1.6
SMB causes CPU to climb up to 100% after 9.2.1.2 update
serial console menu - not working anymore
Add a sysctl which already exists, results in GUI traceback
Prevent edit of volumes in 'Volume Status'
AFP Share fixed and Work, but now Time Machine option broken
FTP fails to start when syslog dataset is added
FreeNAS can't detect disks attached to Marvell 88SX5041 sata ports
pyflakes output
homedirectory path always put in to smb4.conf
AD and LDAP services need manual reconfiguration after an upgrade
Unable to install plugins - libedit.so.7 not found, required by sh
smb4.conf not found
Samba Issues causing High CPU