FreeNAS 8.0.1-BETA2

[jpaetzel]

Release Notes for FreeNAS 8.0.1-BETA2

This is the second of three planned betas in the 8.0.1 release cycle.

Most of the changes from BETA1 are bug fixes. In particular several
bugs have been fixed in the migrations from 8.0-RELEASE. The system
was not relabeling ZFS volumes to use the new devicename-independent
naming scheme correctly in BETA1. Also the database migration
scrips in BETA1 do not migrate NFS shares properly.

Changes since 8.0.1-BETA1:

The upgrade/migration scripts have been improved. In previous versions
failure of the database upgrade was easy to miss, and it could leave the
system booting to single user mode with error messages that had nothing to
do with the root issue. This has been rectified. If a database migration
does fail, the error message will be clear as to what happened, also the
system will save diagnostic information that can be used by the developers
to recover from the failed migration as well as make changes to prevent the
issue from affecting users in the future.

iSCSI has been improved. The SCSI serial number can be set on a per target
basis. This fixes an issue where MMIO was seeing different FreeNAS server
as the same device. Multiple IPs can also be specified per portal.

The ssh daemon now logs to /var/log/auth.log

Several fixes have been incorporated into the volume import procedure.

Several fixes and improvements have been made to the remote replication
process.

The system handles the timezone setting better.

CIFS now defaults to AIO enabled.

Filename:
FreeNAS-8.0.1-BETA2-amd64-Full_Install.xz
SHA256 Hash:
7e2c0e976054af0cf5438af21284e206f191fe8c5043cb8393d2b727bb74f380

Filename:
FreeNAS-8.0.1-BETA2-amd64-GUI_Upgrade.xz
SHA256 Hash:
9209e2806bb52c66a10e22bb60d81703b341e453a0276a969ccd32600690f9e5

Filename:
FreeNAS-8.0.1-BETA2-amd64.iso
SHA256 Hash:
1875774ab7973185fe31ccb7c6ac61e27d8d1c9b5537a9a167839eca5fc2c1cc

Filename:
FreeNAS-8.0.1-BETA2-i386-Full_Install.xz
SHA256 Hash:
27e2791183f50bfd9fcfeb9cb6483e23e1e160d3748484a507197d779d7d27cf

Filename:
FreeNAS-8.0.1-BETA2-i386-GUI_Upgrade.xz
SHA256 Hash:
2052439339f47186dd8eb7c0703025e5001f031f3c307e85c94f653cdb077514

Filename:
FreeNAS-8.0.1-BETA2-i386.iso
SHA256 Hash:
057489385b9c4a222d0e4cb441238ee25456b06766fb8b44cc3571b9e43d7edf

 

[esamett]

"Invalid firmware or checksum"
Filename:
FreeNAS-8.0.1-BETA2-amd64-GUI_Upgrade.xz
SHA256 Hash:
9209e2806bb52c66a10e22bb60d81703b341e453a0276a969c cd32600690f9e5

I think scrub was working in background.

 

[William Grzybowski]

"Invalid firmware or checksum"
Filename:
FreeNAS-8.0.1-BETA2-amd64-GUI_Upgrade.xz
SHA256 Hash:
9209e2806bb52c66a10e22bb60d81703b341e453a0276a969c cd32600690f9e5

I think scrub was working in background.

Did you notice that there is a "space" in the hash, right?
And should be:
9209e2806bb52c66a10e22bb60d81703b341e453a0276a969ccd32600690f9e5

 

[esamett]

checked and failed again...

 

[mrc]

I download update now, sha256 for FreeNAS-8.0.1-BETA2-amd64-GUI_Upgrade.xz is

Code:

9209e2806bb52c66a10e22bb60d81703b341e453a0276a969ccd32600690f9e5

without any spaces.

Maybe, this spaces is forum engine or another bug; look at checksums in http://sourceforge.net/projects/freenas/files/FreeNAS-8.0.1/README/download

 

[esamett]

you are correct mrc. good pickup. The file on the server has a different hash# than that posted on this forum. the hash code on the download site matches the file available there.

 

[Tekkie]

Perhaps the release notes should be extended to say that the update will now auto-reboot the system. ;)

 

[jfr2006]

I have my compiled version installed (FreeNAS-8r6613M-amd64) and it was created to make full use of a 2GB USB stick, so i end up with around 393MB free to add packages. I tried to upgrade this version to the 8.0.1 beta, and it "reformated" all the partitions back to the 1GB use mode, so no free space. Will this 8.0.2 beta do the same? If so, when can we start to choose the space we want to use?

 

[William Grzybowski]

I have my compiled version installed (FreeNAS-8r6613M-amd64) and it was created to make full use of a 2GB USB stick, so i end up with around 393MB free to add packages. I tried to upgrade this version to the 8.0.1 beta, and it "reformated" all the partitions back to the 1GB use mode, so no free space. Will this 8.0.2 beta do the same? If so, when can we start to choose the space we want to use?

Yes, it will...
8.0.x series does not support of install of custom packages, everything you do is on your self, so build your own images everytime... or wait a version that supports custom packages...

 

[joeschmuck]

Yes, it will...
8.0.x series does not support of install of custom packages, everything you do is on your self, so build your own images everytime... or wait a version that supports custom packages...

What drives this action? I like to compile every few days and test out the new changes plus I modify ix-ataidle file so the HDD Standby will actually function properly. So it would be nice to understand why and better yet, how to do a local compile and have it be compatible with an official release.

Thanks,
Mark

 

[William Grzybowski]

This is just a "feature" of NanoSD and how it works, the firmware upgrade process simply overwrite the whole partition and not the files

 

[astronaute]

