NAS4Free 9.3.0.2.1283 Released (FreeBSD 9.3-RELEASE-P7)

[zoon01]

The nas4free team has just released 9.3.0.2.1283.

NAS4Free Upgrade from 9.2.0.1 to 9.3.0.2.xxxx
=========================================

Upgrading NAS4Free "Embedded" or "Full" from 9.2 or older to 9.3.0.2 from webgui or from LiveCD/USB is problematic, due a new size of boot partition.
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 RECOMMENDED WAY.
Sorry for inconvenience.


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 9.3.0.2.1283
=================
Changes
- Upgrade to FreeBSD 9.3 RELEASE p7.
- Upgrade to Samba4.1 and add SMB3 in WebGUI.
- Convert to pkgng.
- Improved WebGUI under PHP 5.6.
- Improved WebGUI with Chrome.
- Improved config restore verbose output.
- Improved ZFS pool usage/tool and import ZFS disks.
- Improved ZFS pool import on embedded.
- Improved HAST switch with net.inet.carp.preempt.
- Improved PHP session handle.
- Replaced /dev/md0 with xmd using LZ4 compression.
- Replaced the server certificate with 2048bits key and sha256 signature.
- Changed rootfs layout. (2GB USB/CF is required. Full is 4GB or more.)
- Changed image files to use XZ.
- Drop SSLv3 support. (HTTPS must use TLS)
- Drop LiveCD mode support with less than 2GB memory. (install/upgrade only)
Supported minimum spec except LiveCD is 512MB memory + 512MB swap device or partition.
1024MB swap device or partition is recommended.
File based swap and ZFS volume swap is not recommended.
- Add WebGUI access restriction.
- Add NFS support in HAST service.
- Add default swap of 512MB for LiveUSB and before user configuration.
- Adjust number of Status|Processes.
- Add MBR partition to LiveUSB.
- Add log/mirrored log support in Disks|ZFS|Pools|Tools.
- Add expires HTTP header. (some js must be force reloaded.)
- Increase http upload size to 512MB.
- Remove last slash of the path added by filechooser.
- Add wait_on and spindown.
- Upgrade e2fsprogs to 1.42.12.
- Upgrade transmission to 2.84.
- Upgrade isboot to 0.2.8.
- Upgrade istgt to 20141125.
- Upgrade smartmontools 6.3
- Upgrade xmlstarlet to 1.6.1.
- Upgrade inadyn-mt to 02.24.43.
- Upgrade zoneinfo to 2014j.
- Change iperf2.x for iperf3.
- Upgrade samba to 4.1.14.
- Upgrade php to 5.6.4.
- Upgrade mDNSResponder to 561.1.1.
- Upgrade xmd to 0.4.2.
- Upgrade bash 4.3 to patch 33.
- Upgrade unison to 2.48.3.

Fixes:
- Never reject SMB3 and sendfile combination.
- Failed to mount NTFS with read-only.
- Missing mount_fusefs in /usr/local/sbin.
- Missing usb device configuration file.
- Missing default pkg repository.
- mount_ntfs is not installed to /sbin.
- Wrong variable in HAST script.
- /boot/kernel/fuse.ko is missing.
- /etc/platform is broken on full installation.
- Some DHCP setting of WebGUI does not work.
- xmlrpc is broken.
- Missing GPT partition in Disks|ZFS|Pools|Tools.
- Switching DHCP and static IP cause unexpected behavior.
- Some drives can't get disk model/description.
- The text on graph is not sized on Chrome.
- Firmware page show incorrectly.
- ntfs-3g is broken.
- Form size is too small on Chrome.
- HAST device is not imported by import disks.
- Stop flooding "Unknown USB device" to syslog.

CIFS/SMB
========
Authentication has changed
Only Local User or Active Directory can be selected.
Anonymous access has been dropped!

Improved security WebGUI access
=============================
When you have WebGUI Login error 403?
Make shure the pc is in the same network!
by default the System|General Setup Hosts allow field is empty so any one on
the same network of LAN interface can access the WebGUI allowed.
With a space delimited set of IP or CIDR notation you can add computers from outer network.
As an example the outer IP address and LAN address for remote access.

