Fix for Mksysb Restore on DVD-RAM using SAN-BOOT method on p595 in AIX

Fix for Mksysb Restore on DVD-RAM using SAN-BOOT method on p595

Problem: Unable to restore mksysb image on DVD-RAM media for LPARs using SAN-BOOT method if

                Lpar corrupted. Unable to make Master OS image to duplicate LPARs.

Fix:

- Add to "/usr/lpp/bosinst/cdfs.optional.list"  
.                                                                    
/usr/lib/drivers/sddpcmke /usr/lib/drivers/sddpcmke devices.sddpcm.52.rte                                                
/usr/lib/drivers/sdduserke /usr/lib/drivers/sdduserke devices.sddpcm.52.rte                                                
/usr/lib/methods/sddpcmrtl /usr/lib/methods/sddpcmrtl devices.sddpcm.52.rte                                                
.                                                                    
- Create new mksysb DVD                                              
.                                                                    
- Boot and install from new mksysb DVD                                

Reviewed the debug boot info.  hdisk0 doesn't configure
during Phase I cfgmgr because cfgscsidisk is not present then.  But  
that's OK--this is CD boot and cfgscsidisk is available for Phase 3  
cfgmgr.  But cfgscsidisk _fails_ in Phase 3 because the SDD PCM RTL an
KE are not available then (though they _were_ available in Phase 1 due
to the proto file change we made):                                    
.                                                                    
cfgmgr is running in phase 1                                          
Ý...¨                                                                
Completed method for: fscsi0, Elapsed time = 0                        
Return code = 0                                                      
***** stdout *****                                                    
hdisk0                                                                
*** no stderr ****                                                    
Ý...¨                                                                
Method: /etc/methods/cfgscsidisk not in boot image configure in phase
Ý...¨                                                                
+ /SPOT/usr/bin/rm -r Ý...¨ /usr/lib/drivers/sddpcmke                
/usr/lib/drivers/sdduserke Ý...¨ /usr/lib/methods/sddpcmrtl          
Ý...¨                                                                
+ ln -s Ý...¨ /SPOT/usr/lib/methods/cfgscsidisk Ý...¨ /usr/lib/methods
Ý...¨                                                                
cfgmgr is running in phase 3                                          
Ý...¨                                                                
Completed method for: fscsi0, Elapsed time = 1                        
Return code = 0                                                      
***** stdout *****                                                    
Ý...¨ hdisk0 Ý...¨                                                    
*** no stderr ****                                                    
Ý...¨                                                                
Method error (/etc/methods/cfgscsidisk -2 -l hdisk0 ):                
        0514-069 Failure loading the platform specific libcfg module.
.                                                                    
.                                                                    
The fix for this would either to ensure that both cfgscsidisk and the
SDD PCM stuff is available during Phase 1 (probably not appropriate),
or to ensure that both are available during Phase 3.                  
.                                                                    
The links from /SPOT/usr/lib/XXXXX to /usr/lib/XXXXX are made by      
/sbin/rc.boot.  They link everything in the SPOT:                    
.                                                                    
                # /usr/lib/drivers, methods, and microcode are        
                # directories, NOT links, so we need to populate them
                ln -s /SPOT/usr/lib/drivers/* /usr/lib/drivers        
                ln -s /SPOT/usr/lib/methods/* /usr/lib/methods        
.                                                                    
So, to make the SDD stuff available for Phase 3, it would simply need
to be in the appropriate SPOT directory.  I believe the content of the
SPOT diretory on a CD is controlled by the files:                    
.                                                                    
# ls -1 /usr/lpp/bosinst/cdfs*                                        
/usr/lpp/bosinst/cdfs.optional.B.list                                
/usr/lpp/bosinst/cdfs.optional.list                                  
/usr/lpp/bosinst/cdfs.required.list                                  
.                                                                    
So, a test would be to:                                              
.                                                                    
- remove the "cd.proto.ext.fcp.disk.sddpcm.rte" file created earlier  
.                                                                    
- Add to "/usr/lpp/bosinst/cdfs.optional.list"  
.                                                                    
/usr/lib/drivers/sddpcmke /usr/lib/drivers/sddpcmke devices.sddpcm.52.rte                                                
/usr/lib/drivers/sdduserke /usr/lib/drivers/sdduserke devices.sddpcm.52.rte                                                
/usr/lib/methods/sddpcmrtl /usr/lib/methods/sddpcmrtl devices.sddpcm.52.rte                                                
.                                                                    
- Create new mksysb DVD                                              
.                                                                    
- Boot and install from new mksysb DVD                                

 
Here is the attached log for Debug boot from DVD-RAM.
 

Here are the instructions on how to capture a debug boot.

Capturing output from a vterm (HMC managed systems)

From an AIX client
1. Start the script command for logging, and ssh to the HMC
# script
# ssh -l hscroot HMC

2. Now you will need to open a vterm window. To do this, we will need to
first get the managed system name by running the following command:
# lssyscfg -r sys -F name

Then run the following command to create the vterm window:
# mkvterm -m <managed system> -p <partition name>

Everything shown on the screen should log to the script session on the client.

Starting the Debug Boot

a. The bootlist should be set to the device you want to capture debug from
(hdisk, cdrom, or tape). If the system is not currently set to boot from that device,
this can be changed using the bootlist command or by booting into SMS.

b. Power the system on, and boot the system to the open firmware prompt.
You can do this by hitting the '8' or 'f8' key during the 'window of opportunity'
(this is after the beep, when you see Keyboard Memeory Speaker etc) or
by accessing SMS, selecting multiboot, and taking the option for the 'ok prompt'.

c. At the open firmware prompt (0>) execute the following command for tape or disk boot debug-
0> boot -s trap

For cdrom boot debug enter-
0> boot cdrom:\ppc\chrp\bootfile.exe -s trap

d. The system should begin booting off the first device in the bootlist. This should be the device
you intend to do the boot debug from. If doing it from tape or cd, you will need to have the media in the
appropriate drive. The system should stop at the kdb> prompt.
     
Enter the following at the debugger prompt:
       mw enter_dbg <enter>
       42 <enter>
       .    <enter>
       g   <enter>

The system will begin booting and the debug output will be displayed on the screen. Once you hit the
problem, you can end your session, and send in the file with the logged output.


Once the debug is captured and you are ready to end the session, enter the following
sequence in the vterm:
# ~.

On the client, end the script command by running:
# exit