NAS4Free 11.0.0.4.4067 released (FreeBSD 11.0-RELEASE-P8)

[zoon01]

The NAS4Free Team is pleased to announce a maintenance release of version 11.0.0.4.4067 - Sayyadina it replaces 4066 release.

Download build 11.0.0.4.4067
Read the readme_11.0

Major Change!
Note for 32-bits users:
===================
We believe that the use of 32-bits versions can not give the end users it's full potential of the OS, for this
further development on the (i386) 32-bits architecture has been stopped upon the 11.0.0.3.xxxx series.
Current 32-bits users are able to use 32-bits 10.3.0.3.xxxx series until their end of life or do reinstall
to use 64-bits NAS4Free and restore config.

Again TIP: Do not upgrade from 10 series directly!
reinstall and restore config is the way to go because of increased partition size!
You avoid lots of problems later on.

Upgrade note:
=============
RRDGraphs extension can no longer be used with 11.x series, disable and deinstall before upgrade!
RRDGraphs are now included in 11.x series, you can setup on webgui System > Advanced > Monitoring Setup.
Do not reinstall the extension!!!

BUILD 11.0.0.4.4067

Changes after release 11.0.0.4.4040
===============================
- Update translations.
- More verbose during embedded upgrade process.
- Upgrade php to 7.1.3.
- Upgrade virtualbox-ose to 5.1.18.
- Upgrade netatalk to 3.1.11.
- upgrade samba to 4.4.11.
- Fix single and double quotes in user passwords.
- Fix hide ntp parameter when ntp is not used.

Known bugs:
===========
- IE11 and Edge browser does not operate correctly with novnc. Enter & Escape button problematic,
this will be fixed at a later release, use Chrome or other browser or connect with putty client.

Enjoy!

Regards,
The NAS4Free Team

[JoseMR]

Thanks Dev Team for this prompt and great release, upgraded with out hassle here.

Keep up the good work

Regards

[Victek]

Thanks devs for the update. I was wondering if I have to update the BIOS of my machine instead of the OS the BIOS Flash will be soon at the end of life (kidding) !!!

[adultery_nas]

No problems here either! Thanks @zoon01 and the N4F team! Been cranking out updates at a pretty good clip lately!

[alexey123]

As for me, it work

[netware5]

I experienced problems during update from 4029, similar to those occurred when updating from 3948 to 4029. After applying 4067 update the server didn't rebooted. The following message appeared on the console: "OS halted, press any key to reboot", but pressing any key didn't work. I was forced to press the power button to resolve the issue.

[raulfg3]

A experienced problems during update from 4029, similar to those occurred when updating from 3948 to 4029. After applying 4067 update the server didn't rebooted. The following message appeared on the console: "OS halted, press any key to reboot", but pressing any key didn't work. I was forced to press the power button to resolve the issue.

If you have a embeded install, my sugest is:

save your actual config, do a new embeded install on a new boot device ( a new USB or disk), and restore your config and test that this time boot sucesfully, perhaps your boot device have some faulty blocks or something corrupt.

[netware5]

A experienced problems during update from 4029, similar to those occurred when updating from 3948 to 4029. After applying 4067 update the server didn't rebooted. The following message appeared on the console: "OS halted, press any key to reboot", but pressing any key didn't work. I was forced to press the power button to resolve the issue.

If you have a embeded install, my sugest is:

save your actual config, do a new embeded install on a new boot device ( a new USB or disk), and restore your config and test that this time boot sucesfully, perhaps your boot device have some faulty blocks or something corrupt.

In first case (from 3948 to 4029) I did a new install on the same USB using LiveUSB. everything was fine. In second case (from 4029 to 4067) everything was fine except that the server didn't reboot. I am not sure that the issue in both cases is caused by faulty USB, as the server didn't reboot. Any fualty blocks would reflect only after reboot (the new OS would be corrupted). My understanding is that the update modifies the boot USB and reboots the server. Then the new OS is active only after reboot. So the problem is in rebooting, i.e. it is still the old OS and update process that should activate the reboot. My problem is with reboot not with boot.

[adultery_nas]

Working OK, except there's a char limit on the CIDR field in the general settings page now that wasn't there before so I'm having trouble exposing my IP range. Aside from that, thank you for your hard work!