<?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 Odd drive assignment for HBA in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/odd-drive-assignment-for-hba/m-p/3885165#M64964</link>
    <description>Our SAN group performed some hardware upgrades over the weekend.  Now I                                                                                         have a Redhat AS4-64Bit system that is assigning SAN drives in a most                                                                                           unusual way.  Prior to this upgrade the Qlogic HBA card assigned the SAN                                                                                        drive to /dev/sda.  Now, the kernel reports that /dev/sda is unavailable                                               and assigns the SAN drive to /dev/sdb instead.  The drive /dev/sdb does                                                                                      work normally.  However, this server is a node for a cluster.  The other                                                                                        member is suffering the same problem.  I'd rather determine the cause                                                                                          and fix it rather than change all references in the configuration files                                                                                       to the new drive location.  Does anyone have any suggestions?</description>
    <pubDate>Mon, 23 Oct 2006 14:25:36 GMT</pubDate>
    <dc:creator>Neil Watson</dc:creator>
    <dc:date>2006-10-23T14:25:36Z</dc:date>
    <item>
      <title>Odd drive assignment for HBA</title>
      <link>https://community.hpe.com/t5/operating-system-linux/odd-drive-assignment-for-hba/m-p/3885165#M64964</link>
      <description>Our SAN group performed some hardware upgrades over the weekend.  Now I                                                                                         have a Redhat AS4-64Bit system that is assigning SAN drives in a most                                                                                           unusual way.  Prior to this upgrade the Qlogic HBA card assigned the SAN                                                                                        drive to /dev/sda.  Now, the kernel reports that /dev/sda is unavailable                                               and assigns the SAN drive to /dev/sdb instead.  The drive /dev/sdb does                                                                                      work normally.  However, this server is a node for a cluster.  The other                                                                                        member is suffering the same problem.  I'd rather determine the cause                                                                                          and fix it rather than change all references in the configuration files                                                                                       to the new drive location.  Does anyone have any suggestions?</description>
      <pubDate>Mon, 23 Oct 2006 14:25:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/odd-drive-assignment-for-hba/m-p/3885165#M64964</guid>
      <dc:creator>Neil Watson</dc:creator>
      <dc:date>2006-10-23T14:25:36Z</dc:date>
    </item>
    <item>
      <title>Re: Odd drive assignment for HBA</title>
      <link>https://community.hpe.com/t5/operating-system-linux/odd-drive-assignment-for-hba/m-p/3885166#M64965</link>
      <description>Hello Neil, please see this link:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1068223" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1068223&lt;/A&gt;</description>
      <pubDate>Mon, 23 Oct 2006 14:51:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/odd-drive-assignment-for-hba/m-p/3885166#M64965</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-10-23T14:51:31Z</dc:date>
    </item>
    <item>
      <title>Re: Odd drive assignment for HBA</title>
      <link>https://community.hpe.com/t5/operating-system-linux/odd-drive-assignment-for-hba/m-p/3885167#M64966</link>
      <description>I believe the dev labelling you mentioned has been superceded by udev:&lt;BR /&gt;&lt;A href="http://kbase.redhat.com/faq/FAQ_43_8082.shtm" target="_blank"&gt;http://kbase.redhat.com/faq/FAQ_43_8082.shtm&lt;/A&gt;</description>
      <pubDate>Wed, 25 Oct 2006 08:26:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/odd-drive-assignment-for-hba/m-p/3885167#M64966</guid>
      <dc:creator>Neil Watson</dc:creator>
      <dc:date>2006-10-25T08:26:19Z</dc:date>
    </item>
  </channel>
</rss>

