<?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: cciss messages in dmesg in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181770#M50991</link>
    <description>At last, I've not been able to exactly figure out why these messages appeared. It seemes that it's not possible in Linux to have the correct answer for each message which is logged by the os. Sometimes a little pain :-( &lt;BR /&gt;</description>
    <pubDate>Fri, 26 Jun 2009 06:58:13 GMT</pubDate>
    <dc:creator>Markus Schibli</dc:creator>
    <dc:date>2009-06-26T06:58:13Z</dc:date>
    <item>
      <title>cciss messages in dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181765#M50986</link>
      <description>Hi&lt;BR /&gt;could someone explain me the following cciss messages which I saw recently in dmesg?&lt;BR /&gt;&lt;BR /&gt;Red Hat Enterprise Linux ES release 4 (Nahant Update 8)&lt;BR /&gt;&lt;BR /&gt;dmesg output (partly):&lt;BR /&gt;&lt;BR /&gt;HP CISS Driver (v 2.6.20.RH1)&lt;BR /&gt;cciss: Device 0x46 has been found at bus 4 dev 3 func 0&lt;BR /&gt;ACPI: PCI Interrupt 0000:04:03.0[A] -&amp;gt; GSI 51 (level, low) -&amp;gt; IRQ 217&lt;BR /&gt;cciss: using DAC cycles&lt;BR /&gt;      blocks= 142253279 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 17433&lt;BR /&gt;&lt;BR /&gt;      blocks= 573480303 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 70280&lt;BR /&gt;&lt;BR /&gt;      blocks= 142253279 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 17433&lt;BR /&gt;&lt;BR /&gt; cciss/c0d0: p1 p2&lt;BR /&gt;      blocks= 573480303 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 70280&lt;BR /&gt;&lt;BR /&gt; cciss/c0d1:&lt;BR /&gt;      blocks= 573480303 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 70280&lt;BR /&gt;&lt;BR /&gt;      blocks= 573480303 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 70280&lt;BR /&gt;&lt;BR /&gt; cciss/c0d1:&lt;BR /&gt;      blocks= 573480303 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 70280&lt;BR /&gt;&lt;BR /&gt;      blocks= 573480303 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 70280&lt;BR /&gt;&lt;BR /&gt; cciss/c0d1:&lt;BR /&gt;      blocks= 573480303 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 70280&lt;BR /&gt;&lt;BR /&gt;      blocks= 573480303 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 70280&lt;BR /&gt;&lt;BR /&gt; cciss/c0d1:&lt;BR /&gt;      blocks= 573480303 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 70280&lt;BR /&gt;&lt;BR /&gt;      blocks= 573480303 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 70280&lt;BR /&gt;&lt;BR /&gt; cciss/c0d1:&lt;BR /&gt;      blocks= 573480303 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 70280&lt;BR /&gt;&lt;BR /&gt;      blocks= 573480303 block_size= 512&lt;BR /&gt;      heads= 255, sectors= 32, cylinders= 70280&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;I can't find information what these messages mean. Any info on that? where to look after?&lt;BR /&gt;&lt;BR /&gt;Many thanks in advance&lt;BR /&gt;Regards&lt;BR /&gt;Markus</description>
      <pubDate>Tue, 16 Jun 2009 13:27:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181765#M50986</guid>
      <dc:creator>Markus Schibli</dc:creator>
      <dc:date>2009-06-16T13:27:23Z</dc:date>
    </item>
    <item>
      <title>Re: cciss messages in dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181766#M50987</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Disks have been detected, probably due to RH's built in multi-pathing capabilities.&lt;BR /&gt;&lt;BR /&gt;Notice they are all the same size.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 16 Jun 2009 13:45:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181766#M50987</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-06-16T13:45:31Z</dc:date>
    </item>
    <item>
      <title>Re: cciss messages in dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181767#M50988</link>
      <description>Hi Steven&lt;BR /&gt;Thanks for your reply.&lt;BR /&gt;I recognised too that the disks are all of the same size, in fact it's always the same disk.&lt;BR /&gt;It's always cciss/c0d1. Why? I saw ~180 exactly the same entries for cciss/c0d1 in dmesg.&lt;BR /&gt;&lt;BR /&gt;Thanks and regards&lt;BR /&gt;Markus</description>
      <pubDate>Tue, 16 Jun 2009 13:52:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181767#M50988</guid>
      <dc:creator>Markus Schibli</dc:creator>
      <dc:date>2009-06-16T13:52:31Z</dc:date>
    </item>
    <item>
      <title>Re: cciss messages in dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181768#M50989</link>
      <description>&lt;BR /&gt;This can't be multipathing with cciss. It an internal RAID controller and only presents disks down one path.  The messages are all related to the same device cciss/c0d1, and for the most part the same block number on that device. Maybe it's detected a bad block on the disk and is attempting to mapping it out and replace it with another?&lt;BR /&gt;&lt;BR /&gt; I'm afraid I have no idea what these messages mean otherwise.  Have you installed the Proliant Support Pack for your system. HP's diagnostic tools might throw more light on this for you.</description>
      <pubDate>Tue, 16 Jun 2009 14:17:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181768#M50989</guid>
      <dc:creator>John McNulty_2</dc:creator>
      <dc:date>2009-06-16T14:17:06Z</dc:date>
    </item>
    <item>
      <title>Re: cciss messages in dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181769#M50990</link>
      <description>I don't have the answer for this exact issue, but cciss can be for non-internal disks. For example, the cciss driver is used for the 700m SAS RAID controller which links to external arrays.</description>
      <pubDate>Tue, 16 Jun 2009 22:20:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181769#M50990</guid>
      <dc:creator>macosta</dc:creator>
      <dc:date>2009-06-16T22:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: cciss messages in dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181770#M50991</link>
      <description>At last, I've not been able to exactly figure out why these messages appeared. It seemes that it's not possible in Linux to have the correct answer for each message which is logged by the os. Sometimes a little pain :-( &lt;BR /&gt;</description>
      <pubDate>Fri, 26 Jun 2009 06:58:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/cciss-messages-in-dmesg/m-p/5181770#M50991</guid>
      <dc:creator>Markus Schibli</dc:creator>
      <dc:date>2009-06-26T06:58:13Z</dc:date>
    </item>
  </channel>
</rss>

