Announcing FreeNAS-8.0.1-RC2

[supernet33]

When will be the new good release? I been waiting to upgrade my freenas for a release :(

 

[Milhouse]

WARNING: The WebGUI Address could not be bind to , using wildcard

Also getting this now after an RC1 to RC2 GUI upgrade (AMD64 on an N36L with an Intel CT NIC, onboard Broadcom NIC disabled).

In addition, I noticed some boot errors/warnings in the console too:

Code:

Sep 23 16:24:32 freenas kernel: Starting syslogd.
Sep 23 16:24:33 freenas kernel: Clearing /tmp (X related).
Sep 23 16:24:33 freenas kernel: /etc/rc: WARNING: /etc/exports is not readable.
Sep 23 16:24:33 freenas kernel: /etc/rc: WARNING: failed precmd routine for mountd
Sep 23 16:24:33 freenas kernel: Starting rpcbind.
Sep 23 16:24:33 freenas kernel: Starting nfsd.
Sep 23 16:24:33 freenas kernel: Starting statd.
Sep 23 16:24:33 freenas kernel: Starting lockd.
Sep 23 16:24:33 freenas kernel: /etc/rc: WARNING: failed precmd routine for vmware_guestd
...
Sep 23 15:49:13 freenas kernel: Starting mountd.
Sep 23 15:49:20 freenas kernel: Usage: grep [OPTION]... PATTERN ...
Sep 23 15:49:20 freenas kernel: Try `grep --help' for more information.
Sep 23 15:49:20 freenas kernel: Waiting for http...

/etc/exports is readable, and contains the following entry:

Code:

/mnt/share -alldirs -maproot=bob:bob

 

[jfr2006]

Ah OK, gotcha. Yeah, 512MB would probably not be enough to allow the xz unpacker to run properly. But 3GB certainly should be! :D

Found out what was the problem. I use the .fullinstall.xz images files to unpack and write directly to the pen, using physdiskwrite. The problem, is that form some strange reason, all the latest images (including the 8.0.1-RC2) are 1GB in size and not 2GB....

 

[parks853]

Found out what was the problem. I use the .fullinstall.xz images files to unpack and write directly to the pen, using physdiskwrite. The problem, is that form some strange reason, all the latest images (including the 8.0.1-RC2) are 1GB in size and not 2GB....

I used the fullinstall.xz to write BETA 4 on my usb drive and my GUI upgrade failed as well (I used some mac tools instead of phydiskwrite). So, what is the easiest way for us to upgrade - write the new fullinstall.xz directly to the usb drive and apply the saved config file? Although, might be easier to hook up a CD drive and do the cd install so the GUI upgrade will work.

 

[jfr2006]

The only 2 viable solutions i found are:

- compile our own version and use the 2GB file generated.
- Use the .iso file and install it using a virtual machine with direct access to the pen (vmware can do this) and the configure this machine with all we want and upload our settings to this machine. After all done, use this pen to boot on the real machine.

Regards.

 

[coe]

I have a big problem with "Change Permissions" in 8.0.1-RC2-amd64 in the GUI.

When I try to chance the permissions to e.g. 750 or 770 for a zfs-dataset-volume recursively it always sets the volume folder to 755 and does not chance anything recursively.

When I try to change the owner recursively it only chances the owner of some files in some folders but not all. Most folders contain files with the new and the old owner. Very strange....

The only way I can change the permissions is via ssh.

Is this a bug or am I doing something wrong? Is there a way to reset the permissions of a folder recursively to a default value?

I'm seeing exactly the same bug. Updated the ticket on it.

http://support.freenas.org/ticket/638

Same problem here as well. 8.0.1-RC2-amd64 via GUI.

drwxrwxrwx 3 root ctankers 4 Sep 26 23:11 a
drwxrwxrwx 5 root ctankers 5 Sep 26 23:14 an
-rw-r--r-- 1 root ctankers 40 Sep 26 19:19 bsdcommands.txt
drwxrwxrwx 7 root ctankers 7 Sep 26 23:13 ga
drwxrwxrwx 3 root ctankers 3 Sep 26 23:17 gf
drwxrwxrwx 3 root ctankers 3 Sep 27 14:43 mu
drwxrwxrwx 2 root ctankers 2 Sep 26 18:22 se
-rwxrwxrwx 1 root ctankers 171 Sep 26 19:47 smartHDDtemps.sh
drwxrwxrwx 3 root ctankers 3 Sep 26 23:13 so
drwxrwxrwx 4 root ctankers 4 Sep 26 23:11 st
drwxrwxrwx 30 root ctankers 30 Sep 26 19:59 vc
drwxrwxrwx 46 root ctankers 46 Sep 26 23:15 vg

As you can see, permissions are all messed up. Trying to correct it by going U+RWX G+RX O-RWX and change the owner group to wheel, just to see what happens. Giving the command via web UI. Set Permissions Recursively ticked on.
Gives "An Error Occured!"

Result:
drwxrwxrwx 3 root ctankers 4 Sep 26 23:11 a
drwxrwxrwx 5 root wheel 5 Sep 26 23:14 an
-rw-r--r-- 1 root wheel 40 Sep 26 19:19 bsdcommands.txt
drwxrwxrwx 7 root ctankers 7 Sep 26 23:13 ga
drwxrwxrwx 3 root ctankers 3 Sep 26 23:17 gf
drwxrwxrwx 3 root wheel 3 Sep 27 14:43 mu
drwxrwxrwx 2 root wheel 2 Sep 26 18:22 se
-rwxrwxrwx 1 root wheel 171 Sep 26 19:47 smartHDDtemps.sh
drwxrwxrwx 3 root wheel 3 Sep 26 23:13 so
drwxrwxrwx 4 root ctankers 4 Sep 26 23:11 st
drwxrwxrwx 30 root ctankers 30 Sep 26 19:59 vc
drwxrwxrwx 46 root wheel 46 Sep 26 23:15 vg

Redoing the operation sets the same directories back to 777 standing and changes group again, giving same "An Error Occured".

This is a 7.1TB ZFS2 volume with no datasets. I think this error started when I created a dataset on the volume, decided I didn't need it, removed the dataset and noticed permissions to be all fubar. I have no idea did this error occur before I created the dataset or after I removed it.

Setting permissions manually at bash shell yields no errors.

 

[chris8051]

RC2 still not working on Dell R710

Still same problem on Dell R710 server. On boot from flash drive:

F1 FreeBSD
F2 FreeBSD
F5 Drive 0

F6 PXE
Boot: F1
<hangs forever here>