XigmaNAS 11.2.0.4.5774 released (FreeBSD 11.2-RELEASE-P0)

[zoon01]

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

Download build 11.2.0.4.5774
Please Read the readme_11.2 file


Changes after release 11.1.0.4.5762
======================
- WebGUI code & framework improvements.
- Update translations.
- Upgrade devcpu-data to 1.18.
- Upgrade e2fsprogs to 1.44.3.
- Upgrade php to 7.2.8.
- Upgrade virtualbox-ose to 5.2.16.

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 nas4free release.

Regards,
Team XigmaNAS

[Snapshot]

Upgraded from 5750 and nothing obviously broken....

[lindsay]

Upgrade OK here too

[provels]

Upgraded here, no issues.

[adultery_nas]

Works perfectly! Thanks for the frequent updates!!

[doktornotor]

Works perfectly! Thanks for the frequent updates!!

+1

[netware5]

Successfully upgraded from 11.1.0.4 rev.5673 Embedded to 11.2.0.4 rev.5774 using LiveCD and fresh install, then imported saved configuration. Zpool also upgraded.

Thanks to the developers!

[apollo567]

Upgrade worked for me also.

[netware5]

I've just discovered that IPMI status is not available anymore. In Diagnostics > Information > IPMI Stats there is a message "No IPMI sensor data available".

In System > Advanced > loader.conf the ipmi_load variable is set to YES.

May be a bug in 5774?

[doktornotor]

I've just discovered that IPMI status is not available anymore. In Diagnostics > Information > IPMI Stats there is a message "No IPMI sensor data available".

In System > Advanced > loader.conf the ipmi_load variable is set to YES.

May be a bug in 5774?

Works just fine here.

[netware5]

I've just discovered that IPMI status is not available anymore. In Diagnostics > Information > IPMI Stats there is a message "No IPMI sensor data available".

In System > Advanced > loader.conf the ipmi_load variable is set to YES.

May be a bug in 5774?

Works just fine here.

Seems to be that something was broken when the config has been imported after upgrade from 11.1 to 11.2. The issue fixed by setting the ipmi_load variable to NO, then apply, then set it again to YES, then apply and reboot.

[kfnas]

since few release ago, I can see some increasing usage of logs, which are by default in /var/log directory mounted /dev/md0 on / (ufs, local, noatime, acls) via mdconfig. Looks like compression is not on and after time the root / of the system become full.

df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/md0 120M 120M 222K 100% /

question:

what is the proper way on the embedded version to add in command scripts or rc.conf menu to enable the compression of the md0 and or resize it please?

It looks like it is not possible to resize it without unmount first:

mdconfig -r -u md0 -s 256M
mdconfig: ioctl(/dev/mdctl): Operation not supported

thank you

[wbond]

I updated from 11.1.0.4 - Atomics (revision 5403) and everything looks good, except UPS monitoring. Status->Monitoring->UPS shows empty graphs:

Screen Shot 08-19-18 at 08.22 AM.PNG

I'm seeing this following error in the system log:

root: ERROR: No DS called 'ovoltage' in '/mnt/pool01/cifs-share-dataset/rrd/ups.rrd' ERROR: No DS called 'ovoltage' in '/mnt/pool01/cifs-share-dataset/rrd/ups.rrd' ERROR: No DS called 'ovoltage' in '/mnt/pool01/cifs-share-dataset/rrd/ups.rrd' ERROR: No DS called 'ovoltage' in '/mnt/pool01/cifs-share-dataset/rrd/ups.rrd'

The UPS status looks normal (Online) on the main status screen and the Diagnostics->Information->UPS screen looks normal as well.

Is anyone else seeing this, or know of a fix?

thanks

[raulfg3]

Delete .rdd files And reboot to regenerarte as new files.

[crest]

I updated from 11.1.0.4 - Atomics (revision 5403) and everything looks good, except UPS monitoring. Status->Monitoring->UPS shows empty graphs:

Screen Shot 08-19-18 at 08.22 AM.PNG

I'm seeing this following error in the system log:

root: ERROR: No DS called 'ovoltage' in '/mnt/pool01/cifs-share-dataset/rrd/ups.rrd' ERROR: No DS called 'ovoltage' in '/mnt/pool01/cifs-share-dataset/rrd/ups.rrd' ERROR: No DS called 'ovoltage' in '/mnt/pool01/cifs-share-dataset/rrd/ups.rrd' ERROR: No DS called 'ovoltage' in '/mnt/pool01/cifs-share-dataset/rrd/ups.rrd'

The UPS status looks normal (Online) on the main status screen and the Diagnostics->Information->UPS screen looks normal as well.

Is anyone else seeing this, or know of a fix?

thanks

Hello wbond,
discovered the same problem and found it broken in r5682, see also here => viewtopic.php?f=46&t=1081&p=86232#p86232

Delete .rdd files And reboot to regenerarte as new files.

This is not working, it just solves the error output to the log but battery voltage data will not be updated.

Regards
crest

[doktornotor]

There's no need to reboot (in fact, completely useless as you've noticed). Just re-save the monitoring settings after deleting the screwed RRDs.

Screenshot_UPS_Monitoring.png

[crest]

There's no need to reboot (in fact, completely useless as you've noticed). Just re-save the monitoring settings after deleting the screwed RRDs.

Screenshot_UPS_Monitoring.png

No, it's not what it is supposed to be
Your screenshot shows the output AC voltage values rather than to show the battery DC voltage like below for a APC Back-UPS ES 550G:

rrd-ups_daily.png

But anyway please provide the raw output of your UPS - you can find it under Diagnostics > Information > UPS > NUT and tick 'Show RAW UPS Info', it would be interesting which parameters are provided by the CyberPower vendor for this UPS.