Array Monitor Daemon error ??

[linuxfan]

Hi Richard,

Looks like the ARMServer was started at 15:51:51 and the mail you received was at 12:32:36.

Have you gotten any mail since then complaining the same?

Did anything change on the autoraid, firmware upgrade? I have sometimes seen arraymond complain that that disk array is not accessible but that's because the ARMServer is not running and the same is documented in the man page for ARMServer (under DEPENDENCIES section)

Also you might want to check the man page for logprint to check the ARMServer log files.

-Ramesh

[someone_4]

I just got two emails @ 3:56
Data on disk array on /dev/rdsk/c1t1d0
at lvadm03 is unavailable.

and

Data on disk array on /dev/rdsk/c0t0d0
at lvadm03 is unavailable.

That is 2 differnt drives.
Could it be the 2 that are blinking?

[linuxfan]

Hi Richard,

Are those disks configured on the system?
If so are the filesystems mounted?
If so are you having any problem accessing those filesystems?
Any errors in syslog? or dmesg?

This is a strange one, but did you try bouncing the array daemons
/sbin/init.d/hparray stop
/sbin/init.d/hparray start
(make sure arraymond and ARMServer startup)

when did you start receiving these emails?
Did you try running logprint?

-Ramesh

[Sanjay_6]

Hi Richard,

It would be good if you replace the two disk which are blinking yellow. Not a good sign. Even if you are able to recover noe, it won't be good for the future.

thanks

[someone_4]

Are those disks configured on the system?
If so are the filesystems mounted?
If so are you having any problem accessing those filesystems?
Any errors in syslog? or dmesg?

How can I find out if these disk are configured and if the filesystems are mounted?
Someone wont admit but syslogd has been turned off. I have a cron job set up now for dmesg so I will be looking though that info.

[Sanjay_6]

Hi,

You can find if those PV are configured into any vg by the "vgdisplay" command.
vgdisplay -v /dev/vg_name
It will list the PV's in use by that vg.
lvdisplay -v /dev/vg_name/lvname will display the PV's on which the lv has got extents.

hope this helps.

thanks

[linuxfan]

Hi Richard,

pvdisplay -v /dev/rdsk/c1t1d0 |more

(i have a feeling c0t0d0 is a PV link, alternate link to the same disk)
this would be the 1st LUN on the autoraid
Look which LVs are on the disk and see if they are mounted or you could use dd just to see if you read from the disk
dd if=/dev/rdsk/c1t1d0 of=/dev/null bs=512
(Ctrl-C to interrupt it)

the other thing you can do is if you started receiving this email only today,
arraydsp -i (gets the serial number)
logprint -s 09181200 -e 09181500 -t disk -e SERIAL |grep -v L000

This would print any errors that have been recorded in the ARMServer log files.

Also did you try hparray stop and start?

-Ramesh

[someone_4]

Im reading my HP Certified book here and the next chapter after Peripheral Devices is .... drum roll please .. HPUX file Systems and Logical Volime Manager !! So I am going to dig into this .. it should clear some things up with this issue. So after I get some knowledge and if I have more questions I will reference back to this post and if I still need help I will post up my questions.

Richard