Configuring HP-UX For Peripherals

Chapter 5 161
Configuring Disk Drives, Disk Arrays, and CD-ROM Drives
Moving a Disk Drive to a Different Address
Step 7. If you are moving a disk drive containing the root file system (and you
want to continue to use it as root), you will need to make sure the AUTO
file on the root disk boot area does not specify a hard-coded hardware
path. To check this,
a. Locate the root disk by executing mount or bdf and looking for the /
entry.
b. View the current contents of the AUTO file by executing the lifcp
command and using - to display the output. For example,
bdf
Filesystem kbytes used avail %used Mounted on
/dev/dsk/c1t6d0 1813487 467756 1164382 29% /
hera:/users 3916236 2978782 545830 85% /hera/home
...
/usr/bin/lifcp /dev/dsk/c1t6d0:AUTO -
hpux (;0)/stand/vmunix
The output from lifcp should appear just as in this example. If
instead, you see output that shows an explicit hardware path (for
example, hpux
(56.6.0;0)/stand/vmunix), you will need to update the AUTO file. To
do so, execute the mkboot command with the -a option and verify
your results:
/usr/sbin/mkboot -a "hpux (;0)/stand/vmunix"
/dev/dsk/c1t6d0
/usr/bin/lifcp /dev/dsk/c1t6d0:AUTO -
hpux (;0)/stand/vmunix
• Once the hardware path is removed, the system will boot using the
path selected from processor-dependent code.
• The ;0 specifies that you are dealing with the entire disk.
• /dev/dsk/c1t6d0 is the device special file for the current location
of the root disk.
CAUTION The mkboot command overwrites the contents of the autoboot string.
Step 8. If your /stand/system file includes (optionally) an explicit reference to
the location of swap and/or dump, and these are located on the disk being
moved, your kernel will have to be rebuilt for the operating system to
find the new locations.