Experimental memory disk (geom_xmd.ko)
=====================================
This version contains a special memory disk driver called "xmd".
The following are the main features.

- on-demand memory allocation and de-allocation (zero fill/TRIM support)
- on-the-fly block level compression
- multiple compression methods and levels (none, LZ4/LZ4HC, ZLIB, LZMA2)
- mixed compressed blocks (can be changed at any time by xmdconfig)
- pre-compressed mfsroot by mkuzip(8) or mkulzma(8)
- provide the ioctl interface for the xmdconfig utility like mdconfig(8)

Regards,
The NAS4Free Team

[Lee Sharp]

Can we get some clue what is actually changing from point release to point release since they are happening so fast? I am working on an intermittent problem, and by the time it happens, there is a new release out so I am on an "unsupported" version... I JUST updated to the latest version this morning, and I am already obsoleted.

[zoon01]

please look here: https://sourceforge.net/p/nas4free/code/commit_browser

[hastdotwhat]

It's not very obvious from the commit browser what's been fixed and what hasn't, the entries have descriptions like "don't use 9", "fix changes", "update makefile", and so on, which can't easily be mapped to "Problem X reported reported in the 1213 thread has been fixed". I really appreciate the work you guys do on Nas4Free, but given that I have to do a complete reinstall (on a headless system with no graphics card and no CDROM drive, I have to wire up all sorts of add-ons to work with it) it's hard to tell whether it's safe to go through the install process yet or whether it's better to wait for further releases.

[zoon01]

If you have installend an 9.3.0.2.xxxx embedded verion you easy can upgrade to an newer verion of the 9.3.0.2.xxxx branche. No need for a reinstall than. We point important changes in webgui and readme, for detailed info you have to search yourself with given link. Anyway a newer build is always better to use than a past version, upgrade regular is our advice! Embedded installs makes for this your live more easy.

[alexey123]

I upgrade x86 over webgui without any problem today. But part of config was lost - minidlna extension was lost, thebrig was restored without any problem. It's probably a ghosts...

[sfranzis]

Upgraded x64 this morning over webgui without any problems.
Hadn't the time for testing everything, but zeroconf (mDNSResponderPosix) seems to work now.

Regards
Stefan

[JoseMR]

Successfully Upgraded N4F-9.3.0.2(1222) to N4F-9.3.0.2(1283) through to web gui and, configuration was maintained and everything working as expected, Thanks for this sweet release.

Regards

[taffeys]

It's not very obvious from the commit browser what's been fixed and what hasn't, the entries have descriptions like "don't use 9", "fix changes", "update makefile", and so on, which can't easily be mapped to "Problem X reported reported in the 1213 thread has been fixed". I really appreciate the work you guys do on Nas4Free, but given that I have to do a complete reinstall (on a headless system with no graphics card and no CDROM drive, I have to wire up all sorts of add-ons to work with it) it's hard to tell whether it's safe to go through the install process yet or whether it's better to wait for further releases.

Can we get some clue what is actually changing from point release to point release since they are happening so fast? I am working on an intermittent problem, and by the time it happens, there is a new release out so I am on an "unsupported" version... I JUST updated to the latest version this morning, and I am already obsoleted.

I agree with both hastdotwhat and Lee Sharp. Please provide an actual change log with specific changes/updates unique to each revision, not a summary of the major change. Don't continue to ask users to parse the commit browser to try and see if they want to apply an update.

[noclaf]

Isn't there a typo in the code?
r1285
b/trunk/etc/inc/config.inc
line 948

I suppose "return FLASE;" should be "return FALSE;"

[Earendil]

Didn't work for me, got

Code: Select all

Fatal error: Call to undefined function verify_xz_file() in /usr/local/www/system_firmware.php on line 255 

