NAS4Free 10.2.0.2.1906 released (FreeBSD 10.2-RELEASE-P5)

[zoon01]

The nas4free team is pleased to announce the release of 10.2.0.2.1906

http://sourceforge.net/projects/nas4fre ... .0.2.1906/

Everyone can upgrade from NAS4Free version 9.3.0.2.1310 or Higher.

README & CHANGELOG

NAS4Free Upgrade from below 9.3.0.2.1310 is NOT possible!!!
=====================================================
Upgrading NAS4Free "Embedded" or "Full" from any version below 9.3.0.2.1310 by webgui or from
LiveCD/USB is problematic, due a new size of boot partition & partition layout.
Please download and save your NAS4Free config to a safe place and backup all files from second
partition if you use boot disk as data disk.
INSTALL FROM SCRATCH IS THE ONLY WAY!
After installation you can restore your config.
Sorry for inconvenience.
** ! Tools to write extracted embedded file are not supported ! **
You must use the liveusb/CD for it's first installation!!!.

Install from scratch notes
======================
** Embedded.img.xz is only for upgrades by WEBGUI, do not extract and write to any media! **

Download NAS4Free livecd or liveusb and boot from it.
The compressed LiveUSB.img.gz needs to be extracted before you can write it to usb media,
you can use it with Win32DiskImager or any other tool.
Press 9 for the install menu and perform an embedded installation.

Upgrade note:
============
You must associate CARP with physical interface explicitly after upgrading to 10.X.
You may need modifying your NFS and AFP share setting.
You may need modifying your ftp setting, no longer SSL is supported (only TLS).
Send Buffer Size/Receive Buffer Size in CIFS/SMB is changed to 128480 since 9.3.0.2.1375.
/var and /var/tmp size has changed.
After the upgrade please do make a new backup of your config System|Backup/Restore.

ZFS User note!
After upgrading, you must re-sync ZFS configuration from Disks|ZFS|Configuration|Synchronize.

Requirements
============
Embedded: 2GB CF/USB/SSD (NAS4free "Embedded" is Recommended Install)
Full: 4GB HDD/SSD (For developers and some advanced users, Not Recommended!)
Swap less: physical memory 2GB or higher needed.
With swap: physical memory 512MB + swap 512MB (swap 1024MB recommended).

*Note: LiveCD is not supported on swap mode except installation and upgrading.

BUILD 10.2.0.2.1902
=================
Changes:
- Upgrade to FreeBSD 10.2-RELEASE-P5.
- Add Mellanox ConnectX-2 EN driver module. (x64 only)
- Add Auxiliary parameters in Samba AD.
- Add bhyve and related files. (CLI only)
- Add hint.acpi_throttle.0.disabled="0", hint.p4tcc.0.disabled="0".
- Add dlna user and group.
- Add minidlna. (CLI only)
- Add VirtualBox with WebSocket VNC server. (x86 and x64 only)
- Add phpVirtualBox and noVNC(HTML5/WebSocket VNC client) for VM management.
- Add ability to mount exFAT disk.
- Add samba local group.
- Add ability to add tap device on bridge interface.
- Remove usesendfile on CIFS/SMB.
- Upgrade bash 4.3 to patch 42.
- Upgrade lighttpd to 1.4.37.
- Upgrade samba to 4.2.4.
- Upgrade isboot to 0.2.11.
- Upgrade tzdata to 2015g.
- Upgrade php to 5.6.14.

