Configuring into Your System a Partitioned Disk Already Containing Data




	NOTE: This procedure is provided for configuring a Series 800 legacy hard-partitioned disk into HP-UX 10.0. Before proceeding, make sure you have read “Planning to Configure into your System a Disk Already Containing Data ” and have performed the examination documented in “Ensuring Against Clashes with HP-UX 10.0”.

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 HP-UX System Administration Tasks.
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:
1. 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
2. Edit the /stand/build/system file to add the absent driver(s).
3. Build the kernel by invoking the mk_kernel command. This creates /stand/build/vmunix_test, a kernel ready for testing.
  /usr/sbin/mk_kernel -s system
4. Save the old system file and kernel by moving them. Thus, if anything goes wrong, you still have a bootable kernel.
  mv /stand/system /stand/system.prev mv /stand/vmunix /stand/vmunix.prev
5. Move the new system file and new kernel into place, ready to be used when you reboot the system.
  mv /stand/build/system /stand/system mv /stand/build/vmunix_test /stand/vmunix
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.
For example,
/sbin/mksf -C disk [ -H hardware_path -I instance ] -s section_number /sbin/mksf -C disk [ -H hardware_path -I instance ] -r -s section_number
Execute /usr/sbin/ioscan -fun -H hardware_path to verify that the device special files were created successfully.

Configuring into Your System a Partitioned Disk Already Containing Data

Technical documentation

» Table of Contents

» Index