Announcing FreeNAS-8.0.2-RELEASE

[jpaetzel]

The FreeNAS team is pleased to announce FreeNAS 8.0.2-RELEASE. This can be considered a minor release that fixes a few of the more glaring issues in 8.0.1-RELEASE.

http://sourceforge.net/projects/freenas/files/FreeNAS-8.0.2/

Release Notes for FreeNAS 8.0.2-RELEASE


*** IMPORTANT ***

The image size increased in 8.0.1-BETA3. The new size requires a 2 GB
storage device. The GUI upgrade can be used to upgrade a system from BETA3,
BETA4, or RC1 but upgrades from earlier releases can only be done from the CD.
The other option is to save the config, reinstall the new version, then
restore the config.

Major changes since 8.0.1-RELEASE:

- The email subsystem was not working correctly in 8.0.1-RELEASE, which
resultd in the system not being able to send mail, as well as disfunction
of the alerting system in the GUI.

Changes since 8.0.1-RELEASE:

- Allow decimal numbers for a dataset quota. (r8728)

- Fix setting recursive ACLs. (r8270)

- Start proftpd after ix-ssl to use the correct SSL cert. (r8246)

- Use wildcards in cron and rsync jobs instead of listing all values. (r8214, r8211)

- Fix case in iSCSI targets to match the behavior specified by RFC 3722. (r8120)

Changes since 8.0-RELEASE

There's too much to list here, but the high points are:

- Divorced the volume members in the database from the FreeBSD devices.
This resolves an issue where FreeBSD can change devices names and the
GUI doesn't pick up the updates due to the devices names being hard-wired
in the database.

- Support exporting ZFS zvols (virtual devices) as device extents via iSCSI.
8.0 was only able to export physical device nodes or file based extents.

- The GUI now has an event notification system.

- The email backend has been refactored.

- Many many changes in the GUI to help it validate and sanitize inputs that
are passed to the backend daemons.

- Added UPS functionality.

- Added rsync client and server functionality.

- Added the ability to schedule cron jobs in the GUI.

- Vastly improved and reworked snapshot replication.

Errata:

CHAP doesn't work with GlobalSAN initiators on OS X.

Upgrades from FreeNAS 0.7 aren't supported.

The installer doesn't check the size of the install media before attempting
an install. A 2 GB device is required, but the install will appear to
complete successfully on smaller devices, only to fail at boot.

The installer will let you switch from i386 to amd64 architecture and
vice-versa, but some files, such as the rrd files used by the statistics
graphing package are architecture dependent.

Code:

Filename:
FreeNAS-8.0.2-RELEASE-amd64-Full_Install.xz
SHA256 Hash:
4363351d478c3ea5134bc1c9f8258e34f228059cbf98c57d21e04663d1694689

Filename:
FreeNAS-8.0.2-RELEASE-amd64-GUI_Upgrade.xz
SHA256 Hash:
5c0562f8fedcda7d91e23d0ae759135d68d6e32c2e1fb2a75cccc682ea0d5588

Filename:
FreeNAS-8.0.2-RELEASE-amd64.iso
SHA256 Hash:
8980fc423bb8f3596cd2de76944527efd2325d1849e8656bea6be9b20c5369b8

Filename:
FreeNAS-8.0.2-RELEASE-i386-Full_Install.xz
SHA256 Hash:
70b1147781da43f2e1f9025636334d003d81d0d08c975d4166a5e90ed1a90c32

Filename:
FreeNAS-8.0.2-RELEASE-i386-GUI_Upgrade.xz
SHA256 Hash:
5db7d54df355eba6c14da72c107ecb0172557d80ef88bcf5675a5fff60008f8f

Filename:
FreeNAS-8.0.2-RELEASE-i386.iso
SHA256 Hash:
3c75c1797ad796cf249290dfd774bfdf50483455834ea4b41e9c3a26e269319d

 

[ProtoSD]

Josh,

Thanks for new release, I know you guys have a lot on your plates. I was wondering if you could give us an update on the GUI Import feature for the non-native filesystems like NTFS, MSDOSFS, etc.? What is preventing it from working? When should we expect to see it work? I know there are a lot of users looking to see it work and the most searched keywords listed at the bottom of the forum are NTFS and IMPORT ;) I also know there are a lot of people looking to see the disk failure notification work like when a disk goes offline or gets unplugged to test it out.

