Several items have changed since 9.2.1 due to various bug fixes. There were eight bug fix releases between FreeNAS® 9.2.1 and 22.214.171.124, where:
This Errata provides a listing of screens and features that differ from the 9.2.1 Users Guide. It is organized by the names of the sections which have changed in numerical order.
FreeNAS® 126.96.36.199 can be downloaded from the download page of the FreeNAS® website.
If you prefer to install FreeNAS® using a menu-driven installer, download the ISO or USB image that matches the architecture of the system you will install onto (32- or 64-bit) and burn it to a CDROM.
you can also write the .usb file to a USB thumbdrive. Since this file is not compressed, it does not need to be uncompressed first using xzcat or 7-Zip.
When using dd, the command shown in the examples will change to:
dd if=FreeNAS-188.8.131.52-RELEASE-x64.usb of=/dev/da0 bs=64k
Burn the downloaded .iso or .usb file to a CDROM.
Remove the last line in the first paragraph.
Figure 3.2d: Managing User Accounts
If you click a user account, the following buttons will appear for that account:
Add this button to “This tab also contains the following buttons:”
Performance Test: runs a series of performance tests and prompts to save the results as a tarball. Since running the tests can affect performance, a warning is provided and the tests should be run at a time that will least impact users.
The “System Dataset” tab, shown in Figure 4.6e, is used to select the pool which will contain the persistent system dataset. The system dataset stores debugging core files and Samba4 metadata such as the user/group cache and share level permissions. If the FreeNAS® system is configured to be a Domain Controller, all of the domain controller state is stored there as well, including domain controller users and groups.
The system dataset can optionally be configured to also store the system log and the Reporting information. If there are lots of log entries or reporting information, moving these to the system dataset will prevent /var/ from filling up as /var/ has limited space.
Figure 4.6e: System Dataset Tab
Use the drop-down menu to select the ZFS volume (pool) to contain the system dataset.
To also store the system log on the system dataset, check the “Syslog” box.
To also store the reporting information, check the “Reporting Database” box.
If you change the pool storing the system dataset at a later time, FreeNAS® will automatically migrate the existing data in the system dataset to the new location.
Figure 6.2b: Adding a Replication Task
In Table 6.2a, replace the entry for “Enable High Speed Ciphers” with:
|Encryption Cipher||drop-down menu||used to select whether or not the data is encrypted during transmission; choices are Standard, Fast, or Disabled|
Add this entry to Table 6.2a:
|Replication Stream Compression||drop-down menu||used to select whether or not the data is compressed during transmission; choices are Off, lz4 (fastest), pigz (all rounder), or plzip (best compression)|
Figure 6.3i: Creating a ZFS Dataset
Add extra entry to Table 6.3d: ZFS Dataset Options:
|Share type||drop-down menu||select the type of share that will be used on the dataset; choices are UNIX for an NFS share, Windows for a CIFS share, or Apple for an AFP share|
Figure 6.3q: Changing Permissions on a Volume or Dataset
In step 4, remove this line:
Server name: freenas
In Step 4, remove this bullet:
First sentence changed to: If you would like each user to authenticate before accessing the CIFS share, configure the share as follows:
Remove the first bullet for “Authentication Model” in Step 5.
Figure 8.2a: AFP Configuration
Add this entry to Table 8.2a: AFP Configuration Options
|Database Path||string||specify the path to store the CNID databases used by AFP (default is the root of the volume); the path must be writable|
Figure 8.3a: Configuring CIFS
Remove these entries from Table 8.3a: CIFS Configuration Options:
Add these entries to Table 8.3a: CIFS Configuration Options:
|Use syslog||checkbox||logs most events to syslog instead of the samba log files|
|Server minimum protocol||drop-down menu||the minimum protocol version the server will support where the default of —— sets automatic negotiation; refer to Table 8.3b for descriptions|
|Server maximum protocol||drop-down menu||the maximum protocol version the server will support; refer to Table 8.3b for descriptions|
|Allow execute always||checkbox||if checked, Samba will allow the user to execute a file, even if that user’s permissions are not set to execute|
|Bind IP Addresses||checkbox(es)||used to specify which IP address(es) the CIFS service will listen on|
Add new table:
Table 8.3b: Description of SMB Protocol Versions
|CORE||used by DOS|
|COREPLUS||used by DOS|
|LANMAN1||used by Windows for Workgroups, OS/2, and Windows 9x|
|LANMAN2||used by Windows for Workgroups, OS/2, and Windows 9x|
|NT1||used by Windows NT|
|SMB2||used by Windows 7; same as SMB2_10|
|SMB2_02||used by Windows Vista|
|SMB2_10||used by Windows 7|
|SMB2_22||used by early Windows 8|
|SMB2_24||used by Windows 8 beta|
|SMB3||used by Windows 8|
|SMB3_00||used by Windows 8, mostly the same as SMB2_24|
Windows 8.1 and Windows Server 2012 R2 use SMB3.02 which is not yet supported by Samba.
Change testparm command to:
Add the following tips:
If clients have problems connecting to the CIFS share, go to Services ‣ CIFS and verify that “Server maximum protocol” is set to “SMB2”.
It is recommended to use a dataset for CIFS sharing. When creating the dataset, make sure that the “Share type” is set to Windows.
Do not use chmod to attempt to fix the permissions on a CIFS share as it destroys the Windows ACLs. The correct way to manage permissions on a CIFS share is to manage the share security from a Windows system as either the owner of the share or a member of the group the share is owned by. To do so, right-click on the share, click “Properties” and navigate to the “Security” tab. If you already destroyed the ACLs using chmod, winacl can be used to fix them. Type winacl from “Shell” for usage instructions.
Add the following entry to Table 8.4a: Active Directory Configuration Options:
|Windbind NSS Info||drop-down menu||select the service for retrieving the user’s home directory and login shell; choices are use sfu (Services for Unix, version 3.x), sfu20 (Services for Unix, version 2.0), or rfc2307 (use LDAP)|
Figure 8.7g Target Global Configuration Variables
Add the following entries to Table 8.7f: Target Global Configuration Settings:
|Enable experimental target||checkbox||this option is for beta testers of kernel iSCSI; requires a reboot|
|Enable multithreaded mode||checkbox||do not check as experimental|
Figure 8.7i: Associating iSCSI Targets/Extents
Add this entry to Table 8.7g: Target/Extents Configuration Settings:
|LUN ID||drop-down menu||specify the ID of the LUN; the default of Auto will select the next available LUN ID, starting at 0|
Figure 8.12b: Permissions Required by SSH Chroot
Figure 9.1a: Using Plugins to Install a PBI
Add the following to the list of PBIs:
Remove the following from the list of PBIs:
Add the following type of jail:
Add VirtualBox to the “Description” of “type” in Table 10.2a.
Figure 10.3a: Listing of Default Jail Templates
Change the bullet on “Instances” to read:
Change second last paragraph to:
Reporting data is saved, allowing you to view and monitor usage trends over time. By default, reporting data is saved to /data/rrd_dir.tar.bz2 and should be preserved across system upgrades and at shutdown. To instead save this data to the system dataset, check the “Reporting database” box in System ‣ Settings ‣ System Dataset.
Change bullet for the Bug Tracker to:
The “FreeNAS 4 N00bs” forum has been renamed to “New to FreeNAS?”.