Disk Crash

[Angela L. Shepherd_1]

I had 2 yellow lights on one of my disk units. I rebooted the machine and the lights went away. I ran an arrayscan and tried to display the disk using the ./dsp -l /dev/rdsk/c0t0d0 command under /usr/hpC2400/bin but I keep receiving the following error message:

dsp: initdev - internal error: Can't locate device mapping file. Run "arrayscan". What am I doing wrong or is it an easier way to make sure my disk are OK.

[Charles McCary · Accepted solution]

Angela,

I would say if you can do the following on the disk in question, it's ok:

1) diskinfo -v /dev/rdsk/c?t?d?
2) pvdisplay -v /dev/dsk/c?t?d?
3) vgdisplay on the vg that the disk belongs to.

If all of these come back without errors, you're probably ok - otherwise you may have a hardware problem.

[paul courry]

Angela, their are old sys admins and bold sys admins, but there are no old, bold sys admins.

With all due respect for my colleague if you have an HP support contract then it is time to let HP earn their money.

If not, then you have to decide if it is worth the money to call them out based on your perceptions.

[Charles McCary]

Angela,

here's some more info:



When going into Disks and Filesystems they get the error:

"The command used to retrieve disk array configuration data,
/usr/sam/lbin/get_array_info, has encountered an error. The stderr
output from the command is shown below. Until the problem mentioned
below is fixed, SAM cannot recognize the array's configuration.

arrayinfo: initdev - internal error: Can't locate device mapping
file. Run "arrayscan".
dsp: initdev - internal error: Can't locate device mapping file. Run
"arrayscan".
arrayinfo: initdev - internal error: Can't locate device mapping
file. Run "arrayscan".
dsp: initdev - internal error: Can't locate device mapping file. Run
"arrayscan".
arrayinfo: initdev - internal error: Can't locate device mapping
file. Run "arrayscan".
dsp: initdev - internal error: Can't locate device mapping file."

Cause Text

pd_devinfo.tx, was delivered with bogus entries for EMC that
were not there in PHCO_11361. This was a mistake. Because
of this the code believes that the EMC is a SCSI CASCADE
array and treats it as such (ie. calls get_array-info).

Fix Text

remove the EMC lines from pd/data/pd_devinfo.tx






--------------------------------------------------------------------------------
You may provide feedback here

To help us improve our content, please provide feedback and any additional comments below. If you have a problem or a question that needs immediate attention, please submit a call or contact your HP Response Center instead.


Relevance to my question
Provided the information I needed.
Helped me and/or pointed me to the information.
Did not pertain to my question/problem.

Content Quality
Is good, please provide more like it.
Is hard to understand and/or needs more detail.
Has incorrect technical information.
Took the recommended action, but it did not solve my problem.

Access to resources
Cannot access the Web site listed.
Cannot find the resource listed.



Comments:
As much as possible, please identify the sections of the document to which your comments relate. When you have finished, press the Submit button to mail your evaluation and comments.

[Angela L. Shepherd_1]

This Question can be closed. Thanks for the help.