NAS4Free 11.0.0.4.4490 released (FreeBSD 11.0-RELEASE-P11)

[zoon01]

The NAS4Free Team is pleased to announce the release of version 11.0.0.4.4490 - Sayyadina

Please upgrade if you still are on older 11 releases than rev: 4303, it fixes CVE-2017-7494.
All versions of Samba from 3.5.0 onwards are vulnerable to a remote code execution vulnerability,
allowing a malicious client to upload a shared library to a writable share, and then cause the server to load
and execute it.

Download build 11.0.0.4.4490
Read the readme_11.0

Major Change!

cifs/smb note:
==============
From Samba 4.5.0 and up the default value for the "ntlm auth" option is changed from "yes" to "no".
This may have impact on very old clients which doesn't support NTLMv2 yet.
Only if you really need NTLMv1 Authentication you can set in Additional Parameters: "ntlm auth = yes".

BUILD 11.0.0.4.4490

Changes after release 11.0.0.4.4383
===============================
- Upgrade FreeBSD 11.0-RELEASE to P11.
- Update translations.
- Some webgui code improvements.
- Upgrade iperf3 to 3.2.
- Upgrade arcconf to v2_04_22665.
- Upgrade minidlna to 1.2.0.
- Upgrade syncthing to 0.14.32.
- Upgrade php to 7.1.7.
- Upgrade samba to 4.6.6.
- Upgrade virtualbox-ose to 5.1.24.
- Upgrade nano to 2.8.6.

Note:
Clear your browser's cache to avoid display issues after upgrade.
Make a new backup of your system configuration and store this on safe location.

Enjoy!

Regards,
The NAS4Free Team

[apollo567]

worked for me !

Regards
apollo

[lindsay]

Works for me too

[feeman]

After upgrade to release 11.0.0.4.4490
When I try to connect vm in virtualbox with novnc , I got disconnect without any password request.
And then ,the vm state from running change to aborted.
But it was OK when I use release 11.0.0.4.4383.
The system log has the message bellow.
kernel: pid 9968 (VBoxHeadless), uid 920: exited on signal 11

[scifimike12]

Same issue as freeman.

[biggsy]

Running 11.0.0.4 - Sayyadina (revision 4375) as ESXi VM (x64-embedded on Intel(R) Xeon(R) CPU E3-1265L V2 @ 2.50GHz)

Upgrade firmware using NAS4Free-x64-embedded-11.0.0.4.4490.img.xz appears to launch but does nothing with no logs.

[raulfg3]

11.1.0.4.4485 works: https://www.nas4free.org/forums/viewtop ... 387#p79387

so bug is in the latest code.

[biggsy]

11.1.0.4.4485 works ...

Yes, it does. Thanks.

Any important changes to note between 4485 and 4490?

[doktornotor]

Any important changes to note between 4485 and 4490?

https://sourceforge.net/p/nas4free/code/4492/log/?path=

[raulfg3]

11.1.0.4.4485 works ...

Yes, it does. Thanks.

Any important changes to note between 4485 and 4490?

none that explain the bug, but i'm not a developer.

[nasser]

hi,
after upgrading to NAS4Free-x64-full-11.0.0.4.4490.tgz (from 4383) and booting stuck on in
"Loading configuration files" and stops, what can I do with this?

What can I do??
I have also some custom scripts in /root/ , so, install from scratsch is not a good option..

[nasser]

ZFSroot Upgrade with USB Live didnt help.

[JoseMR]

hi,
after upgrading to NAS4Free-x64-full-11.0.0.4.4490.tgz (from 4383) and booting stuck on in
"Loading configuration files" and stops, what can I do with this?

What can I do??
I have also some custom scripts in /root/ , so, install from scratsch is not a good option..

Hello nasser, if something goes wrong with a NAS4Free Full(zroot) WebGUI upgrade preventing you from booting, you can still use a LiveCD/USB to rollback to a previous working environment, you need to boot the live media then import "zroot" to an alternate location i.e to /mnt with the -R option, then proceed with the rollback from a working snapshot, also note that NAS4Free Full ZFS should be running on high quality/reliable media such as HDD/SSD's, but branded USB 3.0 can also be used as well.

And remember, is strongly advised for the user to verify the firmware file integrity(checksum) prior to upgrade.

ZFSroot Upgrade with USB Live didnt help.

You should not use a Live media to perform a Full zroot upgrade once you used the newer WebGUI method, since that legacy option is for system running without boot environments and will overwrite existing content without creating a new boot environment.

Regards

[nasser]

Hi,

I did:
zpool import -f -R /mnt zoot
rollback with zfs rollback zroot/ROOT/upgrade-2017-07-25-180632@2017-07-25-18:06:32

now:
internal error: failed to initialize ZFS library

[nasser]

