Announcing FreeNAS 8.0.1-RELEASE

[jpaetzel]

I'm pleased to announce on behalf of the FreeNAS development team FreeNAS 8.0.1-RELEASE, available for download at:

https://sourceforge.net/projects/freenas/files/FreeNAS-8.0.1/


*** 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-RC2:

- django has been updated to 1.3.1 to address multiple security advisories.

- istgt has been updated to 20110928

- Base system has been updated to FreeBSD 8.2-p3, which addresses
http://security.freebsd.org/advisories/FreeBSD-SA-11:05.unix.asc
http://security.freebsd.org/advisories/FreeBSD-SA-11:04.compress.asc

Changes since 8.0.1-RC2

- Fix the regex used to validate iSCSI target names so that - is an
allowed character. (r7827)

- Multiple improvements to the UPS service.
(r7841, r7842, r7843, r7844, r7845, r7846, r7847, r7848, r7849)

- Fix a bug in the GUI where zvols from multiple pools caused GUI corruption.
(r7859)

- Add a button to zpools that will display zpool status in a tab.

- Set each LUN in an iSCSI target to a unique serial number. This allows
vmware ESXi to see multiple LUNs per target. (r7878)

- Change the encryption type in the LDAP config screen to a choicebox
instead of requiring freeform text input. (r7881)

- Remove DDP option from AFP server config. (r7883)

- Fix typo so that hosts allow and deny actually get populated in rsyncd.conf.
(r7906)

- Fix deleting snapshots. (r7916)

- Add a button to volumes to manually kick off a scrub of ZFS volumes. (r7943)

- Fix smartd.conf generation bug. (r7956)

- Fix a bug preventing the import of zpools created on Solaris (r7971)

- Allow adding a public key for user ssh authentication. (r8002)

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.1-RELEASE-amd64-Full_Install.xz
SHA256 Hash:
e70e72c17f947463845a9fb2fdfa64bfd92030e9ec22abc7e2b79afb9924ad88

Filename:
FreeNAS-8.0.1-RELEASE-amd64-GUI_Upgrade.xz
SHA256 Hash:
093aee7f17df8f593fd6038d8c38f1c6ac23bc7eec91ba3511206475f65b7aa5

Filename:
FreeNAS-8.0.1-RELEASE-amd64.iso
SHA256 Hash:
fcac5803bd973bb258838add0edc2b8658238018c2f5c2f98e2639d065d79b15

Filename:
FreeNAS-8.0.1-RELEASE-i386-Full_Install.xz
SHA256 Hash:
933d8985475cd88fe9339bc46f9f83abac0e7c0691d1cac3eaa7ca38b3fed49d

Filename:
FreeNAS-8.0.1-RELEASE-i386-GUI_Upgrade.xz
SHA256 Hash:
dcb82eb99c8cf8c1a35614837c3df5fb46370cfe4d77f0cd7a73bf4b63259a09

Filename:
FreeNAS-8.0.1-RELEASE-i386.iso
SHA256 Hash:
463832e8c03d0c404ca1a6c443cdcf817d48c1527759dda3fe29f0f81c15ce6b

 

[Milhouse]

So far so good, although still getting unpleasant "noise" during boot (AMD64, from GUI update) - see below:

Code:

Sep 30 23:47:51 freenas kernel: /etc/rc: WARNING: /etc/exports is not readable.
Sep 30 23:47:51 freenas kernel: /etc/rc: WARNING: failed precmd routine for mountd
...
Sep 30 23:47:51 freenas kernel: /etc/rc: WARNING: failed precmd routine for vmware_guestd
...
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 1 (min password length), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 2 (password history), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 3 (user must logon to change password), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 4 (maximum password age), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 5 (minimum password age), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 6 (lockout duration), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 7 (reset count minutes), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 8 (bad lockout attempt), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 9 (disconnect time), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 10 (refuse machine password change), returning 0
...
Sep 30 23:48:09 freenas kernel: Starting mountd.
Sep 30 23:48:15 freenas kernel: Usage: grep [OPTION]... PATTERN ...
Sep 30 23:48:15 freenas kernel: Try `grep --help' for more information.
Sep 30 23:48:15 freenas kernel: Waiting for http...

At least the web interface is now bound correctly! :)

 

[Milhouse]

How is 8.0.1-RELEASE determining the disks for SMART tests? I have a problem selecting any of the disks in my ZFS pool (two vdevs, 4 disks each) - see the attached screenshot.

I'm using an LSI 9211-8i controller. The following is the output from "smartctl -a" for one of the disks connected to this controller:

Code:

[root@freenas] /var/log# smartctl -a /dev/da0
smartctl 5.41 2011-06-09 r3365 [FreeBSD 8.2-RELEASE-p3 amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint F4 EG (AFT)
Device Model:     SAMSUNG HD204UI
Serial Number:    S2HGJ1BZ906877
LU WWN Device Id: 5 0024e9 004043c62
Firmware Version: 1AQ10001
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Fri Sep 30 23:59:10 2011 BST

==> WARNING: Using smartmontools or hdparm with this
drive may result in data loss due to a firmware bug.
****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
Buggy and fixed firmware report same version number!
See the following web pages for details:
http://www.samsung.com/global/business/hdd/faqView.do?b2b_bbs_msg_id=386
http://sourceforge.net/apps/trac/smartmontools/wiki/SamsungF4EGBadBlocks

SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (20880) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 255) minutes.
SCT capabilities:              (0x003f) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   071   067   025    Pre-fail  Always       -       9079
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       466
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       3080
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       181
181 Program_Fail_Cnt_Total  0x0022   100   100   000    Old_age   Always       -       13220292
191 G-Sense_Error_Rate      0x0022   252   252   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   064   061   000    Old_age   Always       -       32 (Min/Max 17/39)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       0
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       542

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Completed [00% left] (0-65535)
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

smartd also won't start, fails with the error:

Code:

Oct  1 00:02:04 freenas freenas[1950]: Executing: /usr/sbin/service smartd restart
Oct  1 00:02:04 freenas freenas: smartd not running? (check /var/run/smartd.pid).
Oct  1 00:02:04 freenas freenas: Starting smartd.
Oct  1 00:02:04 freenas smartd[3335]: Configuration file /usr/local/etc/smartd.conf parsed but has no entries (like /dev/hda)
Oct  1 00:02:04 freenas root: /usr/local/etc/rc.d/smartd: WARNING: failed to start smartd
Oct  1 00:02:04 freenas freenas: /usr/local/etc/rc.d/smartd: WARNING: failed to start smartd
Oct  1 00:02:05 freenas freenas[1950]: Executing: /bin/pgrep -F /var/run/smartd.pid smartd

My "smartd.conf":

Code:

[root@freenas] /var/log# cat /usr/local/etc/smartd.conf
################################################
# smartd.conf generated by FreeNAS
################################################
[root@freenas] /var/log#

 

[ProtoSD]

Hmmm, It's probably my imagination, but when I tried to upgrade from the GUI / Firmware Update it fails. I've quadruple checked the HASH, and made sure it was for the correct file. It tells me invalid file or checksum and then next to the "Choose File" button, the filename I choose disappeared. I didn't have any problem going from beta4 to RC2.

 

[Milhouse]

AMD64 GUI Upgrade worked fine for me, upgrading from RC2.

 

[ProtoSD]

Yeah, it's my normal luck. I am upgrading from AMD64 - RC2. I've tried rebooting, running sha256 on the file and comparing the checksum..... I had the upgrade file on both my NAS and on the system I'm initiating the upgrade from. It should be a 'firmware update' and not a service pack, although that is another misleading thing that people get mixed up about....

I'm curious to hear if anyone else is having trouble doing the GUI update from RC2.

 

[ProtoSD]

I just noticed what the problem is I think....
ALL of the hashes above have a space in them!

That was it... but it's weird, you can see the space in the posting and when you copy and paste it, but if you try to edit the post (as a moderator), the spaces aren't there!

 

[Milhouse]

I just noticed what the problem is I think....
ALL of the hashes above have a space in them!

Thought you'd be wise to that by now! ;-)

This perpetually annoying issue would be fixed if the OP would put {code} tags around the filenames and hashes. I'd edit the initial post, but don't want to offend.

Edit: Oh sod it, editing the first post. :)

 

[ProtoSD]

I think we both had the same idea, I was trying to edit it also. I think it was better to get it fixed ASAP than wait for the OP to notice the mistake and have people getting upset... ;-) I'm just getting blind in my mid-age....

 

[gcooper]

So far so good, although still getting unpleasant "noise" during boot (AMD64, from GUI update) - see below:

Code:

Sep 30 23:47:51 freenas kernel: /etc/rc: WARNING: /etc/exports is not readable.
Sep 30 23:47:51 freenas kernel: /etc/rc: WARNING: failed precmd routine for mountd
...
Sep 30 23:47:51 freenas kernel: /etc/rc: WARNING: failed precmd routine for vmware_guestd
...
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 1 (min password length), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 2 (password history), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 3 (user must logon to change password), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 4 (maximum password age), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 5 (minimum password age), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 6 (lockout duration), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 7 (reset count minutes), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 8 (bad lockout attempt), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 9 (disconnect time), returning 0
Sep 30 23:47:56 freenas kernel: account_policy_get: tdb_fetch_uint32 failed for type 10 (refuse machine password change), returning 0
...
Sep 30 23:48:09 freenas kernel: Starting mountd.
Sep 30 23:48:15 freenas kernel: Usage: grep [OPTION]... PATTERN ...
Sep 30 23:48:15 freenas kernel: Try `grep --help' for more information.
Sep 30 23:48:15 freenas kernel: Waiting for http...