but nothing in the logs (except the "device pass" errors). I can recover the N4F server but another try gets the same thing. The .xz file tests ok in 7-Zip and I even re-downloaded it. Rebooting the N4F server results in the same thing. I will mess with it a bit before I do a default embedded install. Good thing I backed up that config file.

Zoon01, a nit pick perhaps but I suddenly feel like a newbie. Which file is used to update with? The .xz file or the .img file (after 7-Zip)? After hitting the "Upgrade firmware" button, using the .xz file gives me the above but using the .img file gives me a blank webpage and this

Code: Select all

lighttpd[2100]: 	(request.c.1162) request-size too long: 539320803 -> 413

in the logs. The nit pick is I suggest in the this web page

N4FUpgradeCapture.PNG

you specifically mention which file to use, the .xz file or the .img after it's been decompressed in 7-Zip.

UPDATE:
After I did a default embedded install, restored my saved config file and rebooted, everything came back as expected for v9.3.0.2.1283. Yet in the logs I still see that

Code: Select all

kernel: 	xptioctl: put "device pass" in your kernel config file
kernel: 	xptioctl: pass driver is not in the kernel

"device pass" message in the logs and in the console. Is that expected?

[alexey123]

Didn't work for me, got

Code: Select all

Fatal error: Call to undefined function verify_xz_file() in /usr/local/www/system_firmware.php on line 255 

but nothing in the logs (except the "device pass" errors).

May be you tried upgrade from 9.2 based over webgui ??
This action is impossible without special modifications NAS4Free (or firmware image need unxz and archive as gz) - 9.2 based version not know work with xz.

Also need resize and format system partition - here small howto viewtopic.php?p=47745#p47745

[lindsay]

Got the same too alexey123 and using NAS4Free 9.3.0.2.1268 Released (FreeBSD 9.3-RELEASE-P7)

[Roman]

Just installed .1283, Webgui firmware update from .1268, using the .xz file.
So far, last 1 hour, all seems to be working.
Sunday night i did a fresh .1268 installation, a new NAS setup.
I had some problems with "Power Daemon" in Advanced settings.
If i enabled this option, my NAS started rebooting, randomly.
Sometimes i was able to bring up login screen and browse arround, but mostly it would reboot as soon as it booted up.
This option is now disabled, it took a while to figure out what was causing the reboots, because i did change a lot of the settings before it started to reboot.
Don't feel like trying to enable that Power Daemon with this firmware, it may take a few re-boots before i get enough time to login and go to the Advanced settings screen to disable it again.

My NAS Hardware:
Platform x64-embedded on AMD Athlon(tm) 5350 APU with Radeon(tm) R3
System ASRock AM1B-ITX
HDD: 4 x 2TB WD Red, SATA III
Firmware: FreeBSD 9.3-RELEASE-p7 #0 r276635M: Sun Jan 4 00:32:46 CET 2015

I do get another error, same as with .1268:
mDNSResponderPosix: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C2FD60 nas.local. (Addr) that's already in the list
mDNSResponderPosix: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C30180 x.x.x.192.in-addr.arpa. (PTR) that's already in the list

Not sure what's causing that, but everything seems to work fine.

Copied some files last night (> 400Gbyte, half the files were 10GB to 20GB in size) and had > 90Mbyte/s transfer (about 90min for the transfer). Small files, like photos, it does drop to about 15Mbtye/s.

[jonheal]

Two small issues with this release for me:

• The Web interface does not log me out when I close the web browser. The next time I browse to the URL, I am in without authentication.
• Once an hour, I get this in the log (I did not configure IPv6):

  Code: Select all

  mDNSResponderPosix: mDNSPlatformSendUDP got error 50 (Network is down) sending packet to FF02:0000:0000:0000:0000:0000:0000:00FB on interface 192.168.1.21/em0/2

[Earendil]

Didn't work for me, got

Code: Select all

Fatal error: Call to undefined function verify_xz_file() in /usr/local/www/system_firmware.php on line 255 

but nothing in the logs (except the "device pass" errors).

