XigmaNAS 11.2.0.4.6171 released (FreeBSD 11.2-RELEASE-P4)

[zoon01]

We are pleased to announce the release of XigmaNAS version 11.2.0.4.6171 - Omnius.

First BACKUP your current Configuration!
READ THE readme_11.2.txt!

Be aware that gvinum and geom raid5 will die for sure!
Softraid note:
==============
The option to create a softraid has been removed, existing softraid configurations are not impacted.
Softraid will be marked as deprecated in future 12.x series.
Please migrate to ZFS if you haven't done yet.

Download build 11.2.0.4.6171
Please Read the readme_11.2 file


Changes after release 11.2.0.4.6154
======================
- WebGUI code & framework improvements.
- Added kernel patch to fix a panic with lagg and vlan.
- Downgrade virtualbox-ose to 5.2.18. (again output on VNC)
- Upgrade tmux to 2.8.
- Upgrade tzdata to 2018g.
- Upgrade dialog to 1.3-20181022.
- Upgrade samba to 4.8.6.

Note:
- Make a new backup of your system configuration and store this on safe location, the system config.xml could be upgraded!
- Clear your browser's cache to avoid display issues after upgrade when coming from older release.

Regards,
Team XigmaNAS

[zoon01]

READ THE readme_11.2.txt!

I have set this in bold, not everyone can upgrade from older embedded versions than minimum 11.2.0.4.6154 and up.
Still to many users did not read and tryed to upgrade to the 11.2.0.4.6154 release

[CrashDavis]

Thanks for the quick release.

[JoseMR]

Thanks XigmaNAS team for this prompt release as always, plain rock solid stable.

RootOnZFS users please READ HERE for the latest changes and improvements.

Regards

[jamaroney]

Embedded upgrade from 6154 went smoothly - thanks!

[Uzi]

When trying to do the recommended new embedded install I had problems with the install routine in the 6171 ISO file.

