- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- DL140G3 upgrade onboard LSI Controller to e200i
ProLiant Servers (ML,DL,SL)
1753703
Members
4957
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2007 12:42 AM
тАО06-28-2007 12:42 AM
DL140G3 upgrade onboard LSI Controller to e200i
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".
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.
What else can be wrong?
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.
What else can be wrong?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-29-2008 05:40 PM
тАО02-29-2008 05:40 PM
Re: DL140G3 upgrade onboard LSI Controller to e200i
I had similar situation. Possible solutions:
1. Chose reinstall during install process (W2k3 actually preserves lot of data). Since you have a image, you can experiment this way.
2. Fresh install W2k3 with e200i installed. (not sure why you didn't try this in the first place)
3. If this would have been Linux we can easily update the initrd and boot with e200i
1. Chose reinstall during install process (W2k3 actually preserves lot of data). Since you have a image, you can experiment this way.
2. Fresh install W2k3 with e200i installed. (not sure why you didn't try this in the first place)
3. If this would have been Linux we can easily update the initrd and boot with e200i
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-29-2008 10:16 PM
тАО02-29-2008 10:16 PM
Re: DL140G3 upgrade onboard LSI Controller to e200i
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.
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.
What you can do is..
1. Use ntbackup to backup server (NOT an image application).
2. Perform fresh installation of Windows and apply latest service pack
3. Restore ntbackup
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.
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.
What you can do is..
1. Use ntbackup to backup server (NOT an image application).
2. Perform fresh installation of Windows and apply latest service pack
3. Restore ntbackup
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP