NAS4Free 9.3.0.2.1310 Released (FreeBSD 9.3-RELEASE-P8)

[daoyama]

BUG: if in hostallow (management allow address) [system:general:hostallow] is subnetmask specified with CIDR width bigger as /24 e.g.

Code: Select all

 0.0.0.0/0 

or

Code: Select all

10.0.0.0/16

after reboot the management is not accessible
in

Code: Select all

cf/conf/config.xml

is the value presented.. looks like it is not properly parsed

Probably other reason. I use 172.18.0.0/16 network and DHCP.
My hostallow is 172.18.0.0/16 only.
Do you check /var/etc/lighttpd.conf?
server.bind and remoteip is written to it.

[daoyama]

* AFPD tries to read/store file metadata in extended attributes of the filesystem. But this fails with ZFS, as ZFS doesn't support extended attributes on FreeBSD. Normaly you wouldn't notice this. Everything worked find. Only Lightroom failed to load nearly 80% of the RAW files because it got disturbed when afpd sent an error about the metadata (maybe a little bug in the Adobe software too - kchkch)
With the auxilliary parameter 'appledouble = v2' in every afp volume metadata are stored in the .AppleDouble directories again and Lightroom is happy too.

It seems checkbox require. thank you.

* small cosmetic issue: when I add auxiliary parameters in the AFP config these parameters are not indented in the file afp.conf

Bildschirmfoto 2015-01-20 um 20.18.42.png

You don't need time machine line. It have checkbox to enable.

[daoyama]

sorry for inconvenience.

hello developers! thankyou for your efforts at this project but.. why for hell (sorry for the expression) are you changing the partitions geometry with each build??? [r1307] for instance?

First change is store large app such as samba4.1. But I didn't think carefully about GPT and swap partitions.
Next GPT and swap, finally adjust alignment for large alignment device such as SSD and SD card.
But some user complain about firmware image. It may change later once again.

Unfortunately, there is no beta line for 9.3 series, you need keeping version if you don't have a problem in current version.

[narenback]

Hi,

this is just plain frustrating.
I'm running a headless install here (and not owning any external display). I managed to update 9.2.0.1.972 -> 9.3.0.2.1283 by browsing the fixed IP after install, but it does not seem to work this time. I don't know what's gone wrong in the boot since I don't have any access to the console or logs this time. Any suggestions how to get the server back online?

BTW There should be a warning for not-straightforward firmware upgrades somewhere, I upgraded thru the GUI.

I'm having the same problem as you did but I was successful attaching a keyboard and using the the console setup menu.
I think my steps was:
Press 2 For ip setup --> This will open up the IP setup interface
Enter for DHCP setup --> This will select DHCP for the default interface
O for OK --> Saving the changes and exit to the console.

My suggestion to the is that DHCP should be the default option for IP, not a strange fixed IP.

[JoseMR]

Hi,

this is just plain frustrating.
I'm running a headless install here (and not owning any external display). I managed to update 9.2.0.1.972 -> 9.3.0.2.1283 by browsing the fixed IP after install, but it does not seem to work this time. I don't know what's gone wrong in the boot since I don't have any access to the console or logs this time. Any suggestions how to get the server back online?

BTW There should be a warning for not-straightforward firmware upgrades somewhere, I upgraded thru the GUI.

There is a warning, is in the Readme.txt

README & CHANGELOG


IMPORTANT - PLEASE READ!


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.

Regards

[anana]

the upgrade as stated in release notices is not possible over web using upgrade modus (actually it is in some rare cases - not standard)

Yes.. only reason I tried to upgrade thru gui in the first place, was the lack of warnings whatsoever. If the gui proposes an update through gui as an option, shouldn't it be safe?

- install on the notebook or any PC an virtualbox or vmware for simplier access (virtualbox might be better choise for novicer)

And I'm truly thankful of this! I've never thought virtualbox sessions as an option and always have made a real LiveUSB with unetbootin, etc. Also the idea of mounting the destination after install and editing config.xml before booting up was a welcome idea.

It's now fixed and running. Thanks.

PS. I would also like to see DHCP as a default option since it's the only thing holding the users back from an easy headless install.

[anana]

These filenames are extremely confusing. First of all, why even bother with LiveCD, nobody burns CD's anymore, just forget that.
Second of all, why can't you have the text 'installer' in the filename of the images that are meant for installing, and 'update' in the filenames that are meant for updating?

