FreeNAS 8.2.0-BETA4

Status
Not open for further replies.
J

jpaetzel

Guest
It's been nearly a month, and several hundred commits later....

The development team is pleased to announce FreeNAS 8.2.0-BETA4, available for immediate download at:

https://sourceforge.net/projects/freenas/files/FreeNAS-8.2.0/BETA4/

We've done a complete refactoring of the plugin networking stack, to allow greater flexibility and functionality. We've added the ability to upgrade plugins, as well as the plugin jail itself.

There have been numerous bug fixes and improvements over previous beta releases.

Release Notes:

*** IMPORTANT ***

- The GUI upgrade format changed in 8.2.0-BETA3 from xz to txz. What
this means is that if you are attempting to do a GUI upgrade to
8.2.0-BETA4 from 8.2.0-BETA3 use the .txz version of the GUI_Upgrade
file. If you are upgrading from any previous version use the .xz file.

- 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.

- FreeBSD can be really touchy with hardware. Please be sure to update
your BIOS/BMC firmware when upgrading / installing FreeNAS if you run
into OS hang issues. There have been cases identified where a BIOS
upgrade has fixed driver hangs, and/or other issues with FreeNAS; one
such example was with an Intel 82578DC motherboard, as noted in the
FreeNAS 8 forum thread titled "8.0.3-RELEASE coming soon..":
http://bit.ly/rq78Q3 , post # 70-88. Again, please only do this if you
experience booting / runtime issues, as some vendors don't test
FreeBSD interoperability as much as others between major firmware
releases.

- Previous builds were branded as i386/amd64 (32-bit and 64-bit
respectively). 8.0.3-RC1+ rebranded the architectures as x86 and x64,
respectively.

- 8.0.1 and 8.0.2 images advertised CIFS shares to Macs by default but
8.0.3 and later images don't advertise CIFS shares by default. If you
want to advertise CIFS shares in 8.0.3 and later, be sure to turn on
"Zeroconf" support in the CIFS global settings.

- Builds prior to 8.0.3-RELEASE with 'CIFS' didn't actually have AIO
(asynchronous I/O) enabled. So, if you experience performance
degradation after upgrading from prior versions of FreeNAS to
8.0.3-RELEASE or newer, turn off AIO or tune the AIO size from '1' to
something more reasonable (the new default in 8.0.3-RELEASE-p1 is 4096
or 4kB).

Changes in the 8.2 branch versus 8.0.x


Overview
========================

The 8.2 branch of FreeNAS introduces many functional changes when
compared with the 8.0.x releases.

ZFS can be manipulated from the CLI, and changes for supported items
tracked by FreeNAS will be reflected in the GUI. zvols, datasets, and
entire volumes can be created, destroyed, or manipulated on the CLI and
will be propagated to the GUI.

The GUI now supports active-passive multipath capable hardware, which
targets mainly SAS drives on dual expander backplanes. Any multipath
capable devices that are detected will be placed in multipath units
which are then exposed to the GUI, and the parent devices will be
hidden.

Plugins are now available. Third party modules can be added to FreeNAS
which will persist across upgrades and can be manipulated and configured
from the GUI. Documentation on using and creating plugins is available
at http://doc.freenas.org/index.php/Plugins . BitTorrent,
DLNA/uPNP, and iTunes plugins are available as of this writing.

The GUI now includes a webshell, which allows you to access a root
shell from within a web browser.

The "Create Volume" modal was renamed to "Volume Manager". Extending
existing pools is more intuitive than it was previously; selecting
multiple disks for a storage volume is now done via a multiselect
widget instead of checkboxes to improve ease of use when creating
volumes.

ZFS volumes can now have periodic scrub tasks configured for them; the
default is set to 35 days to be consistent with the OS default.

An autotuning script is now available -- disabled by default. It sets
various tunables and sysctls based on system resources and components.
The predetermined values are exposed through the GUI from the Sysctls
and Tunables panes.

A newer web toolkit is used, which behaves better with modal dialogs
and more intuitively in general when compared with older versions.
It also has better browser compatibility, including compatibility with
Android / iOS mobile devices!

A more responsive service state detection mechanism was added to
improve FreeNAS interoperability in VM software (VMware, VirtualBox,
etc).

Errata
========================

Starting and stopping the plugin jail multiple
times repeatedly may cause the OS to panic.

