XigmaNAS 11.2.0.4.6154 released (FreeBSD 11.2-RELEASE-P4)

[ernie]

Hello
I am trying to install this new version and I have some questions:

1) data partition of the initial usb for embedded version:

I have data for rrdgraph on this partition. Ok for the save of this data.
But how to put the saved data on the new installation ? As rrdgraph is launched, do I need to disable rrdgraph and then put the saved data ?

2) installation
What is the difference between installation embedded OS/GPT and installation embedded OS/EFI ?
Both are tagged 'preffered'.
If we can have advantage and disadvantage for this 2 choices, it will be good.

Thanks

[JoseMR]

...
Two things while I'm here:
- rolling back was super easy, how would I have done it before beadm? Reinstall? Or is/was there another way to get at the RootOnZFS upgrade snapshots?
- is the last line of the log important?

Thanks,
Andy
...

Hi, thanks for the kind words, to answer your question, to rollback a RootOnZFS install before beadm it was inconvenient for average users, you usually use snapshots if any and manually restore desired locations/files, however to roll back entire system this requires for the user to boot from a live media and import the zroot to an alternate root e.g. "/mnt/zroot" to avoid breaking current environment, rollback to the desired dataset/snapshot and then edit by hand loader.conf if needed, then export and reboot.

As for the log last line, nothing related to RootOnZFS, but maybe to VirtualBox, however since I don't use it I can't confirm for.

Regards

[JoseMR]

RootOnZFS -11.2.0.4.5774 need reinstall or Upgrade from WEBUI?

Hello, sorry for the late reply as I was absent due to my Wi-Fi Hotspot ISP gone down for maintenance/repairs unfortunately.

As far as I can tell RootOnZFS Platform does not need to be reinstalled ever unless denoted, simply Upgraded from the WebGUI, however on major releases, if a safe upgrade path is confirmed, the user can safely Upgrade as well.

Note that I'm not aware for any "rc.firmware or system_firmware.php" file changes that may affect the RootOnZFS Platform WebGUI Upgrade process, though we are always always testing from time to time to make sure nothing affect this Upgrade process further.

Regards

[ernie]

Hello
I am trying to install this new version and I have some questions:

1) data partition of the initial usb for embedded version:

I have data for rrdgraph on this partition. Ok for the save of this data.
But how to put the saved data on the new installation ? As rrdgraph is launched, do I need to disable rrdgraph and then put the saved data ?

2) installation
What is the difference between installation embedded OS/GPT and installation embedded OS/EFI ?
Both are tagged 'preffered'.
If we can have advantage and disadvantage for this 2 choices, it will be good.

Thanks

up
any advice is welcome.
BR

[JoseMR]

Hello
I am trying to install this new version and I have some questions:

1) data partition of the initial usb for embedded version:

I have data for rrdgraph on this partition. Ok for the save of this data.
But how to put the saved data on the new installation ? As rrdgraph is launched, do I need to disable rrdgraph and then put the saved data ?

2) installation
What is the difference between installation embedded OS/GPT and installation embedded OS/EFI ?
Both are tagged 'preffered'.
If we can have advantage and disadvantage for this 2 choices, it will be good.

Thanks

Hi ernie, sorry for overlooking your question.

The #1 requires for user manual backup and restore if data partition is in use on Embedded platforms, hence is advice to never store important data on that partition, alternatively, a postinit/shutdown script to automatically backup/restore this data to a permanent location could be handy, Rsync can be useful here.

As for the #2, the "OS/EFI" is for the latest hardware supporting the UEFI(Unified Extensible Firmware Interface) that replaces the legacy BIOS, pretty sure "OS/GPT" is what you want here.

Regards

[ernie]

Hello
I am trying to install this new version and I have some questions:

1) data partition of the initial usb for embedded version:

I have data for rrdgraph on this partition. Ok for the save of this data.
But how to put the saved data on the new installation ? As rrdgraph is launched, do I need to disable rrdgraph and then put the saved data ?

