FreeNAS-8.0.1-BETA3

Status
Not open for further replies.
J

jpaetzel

Guest
FreeNAS 8.0.1-BETA3 is available for download now at
http://sourceforge.net/projects/freenas/files/FreeNAS-8.0.1/

Release Notes for 8.0.1-BETA3

This is the last BETA planned for the 8.0.1 release cycle.


*** IMPORTANT ***

The image size has been increased from 1GB to 2GB. As more features have
been added to the system it has crept towards the max size. The translations
have brought this to a head, the current image just barely fits in 1GB, but
the translation effort is about 50% finished. Since an image size bump is
inevitable, it's happening now. Due to this size change the system now
requires a 2GB device to install to. Furthermore, the GUI upgrade is not
possible. Booting from the CD will work to do the upgrade, otherwise
save config, reinstall, restore config is the recommended upgrade path.

Changes since 8.0.1-BETA2:

- Several issues relating to permissions with CIFS shares have been resolved.

- Setting permissions from windows using either AD or not should work properly.

- A bug that was preventing folder renames from windows was fixed.

- Samba has been updated to 3.5.9

- Drive replacement in volumes now works properly.

- iSCSI allows targets to be created with no extents, which eases adding
targets to an already configured system.

- Deleting a volume now turns the screen red much like shutdown to alert user
they are doing something potentially destructive.

- Django sessions have been removed from the database and into /tmp

- Importing ext2 volumes now works.

- Timezone issues have been fixed.

- Some fixes for the SATA driver have been backported from FreeBSD STABLE,
this should resolve an issue where certain systems had issues detecting disks.

- GEOM_RAID has been ported from FreeBSD STABLE, allowing the system to use
Intel matrix RAID and some other BIOS RAID solutions.

- SNMP was not validating it's config settings properly, and was only restarting
properly at system boot. This has been resolved.

- Disk sizes match between the GUI and the console.

- A bug in pw preventing users with home directories from being created was
fixed.

- Anonymous AFP has been fixed, as well as time machine.

Filename:
FreeNAS-8.0.1-BETA3-amd64-Full_Install.xz
SHA256 Hash:
855ea3c445a052c04038486a9f41d8cee2e7e73e4cdea5b7c7fbdafbcdd2cbfe

Filename:
FreeNAS-8.0.1-BETA3-amd64.iso
SHA256 Hash:
e07e54b6cdbd40c8a74d75aa6f8c6b0d86b8773d1ae98d0ddfdd94e3c3de36bf

Filename:
FreeNAS-8.0.1-BETA3-i386-Full_Install.xz
SHA256 Hash:
1756e903d7ff5b7c4def781c94a3edbaa8b6c3a59cc61922c2702d39e44774d3

Filename:
FreeNAS-8.0.1-BETA3-i386.iso
SHA256 Hash:
499f64acdf3e21c409a03c7c7231e4e22ad4283dfeb2e04d817f063cf8b7ec5e
 
B

Bohs Hansen

Guest
thanks for all the hard work all the devs put into this, can't wait to apply this later or tomorrow (depending on how my back is doing)
 

jfr2006

Contributor
Joined
May 27, 2011
Messages
174
Nice to see that the image size has been increased to 2GB ;)

I've just compiled the 6834 release and increased it also to 4GB ;)


In the timeline what is the number of this version?
 

Tekkie

Patron
Joined
May 31, 2011
Messages
353
Can't wait for the weekend to give this build a spin :) especially as I've got 2 bad hdd to replace. ;)
 

geordie2011

Dabbler
Joined
May 27, 2011
Messages
20
I have just upgrade from beta 2 to beta 3 and now i can no longer access my shares or the freenas box, any ideas?? i can connect to web interface no problem?
 

super-hornet

Cadet
Joined
Jun 29, 2011
Messages
8
Thanks all for the hardwork!
I just downloaded it. Will upgrade mine from 8.0.1 Beta 2 to Beta 3 in a few minutes time.
I hope it resolve the problem of unable to detect my SATA 3 HDD in Gigabyte GA-770TA-UD3 motherboard.
 