Thanks a lot to you and the rest of the team for the quick response to problems, willingness to listen to suggestions, and a really nice product!

 

[marcusmarcus]

Installed this release last night and today I had the daily run output and the security run output waiting for me in my email. Thanks for fixing!

 

[Heire]

Also did the gui upgrade (RC1 to 8.0.2) and everything is working fine, good job on the development and keep it comming :)

Only I see there is an option to view zpool status in the disk list, but there is no result. What should be expected there?

 

[Milhouse]

Only I see there is an option to view zpool status in the disk list, but there is no result. What should be expected there?

Same output as you would see from "zpool status" at the CLI (assuming you have a pool/volume, of course). Have you tried clearing your browser cache and trying again?

 

[jfr2006]

Unfortunately and i don't understand why, as soon as i load my config to this releases, the machine locks up during the boot after the first automatic reset :(

When i used a self compiled image by myself, i don't have this problems...

 

[Milhouse]

FYI, I'm still seeing a lot of "noise" (WARNINGs, tdb_fetch_uint32 failures etc.) and also flat out errors (see the grep error for mountd) in the 8.0.2-RELEASE boot sequence - I was under the impression some of these were going to be fixed as I raised them in the 8.0.1 thread.

From 8.0.2-RELEASE AMD64...

Code:

