<?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 Re: SCSI Disk Errors in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/scsi-disk-errors/m-p/4980223#M419686</link>
    <description>The EMS HW Monitors are enabled by default; you should not need to run monconfig to turn this on.  Run 'monconfig' and select the Check option to see that the disks affected are listed.&lt;BR /&gt;&lt;BR /&gt;You do NOT configure the EMS HW monitors using SAM (SEP please note!  I think you've stated this before; it's not true.).&lt;BR /&gt;&lt;BR /&gt;The disk monitor, disk_em, does not monitor virtual disk arrays (XP, VA, etc.), so if that's what you have, that would explain why no EMS event was generated.&lt;BR /&gt;&lt;BR /&gt;If these are directly attached SCSI disks, then you need to check you have a current version of the OnlineDiags (running 'cstm' will show the version you have installed, including the patch level).  &lt;BR /&gt;&lt;BR /&gt;Note also that the monitors do not generate an EMS event for every single low-level failure; there are thresholds set so that the events are only generated when the number of failures indicates a likely real problem.  Hardware is resilient to a certain degree, and one or two recoverable errors are acceptable.&lt;BR /&gt;&lt;BR /&gt;I notice you've closed the thread; did you find the answer?&lt;BR /&gt;&lt;BR /&gt;Andrew</description>
    <pubDate>Thu, 25 May 2006 05:09:00 GMT</pubDate>
    <dc:creator>Andrew Merritt_2</dc:creator>
    <dc:date>2006-05-25T05:09:00Z</dc:date>
    <item>
      <title>SCSI Disk Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scsi-disk-errors/m-p/4980219#M419682</link>
      <description>We started receiving read errors on one of our SCSI disk drives a week ago that was not caught:&lt;BR /&gt;&lt;BR /&gt;May 14 15:39:08 ignite1 vmunix: msgcnt 1 vxfs: mesg 038: vx_dataioerr - /dev/vgi&lt;BR /&gt;gn1/ignitelv file system file data read error in block 7399426&lt;BR /&gt;&lt;BR /&gt;May 19 10:42:40 ignite1 vmunix: msgcnt 13 vxfs: mesg 008: vx_direrr: vx_readdir2&lt;BR /&gt;_1 - /var/opt/ignite file system dir inode 103811 block 6422535 dirent inode 0 e&lt;BR /&gt;rror 5&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;When we started doing our weekly Ignite make recoveries this past weekend they all failed due to not being able to write to the Volume.&lt;BR /&gt;&lt;BR /&gt;Is there a way in the Event Monitor to trap these errors so that we receive them in our Event Monitor EMail's ??</description>
      <pubDate>Mon, 22 May 2006 15:01:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scsi-disk-errors/m-p/4980219#M419682</guid>
      <dc:creator>MikeL_4</dc:creator>
      <dc:date>2006-05-22T15:01:57Z</dc:date>
    </item>
    <item>
      <title>Re: SCSI Disk Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scsi-disk-errors/m-p/4980220#M419683</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;You should be able to configure EMS with SAM to trap the issues and notify via email.&lt;BR /&gt;&lt;BR /&gt;You have a bad sector on your disk and probably have block relocation set to enabled.&lt;BR /&gt;&lt;BR /&gt;I'd get a good backup, id the disk with cstm,xstm or mstm and replace the disk.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 22 May 2006 16:17:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scsi-disk-errors/m-p/4980220#M419683</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-05-22T16:17:42Z</dc:date>
    </item>
    <item>
      <title>Re: SCSI Disk Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scsi-disk-errors/m-p/4980221#M419684</link>
      <description>Mike,&lt;BR /&gt;&lt;BR /&gt;Try /etc/opt/resmon/lbin/monconfig to configure receiving EMS alerts&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;rgds,&lt;BR /&gt;&lt;BR /&gt;Ajit</description>
      <pubDate>Mon, 22 May 2006 23:30:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scsi-disk-errors/m-p/4980221#M419684</guid>
      <dc:creator>Ajitkumar Rane</dc:creator>
      <dc:date>2006-05-22T23:30:12Z</dc:date>
    </item>
    <item>
      <title>Re: SCSI Disk Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scsi-disk-errors/m-p/4980222#M419685</link>
      <description>.</description>
      <pubDate>Tue, 23 May 2006 12:50:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scsi-disk-errors/m-p/4980222#M419685</guid>
      <dc:creator>MikeL_4</dc:creator>
      <dc:date>2006-05-23T12:50:23Z</dc:date>
    </item>
    <item>
      <title>Re: SCSI Disk Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scsi-disk-errors/m-p/4980223#M419686</link>
      <description>The EMS HW Monitors are enabled by default; you should not need to run monconfig to turn this on.  Run 'monconfig' and select the Check option to see that the disks affected are listed.&lt;BR /&gt;&lt;BR /&gt;You do NOT configure the EMS HW monitors using SAM (SEP please note!  I think you've stated this before; it's not true.).&lt;BR /&gt;&lt;BR /&gt;The disk monitor, disk_em, does not monitor virtual disk arrays (XP, VA, etc.), so if that's what you have, that would explain why no EMS event was generated.&lt;BR /&gt;&lt;BR /&gt;If these are directly attached SCSI disks, then you need to check you have a current version of the OnlineDiags (running 'cstm' will show the version you have installed, including the patch level).  &lt;BR /&gt;&lt;BR /&gt;Note also that the monitors do not generate an EMS event for every single low-level failure; there are thresholds set so that the events are only generated when the number of failures indicates a likely real problem.  Hardware is resilient to a certain degree, and one or two recoverable errors are acceptable.&lt;BR /&gt;&lt;BR /&gt;I notice you've closed the thread; did you find the answer?&lt;BR /&gt;&lt;BR /&gt;Andrew</description>
      <pubDate>Thu, 25 May 2006 05:09:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scsi-disk-errors/m-p/4980223#M419686</guid>
      <dc:creator>Andrew Merritt_2</dc:creator>
      <dc:date>2006-05-25T05:09:00Z</dc:date>
    </item>
  </channel>
</rss>