The plugin jail networking has been switched to VIMAGE, which
requires bridging the plugin jail with an external interface. On
systems with multiple interfaces there is currently no way to
specify which interface is used. The current system chooses the interface
with the default route.

Changes since 8.2.0-BETA3:

Enhancements
========================

GUI
------------------------

1. Add functionality to upgrade the plugin jail.

2. Add functionality to upgrade plugins.

3. Shuffle around a number of plugin related items.

4. Switch the widget used for rsync extra options to one that allows
arbitrary length input.

5. Limit the path length used in mount points to what the OS will allow.

6. Fix tab completion in the webshell for chrome.

7. Warn that the root email address isn't configured when configuring
email.

8. Add the ability to switch the console locale through the GUI.

9. Log failed attempt to create automatic snapshots.

10. Add the ability to set up SMART tests on multiple disks
simultaneously.

11. Add a disk wipe feature.

12. Show datasets in tree menu.

OS/Third party
------------------------

1. Add support for the qlogic 10Gbe ethernet driver.

2. Change JSON-RPC API to support versioning.


AFP
------------------------

1. Add the ability to set the fperm and dperm in the GUI.

Samba
------------------------

1. Update to Samba 3.6.5


Bugfixes
========================

Middleware
------------------------

1. Fix a bug that caused a traceback getting UFS volume status.

2. Improve logging for LDAP or AD integration.

3. Fix default clone path for Zvols.

4. Fix issue with jail install to keep the jail from being copied twice.

OS/Third party
------------------------

1. Fix remote syslogging.

2. Fix basic/advanced view for forms.

3. Fix ataidle functionality.

4. Remove the arbitrary FTP passive port minimum.

5. Fix setting permissions from the GUI for UTF-8 filenames.

6. Fix UPS email notification.

7. Fix the defaults for the autotuner.

8. Fix database permissions/ownership.

GUI
------------------------

1. Filter out multipath units from view disks screen.

2. Set the replication SSH port in the OS properly.

3. Fix webshell environment and locale.

4. Fix a bug that would leave ghost volumes on delete/export.

5. Fix bug in firmware upgrade.

Filename:
FreeNAS-8.2.0-BETA4-x64.GUI_Upgrade.txz
SHA256 Hash:
bcf5fad12f8a000ffd2bc669be07f3de390031b206ce5bbbb56627c69ab91f3e

Filename:
FreeNAS-8.2.0-BETA4-x64.GUI_Upgrade.xz
SHA256 Hash:
29373d1a68c5baeefdca6534adc2bbb6bff62a0b93230d9d7060b99d9467707b

Filename:
FreeNAS-8.2.0-BETA4-x64.img.xz
SHA256 Hash:
c706ddb9e71675df2227d2ff1ca26953b8b91827b2ffe04e4d761acbe7d27cb1

Filename:
FreeNAS-8.2.0-BETA4-x64.iso
SHA256 Hash:
755546b46cb976137b0e0d865e1b21ccd55c38ba32ac879a525a9f10eca54f4a

Filename:
FreeNAS-8.2.0-BETA4-x86.GUI_Upgrade.txz
SHA256 Hash:
2f04b7e991ca09d8dcaebdec458ef3dbd30f4ccb8628add53def5783d8e4c1c4

Filename:
FreeNAS-8.2.0-BETA4-x86.GUI_Upgrade.xz
SHA256 Hash:
ff08082ed59175183fe0461ec9c9a2c1e455a68ab65fc1b412c6efbba8b18e5e

Filename:
FreeNAS-8.2.0-BETA4-x86.img.xz
SHA256 Hash:
9f662ef7409987d0c559cb93ad7ac2b93eac3fbb71000f5d0ce346fdc98c36a3

Filename:
FreeNAS-8.2.0-BETA4-x86.iso
SHA256 Hash:
322c5170559f5485565ac51d282928eb9332804c684f4833bc4e3b2ab836675f
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
Hi Josh,

Are there new plugins / PBI jail we need to use?

I'm not seeing any of the plugins or jail to download.


Thanks again for all the great work on FreeNAS!
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
Thanks William, you must have just added those, I didn't see them earlier ;)

I'm looking forward to seeing what you've done.

Thanks for everything!
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
Thanks, downloading now and will give it a try on my VM for a few days and then if it looks solid enough I will give it a shot on my real NAS hardware. This will be the first time trying 8.2.0 so it could be a real treat.
 

Quasar

Cadet
Joined
Jun 15, 2012
Messages
5
Did anybody try already plugins in beta4? I've upgraded from beta3 (deleting all plugins and jail before), installed transmission-plugin - it doesn't work at all. I can see only this error: "Couldn't retrieve http://server_ip:80/plugins/transmission/_s/status: HTTP error 502: bad gateway".
Sometimes I get another error: "......<urlopen error timed out>"
 

William Grzybowski

Wizard
iXsystems
Joined
May 27, 2011
Messages
1,754
Make sure the IP you did set for the Jail is reachable using webshell...
paste

# ifconfig

and

# jexec 1 ifconfig

and

# cat /usr/local/etc/nginx/plugins.conf
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
The link above on how to use plugins was deleted 19 April by Dru with no link on where to go next. He should have provided a link. Here is the location that the information now resides. http://doc.freenas.org/index.php/Plugins
 

Quasar

Cadet
Joined
Jun 15, 2012
Messages
5
Thank you for so fast answer!
Ye, it is reachable.

1) ifconfig:
Code:
msk0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=c0018<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWTSO,LINKSTATE>
        ether 00:00:00:17:d5:8f
        inet 10.11.10.2 netmask 0xffffff00 broadcast 10.11.10.255
        media: Ethernet autoselect (1000baseT <full-duplex,flowcontrol,rxpause,txpause>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
        inet6 ::1 prefixlen 128
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether d2:82:a8:d5:c2:67
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: msk0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
        member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 7 priority 128 path cost 14183
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu                                                              1500
        ether 02:80:44:00:07:0a


2) jexec 1 ifconfig:
Code:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=3<RXCSUM,TXCSUM>
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:80:44:00:08:0b
        inet 10.11.10.4 netmask 0xffffff00 broadcast 10.11.10.255
        inet6 fe80::80:44ee:fe00:80b%epair0b prefixlen 64 scopeid 0x2
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>


3) cat /usr/local/etc/nginx/plugins.conf:
Code:
location ~ /plugins/transmission/ {
    fastcgi_pass   10.11.10.4:12346;
    include             fastcgi_params;
    root /usr/pbi/transmission-i386;
}
 

garfunkel

Dabbler
Joined
Jun 15, 2012
Messages
41
Awesome, thanks to the FreeNAS devs!

I made a fresh install with mine and the firefly/transmission plugins seem to work fairly well for me. I am having issues with the miniDLNA plugin though. It seems to run and the logs indicate it is scanning my media but it never advertises itself. I have tried setting the notify interval in the GUI to 30 seconds/10 seconds and restarted the plugin multiple times but it never shows up on any of my devices. Is this the multiasting from jails problem again?
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
I'm experiencing problems with DNS lookups from the Jail. Looking at resolv.conf the DNS server is there, but when I try to do a "pkg_add", it fails. I tried nslookup, but it can't find the command. If I just try ping ftp.freebsd.org or ANY host I get:

Code:
ping: cannot resolve ftp.freebsd.org: Host name lookup failure 


Code:
ifconfig                                                               
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384               
        options=3<RXCSUM,TXCSUM>                                                
        inet 127.0.0.1 netmask 0xff000000                                       
        inet6 ::1 prefixlen 128                                                 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1                              
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>                                  
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500   
        ether 02:48:6f:00:05:0b                                                 
        inet 192.168.2.25 netmask 0xffffff00 broadcast 192.168.2.255            
        inet6 fe80::48:6fff:fe00:50b%epair0b prefixlen 64 scopeid 0x2           
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV> 


Maybe I'm missing something, it's been a long day.
 

labtopia

Dabbler
Joined
May 31, 2011
Messages
47
cannot access installed plugins in gui

i did a clean install and uploaded config. trying to now get any plugins to work. jail installed ok and minidlna says it installed but in the console getting this

manage.py: [services.views:79] Couldn't retrieve http://serverip:80/plugins/minidlna/_s/status: <urlopen error timed out>

this is for any other plugs installed also so they dont show in the settings tree. i tried the previous post about trying jexec 1 ifconfig, but i get invalid arguement. not sure where else to look but the docs and existing posts and dont see anything.

any help would be appreciated.

dave
 

ppmax

Contributor
Joined
May 16, 2012
Messages
111
Just wanted to say that my upgrade from 8.2B3 to 8.2B4 went pretty well and everything is up and running. It also appears that multicast traffic to and from jails now works, and I can finally watch my movies via minidlna.