Oct 14 22:52:24 freenas kernel: Starting syslogd.
Oct 14 22:52:24 freenas kernel: Clearing /tmp (X related).
Oct 14 22:52:24 freenas kernel: /etc/rc: WARNING: /etc/exports is not readable.
Oct 14 22:52:24 freenas kernel: /etc/rc: WARNING: failed precmd routine for mountd
...
Oct 14 22:52:24 freenas kernel: Starting lockd.
Oct 14 22:52:24 freenas kernel: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Oct 14 22:52:28 freenas kernel: Starting smartd.
...
Oct 14 22:52:53 freenas kernel: tdbsam_convert_backup: updated /var/etc/private/passdb.tdb file.
Oct 14 22:52:53 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 1 (min password length), returning 0
Oct 14 22:52:53 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 2 (password history), returning 0
Oct 14 22:52:53 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 3 (user must logon to change password), returning 0
Oct 14 22:52:53 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 4 (maximum password age), returning 0
Oct 14 22:52:53 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 5 (minimum password age), returning 0
Oct 14 22:52:53 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 6 (lockout duration), returning 0
Oct 14 22:52:53 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 7 (reset count minutes), returning 0
Oct 14 22:52:53 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 8 (bad lockout attempt), returning 0
Oct 14 22:52:53 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 9 (disconnect time), returning 0
Oct 14 22:52:53 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 10 (refuse machine password change), returning 0
Oct 14 22:52:53 freenas kernel: Importing account for root...ok
...
Oct 14 22:53:08 freenas kernel: Starting mountd.
Oct 14 22:53:15 freenas kernel: Usage: grep [OPTION]... PATTERN ...
Oct 14 22:53:15 freenas kernel: Try `grep --help' for more information.
Oct 14 22:53:15 freenas kernel: Waiting for http...

 

[Raist3001]

I really thought the NTFS import problem was going to be fixed in this release. Sadly it is not.

 

[Daisuke]

Hi Josh,

Thank you for the release. I upgraded without any issues from 8.0.1 to 8.0.2 (FreeNAS-8.0.2-RELEASE-amd64-GUI_Upgrade.xz). However, the issues I reported in 8.0.1 are still present. Every time I start FreeNAS, I get these errors:

Code:

Oct 15 14:51:28 pluto kernel: SMP: AP CPU #1 Launched!
Oct 15 14:51:28 pluto kernel: SMP: AP CPU #2 Launched!
Oct 15 14:51:28 pluto kernel: SMP: AP CPU #3 Launched!
Oct 15 14:51:28 pluto kernel: GEOM: da0s1: geometry does not match label (16h,63s != 255h,63s).
Oct 15 14:51:28 pluto kernel: GEOM: da0s2: geometry does not match label (16h,63s != 255h,63s).
Oct 15 14:51:28 pluto kernel: Trying to mount root from ufs:/dev/ufs/FreeNASs2a
Oct 15 14:51:28 pluto kernel: ZFS filesystem version 4
Oct 15 14:51:28 pluto kernel: ZFS storage pool version 15
Oct 15 14:51:28 pluto root: /etc/rc: WARNING: /etc/exports is not readable.
Oct 15 14:51:28 pluto root: /etc/rc: WARNING: failed precmd routine for mountd
Oct 15 14:51:28 pluto root: /etc/rc: WARNING: failed precmd routine for vmware_guestd

If I understand correctly, the geometry issues are just noise that I can ignore safely.
However, /etc/exports is readable.
-rw-r--r-- 1 root wheel 55 Oct 15 14:52

I also have the previously reported error related to the vfs.zfs.prefetch_disable setting, that I fixed easy:

Code:

% mount -uw /
% nano /boot/loader.conf
% mount -ur /

I added again this line into /boot/loader.conf:
vfs.zfs.prefetch_disable=0

Still, I should not be doing this... the system should detect automatically that I have 4GB of RAM installed. There is an interesting article that highlights the same errors I listed above.

 

[lagony]

Unprivileged port?

Howdy,

Thanks for the release! I've performed an error free GUI update from 8.0.1 RC4 (I believe) to 8.0.2. However, I do receive the same errors that TECK has experienced on start up. I've also noticed something else with NFS. I use XBMC to connect to an NFS share on my FreeNAS box to access my media. Although it took a lot of trial and error to get this to work (I'm still really new to FreeNAS...), I was able to get the NFS share setup correctly and XBMC was talking beautifully with the share. However, this morning after I performed the update from 8.0.1 RC4 to 8.0.2, XBMC can no longer see my NFS share and I get the following error on my FreeNAS box:

Code:

Oct 15 14:14:29 freenas mountd[2288]: mount request from ip_address from unprivileged port

I tried deleting and recreating the NFS share, but the same error occurs. Since I'm rather new to FreeNAS and FreeBSD in general, I'm wondering if there is something that changed and requires me to setup the share differently, or if there is something else that I might be missing. Any assistance would be greatly appreciated!

 

[tmd3vt]

Is anyone else having issues with deleting or in FreeNAS language "exporting volume"s in the new release? I can create them but not delete them. I click the button and nothing happens. Scrubbing does the same thing. I did a new full install over top my 8.0 install and tried using my old config too? Neither work. Also when I try to create AFS shares I fill everything out and click okay and everything gets erased and it says I need to input Disk Discovery which was filled out before I hit okay. Some strange stuff is going on. My 8.0 system worked great on the same computer. This is using the amd64 image.

 

[Milhouse]

I also have the previously reported error related to the vfs.zfs.prefetch_disable setting, that I fixed easy:

Code:

% mount -uw /
% nano /boot/loader.conf
% mount -ur /

I added again this line into /boot/loader.conf:
vfs.zfs.prefetch_disable=0

Still, I should not be doing this... the system should detect automatically that I have 4GB of RAM installed. There is an interesting article that highlights the same errors I listed above.

Even with 4GB (4096MB) of RAM installed, the amount of physical memory detected by FreeBSD will be every so slightly less than 4GB, eg. 4048MB, in which case the current behaviour is entirely correct.

On my 8GB system (8192MB) the amount of detected physical memory is 8145MB, so slightly less than 8GB. This may be due to the legacy of the PC hardware design, with memory being reserved (and therefore unavailable to the OS) by the BIOS etc.

In short, the test to enable prefetch is very strict - you must have at least 4GB of *detected* physical memory for prefetch to be enabled, one byte less and it will be disabled.

 

[lyzanxia]

Yeah, I really hope disk failure detection,notification & easy replacing a disk is on top on their priority list. This in my opinion is crucial to a nas system.

Josh,

Thanks for new release, I know you guys have a lot on your plates. I was wondering if you could give us an update on the GUI Import feature for the non-native filesystems like NTFS, MSDOSFS, etc.? What is preventing it from working? When should we expect to see it work? I know there are a lot of users looking to see it work and the most searched keywords listed at the bottom of the forum are NTFS and IMPORT ;) I also know there are a lot of people looking to see the disk failure notification work like when a disk goes offline or gets unplugged to test it out.

Thanks a lot to you and the rest of the team for the quick response to problems, willingness to listen to suggestions, and a really nice product!

 

[Daisuke]

Even with 4GB (4096MB) of RAM installed, the amount of physical memory detected by FreeBSD will be every so slightly less than 4GB, eg. 4048MB, in which case the current behaviour is entirely correct.

On my 8GB system (8192MB) the amount of detected physical memory is 8145MB, so slightly less than 8GB. This may be due to the legacy of the PC hardware design, with memory being reserved (and therefore unavailable to the OS) by the BIOS etc.

In short, the test to enable prefetch is very strict - you must have at least 4GB of *detected* physical memory for prefetch to be enabled, one byte less and it will be disabled.

Thank you for the great explanation. Right now, FreeNAS detects 4081MB in GUI. Since my NAS has a Supermicro X7SPA-HF-D525-O Intel Atom D525 1.8GHz mobo, I cannot use more than 4GB of RAM. So I guess I'm stuck doing the file edit on every upgrade. :)

 

[rnicolas]

I wonder if it's worth upgrading just so I can get my email notifications working :-/

 

[ProtoSD]

Since my NAS has a Supermicro X7SPA-HF-D525-O Intel Atom D525 1.8GHz mobo, I cannot use more than 4GB of RAM. So I guess I'm stuck doing the file edit on every upgrade. :)

Just copy loader.conf to your storage and after the upgrade finishes copy it back. Someone in one of the threads did some testing with this turned on and off and I seem to remember the difference in results wasn't that significant, at least for smaller systems like yours and mine.

 

[gustavca]

Hi, I just tried to upgrade the system from 8.0.1 release to 8.0.2 (both of them AMD64) through the GUI upgrade. Everything seamed to work fine during the upgrade process and the system rebooted automatically. However after reboot the system holds after the screen displaying:

F1 FreeBSD
F2 FreeBSD
Boot: F1

It just continues printing "######" while the USB memory LED shows that it is active. First i thought this was fine but after having waited about one hour i decided to force a reboot and try the fallback option. Doing so does however not seem to help since the system wont load at all after choosing the F2 option.

Now I´m not sure what to do next, should I do a full reinstallation of the system from image to the USB drive? or is there possibly any way of checking the log files on the USB drive first? Above everything I of course were stupid enough not to backup the config before the upgrade so I´d really like to try other options before I wipe out the USB drive.

 

[Milhouse]

Above everything I of course were stupid enough not to backup the config before the upgrade so I´d really like to try other options before I wipe out the USB drive.

If you are able to mount the partitions via F2, you can copy off your config from the /data directory - it will be called freenas-v1.db - then try restoring it to a new installation.

 

[audix]

I am upgrading from r7555 with 8.0.2.RELEASE-amd64-GUI_upgrade. I do a firmware update the same as I have done several times before. After hitting "Apply Update" is says "waiting" for some time, and then it reboots. But the update never occurs. I am not seeing any error messages. Any ideas? (maybe update to 8.0.1 before??)

Edit. Tried with 8.0.1.Release. Same results.
Any ideas before I do a new install?

 

[Milhouse]

I am upgrading from r7555 with 8.0.2.RELEASE-amd64-GUI_upgrade. I do a firmware update the same as I have done several times before. After hitting "Apply Update" is says "waiting" for some time, and then it reboots. But the update never occurs. I am not seeing any error messages. Any ideas? (maybe update to 8.0.1 before??)

Edit. Tried with 8.0.1.Release. Same results.
Any ideas before I do a new install?

From the announcement:

The image size increased in 8.0.1-BETA3. The new size requires a 2 GB
storage device. The GUI upgrade can be used to upgrade a system from BETA3,
BETA4, or RC1 but upgrades from earlier releases can only be done from the CD.
The other option is to save the config, reinstall the new version, then
restore the config.

You can't perform an in-place GUI upgrade to 8.0.1-RELEASE or 8.0.2-RELEASE from a release prior to 8.0.1-BETA3 - you must create a new install.