IBM Support

viosupgrade fails on VIOS with error: "Fileset installation failed: 'bos.alt_disk_install'."

Troubleshooting


Problem

Symptom

Scenario #1
Viosupgrade fails on VIOS when upgrading from 2.2.6.41 to 3.1.0.10 using noncustom, mksysb image created from the IBM "flash" ISO file:
$ viosupgrade -l -i /tmp/mksysb_image_vios31 -a hdisk1 -g /tmp/filelist
Welcome to viosupgrade tool.
Operation triggered for given node(s).
Broadcast message from root@vios2-dmzcal1 (vty0) at 23:12:52 ...
WARNING!!! VIOS Upgrade operation is in progress. Kindly Refrain from making any configuration changes...
Please wait for completion..
vios2-dmzcal1: Warning: Either /etc/resolv.conf or /etc/hosts file doesn't exist. For cluster to start after restore, please have these files in current rootvg
Initiating VIOS configuration backup..
VIOS configuration backup successful.
Fileset installation failed: 'bos.alt_disk_install'.

$ ioslevel
2.2.6.41
Scenario #2
Viosupgrade fails when using a custom mksysb
$ viosupgrade -l -i /mksysb_fs/qdriav03.image -a hdisk1 -g /mksysb_fs/filestocopy
Welcome to viosupgrade tool.
Operation triggered for given node(s).
Broadcast message from root@qdriav01 (pts/0) at 09:57:13 ...
WARNING!!! VIOS Upgrade operation is in progress. Kindly Refrain from making any configuration changes...
Please wait for completion..
Upgrading from ioslevel '2.2.6.65' to '3.1.3.10'.
qdriav01: Warning: Either /etc/resolv.conf or /etc/hosts file doesn't exist. For cluster to start after restore, please have these files in current rootvg
Verifying whether the MPIO software(s) is installed on the VIOS.
Verification of the MPIO software(s) is successful.
Initiating VIOS configuration backup..
VIOS configuration backup successful.
Fileset installation failed: 'bos.alt_disk_install'.
Use of uninitialized value in numeric eq (==) at /usr/ios/sbin/viosupg.pl line 2630.
Use of uninitialized value in numeric eq (==) at /usr/ios/sbin/viosupg.pl line 2630.
$ ioslevel
2.2.6.65

Cause

Scenario #1 Probable Cause
Failure can be due to a builddate verification failure, which happens when upgrading from an ioslevel that is newer than the one upgrading to, such as updating from 2.2.6.41 (released May 2019) to 3.1.0.10 (released Nov 2018).  Since 2.2.6.41 is newer than 3.1.0.10, the failure is deemed to be valid.
Scenario #2 Probable Cause
Mksysb image being used was not properly created.

Environment

VIOS 2.2.6.X and wanting to upgrade to V3.1

Diagnosing The Problem

Scenario #1
Determine if the release date of your original 2.2.6.X version is newer than the release date of the 3.1.X.X version you upgraded to in order to determine if the error is valid. 
Original 2.2.6.X Version Release Date
2.2.6.65 2020/07/17
2.2.6.61 2020/05/15
2.2.6.51 2019/12/13
2.2.6.41 2019/05/08
2.2.6.32 2018/11/16
2.2.6.31 2018/09/21
3.1.X.X Version Upgraded To Release Date
3.1.3.14 (ISO Flash) 2021/12
3.1.3.10 (ISO Flash) 2021/09
3.1.3.0 (ISO DVDs) 2021/09
3.1.2.21 (IOS Flash) 2020/04
3.1.2.20 (ISO DVDs) 2020/04
3.1.1.25 (ISO Flash) 2020/07
3.1.1.20 (ISO DVDs) 2020/05
3.1.1.10 (ISO Flash) 2019/11
3.1.1.0 (ISO DVDs) 2019/11
3.1.0.21 (ISO Flash) 2019/05
3.1.0.20 (ISO DVDs) 2019/05
3.1.0.10 (ISO Flash) 2018/11
3.1.0.0 (ISO DVDs) 2018/11
Scenario #2
Determine how the mksysb image was created.

Resolving The Problem

Scenario #1 Solution
Your current 2.2.6.X release date is newer than the release date of the 3.1.X.X version you upgraded to, in this example, from 2.2.6.41 to 3.1.0.10
Boot back from the original 2.2.6.X rootvg, and redo viosupgrade using a 3.1.X.X image with a newer release date, such as 3.1.0.20, in this example.
Alternatively, boot back from the original 2.2.6.X rootvg and uninstall the following two filesets.
In this example, at 2.2.6.41:
$ oem_setup_env
# installp -u bos.alt_disk_install.boot_images
# installp -ug bos.alt_disk_install.rte
Then retry viosupgrade using the same 3.1.X.X image. 
(The 2 filesets previously removed will be re-installed during the 3.1 upgrade.)
Scenario #2 Solution
Ensure the mksysb image being used is created according to IBM Documentation.
For details, refer to the viosupgrade checklist
> item #4 under VIOS Requirements

Document Location

Worldwide

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"Component":"","Platform":[{"code":"PF002","label":"AIX"}],"Version":"VIOS 2.2.6.3x or higher to be migrated to VIOS 3.1.0.x","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

Modified date:
18 March 2022

UID

ibm10967778

Page Feedback