*New 12.1 series Release:
2020-04-17: XigmaNAS 12.1.0.4.7542 - released

*New 11.3 series Release:
2020-04-16: XigmaNAS 11.3.0.4.7538 - released!


We really need "Your" help on XigmaNAS https://translations.launchpad.net/xigmanas translations. Please help today!

Producing and hosting XigmaNAS costs money. Please consider donating for our project so that we can continue to offer you the best.
We need your support! eg: PAYPAL

RootOnZFS Changes and Workarounds

General information about XigmaNAS
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
User avatar
JoseMR
Hardware & Software Guru
Hardware & Software Guru
Posts: 1119
Joined: 16 Apr 2014 04:15
Location: PR
Contact:
Status: Offline

RootOnZFS Changes and Workarounds

#1

Post by JoseMR »

Hello, as part of the RootOnZFS improvements continuation, some changes has been made to the Platform in hope to add additional features bug fixes etc., on top of that we have to adapt in the event when changes are made to FreeBSD base such newer boot loader etc.

As we already know, some base changes do requires for a reinstall(recommended) then import back config to avoid warning messages, errors or simply for the sake of ease, but we also understand that some advanced Full Platform users have lots of changes/packages and making manual backup/restore of such changes may take awhile or simply the user is not familiar with said tasks.

So In order to overcome the aforementioned inconvenience, I will provide here quick steps with details(mostly copy/paste on SSH)
to prevent the user from doing a full reinstall whenever possible, but instead executing a simple command to patch required files if needed.

As many already know, RootOnZFS Platform upgrades highly dependent on the "rc.firmware" file which is in charge of the Boot Environment creation and files extraction, but sometimes it may happens that new added changes may cause firmware upgrade to stale unexpectedly.

Tip: It is worth mentioning that you can always turn on Firmware Upgrade console debug for realtime progress view, since late releases seems to ship with this option turned off by default, just go to "System > Advanced > syslog.conf" and enable the "console debug" item.

===============================
Q: XigmaNAS RootOnZFS Firmware upgrade keeps hanging, what should I do?
A: This is mostly caused by an older "rc.firmware" or "system_firmware.php" files lacking latest code to deal with new features and/or bug fixes, here below are the commands that need to be executed one-time on the shell before the process upgrade, just make sure the server has internet connection and to select the proper command(s) based on your XigmaNAS RootOnZFS version:

Workaround to fix for stale upgrades on XigmaNAS 12.x:

Code: Select all

fetch --no-verify-peer -o /etc/rc.firmware "https://sourceforge.net/p/xigmanas/code/HEAD/tree/trunk/etc/rc.firmware?format=raw"
fetch --no-verify-peer -o /usr/local/www/system_firmware.php "https://sourceforge.net/p/xigmanas/code/HEAD/tree/trunk/www/system_firmware.php?format=raw"
Workaround to fix for stale upgrades on XigmaNAS 11.3:

Code: Select all

fetch --no-verify-peer -o /etc/rc.firmware "https://sourceforge.net/p/xigmanas/code/HEAD/tree/branches/11.3.0.4/etc/rc.firmware?format=raw"
fetch --no-verify-peer -o /usr/local/www/system_firmware.php "https://sourceforge.net/p/xigmanas/code/HEAD/tree/branches/11.3.0.4/www/system_firmware.php?format=raw"
Workaround to fix for stale upgrades on XigmaNAS 11.2:

Code: Select all

fetch --no-verify-peer -o /etc/rc.firmware "https://sourceforge.net/p/xigmanas/code/HEAD/tree/branches/11.2.0.4/etc/rc.firmware?format=raw"
fetch --no-verify-peer -o /usr/local/www/system_firmware.php "https://sourceforge.net/p/xigmanas/code/HEAD/tree/branches/11.2.0.4/www/system_firmware.php?format=raw"
===============================


===============================
Additional Notes for RootOnZFS/MBR users
*This seems to be addressed on later releases but for reference.

