Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

arraydsp failed to find an autoraid 12h

gene egournov_1
Occasional Contributor

arraydsp failed to find an autoraid 12h

Hello,

we have an AutoRaid 12 attached to K380 HPUX server.
No software changes were made to the server. A couple of weeks ago we changed SCSI cabling to the array - instead of core I/O adapter we are using 2 HP-PB controllers.
A few days ago a message appeared in /var/opt/resmon/log/event.log:

"Event data from monitor:

Identification
Array S/N: 0000000E010D, Path: /dev/rdsk/c4t1d0, Path: /dev/rdsk/c3t0d0

Message:
Array with S/N 0000000E010D no longer being monitored.

Action:
Insure that the array named should not be accessible.

Description:
This is generated whenever an array first becomes
inaccessible to the ARMServer."

The output of arraydsp -i
Arrays known to the ARMServer:
No arrays were found by the ARMServer

We've tried arraydsp -R, stopping and restarting ARMServer daemon, restarting diagnostics - no luck.
cstm is unable to get info on the array - "Information incomplete"

The array is still accessable as far as data is concerned.
Patch PHCO_23262 is installed. Array's firmware version=HP60.
HP Response Center has not been able to resolve this.
I've seen a couple of posting were folks experienced the same problem. If anyone knows of the resolution, please let me know.

thanks,
gene egournov
7 REPLIES
Mark Mitchell
Trusted Contributor

Re: arraydsp failed to find an autoraid 12h

I had this problem, there is a new patch for the ARMserver called phco_23262. It requires no reboot so just load it. Then stop and restart the ARMServer by killing the process and going to /opt/hparray/bin/ARMServer to restart or do a /sbin/init.d/hparray stop then
/sbin/init.d/hparray start. After that rebuild
with an arraydsp -R you will see it under the next arraydsp -i.
gene egournov_1
Occasional Contributor

Re: arraydsp failed to find an autoraid 12h

Mark,
I've done all of that - still no luck!

gene egournov
Mark Mitchell
Trusted Contributor

Re: arraydsp failed to find an autoraid 12h

I would suggest opening a hardware call with HP and get someone on sight to look at the scsi cards. Are there any compatability issues? I am sure that you have thought of this but I thought that I would add it anyway. What does an ioscan give you?
gene egournov_1
Occasional Contributor

Re: arraydsp failed to find an autoraid 12h

Mark,
as I mentioned HP is out of ideas for now.

gene egournov
Bob Inglis
Trusted Contributor

Re: arraydsp failed to find an autoraid 12h

I have seen casaes where the old revision of the ARMServer is still being run even after installing the new patch. Try removing all previous revisions on the ARMServer (superceeded patches). You could also remove any ARMServer.lock file that might be on left over.
Plan for the future and tomorrow will take care of itself.
gene egournov_1
Occasional Contributor

Re: arraydsp failed to find an autoraid 12h

Bob,

the only HP AutoRAID Manager patch currently present on the system is PHCO_23262 - I've removed all old patches. Also, just now, stopped ARMServer deamon, removed /var/opt/hparray/ARMServer.lock, started the daemon - still no luck.

thanks,
gene egournov
Mark van Silfhout
Trusted Contributor

Re: arraydsp failed to find an autoraid 12h

Gene,

in /etc/hpC2400 there is a file called arraydevs.lst, this file contains the paths(=devicefile) to lun 0 (and without lun0 it will not see the array), maybe the contents of this file points to the "old" paths of lun0.
Also check /etc/hpC2400/HPARRAY.INFO to see if there are any warnings and/or errors for device files. You may see a message such as cannot stat device file.
4. If there are warnings and/or errors with the device files, check the /etc/hpC2400/hparray.* files. Those files may be empty, (0 bytes) in size. These files map luns, devicefiles, etc.

Regards,

Mark