Steps for updating hpux with update ux
When the boot process has completed, ensure that the drive was detected by the kernel by reviewing the kernel messages in /var/adm/syslog/They should look somewhat similar to the following: Mar 19 bud vmunix: 2/0/1.0 tgt Mar 19 bud vmunix: 2/0/1.0.0 sdisk Mar 19 bud vmunix: 2/0/1.1 tgt Mar 19 bud vmunix: 2/0/1.1.0 sdisk Mar 19 bud vmunix: 2/0/1.6 tgt Mar 19 bud vmunix: 2/0/1.6.0 sdisk This system located three disk drives on controller 0 located at the controller device address 1 and at SCSI IDs 0, 1 and 6.Optionally, the commands to activate this disk can be given from the command line, which is demonstrated here.The physical disk drive should be added to either and an existing volume group or to a newly created volume group.Not a super big deal, since a new system file will be obtained to rebuild a kernel, but it leaves kmtune without a -S parameter a little bit in the dark.This is why I copy or move /stand/build/system to /stand/system as my last step in a kernel rebuild from the command line on 11.11. I realise that things can be so obvious for us (like same timestamps was to be understood within a reasonable time shift due to the edition, the build of new kernel and reboot...) that when it comes to explain, we generate even more confusion...The next step is to fiddle with some parameters with kmtune with -S /stand/build/system to use this particular system file.
To initialize the disk and check the disk for bad blocks the command, mediainit can be used. # newfs -F hfs /dev/rdsk/c0t5d0 mkfs (hfs): Warning - 121 sector(s) in the last cylinder are not allocated.Now 'sysdef' is deprecated, and kmtune is the correct tool to use with 11.11 and post 11.23 you should be using kcweb as in future sysdef should be removed... The tools to create kernels vary fast with HP-UX, but with 11.11, here are some comments...You cannot create a kernel and a system file simultaneously so the timestamps are destined to be different. A copy of the system file used to create the kernel has been stored inside the kernel itself.what about why sysdef does not return values for some params whil kmtune does?So sysdef and kmtune "should" return the same values correct?File systems are created in disk partitions or logical volumes.To view the size of the drive to be configured use the command, diskinfo.Additionally, the command /usr/sbin/ioscan may be run to show further information about the disk drives detected.If the disk device is not found, determine if the device driver needed for the disk and interface are available. As for hpux 11.11 nfile kernel parameter is static and should show same value using kmtune or sysdef, look in /stand if system and vmunix have same timestamp.This may not be true with release of OS where nfile can be set dynamicalyhpux 11.11, I checked on 4 different boxes and vmunix and system do not have the same timestamp on any of them. So sysdef and kmtune "should" return the same values correct?