2) installation
What is the difference between installation embedded OS/GPT and installation embedded OS/EFI ?
Both are tagged 'preffered'.
If we can have advantage and disadvantage for this 2 choices, it will be good.

Thanks

Hi ernie, sorry for overlooking your question.

The #1 requires for user manual backup and restore if data partition is in use on Embedded platforms, hence is advice to never store important data on that partition, alternatively, a postinit/shutdown script to automatically backup/restore this data to a permanent location could be handy, Rsync can be useful here.

As for the #2, the "OS/EFI" is for the latest hardware supporting the UEFI(Unified Extensible Firmware Interface) that replaces the legacy BIOS, pretty sure "OS/GPT" is what you want here.

Regards

Thanks Jose
Concerning #2, my plateform supports both. Is there any advantage of EFI versus GPT ?
I understood that UEFI is based on GPT and not MBR (partition structure). So I have doubt for the choice , as for me both choice are with GPT.
BR

[JoseMR]

Thanks Jose
Concerning #2, my plateform supports both. Is there any advantage of EFI versus GPT ?
I understood that UEFI is based on GPT and not MBR (partition structure). So I have doubt for the choice , as for me both choice are with GPT.
BR

Hi ernie, besides the boot process and few advantages booting of UEFI, no real benefits under a headless server, the OS/EFI integration in XigmaNAS was mainly added because some of the newest hardware boot only on UEFI preventing some users from using XigmaNAS, as well as for future proof.

Regards

[ernie]

Thanks Jose
Concerning #2, my plateform supports both. Is there any advantage of EFI versus GPT ?
I understood that UEFI is based on GPT and not MBR (partition structure). So I have doubt for the choice , as for me both choice are with GPT.
BR

Hi ernie, besides the boot process and few advantages booting of UEFI, no real benefits under a headless server, the OS/EFI integration in XigmaNAS was mainly added because some of the newest hardware boot only on UEFI preventing some users from using XigmaNAS, as well as for future proof.

Regards

It is clear. Thanks

[ernie]

Hello
I tried the installation and I have an issue.
The destination disk is a ssd where the third partition is for the swap.
And when I boot on a new usb key with live USB of Xigmanas for installation, the installation stops as there is issue with the disk.

I tried to use shell with gpart in order to delete all partition, but the partition 3 is always busy.... It is the swap partition and I didn't understand why it is busy as I am on a liveUSB.

I look the liveUSB Xigmanas via webgui and I see in menu 'Advanced/swap' that the partition is used:
Device: /dev/ada4p3 | Total: 17.17GB | Used: 0B | Free: 17.17GB

How can I stop the use of this partition ?

I tried to look in mount point but it is empty.

Edit :
I tried to put another USB key and to choose the new usb key as Swap. It works but now I have 2 swaps !!!!
0% of 17.17GB
Device: /dev/ada4p3 | Total: 17.17GB | Used: 0B | Free: 17.17GB
0% of 8.05GB
Device: /dev/da8p1 | Total: 8.05GB | Used: 0B | Free: 8.05GB

A reboot don't solved the point : always the ada4p3 as swap.

B.R.

[ms49434]

please try

Code: Select all

swapoff /dev/ada4p3
swapoff /dev/da8p1

[ernie]

please try

Code: Select all

swapoff /dev/ada4p3
swapoff /dev/da8p1

Thanks ms49434, it works and the installation was fine.
But I didn’t understand why the live USB seen the swap partition and used it, as I didn’t import disk and Zfs.

BR

[MikeMac]

I suppose this should be updated in the product description "XigmaNAS supports (...), Software RAID (0,1,5)" here https://sourceforge.net/projects/xigmanas/ (probably other places too)

[wsmith]

could someone do an interim build that includes r6167 please. virtualbox is unusable and i cant downgrade xigmanas.

[CrashDavis]

Im also having trouble with virtualbox, vnc does not work properly. anyone else?

[zoon01]

VNC is broken on virtualbox 5.2.20, for that reason i have downgraded to 5.2.18, please upgrade XigmaNAS to new release 11.2.0.4.6171
and it will be working again.

at virtualbox.org there is an open ticket too: see https://www.virtualbox.org/ticket/18072