I had two small hitches:
My machine hung about 15 minutes after the upgrade. After reading about the (possible) need to upgrade the bios on my board, I downloaded a new bios for my ASRock E350M1 (ver 1.60) and rebooted--all went well and FreeNAS hasn't hung since.

Previously in B3 I had created an interface and the alias IP for the jail was defined there. When creating a jail in B4 the IP address is added in the create Jail UI. This through me for a bit of a loop because I wasn't seeing an IP address when executing jls...and ifconfig inside the jail kept showing a weird interface named epai0b. Thinking something was wrong I deleted the jail, reinstalled FireFly and minidlna...and finally read the updated docs (thank you!) and now believe I understand what was going on: the change in how the jails communicate with the outside world appears to be through new virtual interfaces rather than network alias. In fact I have new RRD graphs that show a bridge interface (bridge0) and epair0a which sits "outside" the jail.

Nice work FreeNAS developers--this is a great upgrade! (Also my first upgrade since starting with FreeNAS with 8.2B3)

PP
 

noee

Dabbler
Joined
May 21, 2012
Messages
13
More update feedback...

I upgraded my home NAS from 8.0.4 R3 to this new beta and all was very smooth. I too had the "lock" at about 15 min after the second reboot, so I checked as well and I was running an old beta BIOS on this mobo. It's a really old Asus M3A with an old Athlon 5000+ BE dual-core. Upgraded BIOS to latest and at the same time upgraded to Gbe on my LAN. I have UFS and NTFS vols mixed in RAID0 (only 3GB RAM) for a few Windows only clients (so far). After the LAN upgrade, tweaking the CIFS tunables, and some testing, things are rock solid so far and read/write performance to the NAS is order of magnitude better at least.

Fwiw, the mobo Atheros PCIe Gigabit LAN controller seems to be well supported. Next, I'm planning for miniDLNA but a RAM upgrade is top priority...

Great work!!
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
Dru is a woman ;)
You know, somehow I thought so but I rolled the dice and had a 50/50/90% chance. 50% change is was man or woman, 90% chance getting it wrong.

On the positive side, I was able to get 8.2.0-Beta4 running without much real effort. The PBI for minidlna was not bad but I hadn't used this version and only tried PBI once half a year ago when it wasn't so well built.

Something I am having problems with is when I reboot, Minidlna PBI will not start automatically. I can start it manually and it runs fine. I may remove the plugins and jail and try it all over again just to double check my work but doing the install didn't seem difficult at all.

EDIT: I deleted my jail and started over from scratch but the end result was the same, minidlna does not start on reboot but I can go into the plugin area and click on the ON/OFF button to start it. I must be either missing something or the plugin just does not start on it's own. Think I'll poke around the threads to see if this has popped up in the past.
 

SteveEdson

Cadet
Joined
Jun 16, 2012
Messages
3
I can't start Transmission or FireFly either. Getting messages such as

Code:
Jun 16 22:46:49 freenas manage.py: [services.views:79] Couldn't retrieve http://192.168.0.22:80/plugins/transmission/_s/status: <urlopen error timed out>
Jun 16 22:51:13 freenas notifier: Waiting for http... Done.
Jun 16 22:54:31 freenas notifier: Waiting for http... Done.
Jun 16 22:54:31 freenas manage.py: [services.views:79] Couldn't retrieve http://192.168.0.22:80/plugins/transmission/_s/status: HTTP Error 502: Bad Gateway
Jun 16 22:54:31 freenas manage.py: [freeadmin.navtree:413] Couldn't retrieve http://192.168.0.22:80/plugins/transmission/_s/treemenu: HTTP Error 502: Bad Gateway
Jun 16 23:02:04 freenas notifier: Waiting for http... Done.
 

garfunkel

Dabbler
Joined
Jun 15, 2012
Messages
41
Just want to update. It seems my miniDLNA discovery issue is because of my shitty netgear routers not because of the beta. :)

EDIT: Fixed my stupid routers and now miniDLNA works like a charm. :) First beta where all three plugins seem to 'just work' out of the box with no errors or hair-pulling. FreeNAS 8 was a bit disappointing to me and felt a bit half-baked, the lack of proper storage for software was horrid. But I have to say, with 8.2 I can finally see where this is all leading, and I like it very much. Once we get an updated software stack based on FreeBSD 9 and a new ZFS version and some more plugins I think FreeNAS will be really something excellent.
 
Status
Not open for further replies.
Top