<?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: System Clone a BL860c in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/system-clone-a-bl860c/m-p/4414366#M5908</link>
    <description>You probably need to activate the RAID again.&lt;BR /&gt;&lt;BR /&gt;Use drvcfg to do this. More info needed?</description>
    <pubDate>Wed, 06 May 2009 14:53:59 GMT</pubDate>
    <dc:creator>Torsten.</dc:creator>
    <dc:date>2009-05-06T14:53:59Z</dc:date>
    <item>
      <title>System Clone a BL860c</title>
      <link>https://community.hpe.com/t5/bladesystem-general/system-clone-a-bl860c/m-p/4414365#M5907</link>
      <description>I have a loaner C7000 chassis with 4 x BL860c blades, one of the blades has been created as a Ignite server.  The new production frames have arrived, but unfortunately I have to shutdown and remove the loaner before I can install the new production chassis. &lt;BR /&gt;&lt;BR /&gt;I want to swap the 2 x internal drives that are managed by the SASMGR in hardware raid to the new blade so I can Ignite the new blades. However, in a test of this procedure, I shutdown the O/S (11.31) and powered down the blades and swapped the drives between two of the blades. On powering up the blades both were unable to recognize the internal drives. I think the raid array may have disabled or inactivated the drives. &lt;BR /&gt;&lt;BR /&gt;Does anyone know of a procedure that would allow me to do this?</description>
      <pubDate>Wed, 06 May 2009 14:51:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/system-clone-a-bl860c/m-p/4414365#M5907</guid>
      <dc:creator>Jay Savage</dc:creator>
      <dc:date>2009-05-06T14:51:02Z</dc:date>
    </item>
    <item>
      <title>Re: System Clone a BL860c</title>
      <link>https://community.hpe.com/t5/bladesystem-general/system-clone-a-bl860c/m-p/4414366#M5908</link>
      <description>You probably need to activate the RAID again.&lt;BR /&gt;&lt;BR /&gt;Use drvcfg to do this. More info needed?</description>
      <pubDate>Wed, 06 May 2009 14:53:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/system-clone-a-bl860c/m-p/4414366#M5908</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-05-06T14:53:59Z</dc:date>
    </item>
    <item>
      <title>Re: System Clone a BL860c</title>
      <link>https://community.hpe.com/t5/bladesystem-general/system-clone-a-bl860c/m-p/4414367#M5909</link>
      <description>Reactivating the RAID Controller seems to be the answer. From the EFI shell&amp;gt; drvcfg -s&lt;BR /&gt;&lt;BR /&gt;then manage the array, then reactivate the array. let the controller reset, then reset the blade from the efi shell.&lt;BR /&gt;&lt;BR /&gt;Couple of things I didn't normally have to do:&lt;BR /&gt;&lt;BR /&gt;It still acted like the O/S boot drive wasn't online. So I changed to the boot drive via EFI&amp;gt; fs0:&lt;BR /&gt;then typed: hpux&lt;BR /&gt;this started the boot process on the swapped drive.&lt;BR /&gt;&lt;BR /&gt;Not sure why the array deactivates, but as long as this is working we can shorten the amount of time we need to bring the new chassis online.</description>
      <pubDate>Wed, 06 May 2009 15:36:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/system-clone-a-bl860c/m-p/4414367#M5909</guid>
      <dc:creator>Jay Savage</dc:creator>
      <dc:date>2009-05-06T15:36:16Z</dc:date>
    </item>
    <item>
      <title>Re: System Clone a BL860c</title>
      <link>https://community.hpe.com/t5/bladesystem-general/system-clone-a-bl860c/m-p/4414368#M5910</link>
      <description>The EFI boot entry is stored in the NVRAM of the other server. You need to set it again.&lt;BR /&gt;&lt;BR /&gt;Use "setboot" from running hp-ux.</description>
      <pubDate>Wed, 06 May 2009 17:21:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/system-clone-a-bl860c/m-p/4414368#M5910</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-05-06T17:21:25Z</dc:date>
    </item>
    <item>
      <title>Re: System Clone a BL860c</title>
      <link>https://community.hpe.com/t5/bladesystem-general/system-clone-a-bl860c/m-p/4414369#M5911</link>
      <description>Yeah, this is a test to make sure this is a feasible option so I'll switch the drives back. I just needed to get a procedure in place so when we install the new chassis I can move the ignite server in place without reinstalling the O/S via the USB DVD drive and causing some considerable time required to recreate the ignite server.  The first time I tried this I thought the O/S had been blanked on the drives since they weren't showing up as valid anymore. &lt;BR /&gt;&lt;BR /&gt;Once I get it switched to the new blade I'll do the setboot...&lt;BR /&gt;&lt;BR /&gt;We normally use software raid via lvm on our other Itanium/PA-RISC servers, the hardware raid/SASMGR is throwing us for a little bit of a loop.</description>
      <pubDate>Wed, 06 May 2009 18:07:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/system-clone-a-bl860c/m-p/4414369#M5911</guid>
      <dc:creator>Jay Savage</dc:creator>
      <dc:date>2009-05-06T18:07:19Z</dc:date>
    </item>
  </channel>
</rss>