[nasser]

my NAS is waiting for about an hour with this message

"The firmware is now being installed. The server will reboot automatically."


"A firmware upgrade is in progress."


Version 6026

You did not read the Readme, you need a reinstall not a firmware upgrade, also no embedded file has been released yet!
So i have no clue about what you are doing.

oh!
on the VGA screen it says "x64-full"
so I need to download XigmaNAS-x64-full-11.2.0.4.6177.tgz and do a fresh install?


Thanks!

[doktornotor]

so I need to download XigmaNAS-x64-full-11.2.0.4.6177.tgz and do a fresh install?

No. That file is ONLY for GUI upgrades.

[nasser]

so, how to proceed?!

[doktornotor]

I would urge you to review the fine readme_11.2.txt as already suggested multiple times.

https://sourceforge.net/projects/xigman ... t/download

[nasser]

edit: ah, I should perform a fresh install with Live/USB.
For what is "full"?
embedded for web-gui-upgrade..


I run "sed -i '' -E 's/SIZE=\"320M\"/SIZE=\"384M\"/g' /etc/rc.firmware" on the shell, then:

With
XigmaNAS-x64-embedded-11.2.0.4.6177.img.xz ("Embedded.img.xz is only for upgrades by WEBGUI")
error: "The file you try to flash is not for this platform (x64-full)."

I guess I've a RootOnZFS install
zroot 5.92G 3.71G 88K /zroot
zroot/ROOT 5.91G 3.71G 88K /zroot/ROOT
zroot/ROOT/default-install 3.99M 3.71G 3.00G /
zroot/ROOT/upgrade-2018-09-06-145347 3.61M 3.71G 3.18G /
zroot/ROOT/upgrade-2018-10-18-204806 5.90G 3.71G 3.85G /

[JoseMR]

edit: ah, I should perform a fresh install with Live/USB.
For what is "full"?
embedded for web-gui-upgrade..


I run "sed -i '' -E 's/SIZE=\"320M\"/SIZE=\"384M\"/g' /etc/rc.firmware" on the shell, then:

With
XigmaNAS-x64-embedded-11.2.0.4.6177.img.xz ("Embedded.img.xz is only for upgrades by WEBGUI")
error: "The file you try to flash is not for this platform (x64-full)."

I guess I've a RootOnZFS install
zroot 5.92G 3.71G 88K /zroot
zroot/ROOT 5.91G 3.71G 88K /zroot/ROOT
zroot/ROOT/default-install 3.99M 3.71G 3.00G /
zroot/ROOT/upgrade-2018-09-06-145347 3.61M 3.71G 3.18G /
zroot/ROOT/upgrade-2018-10-18-204806 5.90G 3.71G 3.85G /

Hello, the command [ sed -i '' -E 's/SIZE=\"320M\"/SIZE=\"384M\"/g' /etc/rc.firmware ] for RootOnZFS is to let the users to increase on-the-fly the memory disk used by the firmware process, this is because the "file_name.tgz" used for upgrading RootOnZFS has grown since the MariaDB integration, this removes for the user to have to re-install RootOnZFS, however if the user have the possibility to save *config and re-install Root-OnZFS, it will be preferred, I will address this behavior and completely remove this limitation for RootOnZFS as RootOnZFS should never be re-installed unless denoted.

Edit: As for revision 6179 RootOnZFS platforms have no memory file system size limitation during upgrade process.

Also as as for:

XigmaNAS-x64-embedded-11.2.0.4.6177.img.xz ("Embedded.img.xz is only for upgrades by WEBGUI")
error: "The file you try to flash is not for this platform (x64-full)."

Embedded Platforms Uses: XigmaNAS-x64-embedded-11.2.0.4.XXXX.img.xz
RootOnZFS Platforms Uses: XigmaNAS-x64-full-11.2.0.4.XXXX.tgz

Note that only Full RootOnZFS Platforms can be upgraded by WebGUI witn .TGZ files, Legacy Full Platforms running on UFS can only be upgraded booting LiveMedia as expected.

Regards