4.
Enter the
ibrix_fs
command to set the file system’s data retention and autocommit period
to the desired values. See the
HP StoreAll Storage CLI Reference Guide
for additional
information about the
ibrix_fs
command.
Troubleshooting upgrade issues
If the upgrade does not complete successfully, check the following items. For additional assistance,
contact HP Support.
Automatic upgrade
Check the following:
•
If the initial execution of
/usr/local/ibrix/setup/upgrade
fails, check
/usr/local/ibrix/setup/upgrade.log
for errors. It is imperative that all servers are
up and running the StoreAll software before you execute the upgrade script.
•
If the install of the new OS fails, power cycle the node. Try rebooting. If the install does not
begin after the reboot, power cycle the machine and select the
upgrade
line from the
grub
boot menu.
•
After the upgrade, check
/usr/local/ibrix/setup/logs/postupgrade.log
for errors
or warnings.
•
If configuration restore fails on any node, look at
/usr/local/ibrix/autocfg/logs/appliance.log
on that node to determine which
feature restore failed. Look at the specific feature log file under
/usr/local/ibrix/setup/
logs/
for more detailed information.
To retry the copy of configuration, use the following command:
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade -f -s
•
If the install of the new image succeeds, but the configuration restore fails and you need to
revert the server to the previous install, run the following command and then reboot the machine.
This step causes the server to boot from the old version (the alternate partition).
/usr/local/ibrix/setup/boot_info -r
•
If the public network interface is down and inaccessible for any node, power cycle that node.
NOTE:
Each node stores its
ibrixupgrade.log
file in
/tmp
.
Manual upgrade
Check the following:
•
If the restore script fails, check
/usr/local/ibrix/setup/logs/restore.log
for
details.
•
If configuration restore fails, look at
/usr/local/ibrix/autocfg/logs/appliance.log
to determine which feature restore failed. Look at the specific feature log file under
/usr/
local/ibrix/setup/logs/
for more detailed information.
To retry the copy of configuration, use the following command:
/usr/local/ibrix/autocfg/bin/ibrixapp upgrade -f -s
Offline upgrade fails because iLO firmware is out of date
If the iLO2 firmware is out of date on a node, the
auto_ibrixupgrade
script will fail. The
/usr/
local/ibrix/setup/logs/auto_ibrixupgrade.log
reports the failure and describes how
to update the firmware.
After updating the firmware, run the following command on the node to complete the StoreAll
software upgrade:
/root/ibrix/ibrix/ibrixupgrade -f
182
Cascading Upgrades