<?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: vmunix: SPT in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964858#M416539</link>
    <description>its reported by SPT (SCSI Pass Through) driver when open() system call is&lt;BR /&gt;called with invalid device files that minor number is incorrect.&lt;BR /&gt;&lt;BR /&gt;from man scsi_pt, the minor number format for SPT driver is,&lt;BR /&gt;minor number = 0xIITL00&lt;BR /&gt;          II = card instance number&lt;BR /&gt;          T  = SCSI target ID&lt;BR /&gt;          L  = LU number on the SCSI device.&lt;BR /&gt;          00 = reserved.&lt;BR /&gt;&lt;BR /&gt;major number is 75 so the most likely cause is there are some invalid device files that have correct major number for SPT but incorrect minor number and Omniback or a similar command / backup utility tried to open that device file.&lt;BR /&gt;</description>
    <pubDate>Mon, 06 Mar 2006 11:11:38 GMT</pubDate>
    <dc:creator>Alex Glennie</dc:creator>
    <dc:date>2006-03-06T11:11:38Z</dc:date>
    <item>
      <title>vmunix: SPT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964856#M416537</link>
      <description>What does vmunix: SPT:  (spt_open) Bad device number: 0x4d000000 mean?  This just appeared in one of our servers /var/adm/syslog/syslof.log file for no apparent reason.  No changes have been made.</description>
      <pubDate>Mon, 06 Mar 2006 11:00:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964856#M416537</guid>
      <dc:creator>Danny Crisp</dc:creator>
      <dc:date>2006-03-06T11:00:19Z</dc:date>
    </item>
    <item>
      <title>Re: vmunix: SPT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964857#M416538</link>
      <description>SPT is the SCSI pass-through driver. SPT devices are most-commonly used with tape library robotic devices. You can verify this by doing an lsdev and noting that hex 4D = 77dec do look in /dev for devices with major number 77. An ioscan -fn posting would also be helpful.</description>
      <pubDate>Mon, 06 Mar 2006 11:09:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964857#M416538</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-03-06T11:09:35Z</dc:date>
    </item>
    <item>
      <title>Re: vmunix: SPT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964858#M416539</link>
      <description>its reported by SPT (SCSI Pass Through) driver when open() system call is&lt;BR /&gt;called with invalid device files that minor number is incorrect.&lt;BR /&gt;&lt;BR /&gt;from man scsi_pt, the minor number format for SPT driver is,&lt;BR /&gt;minor number = 0xIITL00&lt;BR /&gt;          II = card instance number&lt;BR /&gt;          T  = SCSI target ID&lt;BR /&gt;          L  = LU number on the SCSI device.&lt;BR /&gt;          00 = reserved.&lt;BR /&gt;&lt;BR /&gt;major number is 75 so the most likely cause is there are some invalid device files that have correct major number for SPT but incorrect minor number and Omniback or a similar command / backup utility tried to open that device file.&lt;BR /&gt;</description>
      <pubDate>Mon, 06 Mar 2006 11:11:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964858#M416539</guid>
      <dc:creator>Alex Glennie</dc:creator>
      <dc:date>2006-03-06T11:11:38Z</dc:date>
    </item>
    <item>
      <title>Re: vmunix: SPT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964859#M416540</link>
      <description>Please find attached ioscan -fun output.  Below is the relavent output from lsdev -C autoch and ioscan -funC autoch: -&lt;BR /&gt;&lt;BR /&gt;Character Block Driver Class&lt;BR /&gt;231       29    schgr  autoch&lt;BR /&gt;&lt;BR /&gt;ClasS  I  H/W Path      Driver S/W State &lt;BR /&gt;autoch 0  10/0/15/1.0.0 schgr  CLAIMED&lt;BR /&gt;                        /dev/rac/c3t0d0&lt;BR /&gt;&lt;BR /&gt;# ll /dev/rac/c3t0d0&lt;BR /&gt;&lt;BR /&gt;crw-------   1 bin        sys        231 0x030000 Feb 16  2005 /dev/rac/c3t0d0&lt;BR /&gt;</description>
      <pubDate>Mon, 06 Mar 2006 11:38:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964859#M416540</guid>
      <dc:creator>Danny Crisp</dc:creator>
      <dc:date>2006-03-06T11:38:28Z</dc:date>
    </item>
    <item>
      <title>Re: vmunix: SPT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964860#M416541</link>
      <description>I couldn't open your attachment. You should note that the process that triggered this error was not using the scghr or autoch devices; it was using scsi pass-thru. The are really looking for something like /dev/spt/c0t0d0.&lt;BR /&gt;&lt;BR /&gt;One way to find these device nodes is to note that 4d (hex) = 77 (dec) and do a find looking for this:&lt;BR /&gt;&lt;BR /&gt;find /dev -type c -exec ls -l {} \; | awk '{if ($5 == 77) print $0}'</description>
      <pubDate>Mon, 06 Mar 2006 11:54:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964860#M416541</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-03-06T11:54:58Z</dc:date>
    </item>
    <item>
      <title>Re: vmunix: SPT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964861#M416542</link>
      <description>One result returned from the example you supplied: -&lt;BR /&gt;&lt;BR /&gt;crw-------   1 root       root        77 0x000000 Sep 13  2004 /dev/ipmi</description>
      <pubDate>Mon, 06 Mar 2006 12:04:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964861#M416542</guid>
      <dc:creator>Danny Crisp</dc:creator>
      <dc:date>2006-03-06T12:04:37Z</dc:date>
    </item>
    <item>
      <title>Re: vmunix: SPT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964862#M416543</link>
      <description>Then that is the device node that the process that triggered your error was using. Do you have any scripts or applications that use that device node?</description>
      <pubDate>Mon, 06 Mar 2006 12:06:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964862#M416543</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-03-06T12:06:56Z</dc:date>
    </item>
    <item>
      <title>Re: vmunix: SPT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964863#M416544</link>
      <description>ipmi = intelligent platform management interface&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B2355-60105/ipmi.7.html" target="_blank"&gt;http://docs.hp.com/en/B2355-60105/ipmi.7.html&lt;/A&gt;</description>
      <pubDate>Mon, 06 Mar 2006 12:10:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964863#M416544</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-03-06T12:10:58Z</dc:date>
    </item>
    <item>
      <title>Re: vmunix: SPT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964864#M416545</link>
      <description>We are using Legato Networker.</description>
      <pubDate>Mon, 06 Mar 2006 12:14:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964864#M416545</guid>
      <dc:creator>Danny Crisp</dc:creator>
      <dc:date>2006-03-06T12:14:35Z</dc:date>
    </item>
    <item>
      <title>Re: vmunix: SPT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964865#M416546</link>
      <description>I have found a solution to this question</description>
      <pubDate>Thu, 27 Apr 2006 05:59:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964865#M416546</guid>
      <dc:creator>Danny Crisp</dc:creator>
      <dc:date>2006-04-27T05:59:45Z</dc:date>
    </item>
    <item>
      <title>Re: vmunix: SPT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964866#M416547</link>
      <description>I am experiencing this same error.  Can you let me know what your resolution was?  The ipmi controller is unclaimed/unknown, which indicates the driver is not present.  I reinstalled the driver, but error is still occurring.  Any assistance you can provide is greatly appreciated.</description>
      <pubDate>Thu, 27 Apr 2006 10:23:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vmunix-spt/m-p/4964866#M416547</guid>
      <dc:creator>EmLea</dc:creator>
      <dc:date>2006-04-27T10:23:31Z</dc:date>
    </item>
  </channel>
</rss>