Fixes:
- Fix NTFS is not detected on Import disks.
- Fix SSL certificate link. (ticket #239)
- Fix NFS share network. (ticket #238)
- Fix boot time ntpdate fail when AD DC enabled.
- Fix wrong path in Samba AD. (ticket #228, #232)
- Undefined symbol "av_find_stream_info" in fuppes/libmetadata_libavformat.so.
- AFP share is not advised.
- Fix webserver user logins.
- Fix wrong path ticket 228.

Note:
- iperf2 has been replaced for iperf3 because of inconsistent results for UDP above 2Gbps.
- iperf3 is not backwards compatible with iperf2.x.

Permanent restrictions:
- It is not possible to format a SoftRAID disk with MSDOS FAT16/32.
- It is not possible to encrypt a disk partition, only complete disks are supported.
- AFP shares with TimeMachine support are limited to max. 4 shares.

Regards,
The NAS4Free Team

[zoon01]

New builds to replace 1902 online

[JoseMR]

WebGUI firmware upgraded from r1905 to r1906 successfully, thanks for the quick fix release.

[wingenieur]

Thanks for updating!

Just playing around with the recently integrated VirtualBox, but getting an error logging in to phpVirtualBox.
Is there a manual regarding this feature?

I'm trying this on my second NAS, where there is no extension installed, that I use on my primary one.

Do I have to care for user rights on any files?
It seems the vbox web service hasn't started at all...

The system log shows this message twice:

Code: Select all

sudo: root : TTY=unknown ; PWD=/usr/local/www ; USER=vboxusers ; COMMAND=/usr/local/bin/VBoxManage list runningvms

[JoseMR]

Have you specified a Home directory for VirtualBox with suitable permissions?

I am able to login and play with VirtualBox, and created a VM without issues.

[daoyama]

Do I have to care for user rights on any files?
It seems the vbox web service hasn't started at all...

Try to reboot the NAS4Free. If your server is waiting to reboot, all service (not only vbox) will not start immediately.

The system log shows this message twice:

Code: Select all

sudo: root : TTY=unknown ; PWD=/usr/local/www ; USER=vboxusers ; COMMAND=/usr/local/bin/VBoxManage list runningvms

Yes, it seems default /etc/syslog.conf have authpriv.info and authpriv.notice on same log.
I think this is a bug but I don't know where to use authpriv.notice.

Code: Select all

*.notice;kern.debug;lpr.info;mail.crit;mail.info;news.err;local0.none;local7.none %/var/log/system.log
auth.info;authpriv.info %/var/log/system.log

[wingenieur]

Have you specified a Home directory for VirtualBox with suitable permissions?

Yes, I hope so... Tried two different directories, one owned by root:wheel, another one owned by vboxusers:vboxusers, each permitted 774, but still no success.

Try to reboot the NAS4Free. If your server is waiting to reboot, all service (not only vbox) will not start immediately.

Did a reboot, no change actually...

But activating/deactivating gives more messages in system log:

Code: Select all

sudo: root : TTY=unknown ; PWD=/usr/local/www ; USER=vboxusers ; COMMAND=/usr/local/bin/VBoxManage setproperty websrvauthlibrary null
sudo: root : TTY=unknown ; PWD=/usr/local/www ; USER=vboxusers ; COMMAND=/usr/local/bin/VBoxManage setproperty websrvauthlibrary null
daemon: _secure_path: cannot stat /mnt/usbdata/vm/.login_conf: Permission denied
root: vbox service started

So I wonder which are the suitable permissions for the home directory?
It is the same output for both mentioned directories.

When deactivating and activating vbox in nas4free webgui, the permission of the selected home directory is changed to vboxusers:vboxusers 755 anyway, I've just noticed...

[sfranzis]

Hi *,

I have the same problem with virtualbox as wingenieur.

[daoyama]

So I wonder which are the suitable permissions for the home directory?
It is the same output for both mentioned directories.

When deactivating and activating vbox in nas4free webgui, the permission of the selected home directory is changed to vboxusers:vboxusers 755 anyway, I've just noticed...

Top of the directory is changed to vboxusers:vboxusers 755, however contents in it is never changed.
So you need empty home directory or change it by hand. Try to create new directory from Advanced|File Manager or CLI.
(e.g. /mnt/data/vbox if data is mount point)

[tonyd]

Wow VirtualBox is part of the release now, nice!

So for those of us that have been using the VBox extension, how do we properly migrate to the built-in version?

[HoPla-HL]

Is there any chance to configure MiniDLNA via Webgui in the next release???

HoPla-HL

[sfranzis]

Thanks for updating!

Just playing around with the recently integrated VirtualBox, but getting an error logging in to phpVirtualBox.
Is there a manual regarding this feature?

I'm trying this on my second NAS, where there is no extension installed, that I use on my primary one.

Do I have to care for user rights on any files?
It seems the vbox web service hasn't started at all...

At my intsallation it was a wrong entry in rc.conf:

Code: Select all

vboxwebsrv_user="vboxuser"

After changing this to vboxusers everything works.
Perhaps this came from a former installation of virtualbox.

Stefan

[wingenieur]

At my intsallation it was a wrong entry in rc.conf:

Code: Select all

vboxwebsrv_user="vboxuser"

After changing this to vboxusers everything works.
Perhaps this came from a former installation of virtualbox.

Thank you for digging and reporting!

Perhaps I've tested a former release of the vbox extension on my second NAS Box, but I cannot remember...
I've checked my rc.conf, there is no entry belonging to vboxwebsrv.
When I add

Code: Select all

vboxwebsrv_enable="YES"
vboxwebsrv_user="vboxusers"

manually, there is no change in behaviour (still not after reboot)...

Top of the directory is changed to vboxusers:vboxusers 755, however contents in it is never changed.
So you need empty home directory or change it by hand. Try to create new directory from Advanced|File Manager or CLI.
(e.g. /mnt/data/vbox if data is mount point)

Thank you for the hint!
I've tried with an empty directory, which was created just for this purpose... sorry to sday this didn't help...

I'm going to install NAS4free from scratch and try again, perhaps some old modifications by certain installers are the reason for this.
Reporting follows...

[sfranzis]

I'm going to install NAS4free from scratch and try again, perhaps some old modifications by certain installers are the reason for this.
Reporting follows...

One more try:
what happens if you call

Code: Select all

/usr/local/etc/rc.d/vboxwebsrv start

from a shell?

Stefan

[daoyama]

I found a bug.
Once you enable vbox, you cannot stop the service even if you uncheck Enable option.
If you want change homedir after enable, run /etc/rc.d/vbox onestop before changing or reboot NAS4Free after changing.
fixed at 1909.

[wingenieur]

One more try:
what happens if you call

Code: Select all

/usr/local/etc/rc.d/vboxwebsrv start

from a shell?

It says

Code: Select all

Starting vboxwebsrv.

But when I stop the same way, it says

Code: Select all

vboxwebsrv not running? (check /var/run/vboxwebsrv.pid).

Anyway, I'm going to reinstall from scratch later...
Thank you for advice!

[wingenieur]

Hi all!

Just to close my own request: I've finally found the reason.
The dataset itself was permitted 774 to root:wheel.

So vboxusers:vboxusers couldn't execute or write correctly.

Now it works like a charm.
Thank you all for supporting!