<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Disk Crash in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-crash/m-p/2515278#M870801</link>
    <description>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:&lt;BR /&gt;&lt;BR /&gt;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.</description>
    <pubDate>Mon, 09 Apr 2001 18:39:16 GMT</pubDate>
    <dc:creator>Angela L. Shepherd_1</dc:creator>
    <dc:date>2001-04-09T18:39:16Z</dc:date>
    <item>
      <title>Disk Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-crash/m-p/2515278#M870801</link>
      <description>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:&lt;BR /&gt;&lt;BR /&gt;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.</description>
      <pubDate>Mon, 09 Apr 2001 18:39:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-crash/m-p/2515278#M870801</guid>
      <dc:creator>Angela L. Shepherd_1</dc:creator>
      <dc:date>2001-04-09T18:39:16Z</dc:date>
    </item>
    <item>
      <title>Re: Disk Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-crash/m-p/2515279#M870802</link>
      <description>Angela,&lt;BR /&gt;&lt;BR /&gt;I would say if you can do the following on the disk in question, it's ok:&lt;BR /&gt;&lt;BR /&gt;1) diskinfo -v /dev/rdsk/c?t?d?&lt;BR /&gt;2) pvdisplay -v /dev/dsk/c?t?d?&lt;BR /&gt;3) vgdisplay on the vg that the disk belongs to.&lt;BR /&gt;&lt;BR /&gt;If all of these come back without errors, you're probably ok - otherwise you may have a hardware problem.</description>
      <pubDate>Mon, 09 Apr 2001 18:53:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-crash/m-p/2515279#M870802</guid>
      <dc:creator>Charles McCary</dc:creator>
      <dc:date>2001-04-09T18:53:49Z</dc:date>
    </item>
    <item>
      <title>Re: Disk Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-crash/m-p/2515280#M870803</link>
      <description>Angela, their are old sys admins and bold sys admins, but there are no old, bold sys admins.&lt;BR /&gt;&lt;BR /&gt;With all due respect for my colleague &lt;BOW&gt; if you have an HP support contract then it is time to let HP earn their money.&lt;BR /&gt;&lt;BR /&gt;If not, then you have to decide if it is worth the money to call them out based on your perceptions.&lt;/BOW&gt;</description>
      <pubDate>Mon, 09 Apr 2001 23:18:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-crash/m-p/2515280#M870803</guid>
      <dc:creator>paul courry</dc:creator>
      <dc:date>2001-04-09T23:18:53Z</dc:date>
    </item>
    <item>
      <title>Re: Disk Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-crash/m-p/2515281#M870804</link>
      <description>Angela,&lt;BR /&gt;&lt;BR /&gt;here's some more info:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;When going into Disks and Filesystems they get the error:&lt;BR /&gt;&lt;BR /&gt;"The command used to retrieve disk array configuration data,&lt;BR /&gt;/usr/sam/lbin/get_array_info, has encountered an error.  The stderr&lt;BR /&gt;output from the command is shown below.  Until the problem mentioned&lt;BR /&gt;below is fixed, SAM cannot recognize the array's configuration.&lt;BR /&gt;&lt;BR /&gt;arrayinfo: initdev - internal error: Can't locate device mapping&lt;BR /&gt;file.  Run "arrayscan".&lt;BR /&gt;dsp: initdev - internal error: Can't locate device mapping file.  Run&lt;BR /&gt;"arrayscan".&lt;BR /&gt;arrayinfo: initdev - internal error: Can't locate device mapping&lt;BR /&gt;file.  Run "arrayscan".&lt;BR /&gt;dsp: initdev - internal error: Can't locate device mapping file.  Run&lt;BR /&gt;"arrayscan".&lt;BR /&gt;arrayinfo: initdev - internal error: Can't locate device mapping&lt;BR /&gt;file.  Run "arrayscan".&lt;BR /&gt;dsp: initdev - internal error: Can't locate device mapping file."&lt;BR /&gt;&lt;BR /&gt;Cause Text&lt;BR /&gt;&lt;BR /&gt;pd_devinfo.tx, was delivered with bogus entries for EMC that&lt;BR /&gt;were not there in PHCO_11361.  This was a mistake.  Because&lt;BR /&gt;of this the code believes that the EMC is a SCSI CASCADE&lt;BR /&gt;array and treats it as such (ie. calls get_array-info).&lt;BR /&gt;&lt;BR /&gt;Fix Text&lt;BR /&gt;&lt;BR /&gt;remove the EMC lines from pd/data/pd_devinfo.tx&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;You may provide feedback here &lt;BR /&gt;&lt;BR /&gt;    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.&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; Relevance to my question &lt;BR /&gt;           Provided the information I needed. &lt;BR /&gt;           Helped me and/or pointed me to the information. &lt;BR /&gt;           Did not pertain to my question/problem. &lt;BR /&gt; &lt;BR /&gt; Content Quality &lt;BR /&gt;           Is good, please provide more like it. &lt;BR /&gt;           Is hard to understand and/or needs more detail. &lt;BR /&gt;           Has incorrect technical information. &lt;BR /&gt;           Took the recommended action, but it did not solve my problem. &lt;BR /&gt; &lt;BR /&gt; Access to resources &lt;BR /&gt;           Cannot access the Web site listed. &lt;BR /&gt;           Cannot find the resource listed. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Comments:&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;  &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Apr 2001 18:41:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-crash/m-p/2515281#M870804</guid>
      <dc:creator>Charles McCary</dc:creator>
      <dc:date>2001-04-10T18:41:10Z</dc:date>
    </item>
    <item>
      <title>Re: Disk Crash</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-crash/m-p/2515282#M870805</link>
      <description>This Question can be closed.  Thanks for the help.</description>
      <pubDate>Fri, 13 Apr 2001 16:04:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-crash/m-p/2515282#M870805</guid>
      <dc:creator>Angela L. Shepherd_1</dc:creator>
      <dc:date>2001-04-13T16:04:04Z</dc:date>
    </item>
  </channel>
</rss>