At least the web interface is now bound correctly! :)

- Fixed the mountd noise.
- Quieted down pdbedit a bit (that's what's printing out the tdb* noise above).
- Fixed the httpd noise.

 

[gcooper]

Yeah, it's my normal luck. I am upgrading from AMD64 - RC2. I've tried rebooting, running sha256 on the file and comparing the checksum..... I had the upgrade file on both my NAS and on the system I'm initiating the upgrade from. It should be a 'firmware update' and not a service pack, although that is another misleading thing that people get mixed up about....

I'm curious to hear if anyone else is having trouble doing the GUI update from RC2.

Part of the reason why I hate the name choice. "Service Pack" should be "Hot Patch".

 

[gcooper]

How is 8.0.1-RELEASE determining the disks for SMART tests? I have a problem selecting any of the disks in my ZFS pool (two vdevs, 4 disks each) - see the attached screenshot.

I'm using an LSI 9211-8i controller. The following is the output from "smartctl -a" for one of the disks connected to this controller:

I'll look at this this weekend. This might affect customers.

 

[jfr2006]

Tried this version. Boot up.. Then update with my config. Reboot and then it stays there hang up at the Press F1 forever. Why: because the installation version creates a 1GB partition, not 2 GB

When is this bug going to be corrected? Have to go compile my own version :(

 

[gcooper]

Tried this version. Boot up.. Then update with my config. Reboot and then it stays there hang up at the Press F1 forever. Why: because the installation version creates a 1GB partition, not 2 GB

When is this bug going to be corrected? Have to go compile my own version :(

1. How big is your CF/SD/memstick?
2. How did you upgrade (CD, .xz upgrade image)?

BTW, don't do the update as "firmware update", not "service pack". "service pack" images currently aren't being distributed by the FreeNAS project; given how many people might have been bit by this confusing terminology, I'm tempted just to change the wording and be done with it because Windows users are used to service packs being HUGE updates (even though technically they're updates between official release versions, kind of like a subminor version release).

I've made the install/upgrade process more robust on trunk (after breaking things by accident for a week.. heh), but it didn't get back into 8.0.1 because it was too bleeding edge.

 

[jfr2006]

Hi:

1. It's 4GB size
2. I pick up the .iso file and made an fresh and clean installation

Regards.

 

[jim82]

Anyone else having problems with setting the permissions? I've tried setting them from the GUI, with no result. It just hangs there. Setting them from CLI work fine of course.

Completely clean install from the x64 ISO.

 

[Durkatlon]

Hmm, seems I'm no longer getting the nightly emails since upgrading. I tried sending a test email from the GUI and that worked fine.

 

[Milhouse]

Hmm, seems I'm no longer getting the nightly emails since upgrading. I tried sending a test email from the GUI and that worked fine.

I agree - I haven't received the "security run output" or "daily run output" emails since upgrading from RC2 to Release. Test email is working correctly.

I noticed this in /var/log/maillog which looks like the smoking gun...

Code:

[root@freenas] /var/log# cat maillog
Oct  3 02:31:10 freenas newsyslog[1129]: logfile first created
Oct  3 03:01:42 freenas freenas[6516]: Traceback (most recent call last):
Oct  3 03:01:42 freenas freenas[6516]:   File "/usr/local/www/freenasUI/common/system.py", line 146, in send_mail
Oct  3 03:01:42 freenas freenas[6516]:     msg)
Oct  3 03:01:42 freenas freenas[6516]:   File "/usr/local/lib/python2.7/smtplib.py", line 724, in sendmail
Oct  3 03:01:42 freenas freenas[6516]:     raise SMTPRecipientsRefused(senderrs)
Oct  3 03:01:42 freenas freenas[6516]: SMTPRecipientsRefused: {'root': (553, "5.1.2 We weren't able to find the recipient domain. Please check for any\n5.1.2 spelling errors, and make sure you didn't enter any spaces, periods,\n5.1.2 or other punctuation after the recipient's email address. h39sm20951060wbo.0")}
Oct  3 03:01:42 freenas freenas[6575]: Traceback (most recent call last):
Oct  3 03:01:42 freenas freenas[6575]:   File "/usr/local/www/freenasUI/common/system.py", line 146, in send_mail
Oct  3 03:01:42 freenas freenas[6575]:     msg)
Oct  3 03:01:42 freenas freenas[6575]:   File "/usr/local/lib/python2.7/smtplib.py", line 724, in sendmail
Oct  3 03:01:42 freenas freenas[6575]:     raise SMTPRecipientsRefused(senderrs)
Oct  3 03:01:42 freenas freenas[6575]: SMTPRecipientsRefused: {'root': (553, "5.1.2 We weren't able to find the recipient domain. Please check for any\n5.1.2 spelling errors, and make sure you didn't enter any spaces, periods,\n5.1.2 or other punctuation after the recipient's email address. fo7sm6086819wbb.20")}

I haven't changed the root user setup - the root user is configured exactly as it was in RC2. I can also confirm the email address for the root user remains correctly set, ie. it is my normal public email address.

 

[ProtoSD]

Looks like a bug, I just checked my folder for those messages and the last one I got was before updating to 8.01 from RC2. I tried checking my logfile, but it's already rolled over. I'll have to have a look in the morning.... Ugghhh.

 

[Durkatlon]

I have the same entries in my maillog. Appears to be a bug with the mail configuration. If you try to send a manual mail to root (mail -s "test email" root) you get the same error. If you change the recipient to root@localhost everything appears fine, but no email ever arrives. If you change it to a fully qualified username (e.g. you@yourdomain.com) everything works.

I don't care too much about the nightly emails so I'll probably just wait for the official fix, but for now if you must receive the emails, edit the "daily_output" variable in /etc/defaults/periodic.conf and /conf/base/etc/defaults/periodic.conf to have your fully qualified email address and you should be back in business.