This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Request an enhancement to alt_disk_mksysb (or alternatively alt_rootvg_op -St) that would force an attempt at rebuilding the alternate disk's boot image.
In the referenced PMR, the use case was to take a troubled rootvg image from a Production LPAR and load it onto a Test LPAR. The primary disk and alternate disk were at the same AIX version+TL+SP+efix level. Where this gets interesting is that the efix list contained specific changes to the kernel & libc. The libc efix was not compatible with the "vanilla" kernel deployed in the fixed boot image, so the resulting alternate disk could not complete IPL after /usr was mounted.
Currently the alt_disk_mksysb process is written to deploy a fixed "vanilla" boot image. The process does NOT bosboot (i.e. does not construct a customized bootable image) on the alternate disk. This is significant. See /usr/sbin/alt_disk_mksysb function create_mksysb_boot_image, which deploys the fixed image in /usr/lpp/bos.alt_disk_install/bin/alt_init_br_chrp. It is now understood that this was done deliberately to facilitate certain porting situations, though this is unexpected from the customers' point of view.
The proposed enhancement would give the customer an option or procedure to create a viable boot image for the alternate disk on a best efforts basis.
An alternative approach might be to include an updated fixed boot image in the efix set anytime a kernel efix is issued. However, this approach makes the limiting assumption that the primary disk always has the "highest" level of software.
Idea priority | Low |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Creating a new RFE based on Community RFE #92257 in product IBM AIX.