NAME

mkrs − construct a recovery system

SYNOPSIS

/etc/mkrs [-v] [-q] [-s] [-f rcdev] [-r rootdev] [-m series]

DESCRIPTION

mkrs constructs a recovery system on removable media (or a hard disk drive).  If a system is unbootable due to a corrupt root disk, the system administrator boots the recovery system and uses it as a temporary root volume.  Once booted on the recovery system, the administrator uses the tools it provides to repair the corrupt root disk. 

Options

mkrs recognizes the following options:

-q If enough free disk space is available in /usr/tmp (typically 10-20Mb), the -q option can be used to make mkrs create an image of the recovery system in this directory before copying it to the recovery media.  This option generally saves a great deal of time due to reduced seeking on non-random-access recovery media (cartridge tape and DDS).  Note: for DDS tape recovery systems, the -q option is assumed. 

-s When creating a DDS recovery system for a small memory system (8Mb or less), the -s option should be used to specify that a smaller set of files be placed on the recovery system. 

-v (verbose) Prints a running history of the construction process.  Normally, mkrs does its work silently. 

-f rcdev Specify the name of the device file for the recovery system (that is, the cartridge tape drive, magneto-optical disk drive, or alternate hard disk drive on which the recovery system is created).  mkrs, by default, uses the following device file:

/dev/update.src
if it exists as a character device file, else

/dev/rct/c0 if it exists as a character device file, else

/dev/rct if it exists as a character device file,

else the device file must be specified. 

If none of the above defaults exist on the system, one of these device files must be created or the -f option must be used to specify the device file to be used (the recovery device file can be either a block or a character device file). 

-r rootdev Specify the name of the device file for the root device.  mkrs, by default, uses the following device file:

/dev/dsk/0s0 if it exists as a block device file, else

/dev/root if it exists as a block device file, else

/dev/hd if it exists as a block device file,

else the device file must be specified. 

If none of the above defaults exist on the system, one of these device files must be created or the -r option must be used to specify the device file to be used (the root device file must be a block device file). 

-m series Specify which type of machine is running this software (for example, -m 300).  Normally, mkrs properly identifies the machine type.  This option can be used if mkrs is unable to identify the machine type. 

DIAGNOSTICS

An error message results if:

• None of the default device files for the recovery device exist and the -f option is not used to specify a recovery device file. 

• None of the default device files for the root device exist and the -r option is not used to specify a root device file. 

• The machine type cannot be determined and the -m option is not used to specify the machine type. 

WARNINGS

Incorrectly specifying the recovery device may cause file system damage during recovery system construction. 

The recovery system provides super-user capabilities; the system administrator should have exclusive responsibility for its use. 

The recovery system uses the swap area of the system being repaired for its swap space. 

Recovery systems that are created on DDS tape devices will only work if the DDS tape device has a SCSI interface. 

mkrs expects that the recovery media specified has already been formatted with mediainit in the case of magneto-optical or hard disk drives. 

When executing from a recovery system, the mkboot command (if used) must be invoked with the -f option; otherwise it will not be able to replace the boot area on your disk. 

DEPENDENCIES

Series 300

Series 300 systems must have Revision D or newer boot ROM s to support DDS tape recovery systems. 

Series 700

The -s option is necessary for building Series 700 DDS tape recovery systems. 

AUTHOR

mkrs was developed by HP. 

SEE ALSO

HP-UX System Administrator manuals. 

config(1M), mkfs(1M). 

Hewlett-Packard Company  —  HP-UX Release 9.03: April 1994