<?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: Identify SAN Disks in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922728#M26577</link>
    <description>If you have a ProLiant server connected to a SAN the '/dev/cciss/*' devices are local storage and /dev/sd* devices are probably SAN disks.&lt;BR /&gt;&lt;BR /&gt;Make sure you install the fibreutils RPM from the HP ProLiant Support Pack. They include a couple of useful utilities to identify SAN disks &amp;amp; devices:&lt;BR /&gt;&lt;BR /&gt;- lssg (display generic san devices)&lt;BR /&gt;- lssd (display san disk devices)&lt;BR /&gt;- adapter_info &lt;DEVICE&gt; (display hba information)&lt;BR /&gt;&lt;BR /&gt;You can also take a look inside the /proc filesystem to get useful information:&lt;BR /&gt;&lt;BR /&gt;Smart Array Controller: /proc/driver/cciss/&lt;BR /&gt;SCSI devices: /proc/scsi/scsi&lt;BR /&gt;QLA Host Bus Adapter: /proc/scsi/qla2300&lt;BR /&gt;&lt;BR /&gt;&lt;/DEVICE&gt;</description>
    <pubDate>Wed, 10 Jan 2007 18:51:10 GMT</pubDate>
    <dc:creator>Siert Zijl</dc:creator>
    <dc:date>2007-01-10T18:51:10Z</dc:date>
    <item>
      <title>Identify SAN Disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922723#M26572</link>
      <description>Please let me what command would tell me the difference between local and the SAN disks. linux redhat AS 3.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;THOMAS</description>
      <pubDate>Mon, 08 Jan 2007 17:58:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922723#M26572</guid>
      <dc:creator>M.Thomas</dc:creator>
      <dc:date>2007-01-08T17:58:51Z</dc:date>
    </item>
    <item>
      <title>Re: Identify SAN Disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922724#M26573</link>
      <description>fdisk -l&lt;BR /&gt;&lt;BR /&gt;The hardware path for local disks are almost always displayed before SAN.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 09 Jan 2007 03:58:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922724#M26573</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-01-09T03:58:30Z</dc:date>
    </item>
    <item>
      <title>Re: Identify SAN Disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922725#M26574</link>
      <description>The path names will tell you if the local disks are "IDE", but not if they are SCSI since SAN's use sudo-SCSI drivers.&lt;BR /&gt;&lt;BR /&gt;Take a look at your dmesg output and identifiy the name of your SAN adapter. lspci may also show the name of the card. Next look at "/proc/scsi/adapter-name" and "/proc/scsi/scsi" and this should give further clues.&lt;BR /&gt;&lt;BR /&gt;Some adapter code also adds utilities such as: probe-luns so it's worth looking for any extra RPM's that were loaded.</description>
      <pubDate>Wed, 10 Jan 2007 04:33:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922725#M26574</guid>
      <dc:creator>Andrew Cowan</dc:creator>
      <dc:date>2007-01-10T04:33:18Z</dc:date>
    </item>
    <item>
      <title>Re: Identify SAN Disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922726#M26575</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;if you are using a ProLiant with a Smart Array controller, the disks attatched to the Smart Array will use /dev/cciss/c0d0, /dev/cciss/c0d1 ... as device name. Logical drives from a storage in you SAN will use the traditional device names like /dev/sda, /dev/sdb... Take a look at /proc/scsi/scsi or the output of dmesg.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Patrick</description>
      <pubDate>Wed, 10 Jan 2007 05:45:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922726#M26575</guid>
      <dc:creator>Patrick Terlisten</dc:creator>
      <dc:date>2007-01-10T05:45:39Z</dc:date>
    </item>
    <item>
      <title>Re: Identify SAN Disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922727#M26576</link>
      <description>Dear Sir,&lt;BR /&gt;&lt;BR /&gt;By default scsi internal disk will be /dev/sdb.&lt;BR /&gt;&lt;BR /&gt;And for next available device either san or another scsi channel it will be sdb.&lt;BR /&gt;&lt;BR /&gt;Use fdisk -l will list the availbale disk seen.This coammnd will not do any modification in ur disk , Need not tor worry.&lt;BR /&gt;Regds&lt;BR /&gt;B.Ganesh</description>
      <pubDate>Wed, 10 Jan 2007 06:00:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922727#M26576</guid>
      <dc:creator>Ganesh Balraman</dc:creator>
      <dc:date>2007-01-10T06:00:31Z</dc:date>
    </item>
    <item>
      <title>Re: Identify SAN Disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922728#M26577</link>
      <description>If you have a ProLiant server connected to a SAN the '/dev/cciss/*' devices are local storage and /dev/sd* devices are probably SAN disks.&lt;BR /&gt;&lt;BR /&gt;Make sure you install the fibreutils RPM from the HP ProLiant Support Pack. They include a couple of useful utilities to identify SAN disks &amp;amp; devices:&lt;BR /&gt;&lt;BR /&gt;- lssg (display generic san devices)&lt;BR /&gt;- lssd (display san disk devices)&lt;BR /&gt;- adapter_info &lt;DEVICE&gt; (display hba information)&lt;BR /&gt;&lt;BR /&gt;You can also take a look inside the /proc filesystem to get useful information:&lt;BR /&gt;&lt;BR /&gt;Smart Array Controller: /proc/driver/cciss/&lt;BR /&gt;SCSI devices: /proc/scsi/scsi&lt;BR /&gt;QLA Host Bus Adapter: /proc/scsi/qla2300&lt;BR /&gt;&lt;BR /&gt;&lt;/DEVICE&gt;</description>
      <pubDate>Wed, 10 Jan 2007 18:51:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922728#M26577</guid>
      <dc:creator>Siert Zijl</dc:creator>
      <dc:date>2007-01-10T18:51:10Z</dc:date>
    </item>
    <item>
      <title>Re: Identify SAN Disks</title>
      <link>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922729#M26578</link>
      <description>morning&lt;BR /&gt;&lt;BR /&gt;use "lsscsi" to list all SCSI devices or "scsi_info /dev/&lt;DEVICE&gt;" to see more info like WWN and LUN WWID.&lt;BR /&gt;&lt;BR /&gt;regards&lt;/DEVICE&gt;</description>
      <pubDate>Thu, 18 Jan 2007 02:40:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/identify-san-disks/m-p/3922729#M26578</guid>
      <dc:creator>SJO EGGER</dc:creator>
      <dc:date>2007-01-18T02:40:31Z</dc:date>
    </item>
  </channel>
</rss>