May be you tried upgrade from 9.2 based over webgui ??
This action is impossible without special modifications NAS4Free (or firmware image need unxz and archive as gz) - 9.2 based version not know work with xz.

Also need resize and format system partition - here small howto viewtopic.php?p=47745#p47745

Not quite Alexey. As you can see in the attached picture I was going from v9.3.0.2.1213 to the latest, v9.3.0.2.1283. Oh well, a default embedded install worked so no worries. Now all I need to wait for is your next version of TheBrig.

[Roman]

Now all I need to wait for is your next version of TheBrig.

Why wait, is the current TheBrig version not working with 9.3.0.2?
I will be installing it tonight, or should I wait?

[alexey123]

Current TheBrig version work on 9.3, because we use special /etc/rc.d/jail file, which replace system /etc/rc.d/thebrig during boot server.
I tested
New version will work with jail.conf https://www.freebsd.org/cgi/man.cgi?que ... tion=5&n=1 for give to work vnet , mount zfs.

---

I tried to boot in save mode - and without success


But over escape to loader prompt - pressed key 5 I successfully boot in single user mode.

Code: Select all

boot -s

Sommothing wrong, but may be add option on boot menu for boot in single user mode ?

[jack47]

Zeroconf has been fixed with this release or is still broken?

Regards Jack

[sfranzis]

Zeroconf has been fixed with this release or is still broken?

Regards Jack

viewtopic.php?p=48368#p48368

[jack47]

Zeroconf has been fixed with this release or is still broken?

Regards Jack

viewtopic.php?p=48368#p48368

thanks, didn't see the post

[crest]

Hi,

did an embedded installation (OS+Data+Swap) from scratch with a new USB stick and tried to get the data partition mounted (da0, MBR partition 2, file system UFS, mount point name LOG) but it's not accepted, see error msg:

Code: Select all

The following input errors were detected:
    /dev/da0s2: Can't get UFS ID.
    dumpfs: /dev/da0s2: could not read superblock to fill out disk

This is the partition layout made by the installer (livecd)

Code: Select all

Gerät /dev/da0 - Generic Flash Disk 5.00