super-hornet

Cadet
Joined
Jun 29, 2011
Messages
8
Nope!. This Beta 3 still unable to detect my SATA3 HDD that is connected to GA-770TA-UD3's SATA 3 port. Tried both IDE and AHCI and still the same. Turn off all SATA except SATA3 port and also the same. BIOS able to detect the HDD.
 

Lacrimosa

Cadet
Joined
Jun 29, 2011
Messages
2
Just installed it. Everything works fine so far except S.M.A.R.T. service. Cant start it - the service could not be started.
 

pauldonovan

Explorer
Joined
May 31, 2011
Messages
76
Still no /data/zfs/zpool.cache in BETA3.

I think at one point between BETA2 and BETA3 it worked, but it's been broken again for a few days. Check /var/log/messages - from memory it's trying to do the fix for the cache location each time a volume is imported or created but there's no /data/zfs directory for it to be placed in. If you create /data/zfs from the CLI then it will work from then on.

Paul
 

Milhouse

Guru
Joined
Jun 1, 2011
Messages
564
I think at one point between BETA2 and BETA3 it worked, but it's been broken again for a few days. Check /var/log/messages - from memory it's trying to do the fix for the cache location each time a volume is imported or created but there's no /data/zfs directory for it to be placed in. If you create /data/zfs from the CLI then it will work from then on.

Paul

Yes, creating the directory manually fixes the problem.

It looks like this may have been fixed in r6745, but no idea what release this BETA is based on - presumably it pre-dates r6745.
 

cbray

Explorer
Joined
Jun 16, 2011
Messages
68
I also would like to thank the guys who put the time and effort into the FreeNAS 8 project.

A great Sincere Thank-You!

CB
 

sam_freenas

Cadet
Joined
Jun 30, 2011
Messages
2
Just installed beta 3 and I dont seem to be able to make the changes 'stick' when setting permissions in volumes... bug?
 
J

jpaetzel

Guest
The SVN history of beta3 is a tad muddled. It originally was going to be a service pack, but due to stuff in my life that got delayed, so we ended up doing beta3 a lot sooner than we would've liked, and of course fixing some fairly serious bugs in beta2 a lot later than we would've liked.

tags/8.0.1-BETA3

Property svn:mergeinfo changed
/trunk merged: 6753,​6771-6772,​6774-6793,​6797-6832

6745 is indeed in the build, and I've confirmed that new installs do end up with a /data/zfs dir after a zpool is created, but existing installs that are upgraded won't be touched by that change.
 

Milhouse

Guru
Joined
Jun 1, 2011
Messages
564
6745 is indeed in the build, and I've confirmed that new installs do end up with a /data/zfs dir after a zpool is created, but existing installs that are upgraded won't be touched by that change.

Thanks for the clarification. I can confirm that in my case I uploaded a BETA2 config to a fresh BETA3 install, and this would have imported my existing (BETA1!) zpool. :)

It does seem odd that the /data/zfs directory is only created on a create, and not on import.
 

geordie2011

Dabbler
Joined
May 27, 2011
Messages
20
i had beta 2 working fine using NFS and CIFS but since upgrading to beta3 i can no longer access \\freenas or \\freenas\myshare nothing has changed in the config all i get is windows cannot access \\freenas

I can however use \\ipaddress to access the area?

cifs is using guest access and account is set to www.

what else could i check?? thanks very much
 

Milhouse

Guru
Joined
Jun 1, 2011
Messages
564
i had beta 2 working fine using NFS and CIFS but since upgrading to beta3 i can no longer access \\freenas or \\freenas\myshare nothing has changed in the config all i get is windows cannot access \\freenas

I can however use \\ipaddress to access the area?

cifs is using guest access and account is set to www.

what else could i check?? thanks very much

Just to clarify my comment #15, CIFS is working fine using local user authentication (and Win7 Ultimate as client).
 
Status
Not open for further replies.

Similar threads

J
Replies
20
Views
16K
J
Replies
42
Views
25K
Joshua Parker Ruehlig
J
Top