The nas4free wiki is not acceptable, there is no master index, and i constantly find 'guides' deep in some forum thread that i never even knew about, totally absent from any 'master' wiki pages.

The installer suggests using the entire available space from the empty unformatted destination USB device as swap by default, pressing enter there as in going by defaults will result in an error.
regards, mike

I know this isn't the thread for discussing this, but these are all true and valid suggestions.

Even the the master Download link is unintuitive and I spent a minute clicking around nas4free -pages before I got it: the link is up in the header, not under "Downloads" -side bar link.
The first time I was installing this a year ago, it was difficult to find information about which file to download. LiveCD:s are traditionally for TESTING the product before installing. And since it read everywhere that embedded is the recommended install, of course I went and downloaded the "embedded"-file.
Last time I was updating from 9.2. to 9.3. branch I searched for half'n'hour trying to find out the benefits and necessity of a swap partition and finally find the answer from some FreeNAS-forum thread and some individual blog post about ZFS being a memory hog.
So It's a good update the preferred partition table is now in the "recommended" section, but I still haven't found out a clear and official reason for having a swap partition on USB stick.

Other than this general unintuivitity, I'm very pleased of this software and will donate. Thanks.

[macafee]

Upgraded from rev 1213 in webgui
embedded x64, boot device is 4GB USB
Running fine, but In System->Firmware Error message: Boot partition is too small. You need reinstall from LiveCD or LiveUSB, or resize boot partition of da0s1a.

Backup your configuration.
Install from scratch.
Restore configuration.

Bildschirmfoto 2015-01-18 um 22.53.56.png

I install from scratch with physdiskwrite ver0.52 tools but the problem is still existent. What's wrong?

[daoyama]

Even the the master Download link is unintuitive and I spent a minute clicking around nas4free -pages before I got it: the link is up in the header, not under "Downloads" -side bar link.
The first time I was installing this a year ago, it was difficult to find information about which file to download.

You are right. It seems it's not user friendly!
I think Download link should write in Downloads page, too.

[ggibeau]

Here is my issue.

Running NAS4Free for a while now. Just upgraded from 1283 to 1310.

Taking the warnings to heart - I did not use the Web GUI firmware upgrade path.

I first backed up the current configuration using system-firmware-backup, powered down the machine, removed USB stick from motherboard, downloaded NAS4Free-x64-embedded-9.3.0.2.1310.img.xz file. Using 7Zip - extracted to .img file. Using Win32DiskImager - wrote image to USB stick (over writing 1283 version).

Replaced USB stick on motherboard - powered on system.

Initially - tried to restore config - and received message about file being incompatible file type. Did some reading on forum - and went to Disks - Management and clicked "Clear config and Import disks". Disks imported ok - then went to Disks - ZFS and detected and synchronized to get ZFS pool and mount points to display.

Went back to restore config - same message (incompatible file type). Restored an older config (from October) - system restored and rebooted. Upon reboot - tried restoring backup from tonight - and then it worked just fine - weird.

I can access shares just fine - and all configs seem to be intact.

However, under System - Firmware - I still get the message - "Boot partition is too small. You need reinstall from LiveCD or LiveUSB, or resize boot partition of da0s1a. ".

What do I need to do to burn the img file so the partition sizes are correct?

Thanks in advance,

George

[kfnas]

BUG: if in hostallow (management allow address) [system:general:hostallow] is subnetmask specified with CIDR width bigger as /24 e.g.

Code: Select all

 0.0.0.0/0 

or

Code: Select all

10.0.0.0/16

after reboot the management is not accessible
in

Code: Select all

cf/conf/config.xml

is the value presented.. looks like it is not properly parsed

Probably other reason. I use 172.18.0.0/16 network and DHCP.
My hostallow is 172.18.0.0/16 only.
Do you check /var/etc/lighttpd.conf?
server.bind and remoteip is written to it.

Code: Select all

$HTTP["remoteip"] == "0.0.0.0/0" {
        url.access-deny = ( "~", ".inc", ".htpasswd" )
}

looks like then, lighttpd have issues with such mask, tested on vbox, had to kill the process and reinialized with

Code: Select all

/usr/local/sbin/lighttpd -f /var/etc/lighttpd.conf -m /usr/local/lib/lighttpd

definitely

Code: Select all

