Before you move a disk from one
system to another, you must create a clear record of
how the disk is set up on its original system. Make a record of
the following output:
bdf, for information on what file systems are mounted.
/etc/fstab, for information about the file systems mounted
on the disk at boot time. (If the disk is being moved from a 9.x system, the equivalent file will have been called /etc/checklist. If the disk being moved is partitioned, /etc/checklist will be your only source of
information for what partitions (sections) are being used.)
swapinfo, for information on device and file-system swap
space enabled on the disk.
If the disk is used for a database, make a record
of the database configuration file.
Back up the data on the disk; see the backup chapter
in Managing Systems and Workgroups.
Create a record of your system's current disk configuration
for later comparison:
/usr/sbin/ioscan -fun -C disk
Note whether the current configuration includes the
device driver(s) needed to communicate with the disk you intend
to configure. Consult the tables in “Selecting Device Drivers for a Disk Device and
Interface” for guidelines
on compatible disks, device drivers, and interfaces. If any necessary
device driver is absent from the kernel, you will need to rebuild
the kernel to include it. Here is how you rebuild the kernel:
Change
directory to the build environment (/stand/build). There, execute a system preparation script,
system_prep. system_prep writes a system file based on your current kernel
in the current directory. (That is, it creates /stand/build/system.) The -v provides verbose explanation as the script executes.
cd /stand/build/usr/lbin/sysadm/system_prep -v -s system
Modify the /stand/build/system file to add the absent driver(s) by invoking the kmsystem command. The -c Y specifies that driver-name is to be configured
into the system.
/usr/sbin/kmsystem -S /stand/build/system -c Y driver-name
NOTE: To avoid introducing format errors, do not edit the
HP-UX system description files directly. Instead, use the commands kmsystem and kmtune. These commands are new for Release 11.0; consult kmsystem(1M) and kmtune(1M) in
the HP-UX Reference.
Build the new kernel by invoking the mk_kernel command. This creates /stand/build/vmunix_test, a kernel ready for testing.
/usr/sbin/mk_kernel -s /stand/build/system
Save the old system file by moving it. Then move the
new system file into place.
Prepare for rebooting by invoking the kmupdate command. This sets a flag that tells the system
to use the new kernel when it restarts.
/usr/sbin/kmupdate
Bring the system down and physically install the disk
device.
Turn on the power to all peripheral devices. Wait for
them to become "ready", then turn on power
to the SPU.
On booting up, HP-UX detects the new disk and associates it
with its device driver. insf creates a single character device special file
and a single block device special file to communicate with the entire
disk.
Execute /usr/sbin/ioscan -fun
-C disk again, to verify that the disk device configured
successfully and to identify its whole-disk device special files
(/dev/[r]dsk/c#t#d#).
Use the mksf command to create device special files for each
individual section being used on the disk. (Refer to the printout
of /etc/checklist to identify the sections.)
Note, as of HP-UX 10.0, sections 2 and 0 have been switched: s0 now specifies whole disk; s2 specifies the portion of the disk that was previously
represented by s0. Also, since sections are only minimally supported
at 10.0, consult earlier documentation or version of /etc/disktab for disk sectioning geometry.