<?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: Interim Recovery Mode and bad disk in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/interim-recovery-mode-and-bad-disk/m-p/4684014#M105601</link>
    <description>Seem perfectly well to me :)&lt;BR /&gt;&lt;BR /&gt;I know absolutely nothing aboute Linux.&lt;BR /&gt;&lt;BR /&gt;You would see the same events in Windows, when you have the insight agents running.&lt;BR /&gt;My gues is that you got the insight agents installed.&lt;BR /&gt;&lt;BR /&gt;You should see these as a service messages to the system administrator.&lt;BR /&gt;&lt;BR /&gt;It tell you, a disk has faile.&lt;BR /&gt;Wich physical and logical disk.&lt;BR /&gt;It report, that it has discovered a disk change.&lt;BR /&gt;And that rebuild has startet.&lt;BR /&gt;And best of all, that it has finished.&lt;BR /&gt;&lt;BR /&gt;You should be Happy :)&lt;BR /&gt;&lt;BR /&gt;BR&lt;BR /&gt;/jag&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 07 Sep 2010 09:26:47 GMT</pubDate>
    <dc:creator>gregersenj</dc:creator>
    <dc:date>2010-09-07T09:26:47Z</dc:date>
    <item>
      <title>Interim Recovery Mode and bad disk</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/interim-recovery-mode-and-bad-disk/m-p/4684012#M105599</link>
      <description>hello,&lt;BR /&gt;&lt;BR /&gt;DL380-G5, fw from 2009, redHat 5.4.&lt;BR /&gt;&lt;BR /&gt;I have setup an 0+1 array of 6 disks a while ago.&lt;BR /&gt;One of these disk failed (between sunday and monday), an it seems that disk report an error,  turning filesystems readonly. (And of course we need to reboot host).&lt;BR /&gt;&lt;BR /&gt;Shouldn't array stuff prevent us from seeing the error ?&lt;BR /&gt;&lt;BR /&gt;Jean-Yves Picard &lt;BR /&gt;&lt;BR /&gt;cma's report:&lt;BR /&gt;Sep  6 16:14:23 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status OK to Physical Drive Not Properly Connected&lt;BR /&gt;Sep  6 16:14:23 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status Physical Drive Not Properly Connected to Interim Recovery&lt;BR /&gt;Sep  6 16:14:28 redhat54 cmaidad[7781]: Logical Drive Status Change: Slot 1, Drive: 2. Status is now Interim Recovery.&lt;BR /&gt;Sep  6 16:14:28 redhat54 cmaidad[7781]: Physical Drive Status Change: Slot 1 Port 2I Box 1 Bay 2. Status is now Failed.&lt;BR /&gt;Sep  7 11:18:55 redhat54 cmaeventd[7661]: Hot-plug drive inserted: Port 2I Box 1 Bay 2 of Array Controller in slot 1.&lt;BR /&gt;Sep  7 11:18:59 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status Interim Recovery to Ready For Rebuild&lt;BR /&gt;Sep  7 11:18:59 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status Ready For Rebuild to Rebuilding&lt;BR /&gt;Sep  7 11:19:05 redhat54 cmaidad[7781]: Logical Drive Status Change: Slot 1, Drive: 2. Status is now Rebuilding.&lt;BR /&gt;Sep  7 11:19:05 redhat54 cmaidad[7781]: Physical Drive Status Change: Slot 1 Port 2I Box 1 Bay 2. Status is now OK.&lt;BR /&gt;Sep  7 11:54:00 redhat54 cmaeventd[7661]: Logical drive 2 of Array Controller in slot 1, has changed from status Rebuilding to OK&lt;BR /&gt;Sep  7 11:54:07 redhat54 cmaidad[7781]: Logical Drive Status Change: Slot 1, Drive: 2. Status is now OK.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Sep 2010 09:06:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/interim-recovery-mode-and-bad-disk/m-p/4684012#M105599</guid>
      <dc:creator>Jean-Yves Picard</dc:creator>
      <dc:date>2010-09-07T09:06:36Z</dc:date>
    </item>
    <item>
      <title>Re: Interim Recovery Mode and bad disk</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/interim-recovery-mode-and-bad-disk/m-p/4684013#M105600</link>
      <description>You are right; normally this is transparent to the OS. The log you sent looks normal. There must be a problem anywhere else (maybe controller firmware, cabling, another bad disk, etc ...)</description>
      <pubDate>Tue, 07 Sep 2010 09:15:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/interim-recovery-mode-and-bad-disk/m-p/4684013#M105600</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-09-07T09:15:23Z</dc:date>
    </item>
    <item>
      <title>Re: Interim Recovery Mode and bad disk</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/interim-recovery-mode-and-bad-disk/m-p/4684014#M105601</link>
      <description>Seem perfectly well to me :)&lt;BR /&gt;&lt;BR /&gt;I know absolutely nothing aboute Linux.&lt;BR /&gt;&lt;BR /&gt;You would see the same events in Windows, when you have the insight agents running.&lt;BR /&gt;My gues is that you got the insight agents installed.&lt;BR /&gt;&lt;BR /&gt;You should see these as a service messages to the system administrator.&lt;BR /&gt;&lt;BR /&gt;It tell you, a disk has faile.&lt;BR /&gt;Wich physical and logical disk.&lt;BR /&gt;It report, that it has discovered a disk change.&lt;BR /&gt;And that rebuild has startet.&lt;BR /&gt;And best of all, that it has finished.&lt;BR /&gt;&lt;BR /&gt;You should be Happy :)&lt;BR /&gt;&lt;BR /&gt;BR&lt;BR /&gt;/jag&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Sep 2010 09:26:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/interim-recovery-mode-and-bad-disk/m-p/4684014#M105601</guid>
      <dc:creator>gregersenj</dc:creator>
      <dc:date>2010-09-07T09:26:47Z</dc:date>
    </item>
  </channel>
</rss>

