<?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: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942468#M46396</link>
    <description>"# lssd" shows that the MPIO is working. I suggest you check and make sure that the proper failover policy ("Path A/B-Failover only") is set on the virtual disks.</description>
    <pubDate>Wed, 23 Nov 2005 09:23:48 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2005-11-23T09:23:48Z</dc:date>
    <item>
      <title>FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942458#M46386</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I am running Redhat Entreprise Edition V3 update3, with the Qlogic driver&lt;BR /&gt;&lt;BR /&gt;QLogic PCI to Fibre Channel Host Adapter for QLA2340         :&lt;BR /&gt;        Firmware version:  3.02.28, Driver version 7.00.03-RH1&lt;BR /&gt;Entry address = f88dc060&lt;BR /&gt;HBA: QLA2312 , Serial# R07449&lt;BR /&gt;Request Queue = 0x3630000, Response Queue = 0x3620000&lt;BR /&gt;Request Queue count= 512, Response Queue count= 512&lt;BR /&gt;Total number of active commands = 0&lt;BR /&gt;Total number of interrupts = 1185947&lt;BR /&gt;Total number of IOCBs (used/max) = (0/600)&lt;BR /&gt;Total number of queued commands = 0&lt;BR /&gt;    Device queue depth = 0x10&lt;BR /&gt;Number of free request entries = 500&lt;BR /&gt;Number of mailbox timeouts = 0&lt;BR /&gt;Number of ISP aborts = 0&lt;BR /&gt;Number of loop resyncs = 0&lt;BR /&gt;Number of retries for empty slots = 0&lt;BR /&gt;Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0&lt;BR /&gt;Host adapter:loop state= &lt;READY&gt;, flags= 0x6860813&lt;BR /&gt;Dpc flags = 0x0&lt;BR /&gt;MBX flags = 0x0&lt;BR /&gt;SRB Free Count = 4096&lt;BR /&gt;Link down Timeout = 008&lt;BR /&gt;Port down retry = 064&lt;BR /&gt;Login retry count = 016&lt;BR /&gt;Commands retried with dropped frame(s) = 0&lt;BR /&gt;Configured characteristic impedence: 50 ohms&lt;BR /&gt;Configured data rate: 1-2 Gb/sec auto-negotiate&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;SCSI Device Information:&lt;BR /&gt;scsi-qla0-adapter-node=200000e08b1ab90d;&lt;BR /&gt;scsi-qla0-adapter-port=210000e08b1ab90d;&lt;BR /&gt;scsi-qla0-target-0=50001fe15003e889;&lt;BR /&gt;scsi-qla0-target-1=50001fe1500425dc;&lt;BR /&gt;scsi-qla0-target-2=100000e00222dff3&lt;BR /&gt;&lt;BR /&gt;I have added two luns and also reboot my server.&lt;BR /&gt;fdisk doesn't work on my new luns&lt;BR /&gt;&lt;BR /&gt;fdisk /dev/sdd : Cannot read /dev/sdd&lt;BR /&gt;&lt;BR /&gt;output of lssd&lt;BR /&gt;&lt;BR /&gt;sda  0,0,0,1         HP HSV100 2001  5000-1fe1-5003-e889&lt;BR /&gt;sdb  0,0,0,2         HP HSV100 2001  5000-1fe1-5003-e889&lt;BR /&gt;sdc  0,0,1,1         HP HSV100 2001  5000-1fe1-5004-25dc&lt;BR /&gt;sdd  0,0,1,2         HP HSV100 2001  5000-1fe1-5004-25dc&lt;BR /&gt;&lt;BR /&gt;Any idea's&lt;BR /&gt;&lt;/READY&gt;</description>
      <pubDate>Wed, 23 Nov 2005 04:11:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942458#M46386</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-11-23T04:11:12Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942459#M46387</link>
      <description>What is the output of fdisk -l? Did you try using parted instead of fdisk?</description>
      <pubDate>Wed, 23 Nov 2005 06:47:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942459#M46387</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-11-23T06:47:46Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942460#M46388</link>
      <description>Also, ensure that the OS TYPE in the host definition is correct.</description>
      <pubDate>Wed, 23 Nov 2005 06:48:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942460#M46388</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-11-23T06:48:41Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942461#M46389</link>
      <description>HOST Type is Sun Solaris (OK for LX)&lt;BR /&gt;fdisk in neither working</description>
      <pubDate>Wed, 23 Nov 2005 06:49:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942461#M46389</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-11-23T06:49:43Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942462#M46390</link>
      <description>Do you have multiple HBA? Do you have a multipath software installed?</description>
      <pubDate>Wed, 23 Nov 2005 07:51:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942462#M46390</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-11-23T07:51:59Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942463#M46391</link>
      <description>Mpio is embedded in the Qlogic driver.&lt;BR /&gt;This is not the issue because my other Luns are working fine</description>
      <pubDate>Wed, 23 Nov 2005 08:16:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942463#M46391</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-11-23T08:16:30Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942464#M46392</link>
      <description>It may be that this disk is active on the other controller (?).&lt;BR /&gt;&lt;BR /&gt;Any other error, like cannot read, not such file, or I/O error. Any log on /var/log/messages.</description>
      <pubDate>Wed, 23 Nov 2005 08:34:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942464#M46392</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-11-23T08:34:29Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942465#M46393</link>
      <description>This is the only relevant info in messages&lt;BR /&gt;&lt;BR /&gt;Nov 23 11:20:18 san-leandro kernel:  sdd:&amp;lt;6&amp;gt;Device 08:30 not ready.&lt;BR /&gt;Nov 23 11:20:18 san-leandro kernel:  I/O error: dev 08:30, sector 0&lt;BR /&gt;Nov 23 11:20:18 san-leandro kernel: Device 08:30 not ready.&lt;BR /&gt;Nov 23 11:20:18 san-leandro kernel:  I/O error: dev 08:30, sector 0&lt;BR /&gt;Nov 23 11:20:18 san-leandro kernel:  unable to read partition table</description>
      <pubDate>Wed, 23 Nov 2005 08:40:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942465#M46393</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-11-23T08:40:15Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942466#M46394</link>
      <description>Just for testing, can you turn off one of the controllers? I want to be sure that all disks are on presented by the same controller.</description>
      <pubDate>Wed, 23 Nov 2005 09:07:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942466#M46394</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-11-23T09:07:52Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942467#M46395</link>
      <description>Ivan, I have one card in by server.&lt;BR /&gt;Two controllers on my EVA3000, no I cannot turn this of, this is a production environment</description>
      <pubDate>Wed, 23 Nov 2005 09:11:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942467#M46395</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-11-23T09:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942468#M46396</link>
      <description>"# lssd" shows that the MPIO is working. I suggest you check and make sure that the proper failover policy ("Path A/B-Failover only") is set on the virtual disks.</description>
      <pubDate>Wed, 23 Nov 2005 09:23:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942468#M46396</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-11-23T09:23:48Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942469#M46397</link>
      <description>On the eva3000, it is set&lt;BR /&gt;PathA / Failover only&lt;BR /&gt;&lt;BR /&gt;This is the output of lssd&lt;BR /&gt;&lt;BR /&gt;sda  0,0,0,1         HP HSV100 2001  5000-1fe1-5003-e889&lt;BR /&gt;sdb  0,0,0,2         HP HSV100 2001  5000-1fe1-5003-e889&lt;BR /&gt;sdc  0,0,1,1         HP HSV100 2001  5000-1fe1-5004-25dc&lt;BR /&gt;sdd  0,0,1,2         HP HSV100 2001  5000-1fe1-5004-25dc&lt;BR /&gt;&lt;BR /&gt;the output off fdisk&lt;BR /&gt;&lt;BR /&gt;fdisk /dev/sdd&lt;BR /&gt;&lt;BR /&gt;cannot read /dev/sdd</description>
      <pubDate>Wed, 23 Nov 2005 09:33:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942469#M46397</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-11-23T09:33:20Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942470#M46398</link>
      <description>Just to clarify, you should be able to power off one controller even in production, what about if the controller fails? But as you have only one HBA this is not the issue.&lt;BR /&gt;&lt;BR /&gt;Is the zoning configuration correct?</description>
      <pubDate>Wed, 23 Nov 2005 10:15:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942470#M46398</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-11-23T10:15:52Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942471#M46399</link>
      <description>Zoning is 100 % correct.&lt;BR /&gt;sda en sdc are working fine.&lt;BR /&gt;I have added sdb en sdd, I cannot format those luns&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Nov 2005 10:17:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942471#M46399</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-11-23T10:17:36Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942472#M46400</link>
      <description>Are these luns presented to another host. Maybe you have a FC RESERVATION problem. All posts with FC reservation problems where solved by powering off the storage device.</description>
      <pubDate>Wed, 23 Nov 2005 13:06:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942472#M46400</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-11-23T13:06:29Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942473#M46401</link>
      <description>Ivan,&lt;BR /&gt;These lun are prestented only to one host.&lt;BR /&gt;Restarting the EVA is not an issue at this moment.&lt;BR /&gt;It is a production environment with&lt;BR /&gt;10 servers</description>
      <pubDate>Thu, 24 Nov 2005 02:20:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942473#M46401</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-11-24T02:20:34Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942474#M46402</link>
      <description>That doesn't look right to me:&lt;BR /&gt;&lt;BR /&gt;&amp;gt; On the eva3000, it is set PathA / Failover only&lt;BR /&gt;&amp;gt;&lt;BR /&gt;&amp;gt;This is the output of lssd&lt;BR /&gt;&amp;gt;&lt;BR /&gt;...&lt;BR /&gt;&amp;gt;sdd 0,0,1,2 HP HSV100 2001 5000-1fe1-5004-25dc&lt;BR /&gt;&lt;BR /&gt;Normally, controller A owns WWPNs that end in 8+9. If that is true on your system, |/dev/sdd| is owned by controller B or the MPIO driver has choosen a wrong path.&lt;BR /&gt;&lt;BR /&gt;Can you try and select "PathB / Failover only"" ?</description>
      <pubDate>Thu, 24 Nov 2005 02:33:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942474#M46402</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-11-24T02:33:54Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942475#M46403</link>
      <description>Uwe, &lt;BR /&gt;&lt;BR /&gt;You were right.&lt;BR /&gt;&lt;BR /&gt;PathB / Failover only solved my problem</description>
      <pubDate>Fri, 25 Nov 2005 09:37:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942475#M46403</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-11-25T09:37:53Z</dc:date>
    </item>
    <item>
      <title>Re: FDISK FAILURE ON NEW LUNS FROM EVA3000 REDHAT</title>
      <link>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942476#M46404</link>
      <description>That means that in case of failover you won't be able to access the lun?</description>
      <pubDate>Mon, 28 Nov 2005 06:44:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/fdisk-failure-on-new-luns-from-eva3000-redhat/m-p/4942476#M46404</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-11-28T06:44:59Z</dc:date>
    </item>
  </channel>
</rss>

