HPlogo HP-UX Reference Volume 2 of 5 > a

arrayscan(1M)

» 

Technical documentation

Complete book in PDF

 » Table of Contents

 » Index

NAME

arrayscan — search system for disk arrays

SYNOPSIS

arrayscan

DESCRIPTION

arrayscan searches the system I/O buses to locate the address(es) of attached HP disk array devices. The utility can also be used to determine which logical units are configured on a disk array.

arrayscan performs several functions, including:

  • Ensuring device special files exist.

    arrayscan verifies that block and character device special files exist for all LUNs configured. On Series 700 systems, device files are created for all possible LUNs.

  • Ensuring disk array software was downloaded.

    arrayscan verifies that the disk array software has been downloaded for each disk array it encounters. If arrayscan encounters a disk array that does not have disk array software loaded, it automatically downloads the array software.

  • Updating monitor, and pscan device lists.

    Two files, /etc/hpC2400/hparray.devs, and /etc/hpC2400/hparray.luns are updated by arrayscan. /etc/hpC2400/hparray.devs is used by the monitor daemon (/usr/lbin/hpC2400/arraymond) to determine which devices to monitor. /etc/hpC2400/hparray.luns is used by the parity scan utilities (pscan, scn, and rpr) to determine which LUNs to monitor.

RETURN VALUE

arrayscan returns the following values:

0

Successful completion

-1

Command failed (an error occurred).

DIAGNOSTICS AND ERRORS

Errors can originate from problems with:

  • arrayscan

  • SCSI (device level) communications

  • system calls

Error messages generated by arrayscan:

arrayscan: Cannot access lock file. Create an empty file <FILE>

Two semaphore files are used by arrayscan, /etc/hpC2400/pscan.lock, and /etc/hpC2400/monitor.lock. If these files do not exist when arrayscan begins, it assumes that the monitor daemon is executing. If the period of time required for the monitor daemon to execute expires, and the files still do not exist, it is assumed that they need to be created. You can create these files, if necessary, using the touch command (see touch(1));

arrayscan: Unable to open Array Parity Scan list <FILE>

arrayscan updates /etc/hpC2400/hparray.luns, and /etc/hpC2400/hparray.devs. arrayscan was unable to write to this file.

arrayscan: Error from process insf.

An error occurred while executing insf (see insf(1M)). insf is used by arrayscan on Series 800 systems to create device files for newly configured disk array devices.

arrayscan: Error from process ioscan.

An error occurred while executing ioscan. ioscan is used by arrayscan to scan for all devices. Disk array devices are filtered from the ioscan output.

arrayscan: No SCSI devices identified. Check SCSI connections.

No SCSI devices were identified. Check SCSI cables and power connections and retry the command.

arrayscan: Unable to create char device special file for path <FILE>

arrayscan will create character, and block device files for all disk array devices it encounters. arrayscan was unable to create the device file.

arrayscan: Insufficient dynamic memory

An attempt to allocate dynamic memory failed.

DEPENDENCIES

This utility is supported only on HP C2425D, HP C2430D, HP C3595A and HP C3596A disk array devices.

AUTHOR

arrayscan was developed by HP.

FILES

/etc/hpC2400/hparray.luns

/etc/hpC2400/hparray.devs

/etc/hpC2400/pscan.lock

/etc/hpC2400/monitor.lock

© Hewlett-Packard Development Company, L.P.