Updating your technology know strange dating
This is of concern in environments with smaller disk sizes, and should be checked before running an update.# lsvg -l rootvg |grep hd5 hd5 boot 1 1 1 closed/syncd N/A # lsvg rootvg |grep SIZE VG STATE: active PP SIZE: 32 megabyte(s) The single partition (in bold (1)) is 32meg in size. Smaller partition sizes will require more partitions to be allocated.Recommended back out methods include : mksysb restore, sysback restore, altinst_rootvg clone, and multibos.More information on any of these back-out methods can be found at the publib documentation site by using this link to click through to the appropriate infocenter and search features found here : 2.Any other entries under “PV2”..etc, simply represent mirrored copies.Next, verify your boot image can be successfully recreated using the hdisk# from above and by using /dev/ipldevice.If your partitions are not contiguous, or are not covered on the first partitions of the disk please call the software support line for assistance with correcting this. Firmware Firmware should be kept up to date and be checked whenever a technology level update is considered.Again, you may only have 1 partition that is large enough to handle the boot image, or you may have multiple smaller partitions. In general firmware updates should be applied before software updates, but that is not a rule set in stone.
You can always use a download directory or nfs mount point, simply substitute the input device as necessary. You can either scroll down or exit out and view the /file for the log of the installation.In order to do this you will first have to install the fileset “install”.Following are two examples of how to update this fileset first, so a preview update_all can be executed.First, find out which disk contains your hd5 logical volume.# lslv -m hd5 hd5: N/A LP PP 0001 hdisk0 The listing under the “PV1” column indicates on which disk hd5 is located.If you do receive output and are unfamiliar with how to resolve it, please call the support center for assistance before running your upgrade. Space In order to see if you have enough space for your update you can run the update_all operation in preview mode.This will provide you with an estimated system resources listing of the necessary space.# bosboot -ad /dev/hdisk0 bosboot: Boot image is 35795 512 byte blocks.# bosboot -ad /dev/ipldevice bosboot: Boot image is 35795 512 byte blocks.This document describes the recommended preparation and process when considering updating your system to a new technology level or adding a service pack to an existing technology level. With the introduction of 5300-06 you will notice more information provided when running the ‘oslevel’ command.In all we will review some key words and terminology, run through recommended pre-checks, discuss the update_all process using both SMIT and command line, and finally post-checks & FAQ. # oslevel -s 6100- The addition of the last four digits simply represents the year (11) and week (40) of the release of your technology level/service pack (-06-06).