NAS4Free 9.3.0.2.1283 Released (FreeBSD 9.3-RELEASE-P7)

[JoseMR]

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

Hi, have you tried accessing your server with the new hostname without the .local ?

I can access my NAS4Free with my new hostname if i omit the .local, example http://myserver

Regards

[romanov.df]

https://wiki.samba.org/index.php/FAQ

Trusts

Does Samba support trust relationship with AD?

Trusts are currently not finished implemented.Samba can be trusted, but can't trust yet.
But even this is unofficial and should not be relied on, because "parts that appear to work are a partial development that just happen to be in our released versions" (July 2014).

F....K !!!!

Why you add this version?!

[qzbman]

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.

I have the same issue, (and same build) but as this is a new build I cannot tell if it is only this release or if the issue existed in other releases. Has anyone with this mboard/CPu config been able to enable "Power Daemon" without the continuous reboots on earlier builds?

[STAMSTER]

Where can I find drivers list for this release? I'm looking for an em Intel driver (version).

[raulfg3]

https://www.freebsd.org/releases/9.3R/announce.html

https://www.freebsd.org/releases/9.3R/relnotes.html

no news about em driver on BSD 9.3

[STAMSTER]

Thank you raulfg3! I'm having issues with em driver / i217LM Intel chip.... igb driver and i210AT chip working fine.

[Pappmann]

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

I have the same problem, is there any solution??

[svily0]

It is /dev/da0s2a
Find out what's in slice 2 with:

Code: Select all

bsdlabel /dev/da0s2

[Pappmann]

no, its now da0s3, da0s2 is now standart swap partition...