I guess it has something todo with the mountpoints ( http://docs.oracle.com/cd/E19253-01/819 ... index.html )

but I am not sure which dataset should I set for /

[JoseMR]

I guess it has something todo with the mountpoints ( http://docs.oracle.com/cd/E19253-01/819 ... index.html )

but I am not sure which dataset should I set for /

Hi, anything below "zroot/ROOT/" i.e "zroot/ROOT/this_dataset_clone" can be used for the rollback/root, however you may need to edit system scripts like "loader.conf", "set bootfs", "set freebsd:boot-environment=1" and the like since manually rollback will not auto-set/edit things like the "beadm" utility auto performs, though I will strongly recommend you to backup any newer custom made scripts before rollback just in case a fresh install is needed/easier.

I will perform more research about this definitely, though currently have plans on working/testing on the GRUB addition for NAS4Free RootOnZFS, for easier menu-driven ZFS dataset boot selection to avoid manual/hand re-configurations upon specific dataset boot failures.

Really sorry for any inconveniences.

[nasser]

Hi,
ok, so its not done with just a rollback. So, the question is, why there are these backup-snapshots, when they are really useless in the case of misfunction e.g. after an upgrade.

beadm create upgrade
beadm activate upgrade

in the live media shell is not enough?

[JoseMR]

Hi,
ok, so its not done with just a rollback. So, the question is, why there are these backup-snapshots, when they are really useless in the case of misfunction e.g. after an upgrade.

beadm create upgrade
beadm activate upgrade

in the live media shell is not enough?

Hi, this snapshots/clones are definitely system "backups" and aslong as the system boots normally, any user can just use "beadm" to activate roll-back to a specific point in case something miss-behave, however under a major failure where the system cannot boot, the user have to manually edit few things, hence one reason why "NAS4Free Full Installs" are targeted to Advanced/Experienced users/devs primarily .

A manual system roll-back script could be another option for perform "on-the-fly" reverts with out the dirty work, though I'm a bit narrow on time lately but definitely I will try to play with until GRUB is fully working/functional.

Here is an example of what happens/need to be done in order to point and boot a ZFS environment/dataset:

Code: Select all

zfs set canmount=off ${ZROOT}
zfs create -o canmount=off ${ZROOT}${DATASET}
zfs create -o mountpoint=/ ${ZROOT}${DATASET}${BOOTENV}
zfs set freebsd:boot-environment=1 ${ZROOT}${DATASET}${BOOTENV}
zpool set bootfs=${ZROOT}${DATASET}${BOOTENV} ${ZROOT}

Here is a sample of the loader.conf line that need edit:

Code: Select all

...
vfs.root.mountfrom="zfs:zroot/ROOT/upgrade-2017-07-28-212555"
...

I will try to provide a simple script/workaround to make rollbacks from a LiveMedia, in the event the system cannot boot the OS, though most advanced/experienced users will prefer to perform this manually.

Sorry for any inconveniences.

[amaedl]

After Upgrade from 4303 (embedded) minidlna does not work any more.
(re-) starting it causes a kernel panic immediately.

Status > Services shows for DLNA/UPnP MiniDLNA
enabled is "OK" but status is "-"


it seems it is started - but then stopsn working.
Log says: (Pathes replaced by "...")

2017/08/02 23:41:40 monitor inotify_add_watch[kqueue,open](/....) [No such file or directory]
2017/08/02 23:41:40 monitor inotify_add_watch[kqueue,open](/....) [No such file or directory]
2017/08/02 23:41:40 monitor inotify_add_watch[kqueue,open](.....) [No such file or directory]
... (it complains all pathes that really do not exist (anymore) - it is no permission problem.
...
2017/08/02 23:43:29 monitor Added watch to .... [4480]
2017/08/02 23:43:30 upnpevents upnpevents_selectfds: file descriptor 4483 too big for select, limit is 1024
(thats the last entry)

any ideas? where else could I get a hint (log-file?)

[raulfg3]

Try to stop minidlna, delete share, start minidlna, And check that star service, once works, add shares.

[amaedl]

Addition:
almost same Problem with DAAP:
Stopping it causes a kernel panic immediately also.. :-/

I cannot exactly remember - but I think there was already a similar Bug in an earlier Version of nas4free in conjunction with LAGG - I am using a LAGG also....
?
https://sourceforge.net/p/nas4free/bugs/323/

? in build 3958 i already expierienced this problem also - but can't remember at which build after that it was fixed:
https://www.nas4free.org/forums/viewtop ... agg#p75885

[doktornotor]

? in build 3958 i already expierienced this problem also - but can't remember at which build after that it was fixed:
https://www.nas4free.org/forums/viewtop ... agg#p75885

Has never been fixed. The lagg has been completely screwed for quite some time.

https://sourceforge.net/p/nas4free/bugs/301/
https://sourceforge.net/p/nas4free/bugs/323/

[Jack Foobar]

Hello NAS peoples. I have a associated question for folks that have upgraded. Is there any functional difference in options between 10.3 and 11.0? I'm still on 10.3.0.3, and I'm trying to find the motivation to upgrade this thing. I'm doing plex, and samba, and all that jazz. Not sure what 11 brings over than a new OS underneath. Feel free to motivate me or demotivate me in any way you choose. All opinions or facts are welcome.

[raulfg3]

The only motivación is that 10.3 is end so no moré updates are offered.

So please consider to do a new fresh install on a new boot device, so You can test new 11 series And can revert to 10.3 If You need.