******* Working on device /dev/da0 *******
parameters extracted from in-core disklabel are:
cylinders=515 heads=255 sectors/track=63 (16065 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=515 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 63, size 3678822 (1796 Meg), flag 80 (active)
	beg: cyl 0/ head 1/ sector 1;
	end: cyl 228/ head 254/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 3678885, size 3036285 (1482 Meg), flag 0
	beg: cyl 229/ head 0/ sector 1;
	end: cyl 417/ head 254/ sector 63
The data for partition 3 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    start 6715170, size 1558305 (760 Meg), flag 0
	beg: cyl 418/ head 0/ sector 1;
	end: cyl 514/ head 254/ sector 63
The data for partition 4 is:
<UNUSED>

Did I miss something or is it an error?

Regards
crest

[kfnas]

Hello, big thanks for upcomming .1283 update! anyway, two issues:
- how to load by default in embedded version aesni.ko ? in dmesg this feature was detected but kernel module was not loaded automatically

Code: Select all

CPU: Intel(R) Atom(TM) CPU  C2750  @ 2.40GHz (2400.14-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x406d8  Family = 0x6  Model = 0x4d  Stepping = 8
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x43d8e3bf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,AESNI,RDRAND>
  AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
  AMD Features2=0x101<LAHF,Prefetch>
  Standard Extended Features=0x2282<TSCADJ,SMEP,ENHMOVSB>
  TSC: P-state invariant, performance statistics

- sadly also in this release the config parser for lagg0 and VLANs under lagg0 is not working correctly
I have to do a workaround and write under rc.conf

Code: Select all

cloned_interfaces 	lagg0

and command scripts

Code: Select all

ifconfig vlan11 create vlan 11 vlandev lagg0 up 	PostInit 

the goal here is to have lacp config of two igb0/igb1 to create lagg0 (with IP layer on it without VLAN 802.11Q tag e.g. untagged) and create VLANs under lagg0 (without IP either and here exclusively for VBOX service)

thankyou!

[daoyama]

Currently direct loading of xmd is enabled on Raspberry Pi only.
However, you can enable it if you create mdlocal.uzip in the same location of mdlocal.xz.

This is unsupported feature.
Before doing, don't forget make a backup configuration.

1. prepare enough work space for about 1GB. (e.g. /mnt/data)
2. decompress mdlocal.xz to work space.
# xz -dcv /cf/mdlocal.xz > /mnt/data/mdlocal
3. create compressed image by mkuzip (32KB compressed chunks)
# mkuzip -s 32768 /mnt/data/mdlocal
4. copy it into /cf
# mount -u -rw /cf
# cp /mnt/data/mdlocal.uzip /cf
5. reboot the server
# shutdown -r now

If you don't want this feature, delete /cf/mdlocal.uzip.

Note:
xmd can handle other compression type but startup script check only uzip.
You can decompress uzip file by uncloop command
# uncloop /cf/mdlocal.uzip > /mnt/data/mdlocal2

[Triskkele]

Unable to use live CD of Nas4Free 9.3.0.2.xxxx series due to the memory disk driver xmd which cannot mount the virtual drive into memory.

[jack47]

Zeroconf has been fixed with this release or is still broken?

Regards Jack

viewtopic.php?p=48368#p48368

thanks, didn't see the post

Installed build 1283.
ZEROCONF IS STILL BROKEN! Can't access nas4free using hostname (example: http://nas4free.local or ssh user@nas4free.local ) and OSX does NOT see AFP shares automatically (accessing usign afp://IP_OF_NAS is working though).

In build 972 it worked.

Please fix it.

Regards Jack

[sleid]

9.3.0.2 - Nayla (revision 1283)

smbd[27866]: unknown tag type 64

And same error: fixed
https://forums.freebsd.org/threads/smbd ... ror.35851/

[Earendil]

Current TheBrig version work on 9.3, because we use special /etc/rc.d/jail file, which replace system /etc/rc.d/thebrig during boot server.
I tested
New version will work with jail.conf https://www.freebsd.org/cgi/man.cgi?que ... tion=5&n=1 for give to work vnet , mount zfs.

Sorry Roman, I should have been more clear. I was waiting for Alexey's improvements to TheBrig.

Alexey thanks, I will try out the new version you sent me on my new N4F server - no data to loose yet. Will post any findings in TheBrig's thread.

---

UPDATE:
After I did a default embedded install, restored my saved config file and rebooted, everything came back as expected for v9.3.0.2.1283. Yet in the logs I still see that

Code: Select all

kernel: 	xptioctl: put "device pass" in your kernel config file
kernel: 	xptioctl: pass driver is not in the kernel

"device pass" message in the logs and in the console. Is that expected?

Anyone have an idea why I am getting these messages in the logs and the console?

[JoseMR]

9.3.0.2 - Nayla (revision 1283)

smbd[27866]: unknown tag type 64

And same error: fixed
https://forums.freebsd.org/threads/smbd ... ror.35851/

Used to have this error in my NAS log every time i interact with my smb shares, i think while writing most to shares but with some research and testing concluded that selecting "Enable ZFS ACL" on my smb shares fixed this issue, also the link you posted from the FreeBSD forums is another workaround for this, but on NAS4Free just simply checking Enable ZFS ACL on the smb shares fix this issue, at least for me on varios revisions from 1190 and later.

Regards

[sleid]

9.3.0.2 - Nayla (revision 1283)

smbd[27866]: unknown tag type 64

And same error: fixed
https://forums.freebsd.org/threads/smbd ... ror.35851/

Used to have this error in my NAS log every time i interact with my smb shares, i think while writing most to shares but with some research and testing concluded that selecting "Enable ZFS ACL" on my smb shares fixed this issue, also the link you posted from the FreeBSD forums is another workaround for this, but on NAS4Free just simply checking Enable ZFS ACL on the smb shares fix this issue, at least for me on varios revisions from 1190 and later.

Regards

Fixed ! thanks