0.0.0.0/0

is not ok

[ku-gew]

When I was using 9.2.x I never had problems of any kind, but now with 9.3.x on the same HP N40L (I only switched USB boot stick) I get an unresponsive system after about a week of uptime. I don't even know how to get what's wrong, since the logs are obviously not saved ("embedded" installation).
Anyone had "similar" issues?

[kfnas]

I'm running it approx within week (heavy load with virtualbox inside as plugin) and have no PERFORMANCE issuses till now...

whatever start with dmesg when the system is not responsive...
What I had as issue was a stuck smbd within kernel on ZFS which locked out one files ACL and then it crashed.. don't know who to blame... ZFS or SAMBA... but that was terrible...
perhaps you are hitting same bug issue here? if you are experienced, you should get the notion about what is approx wrong..

Code: Select all

ps aux

or

Code: Select all

dmesg

or

Code: Select all

gstat

runned from shell might give some answers.. in my issue with that locked file.. any service (user/kernel) which wanted to read the file descriptor (ZFS ACL/TIME/UNIX ACL...) went as dead process ... so the system was unresponsive....

[ku-gew]

I'll try to log in from the same network, hoping it works... because from remote, I cannot reach it by SSH.

[slaycock]

Trying to do an upgrade from 1283 to 1310 via the img file. Done several downloads and unzipped it using various versions of 7-zip but I keep getting an error message that the image is corrupt. Recently did a new install of the version before 1283 with no problems.

[svily0]

@slaycock
Had you read the first message in this thread you would've known that it's not possible to upgrade from any previous version.
Do a clean install and restore your config.

Regards!

[slaycock]

Ah.. My bad. I knew this was an issue for another recent version. It does beg the question though as to why there is an .img file if upgrading isn't possible.

[hastdotwhat]

These filenames are extremely confusing. First of all, why even bother with LiveCD, nobody burns CD's anymore, just forget that.

The USB install has a history of being somewhat problematic while the CD install just seems to work, so it provides a known-good (if somewhat awkward to deal with) install option.

[noclaf]

Possible bug in samba.
When I check "use sendfile" after applying changes the check is gone. I solved it (I hope) by putting "use sendfile = yes" into auxilliary parameters, but this error should be tackled. thx

[JoseMR]

Hi Developers, also listen NAS4Free users, I found a strange password bug that can be the cause of many shady/unresolved issues on N4F for some users.

#1 If you cannot longer access the Advanced|File Manager, you probably used this character: \ in your WebGUI password.

#2 If you cannot apply the UPS configuration under Services|UPS because of this: Error: The changes could not be applied (error code 1). you probably used a strong password with special characters including this ones: \ # @ and so on, however after a reboot the UPS Status will show the load or the battery level but the system will now shutdown after the specified time during battery operation.

Note: My WebGUI password is a strong 16 chars length with mixed upper/lower case letters and numbers but also have this characters: \ # @ also this two bugs has been driving me nuts for quiet some time, but i decided to test/research in my own physical server to be sure i am correct about it.

My solution:
Eliminating the following characters: \ # @ from my password fixed these strange behaviors, just replaced them with numbers, in short it appears that N4F don't like special characters on the root password.

Tested on N4F 9.3.0.2 Nayla, revision 1310 and revision 1283 Embedded and Full

Kind Regards
José

[dundermiflin]

Upgraded from rev 1213 in webgui
embedded x64, boot device is 4GB USB
Running fine, but In System->Firmware Error message: Boot partition is too small. You need reinstall from LiveCD or LiveUSB, or resize boot partition of da0s1a.

Backup your configuration.
Install from scratch.
Restore configuration.

Bildschirmfoto 2015-01-18 um 22.53.56.png

I install from scratch with physdiskwrite ver0.52 tools but the problem is still existent. What's wrong?

I'm in the same situation.

Installed from scratch in a totally new USB stick.
Restored config file from old 9.2 installation.
All pools, zfs, and almost everything is working normally, but in FIRMWARE section I have :

Boot partition is too small. You need reinstall from LiveCD or LiveUSB, or resize boot partition of da0s1a

[ChriZathens]

Download the liveusb image and transfer it to a usb stick.
Get a second usb stick
Plug them both and boot from the liveusb stick.
Select to install to usb and select the second stick as destination
Once done remove the stick with the live usb version and boot from the second
Restore config