<?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 Extended Sense Data from Device in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734641#M19183</link>
    <description>We have few Itanium RX2620 server with OpenVMS 8.2-1 always encounter Extended Sense Data from Device. How to solve it? Pls refer to the attachment for full error log details. Thanks.</description>
    <pubDate>Thu, 06 Jan 2011 10:38:05 GMT</pubDate>
    <dc:creator>CCH_3</dc:creator>
    <dc:date>2011-01-06T10:38:05Z</dc:date>
    <item>
      <title>Extended Sense Data from Device</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734641#M19183</link>
      <description>We have few Itanium RX2620 server with OpenVMS 8.2-1 always encounter Extended Sense Data from Device. How to solve it? Pls refer to the attachment for full error log details. Thanks.</description>
      <pubDate>Thu, 06 Jan 2011 10:38:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734641#M19183</guid>
      <dc:creator>CCH_3</dc:creator>
      <dc:date>2011-01-06T10:38:05Z</dc:date>
    </item>
    <item>
      <title>Re: Extended Sense Data from Device</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734642#M19184</link>
      <description>&lt;!--!*#--&gt;&amp;gt; [...] refer to the attachment [...]&lt;BR /&gt;&lt;BR /&gt;Does OpenVMS 8.2-1 create a Microsoft Word&lt;BR /&gt;document for its error messages, or was that&lt;BR /&gt;your idea?  If the data started out as plain&lt;BR /&gt;text, then why not leave them as plain text?&lt;BR /&gt;Everyone can read plain text.  Not everyone&lt;BR /&gt;can read a Microsoft Word document.</description>
      <pubDate>Thu, 06 Jan 2011 11:17:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734642#M19184</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2011-01-06T11:17:20Z</dc:date>
    </item>
    <item>
      <title>Re: Extended Sense Data from Device</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734643#M19185</link>
      <description>The most useful information is often the ASC/ASCQ: &lt;BR /&gt;&lt;BR /&gt;x47, x3 -&amp;gt; (SCSI) Bus CRC error.&lt;BR /&gt;&lt;BR /&gt;Cabling/seating would seem like the obvious place to start looking. &lt;BR /&gt;&lt;BR /&gt;HP also tend to provide fairly frequent updates to controller and drive firmware (amongst other things). I don't suggest you go out and update now; it might be worth reviewing your current revisions though.&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Jan 2011 11:23:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734643#M19185</guid>
      <dc:creator>Richard Brodie_1</dc:creator>
      <dc:date>2011-01-06T11:23:49Z</dc:date>
    </item>
    <item>
      <title>Re: Extended Sense Data from Device</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734644#M19186</link>
      <description>Event: VMS Device Error Event occurred at Sun 5 Dec 2010 18:12:07 GMT+10:00&lt;BR /&gt;COMMON EVENT HEADER (CEH) V2.0 Event_Leader xFFFF FFFE&lt;BR /&gt;Header_Length 284&lt;BR /&gt;Event_Length 704&lt;BR /&gt;Header_Rev_Major 2&lt;BR /&gt;Header_Rev_Minor 1&lt;BR /&gt;OS_Type 2 -- OpenVMS&lt;BR /&gt;Hardware_Arch 6 -- ItaniumÂ®-based computers&lt;BR /&gt;CEH_Vendor_ID 3,564 -- Hewlett-Packard Company&lt;BR /&gt;Hdwr_Sys_Type 64 -- IntelÂ® ItaniumÂ® architecture&lt;BR /&gt;Logging_CPU 0 -- CPU Logging this Event&lt;BR /&gt;CPUs_In_Active_Set 1 &lt;BR /&gt;Major_Class 1 &lt;BR /&gt;Minor_Class 1 &lt;BR /&gt;Entry_Type 1,001 -- VMS Device Error Event &lt;BR /&gt;DSR_Msg_Num 0 -- Unused&lt;BR /&gt;Chip_Type 31 -- ItaniumÂ® 2 processor&lt;BR /&gt;CEH_Device 54 &lt;BR /&gt;CEH_Device_ID_0 x0000 0000 &lt;BR /&gt;CEH_Device_ID_1 x0000 0000 &lt;BR /&gt;CEH_Device_ID_2 x0000 0000 &lt;BR /&gt;Unique_ID_Count 6,098 &lt;BR /&gt;Unique_ID_Prefix 1,510 &lt;BR /&gt;Exact_Length 409 &lt;BR /&gt;Num_Strings 6 &lt;BR /&gt;&lt;BR /&gt;TLV Section of CEH TLV_DSR_String  HP rx2620 (1.30GHz/3.0MB&lt;BR /&gt;TLV_DDR_String HP 73.4G ST373453LC&lt;BR /&gt;TLV_Sys_Serial_Num SGH46150V1&lt;BR /&gt;TLV_Time_as_Local Sun 5 Dec 2010 18:12:07 GMT+10:00&lt;BR /&gt;TLV_OS_Version V8.2-1 &lt;BR /&gt;TLV_Computer_Name SYSC&lt;BR /&gt;&lt;BR /&gt;Entry_Type 1,001&lt;BR /&gt;EMB_Block emb_ertcnt 16 Error Count&lt;BR /&gt;emb_ertmax 16 Max error count&lt;BR /&gt;emb_iosb 0 &lt;BR /&gt;emb_sts x1802 1810 &lt;BR /&gt;emb_class 1 Disk Class&lt;BR /&gt;emb_type 54 &lt;BR /&gt;emb_rqpid 65,642 &lt;BR /&gt;emb_boff 2,048 &lt;BR /&gt;emb_bcnt 63,488 &lt;BR /&gt;emb_media 7,195,652 &lt;BR /&gt;emb_unit 200 &lt;BR /&gt;emb_errcnt 8 &lt;BR /&gt;emb_opcnt 80,474 &lt;BR /&gt;emb_ownuic x0001 0004 &lt;BR /&gt;emb_char x1C4D 4008 &lt;BR /&gt;emb_Device_Number 0 &lt;BR /&gt;emb_func 8,203 &lt;BR /&gt;emb_name_len 8 &lt;BR /&gt;emb_name SYSC$DKB &lt;BR /&gt;emb_dtname_len 19 &lt;BR /&gt;emb_dtname HP 73.4G ST373453LC &lt;BR /&gt;Generic DK Driver Header Revision 2 HW_Revision HPC5&lt;BR /&gt;DK_Error_Type x05 Extended Sense Data from Device&lt;BR /&gt;DK2_SCSI_ID 2 &lt;BR /&gt;DK2_SCSI_LUN 0 &lt;BR /&gt;DK2_SCSI_SubLUN 0 &lt;BR /&gt;DK_Port_Status x0000 0001 Normal Successful Completion&lt;BR /&gt;DK2_SCSI_CMD_Len 10 &lt;BR /&gt;DK2_SCSI_CMD Dump starting at offset: x1a8&lt;BR /&gt; [x0] x6d00002a&lt;BR /&gt; [x4] x004cc&lt;BR /&gt; [x8] x000 &lt;BR /&gt;SCSI_Status 2 Check Condition&lt;BR /&gt;DK2_Additional_Data_Len 18 &lt;BR /&gt;DK_Sense_Data Sense_byte_0 xF0&lt;BR /&gt;   Error_Code[6:0] x70 Current Error&lt;BR /&gt;   Valid[7] x1 Valid&lt;BR /&gt;Segment_Num 0 &lt;BR /&gt;Sense_Key x0B &lt;BR /&gt;   Sense_Key[3:0] xB Abort Command&lt;BR /&gt;Info_bytes x006D CC04 Usually LBA&lt;BR /&gt;Additional_Sense_Len 10 Extended Sense Data Length&lt;BR /&gt;Cmd_spec_info x0000 0000 &lt;BR /&gt;ASCQ_ASC x0347 &lt;BR /&gt;   ASC[7:0] x47 &lt;BR /&gt;   ASCQ[15:8] x3 &lt;BR /&gt;FRU_code x08 &lt;BR /&gt;Sense_Key_Specfic_Byte0 x00 &lt;BR /&gt;   Bit_Pointer[2:0] x0 &lt;BR /&gt;   BPV[3] x0 BPV Invalid&lt;BR /&gt;   C/D[6] x0 Data parameters&lt;BR /&gt;   Sense_Key_Specific_Valid[7] x0 Invalid&lt;BR /&gt;Sense_Key_Specfic_Bytes 0 &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Jan 2011 11:25:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734644#M19186</guid>
      <dc:creator>CCH_3</dc:creator>
      <dc:date>2011-01-06T11:25:14Z</dc:date>
    </item>
    <item>
      <title>Re: Extended Sense Data from Device</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734645#M19187</link>
      <description>Generic extended sense data reception is normal.&lt;BR /&gt;&lt;BR /&gt;As for the x47/x00 code, that's a SCSI parity error.  &lt;BR /&gt;&lt;BR /&gt;Possibly entirely transient. &lt;BR /&gt;&lt;BR /&gt;A bus parity error can also indicate a hardware or cabling or termination error, loose connection, signal transient, power supply problem,  etc.    This particularly if these or related errors are repeating or particularly increasingly frequent, or are involving other devices on this SCSI bus.&lt;BR /&gt;&lt;BR /&gt;The obvious inferences in aggregate imply that this error might be reoccurring.&lt;BR /&gt;&lt;BR /&gt;Which leads to the generic answer for all hardware errors...&lt;BR /&gt;&lt;BR /&gt;Contact your hardware support provider for assistance.&lt;BR /&gt;&lt;BR /&gt;Confirm that you have consistent and full backups of this disk data, too.  (I wouldn't expect to need it here, but it's useful to have a good backup any time somebody goes near the hardware.)&lt;BR /&gt;&lt;BR /&gt;Also consider whether RAID-1 is appropriate; host-based volume shadowing (HBVS) or bus-based or storage controller-based RAID mirroring.&lt;BR /&gt;&lt;BR /&gt;And for completeness, your operating system software is quite stale.  This could well be a software bug; there have been a number of updates to the SCSI driver stack since your release.</description>
      <pubDate>Thu, 06 Jan 2011 15:08:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734645#M19187</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2011-01-06T15:08:42Z</dc:date>
    </item>
    <item>
      <title>Re: Extended Sense Data from Device</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734646#M19188</link>
      <description>Correction, mis-read on my part, that's 47/03 and not 47/00, and that 47/03 is...&lt;BR /&gt;&lt;BR /&gt;"INFORMATION UNIT iuCRC ERROR DETECTED"&lt;BR /&gt;&lt;BR /&gt;That's a CRC detected between the host and the widget.&lt;BR /&gt;&lt;BR /&gt;Same triggers as before, however.  Check the SCSI cable, bus length, improper termination, HBA problems, another device, etc., and call your preferred hardware service vendor.&lt;BR /&gt;&lt;BR /&gt;Reposting due to ITRC glitch.</description>
      <pubDate>Thu, 06 Jan 2011 17:13:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/extended-sense-data-from-device/m-p/4734646#M19188</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2011-01-06T17:13:24Z</dc:date>
    </item>
  </channel>
</rss>