I got a completely blue screen after choosing the install options (always #1) and right before the source has to be chosen. After waiting for over 3 minutes I pressed CTRL+C and was back at the start of the installer.
After several attempts I just used the ISO of 6154 which worked flawless. Said blue screen appeared for about 6 seconds.
The following embedded upgrade from 6154 to 6171 worked flawless as well.

Hardware: Supermicro X11SSM-F/ 32GB RAM/ Intel(R) Xeon(R) CPU E3-1260L v5/ BIOS 2.1a/ 12x ST8000VN0022/ 2x LSI SAS2008 Controllers (1 used for 4 HDDs)/ normal Boot Media: SanDisk Ultra Fit 16GB/ ISO mounted as USB-DVD-Drive by the IPMI Java Console

[doktornotor]

1/ The phpMyAdmin config created by the init script is broken:

Code: Select all

root@nas4free:/usr/local/www/phpMyAdmin# php index.php
<p>Failed to load phpMyAdmin configuration (./config.inc.php:3): syntax error, unexpected '$i' (T_VARIABLE)</p>

Fix:

Code: Select all

--- /etc/rc.d/mysqldb     2018-11-03 23:27:13.436970000 +0100
+++ /etc/rc.d/mysqldb   2018-11-03 23:25:45.511306000 +0100
@@ -80,7 +80,7 @@
                --match '//mariadb' \
                        --output '<?php' --nl \
                        --if 'string-length(phrasecookieauth) > 0' \
-                               --output "\$cfg['blowfish_secret'] = '" --value-of "phrasecookieauth" --output "'" --nl \
+                               --output "\$cfg['blowfish_secret'] = '" --value-of "phrasecookieauth" --output "';" --nl \
                        --break \
                        --output '$i = 0;' --nl \
                        --output '$i++;' --nl \

2/ Dunno what was the idea with my.cnf GUI configuration but the configuration has no effect since it's expected in

Code: Select all

--defaults-extra-file=/var/db/mysql/my.cnf

but instead it's placed to

Code: Select all

/usr/local/etc/my.cnf

Alternative (global) location that is honored is /usr/local/etc/mysql/my.cnf. The one currectly used in the init script does nothing. This works for me:

Code: Select all

--- /etc/rc.d/mysqldb       2018-11-03 23:25:45.511306000 +0100
+++ /etc/rc.d/mysqldb   2018-11-04 00:32:06.637252000 +0100
@@ -29,7 +29,7 @@
 mkconf_cmd="mysqldb_mkconf"

 phpmyadmin_conf=${phpmyadmin_conf:-"/usr/local/www/phpMyAdmin/config.inc.php"}
-mysqldb_conf=${mysqldb_conf:-"/usr/local/etc/my.cnf"}
+mysqldb_conf=${mysqldb_conf:-"/var/db/mysql/my.cnf"}
 mysql_user=${mysql_user:-"mysql"}
 mysql_group=${mysql_group:-"mysql"}
 mysqldb_ipaddr=${mysqldb_ipaddr:-"127.0.0.1"}
 

(Alternatively, you could define the mysqldb_conf variable in System > Advanced > rc.conf, I guess.)

[Shperrung]

Readme file says what shouldn't be done:

Do NOT upgrade servers lower than XigmaNAS 11.2.0.4.6154
========================================================
Upgrading XigmaNASо "Embedded" or "Full" from any version below XigmaNAS 11.2.0.4.6154 by
webgui or from LiveCD/USB will be problematic!!!

But what we have to do if need to upgrade version lower than XigmaNAS 11.2.0.4.6154?
Do we need to setup XigmaNAS 11.2.0.4.6154 as essential interim update before 11.2.0.4.6171?
And what actions have to be done at this step on 11.2.0.4.6154 before next upgrade (load config file, zfs synchronization...)?

[Uzi]

But what we have to do if need to upgrade version lower than XigmaNAS 11.2.0.4.6154?
Do we need to setup XigmaNAS 11.2.0.4.6154 as essential interim update before 11.2.0.4.6171?
And what actions have to be done at this step on 11.2.0.4.6154 before next upgrade (load config file, zfs synchronization...)?

What you have to do is written in the next paragraph of the readme:

Please download and save your config from WebGUI first and backup all files from the second data partition
if used on the install media! Now you can perform a reinstall from LiveCD/USB, after installation you
can restore your previously saved config.

Technically you don't have to setup XigmaNAS 11.2.0.4.6154 as an essential update (but I had to do it, see my post above).
After reinstall, you restore the config you saved before, reboot and are done. If you used the data partition you'll only have to set the mount point again and restore the data on the data partition afterwards.

[JoseMR]

When trying to do the recommended new embedded install I had problems with the install routine in the 6171 ISO file.

I got a completely blue screen after choosing the install options (always #1) and right before the source has to be chosen. After waiting for over 3 minutes I pressed CTRL+C and was back at the start of the installer.
After several attempts I just used the ISO of 6154 which worked flawless. Said blue screen appeared for about 6 seconds.
The following embedded upgrade from 6154 to 6171 worked flawless as well.

Hardware: Supermicro X11SSM-F/ 32GB RAM/ Intel(R) Xeon(R) CPU E3-1260L v5/ BIOS 2.1a/ 12x ST8000VN0022/ 2x LSI SAS2008 Controllers (1 used for 4 HDDs)/ normal Boot Media: SanDisk Ultra Fit 16GB/ ISO mounted as USB-DVD-Drive by the IPMI Java Console

What happens if you call directly:

Code: Select all

# /etc/install/zfsinstall.sh

You don't have to roll XigmaNAS RootOnZFS, I Just asking since RootOnZFS installer is written completely in shell unlike the standard XigmaNAS installers, if this installer do works for you, then we can check on the files.php, if this shell installer still gives a blank blue screen it may be some settings on the dialog.

Regards

[lindsay]

Actually nice that you have to install new version and import settings.
Then i can install xigmanas and root on zfs.
Why i have not done it yet is beacuse of i am lazy

[adultery_nas]

Went smoothy for me as usual! Thanks @zoon01 !

[Uzi]

What happens if you call directly:

Code: Select all

# /etc/install/zfsinstall.sh

You don't have to roll XigmaNAS RootOnZFS, I Just asking since RootOnZFS installer is written completely in shell unlike the standard XigmaNAS installers, if this installer do works for you, then we can check on the files.php, if this shell installer still gives a blank blue screen it may be some settings on the dialog.

After choosing install option #1 I get straight to the dialogue where I chose the destination drive. I didn't dare to go further.

[JoseMR]

What happens if you call directly:

Code: Select all

# /etc/install/zfsinstall.sh

You don't have to roll XigmaNAS RootOnZFS, I Just asking since RootOnZFS installer is written completely in shell unlike the standard XigmaNAS installers, if this installer do works for you, then we can check on the files.php, if this shell installer still gives a blank blue screen it may be some settings on the dialog.

After choosing install option #1 I get straight to the dialogue where I chose the destination drive. I didn't dare to go further.

Thanks for report back, I will forward to dev team to look into whats causing the Standard php installer to hang on you, though I suspect is something waiting for response here causing the halt.

Regards

[zoon01]

lets go to 6177