<?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: system not booting in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/system-not-booting/m-p/3743036#M256491</link>
    <description>To understand the problem better please do the following steps&lt;BR /&gt; Does the same issue persist with both the server? If so &lt;BR /&gt;1. Disconnect MSA 30 Box and see the problem exists&lt;BR /&gt;2. If issue doesnot persist, then switch of one server and try to boot other server with MSA30 attached.&lt;BR /&gt;3. If problem doesnot persist then the issue could be scsi id. Set the Controller ID in one of the server to a value other than the default value 7. Ideally you can set the controller ID  to 6.</description>
    <pubDate>Fri, 03 Mar 2006 01:55:23 GMT</pubDate>
    <dc:creator>James Watt_1</dc:creator>
    <dc:date>2006-03-03T01:55:23Z</dc:date>
    <item>
      <title>system not booting</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-not-booting/m-p/3743034#M256489</link>
      <description>Hi friends,&lt;BR /&gt;I have itanium rx2620 server with dual channel msa30 encloser second channel attached on unother rx2620 server .&lt;BR /&gt;&lt;BR /&gt;Now my problem is my one server is not booting and it stuck at the below error in even single user mod can any body guid me how to solve this porblem it is very urgent .&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;error is :- The diagnostic logging facility has started receiving excessive&lt;BR /&gt;   errors from the I/O subsystem.  I/O error entries will be lost&lt;BR /&gt;   until the cause of the excessive I/O logging is corrected.&lt;BR /&gt;   If the diaglogd daemon is not active, use the Daemon Startup command&lt;BR /&gt;   in stm to start it.&lt;BR /&gt;   If the diaglogd daemon is active, use the logtool utility in stm&lt;BR /&gt;   to determine which I/O subsystem is logging excessive errors.&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Mar 2006 15:44:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-not-booting/m-p/3743034#M256489</guid>
      <dc:creator>Shah Gaurang B.</dc:creator>
      <dc:date>2006-03-02T15:44:33Z</dc:date>
    </item>
    <item>
      <title>Re: system not booting</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-not-booting/m-p/3743035#M256490</link>
      <description>Howdy,&lt;BR /&gt;I am a little confused...&lt;BR /&gt;Which MSA30 is this - the dual-bus or the Multi-initiator? I have only seen this on the MI model when 2 servers share disks as a cheap way of having shared storage for serviceguard. &lt;BR /&gt;&lt;BR /&gt;If you have both servers plugged into the same scsi bus you must change one of the scsi controllers to scsi ID 6 rather than the default of 7 using the service scsi option of the BCH&amp;gt; prompt. &lt;BR /&gt;You cannot have two id 7's.&lt;BR /&gt;If you do this you must not have a disk in slot 6 of course. &lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;Ian&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Mar 2006 18:01:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-not-booting/m-p/3743035#M256490</guid>
      <dc:creator>Ian Vaughan</dc:creator>
      <dc:date>2006-03-02T18:01:14Z</dc:date>
    </item>
    <item>
      <title>Re: system not booting</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/system-not-booting/m-p/3743036#M256491</link>
      <description>To understand the problem better please do the following steps&lt;BR /&gt; Does the same issue persist with both the server? If so &lt;BR /&gt;1. Disconnect MSA 30 Box and see the problem exists&lt;BR /&gt;2. If issue doesnot persist, then switch of one server and try to boot other server with MSA30 attached.&lt;BR /&gt;3. If problem doesnot persist then the issue could be scsi id. Set the Controller ID in one of the server to a value other than the default value 7. Ideally you can set the controller ID  to 6.</description>
      <pubDate>Fri, 03 Mar 2006 01:55:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/system-not-booting/m-p/3743036#M256491</guid>
      <dc:creator>James Watt_1</dc:creator>
      <dc:date>2006-03-03T01:55:23Z</dc:date>
    </item>
  </channel>
</rss>

