<?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 DL140G3 upgrade onboard LSI Controller to e200i in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl140g3-upgrade-onboard-lsi-controller-to-e200i/m-p/4028679#M66505</link>
    <description>&lt;!--!*#--&gt;Installed  DL140G3 with W2k3 using onboard LSI/SATA hotplugs. Applied e200i (without disks), installed e200i drivers, imaged disk away, unplugged disk from LSI, connected to e200i, restored image, fixed boot record and MBR, but still unable to boot W2k3, message "error loading operating system". &lt;BR /&gt;When starting system with Recovery Console, I'm able to access the disk and it does look perfect; checked hpcisss2.sys (boot) and disabled lsi_sas.sys.&lt;BR /&gt;What else can be wrong?</description>
    <pubDate>Thu, 28 Jun 2007 07:42:03 GMT</pubDate>
    <dc:creator>ThomasR_1</dc:creator>
    <dc:date>2007-06-28T07:42:03Z</dc:date>
    <item>
      <title>DL140G3 upgrade onboard LSI Controller to e200i</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl140g3-upgrade-onboard-lsi-controller-to-e200i/m-p/4028679#M66505</link>
      <description>&lt;!--!*#--&gt;Installed  DL140G3 with W2k3 using onboard LSI/SATA hotplugs. Applied e200i (without disks), installed e200i drivers, imaged disk away, unplugged disk from LSI, connected to e200i, restored image, fixed boot record and MBR, but still unable to boot W2k3, message "error loading operating system". &lt;BR /&gt;When starting system with Recovery Console, I'm able to access the disk and it does look perfect; checked hpcisss2.sys (boot) and disabled lsi_sas.sys.&lt;BR /&gt;What else can be wrong?</description>
      <pubDate>Thu, 28 Jun 2007 07:42:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl140g3-upgrade-onboard-lsi-controller-to-e200i/m-p/4028679#M66505</guid>
      <dc:creator>ThomasR_1</dc:creator>
      <dc:date>2007-06-28T07:42:03Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G3 upgrade onboard LSI Controller to e200i</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl140g3-upgrade-onboard-lsi-controller-to-e200i/m-p/4028680#M66506</link>
      <description>I had similar situation. Possible solutions:&lt;BR /&gt;&lt;BR /&gt;1. Chose reinstall during install process (W2k3 actually preserves lot of data). Since you have a image, you can experiment this way.&lt;BR /&gt;2. Fresh install W2k3 with e200i installed. (not sure why you didn't try this in the first place)&lt;BR /&gt;3. If this would have been Linux we can easily update the initrd and boot with e200i</description>
      <pubDate>Sat, 01 Mar 2008 01:40:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl140g3-upgrade-onboard-lsi-controller-to-e200i/m-p/4028680#M66506</guid>
      <dc:creator>Cyberswim</dc:creator>
      <dc:date>2008-03-01T01:40:36Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G3 upgrade onboard LSI Controller to e200i</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl140g3-upgrade-onboard-lsi-controller-to-e200i/m-p/4028681#M66507</link>
      <description>You may well find some reghack to make this work, but ultimately what is wrong is that this is not a procedure that's meant to work.&lt;BR /&gt;&lt;BR /&gt;Windows stores data relating to its C: and its storage in the registry, and you can't just "install a driver" for another card and then expect it to boot.&lt;BR /&gt;&lt;BR /&gt;What you can do is..&lt;BR /&gt;&lt;BR /&gt;1. Use ntbackup to backup server (NOT an image application).&lt;BR /&gt;2. Perform fresh installation of Windows and apply latest service pack&lt;BR /&gt;3. Restore ntbackup&lt;BR /&gt;&lt;BR /&gt;Why this works is ntbackup System State restore does a registry "merge" instead of overwrite. This will leave the correct mass storage keys in place.&lt;BR /&gt;</description>
      <pubDate>Sat, 01 Mar 2008 06:16:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl140g3-upgrade-onboard-lsi-controller-to-e200i/m-p/4028681#M66507</guid>
      <dc:creator>Joshua Small_2</dc:creator>
      <dc:date>2008-03-01T06:16:27Z</dc:date>
    </item>
  </channel>
</rss>

