XigmaNAS 11.2.0.4.5746 released (FreeBSD 11.2-RELEASE-P0)

[zoon01]

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

Removed SF
Please Read the readme_11.2 file


Changes after NAS4Free release 11.1.0.4.5673
===============================
- Changes to use our final name: XigmaNAS.
- Upgrade FreeBSD to 11.2-RELEASE-P0.
- Change syscons sc to vt virtual terminal console driver.
- Add UEFI support for Embedded and Full(UFS) platforms.
- Upgrade samba to 4.8.2.
- Upgrade php to 7.2.7.
- Upgrade iperf3 to 3.6.
- Upgrade msmtp to 1.6.8.
- Upgrade virtualbox-ose to 5.2.14.
- Fix export/import function phpvirtiualbox.

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.
- Hostname and netbios name might get reset to default xigmanas.

Regards,
Team XigmaNAS

[zoon01]

ZFS Upgrade note:

Upgrade your ZFS pools only if you are 100% sure you do not return to older 11.1 releases
This is as always a one direction -> upgrade!

[maulbongo]

Hi zoon,

After upgrade from nas4free to xigmanas, hostname and netbiosname changed to xigmanas.

[zoon01]

Hi zoon,

After upgrade from nas4free to xigmanas, hostname and netbiosname changed to xigmanas.

Great isn't it, glad that that works

[2bob]

Hi zoon,

After upgrade from nas4free to xigmanas, hostname and netbiosname changed to xigmanas.

Great isn't it, glad that that works

No so great if the user had already set a specific hostname/netbiosname

[zoon01]

Sorry, but you can easy set your specific hostname/netbiosname back!
We did not want to mix names so we choose to upgrade all those like in default config.

[JoseMR]

Upgraded zroot successfully, really nice step forward for a great and functional NAS appliance, keep up the good work.

Regards

[king8]

Server of ASRock-J3170 found failed and halt on booting screen, needs to revert nas4free-5673.

However another server of Gigabyte upgraded successfully.

[Snapshot]

Upgrading HP Gen8 in sig from to 5673 to 5746. Luckily I was watching on the iLO console and got a screen grab. Not fixed by a cold start. So what should I try next? A clean install of 5746 or revert to 5673, try a different USB key or something else?

[maulbongo]

Hi Snapshot,

This Problem is related to the Broadcom Netxtreme nic (bge).
For the moment the only thing you could do, is to install an Intel nic, or revert to 11.1.0.4

This is not a XigmaNAS problem, it's a FreeBSD problem.

Hi folks,
I updated three machines, all of them didn't boot up afterwards.
What I could see at start up was a panic right after nic was initialized.
Unfortunately it was too fast, so I just saw "panic".
The nics are the already well know (for bugs) Broadcom Netxtreme bcm5720.
None of the already existing workarounds helped.
So, I had to revert to 11.1.0.4.5606 and everythings fine.

[netware5]

I am with HP Microserver Gen8 too. So I should wait until FreeBSD team fixes the Broadcom NIC problem?

[Snapshot]

Thanks, maulbongo. Of course, that server is at the bottom of the stack so it's a pain to access. I might borrow the USB3-to-Gigabit adapter from my laptop and fiddle with the DHCP reservation on the router instead until the fix arrives. Fortunately, it's normally only used once a week for backups so it won't matter if things are a bit slower.

@netware5: YES! Wait until zoon01 tells us it's fixed.

[netware5]

Hi, maulbongo and Snapshot,

I confirm that kernel panic replicated on my Microserver Gen8. The NIC is standard embedded NIC for this box - 332i, which is based on Broadcom bcm5720. I hope @zoon01 will pass this information to the core FreeBSD team. The HPE MS Gen8 is a very nice server box and I hope to be able to continue to use it.

Hi folks,
I updated three machines, all of them didn't boot up afterwards.
What I could see at start up was a panic right after nic was initialized.
Unfortunately it was too fast, so I just saw "panic".
The nics are the already well know (for bugs) Broadcom Netxtreme bcm5720.
None of the already existing workarounds helped.
So, I had to revert to 11.1.0.4.5606 and everythings fine.

[gaspen]

Got the same problem with broadcom nic on a server. No problem when i booted a standard 11.2-RELEASE dvd. I switched that server over to only use the 10GbE adapter by disabling the onboard in bios.

[gaspen]

virtualbox have problems starting up after the upgrade. Getting the error VBoxManage: error: Failed to initialize COM! (hrc=NS_ERROR_FAILURE). Seems the problem is that it does not get the config correctly. I do not know the difference of the handling of the scripts from FreeBSD 11.1 and 11.2 yet.

[zoon01]

virtualbox have problems starting up after the upgrade. Getting the error VBoxManage: error: Failed to initialize COM! (hrc=NS_ERROR_FAILURE). Seems the problem is that it does not get the config correctly. I do not know the difference of the handling of the scripts from FreeBSD 11.1 and 11.2 yet.

Confirmed, this will be fixed asap for next release!
I need some time to sort out as my test builds are fine, however for release something seems changed
Sometimes nothing wants to go smooth.

[gaspen]