FreeBSD ZFS/MBR seems to be a little buggy and some users are experiencing that the zpool "bootpool" which is required for the MBR to work correctly is not being imported after boot, causing unexpected issues and upgrade failures, however as a workaround adding a PostInit command under "System > Advanced > Command Scripts" to import "bootpool" if not detected may help prevent this issue, below is the command needed as PostInit:

Code: Select all

if ! zpool status | grep -qw bootpool; then zpool import -f bootpool; fi
Sample screenshot:
ZFS_MBR_PostInit_CMD.png
References about bootpool:
FreeBSD reference #1
FreeBSD reference #2
FreeBSD bug report
===============================


Last updated (04-05-2020)
Regards
You do not have the required permissions to view the files attached to this post.
System: FreeBSD 12 RootOnZFS Mirror, MB: Supermicro X8SI6-F, Xeon X3450, 16GB DDR3 ECC RDIMMs.
XigmaNAS RootOnZFS
Addons at GitHub
BastilleBSD
Boot Environments Intro
Resources Home Page

nasrocks
Starter
Starter
Posts: 43
Joined: 05 Nov 2014 03:39
Status: Offline

Re: RootOnZFS Changes Notice

#2

Post by nasrocks »

Spoon is Xigmanas going to go to onlyto RootOnZFS or is it going to remain as an option?

User avatar
JoseMR
Hardware & Software Guru
Hardware & Software Guru
Posts: 1119
Joined: 16 Apr 2014 04:15
Location: PR
Contact:
Status: Offline

Re: RootOnZFS Changes Notice

#3

Post by JoseMR »

nasrocks wrote:
05 Jun 2019 03:12
Spoon is Xigmanas going to go to onlyto RootOnZFS or is it going to remain as an option?
Hi nasrocks, the RootOnZFS platform will remain as an advanced install option targeted for advanced users and developers only, the traditional Embedded and Full UFS platforms will be left intact as always.

Regards
System: FreeBSD 12 RootOnZFS Mirror, MB: Supermicro X8SI6-F, Xeon X3450, 16GB DDR3 ECC RDIMMs.
XigmaNAS RootOnZFS
Addons at GitHub
BastilleBSD
Boot Environments Intro
Resources Home Page

User avatar
JoseMR
Hardware & Software Guru
Hardware & Software Guru
Posts: 1119
Joined: 16 Apr 2014 04:15
Location: PR
Contact:
Status: Offline

Re: RootOnZFS Changes Notice

#4

Post by JoseMR »

Root partition check has been disabled for RootOnZFS Platforms since this is not required as for revision 6720.

So "Boot partition is too small" error will be no longer a problem upon drive changes/shifting.
System: FreeBSD 12 RootOnZFS Mirror, MB: Supermicro X8SI6-F, Xeon X3450, 16GB DDR3 ECC RDIMMs.
XigmaNAS RootOnZFS
Addons at GitHub
BastilleBSD
Boot Environments Intro
Resources Home Page

wsmith
NewUser
NewUser
Posts: 6
Joined: 10 Aug 2018 19:21
Status: Offline

Re: RootOnZFS Changes and Fixes

#5

Post by wsmith »

the above fixed my issue with the upgrade hanging the gui and not completing. thx.

User avatar
JoseMR
Hardware & Software Guru
Hardware & Software Guru
Posts: 1119
Joined: 16 Apr 2014 04:15
Location: PR
Contact:
Status: Offline

Re: RootOnZFS Changes and Fixes

#6

Post by JoseMR »

wsmith wrote:
20 Jun 2019 14:03
the above fixed my issue with the upgrade hanging the gui and not completing. thx.

Hi wsmith, this hopefully has been already fixed with chflags backup/restore functions as of r.6741.

Just happen that newly added content into base may cause the tar command exiting with errors during files extraction, notoriously for some protected libs.

Sorry for any inconvenience.

Regards
System: FreeBSD 12 RootOnZFS Mirror, MB: Supermicro X8SI6-F, Xeon X3450, 16GB DDR3 ECC RDIMMs.
XigmaNAS RootOnZFS
Addons at GitHub
BastilleBSD
Boot Environments Intro
Resources Home Page

Post Reply

Return to “GENERAL INFORMATION”