HP Surestore Disk Array 12h and FC60 - Manual (Page 223)

Solving Common Installation Problems 223
Inst
alla
tion
Solving Common Installation Problems
Problem. When performing an ioscan, the host sees the disk array controllers but none of
the disks or LUNs in the disk array.
Solution. This is typically caused by powering on the disk array controller enclosure
before powering on the disk enclosure(s). Turn off power to all disk array components,
power on the disk enclosures and wait for the disks to spin up, then power on the
controller enclosure.
Problem. When installing a factory-assembled disk array, Array Manager 60 does not see
the array. The amdsp -R command does not detect the array, although an ioscan displays
the disk array LUNs.
Solution. This can result if any of the disk array enclosures are not powered on, or they
have been disconnected or removed from the cabinet. Factory-assembled disk arrays have
an entire LUN structure created on them. If any of the disk enclosures are missing when
the disk array is powered on, the LUNs will appear but they will all have a size of zero
bytes. Make sure all disk enclosures are present and powered on before the controller
enclosure is powered on.
Problem. The ioscan results shows extra LUNs on the disk array. There are several LUN 0
entries for the disk array that I did not bind.
Solution. The volume set addressing used by the disk array creates virtual SCSI busses to
support addressing up to 32 LUNs. These LUNs do not really exist on the disk array, but are
displayed in the ioscan output.
For more information, see "Volume Set Addressing" on page 209 .
Problem. The Array Manager 60 commands are not working. When I attempt to execute a
command I get a message indicating that AM60Srvr is not running.
Solution. If the AM60Srvr daemon has stopped, no Array Manager 60 commands can
execute. AM60Srvr can be restarted using the following command:
/opt/hparray/bin/AM60Srvr