<?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: Disk migration RAID 1 problem in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779506#M52358</link>
    <description>I know some people will say it's safe, ... No &lt;BR /&gt;Pulling drive out on the fly can cause all kind Problems: including data loss, Array configuration corruption, RIS ..est&lt;BR /&gt;Hot Plug is not a Hot Pull - see attachment &lt;BR /&gt;</description>
    <pubDate>Sat, 29 Apr 2006 08:28:14 GMT</pubDate>
    <dc:creator>Oleg Koroz</dc:creator>
    <dc:date>2006-04-29T08:28:14Z</dc:date>
    <item>
      <title>Disk migration RAID 1 problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779503#M52355</link>
      <description>Hi,&lt;BR /&gt;I want to migrate my Win2K-Installtion from a ML350 G2 with Smart Array 641 to ML 370 G3 with Smart Array 642 Controller. The OS-Partition of the source server is mirrored with RAID1.&lt;BR /&gt;The idea is to take off one of the mirrored disks and put it in server 2. After this the 642-controller reports "1787-Slot1 Drive Array Operating in Interim Recovery Mode". So far so good. I then performed a Win2k repair installation and my system is up again. Everything seems to run ok.&lt;BR /&gt;As next step I added a second disk to rebuild the mirror. But ACU still tells me that the array is running in Interim Recovery Mode.&lt;BR /&gt;I can't find a way to rebuild or to manage the mirror. Also I can't tell the controller to operate with the second disk.&lt;BR /&gt;Can anybody help me?&lt;BR /&gt;TIA&lt;BR /&gt;Frank&lt;BR /&gt;</description>
      <pubDate>Fri, 28 Apr 2006 05:24:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779503#M52355</guid>
      <dc:creator>Frank Euskirchen</dc:creator>
      <dc:date>2006-04-28T05:24:46Z</dc:date>
    </item>
    <item>
      <title>Re: Disk migration RAID 1 problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779504#M52356</link>
      <description>did you pull drive, on the fly or you powered down server ?</description>
      <pubDate>Fri, 28 Apr 2006 11:16:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779504#M52356</guid>
      <dc:creator>Oleg Koroz</dc:creator>
      <dc:date>2006-04-28T11:16:54Z</dc:date>
    </item>
    <item>
      <title>Re: Disk migration RAID 1 problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779505#M52357</link>
      <description>Hi,&lt;BR /&gt;I pulled the drive (hot plug) without shutting down the server.&lt;BR /&gt;Is there a difference between the two methods?&lt;BR /&gt;Thanks&lt;BR /&gt;Frank</description>
      <pubDate>Sat, 29 Apr 2006 03:46:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779505#M52357</guid>
      <dc:creator>Frank Euskirchen</dc:creator>
      <dc:date>2006-04-29T03:46:04Z</dc:date>
    </item>
    <item>
      <title>Re: Disk migration RAID 1 problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779506#M52358</link>
      <description>I know some people will say it's safe, ... No &lt;BR /&gt;Pulling drive out on the fly can cause all kind Problems: including data loss, Array configuration corruption, RIS ..est&lt;BR /&gt;Hot Plug is not a Hot Pull - see attachment &lt;BR /&gt;</description>
      <pubDate>Sat, 29 Apr 2006 08:28:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779506#M52358</guid>
      <dc:creator>Oleg Koroz</dc:creator>
      <dc:date>2006-04-29T08:28:14Z</dc:date>
    </item>
    <item>
      <title>Re: Disk migration RAID 1 problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779507#M52359</link>
      <description>But what happens to RAID1 configurations when the server crashes?&lt;BR /&gt;In that situation I don't have the choice to shut down the server to pull out the disk. In other words: I don't have a chance to eject the disk in a "safe mode".&lt;BR /&gt;Isn't there any chance to rebuild the mirror?&lt;BR /&gt;Does the state stay in "Interim Recovery Mode" or are there any tools to rebuild the mirror?&lt;BR /&gt;&lt;BR /&gt;Frank</description>
      <pubDate>Mon, 01 May 2006 02:03:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779507#M52359</guid>
      <dc:creator>Frank Euskirchen</dc:creator>
      <dc:date>2006-05-01T02:03:47Z</dc:date>
    </item>
    <item>
      <title>Re: Disk migration RAID 1 problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779508#M52360</link>
      <description>Hi Frank.&lt;BR /&gt;&lt;BR /&gt;Did you changed the drive's position? bay?&lt;BR /&gt;&lt;BR /&gt;Run ADU, save report and call HP support, ask the agent if he can help you finding SCSI backplane errors on the report.&lt;BR /&gt;&lt;BR /&gt;The rebuild process might be been queued by other operation.&lt;BR /&gt;&lt;BR /&gt;If the Raid 1 is still running on ACU, try assigning the drive as a hot spare for the raid to see if the controller start the rebuild on this drive.&lt;BR /&gt;&lt;BR /&gt;Regards.</description>
      <pubDate>Mon, 01 May 2006 23:16:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779508#M52360</guid>
      <dc:creator>chongkan</dc:creator>
      <dc:date>2006-05-01T23:16:32Z</dc:date>
    </item>
    <item>
      <title>Re: Disk migration RAID 1 problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779509#M52361</link>
      <description>Download and install latest firmware before</description>
      <pubDate>Mon, 01 May 2006 23:21:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779509#M52361</guid>
      <dc:creator>chongkan</dc:creator>
      <dc:date>2006-05-01T23:21:24Z</dc:date>
    </item>
    <item>
      <title>Re: Disk migration RAID 1 problem</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779510#M52362</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;With regards to your concerns. I understand the arguement. It "feels" like you should be able to pull a drive out on the fly, because that's exactly what you do when a drive crashes and you hot replace it.&lt;BR /&gt;&lt;BR /&gt;The difference is that when a drive crashes, it's the dead drive you remove. It becomes corrupted by being hot pulled, but it's already gone.&lt;BR /&gt;&lt;BR /&gt;The drive which stays in the server, because there was nothing wrong with it, is unaffected by your actions on the dead drive and hence keeps running.&lt;BR /&gt;&lt;BR /&gt;In other words, a drive is only "consistent" when pulled from a shutdown server, and if you think hard enough, this is not a problem in general.&lt;BR /&gt;</description>
      <pubDate>Tue, 02 May 2006 01:28:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/disk-migration-raid-1-problem/m-p/3779510#M52362</guid>
      <dc:creator>Joshua Small_2</dc:creator>
      <dc:date>2006-05-02T01:28:22Z</dc:date>
    </item>
  </channel>
</rss>