config.xml have the setting to set the home directory for user virtualboxusers to what you have entered in the settings for virtualbox home. This is not set for the user in the system though so when the virtualbox services start up, they do not know where home dir is and can not find the config. I manually set the home dir for the user and it did start but something was still not fully right.

[Victek]

Upgraded and working, thanks for the release.. wow.. nice logo also for xigmanas, it's a product now.. the "free" has gone?

Thanks!

[liming]

My server halt on booting screen, too
Board is Asrock N3700-ITX

[slaycock]

Upgrade of embedded fron previous NAS4Free has failed with 'can't determine rootfs'

The root filing system is on a 32gb SSD,

[netware5]

I've flashed the latest FW for embedded NIC of my HP Microserver Gen8, but the kernel panic still persists. Seems to be all owners of HP Microserver Gen8 have to wait kernel to be fixed before upgrading to 11.2.

Note: I've tried XigmaNAS 11.2.0.4.5746 LiveCD mounted by iLO as virtual media.

[raulfg3]

Plex menu lost, but still load plex and can work.

Probably plex use old name to show menu.

eg:

Code: Select all

product_check()
{
	# Check for working product.
	if [ "${PRODUCT}" == "NAS4FREE-x64" ]; then
		postinit_cmd
		gui_start

Probably need to be:

Code: Select all

product_check()
{
	# Check for working product.
	if [ "${PRODUCT}" == "XigmaNAS-x64" ]; then
		postinit_cmd
		gui_start

[netware5]

Got the same problem with broadcom nic on a server. No problem when i booted a standard 11.2-RELEASE dvd. I switched that server over to only use the 10GbE adapter by disabling the onboard in bios.

I confirm that my HP Microserver Gen8 with Broadcom NIC successfully booted a standard FreeBSD 11.2 CD in LiveCD mode. So seems to be that the problem is in XigmaNAS not in FreeBSD.

[doktornotor]

Got the same problem with broadcom nic on a server. No problem when i booted a standard 11.2-RELEASE dvd. I switched that server over to only use the 10GbE adapter by disabling the onboard in bios.

I confirm that my HP Microserver Gen8 with Broadcom NIC successfully booted a standard FreeBSD 11.2 CD in LiveCD mode. So seems to be that the problem is in XigmaNAS not in FreeBSD.

+1, you guys have some broken kernel patches in there, no such issue with vanilla FreeBSD.

[zoon01]

virtualbox have problems starting up after the upgrade. Getting the error VBoxManage: error: Failed to initialize COM! (hrc=NS_ERROR_FAILURE). Seems the problem is that it does not get the config correctly. I do not know the difference of the handling of the scripts from FreeBSD 11.1 and 11.2 yet.

Confirmed, this will be fixed asap for next release!
I need some time to sort out as my test builds are fine, however for release something seems changed
Sometimes nothing wants to go smooth.

Update
We found the cause, I made a misstake,
new release later today that will fix the config upgrades and makes vbox working again

you also can on 5746 remove duplicate user/and groups or
flash .5746 to newer 5748 and restore older saved config.

[zoon01]

Got the same problem with broadcom nic on a server. No problem when i booted a standard 11.2-RELEASE dvd. I switched that server over to only use the 10GbE adapter by disabling the onboard in bios.

I confirm that my HP Microserver Gen8 with Broadcom NIC successfully booted a standard FreeBSD 11.2 CD in LiveCD mode. So seems to be that the problem is in XigmaNAS not in FreeBSD.

+1, you guys have some broken kernel patches in there, no such issue with vanilla FreeBSD.

let's find out if the cause is bge patch for wol:)
i will make a separate build without patches to it, i will pm above users to give download link.

[JoseMR]

Plex menu lost, but still load plex and can work.

Probably plex use old name to show menu.

eg:

Code: Select all

product_check()
{
	# Check for working product.
	if [ "${PRODUCT}" == "NAS4FREE-x64" ]; then
		postinit_cmd
		gui_start

Probably need to be:

Code: Select all

product_check()
{
	# Check for working product.
	if [ "${PRODUCT}" == "XigmaNAS-x64" ]; then
		postinit_cmd
		gui_start

Hi raul, support for XigmaNAS has been addeded as for Plex Extension v4.2.080, upgrade and restart from CLI with following commands for the changes to get effect:

Code: Select all

To upgrade
	#plexinit -u
To initialize:
	#plexinit

If you still have problem with above commands, remove the "version" file from the extension directory and run "plexinit" to re-fetch extension only.

P.S thanks for the catch, I will add this to Plex Extension OP.

Regards

[provels]

Upgraded embedded fine for me. I have BGE NICs, too, but they are so old (2004), I could probably mount them with two sticks and a rock.

[raulfg3]

Hi raul, support for XigmaNAS has been addeded as for Plex Extension v4.2.080, upgrade and restart from CLI with following commands for the changes to get effect:

Code: Select all

To upgrade
	#plexinit -u
To initialize:
	#plexinit

If you still have problem with above commands, remove the "version" file from the extension directory and run "plexinit" to re-fetch extension only.

P.S thanks for the catch, I will add this to Plex Extension OP.

Regards

Confirmed, works like a charm.


Great work.

[zoon01]

Build without bge wol patches

I do have made test build for some users above as promised.
Also pm send out with your dl link!

If i forgotten someone to pm?
do contact me please