How long do I have to wait for the upgrade to finish via GUI ?
It's been 15 mns and I still don't get the message "You have successfully uploaded a firmware!". The update button is showing "Please wait..." message.

I'm upgrading from FreeNAS 8.0.0 amd64 using FreeNAS-8.0.1-BETA2-amd64-GUI_Upgrade.xz and the hash :

Code:

9209e2806bb52c66a10e22bb60d81703b341e453a0276a969ccd32600690f9e5

I hope my system is not damaged or something?

Last message in the web footer console is:

Code:

...
Jun 19 17:12:46 freenas proftpd[1675]: 127.0.0.1 - ProFTPD 1.3.3d (maint) (built Wed Apr 6 2011 05:17:18 UTC) standalone mode STARTUP 
Jun 19 17:12:46 freenas mountd[1330]: can't open /etc/exports
Jun 19 17:12:49 freenas mountd[1330]: can't open /etc/exports
Jun 19 17:12:55 freenas ntpd[1573]: kernel time sync status change 2001
Jun 19 08:17:25 freenas freenas[1721]: Executing: /bin/rm -rf /var/tmp/firmware
Jun 19 08:17:25 freenas freenas[1721]: Executing: /bin/mkdir -p /mnt/media/.freenas
Jun 19 08:17:25 freenas freenas[1721]: Executing: /usr/sbin/chown www:www /mnt/media/.freenas
Jun 19 08:17:25 freenas freenas[1721]: Executing: /bin/ln -s /mnt/media/.freenas /var/tmp/firmware

And nothing else happens since 15mns, what I have to do please ?

 

[astronaute]

Rebooted, given permissions to "others" on /mnt/media/ and now upgrade works.

 

[Paktas]

service startup

* I couldn't start any of the services after clean install into Wmare Player on Win7 until I did another reboot. Now the services are starting up.
* I'd say the "ON" icon for service should be green, not blue.
* on System Information it says "Memory: 497MB" although I assigned 512MBs when setting up virtual image.

 

[TravisT]

I too am having problems upgrading to beta2 from 8.0 release amd64. I keep getting "undefined" displayed after several seconds of "please wait" on the upgrade firmware screen. I've tried permissions and everything else I can think of. Any suggestions?

Edit: Here are the last few lines of logs from the server. I tried deleting snapshot tasks because it seemed that was interfering at first, but it made no difference.

Code:

Jun 19 16:33:41 vFreeNAS freenas[1549]: Popen()ing: /sbin/zfs list -t snapshot -H -S creation
Jun 19 16:33:59 vFreeNAS freenas[1549]: Executing: /bin/rm -rf /var/tmp/firmware
Jun 19 16:33:59 vFreeNAS freenas[1549]: Executing: /bin/mkdir -p /mnt/cargo/upgrade/.freenas
Jun 19 16:33:59 vFreeNAS freenas[1549]: Executing: /usr/sbin/chown www:www /mnt/cargo/upgrade/.freenas
Jun 19 16:33:59 vFreeNAS freenas[1549]: Executing: /bin/ln -s /mnt/cargo/upgrade/.freenas /var/tmp/firmware

 

[William Grzybowski]

I too am having problems upgrading to beta2 from 8.0 release amd64. I keep getting "undefined" displayed after several seconds of "please wait" on the upgrade firmware screen. I've tried permissions and everything else I can think of. Any suggestions?

Edit: Here are the last few lines of logs from the server. I tried deleting snapshot tasks because it seemed that was interfering at first, but it made no difference.

Code:

Jun 19 16:33:41 vFreeNAS freenas[1549]: Popen()ing: /sbin/zfs list -t snapshot -H -S creation
Jun 19 16:33:59 vFreeNAS freenas[1549]: Executing: /bin/rm -rf /var/tmp/firmware
Jun 19 16:33:59 vFreeNAS freenas[1549]: Executing: /bin/mkdir -p /mnt/cargo/upgrade/.freenas
Jun 19 16:33:59 vFreeNAS freenas[1549]: Executing: /usr/sbin/chown www:www /mnt/cargo/upgrade/.freenas
Jun 19 16:33:59 vFreeNAS freenas[1549]: Executing: /bin/ln -s /mnt/cargo/upgrade/.freenas /var/tmp/firmware

Try upgrading from ssh:
# xz -cd /pah/to/img.xz | /root/update && touch /data/need-update && reboot

tell us if any suspicious message shows up, thanks

 

[TravisT]

I ended up doing the iso upgrade, but I'm seeing several gui problems in beta2 in google chrome. Mainly on the Cron and Rsync screens. IE 8 seems ok so far.

 

[William Grzybowski]

I ended up doing the iso upgrade, but I'm seeing several gui problems in beta2 in google chrome. Mainly on the Cron and Rsync screens. IE 8 seems ok so far.

Thats probably your cache in Chrome

 

[ohnename]

I update from beta1 to beta2 32bit via CD and not via GUI this time because my https GUI was broken since update FN8 -> beta1.
Now I have finally access to the gui again

 

[gazza]

FreeNAS-8.0.1-BETA2-i386 still broken for me...

1) Installed it in VMWare with 2GB memory under the FreeBSD 32bit.
2) added this to the /boot/loader.conf file
vm.kmem_size_min="800M"
vm.kmem_size_max="1024M"
vfs.zfs.arc_min="32M"
vfs.zfs.arc_max="256M"

rebooted....
Got the Good Old Panic: Kmem_suballoc: bad status return of 3

I am not too sure where is the bug tracker site to submit this...

Funny thing is that the i386 version never seems to use more the 512MB of ram...


I tried the i386 without any tuning for the zfs.... under heavy load... it will panic as well with zfs drives... basically the i386 version is not usable with zfs.