HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Re: ML350G3 SmartArray Controller Failure SA641 re...
Windows Server 2003
1833126
Members
3358
Online
110051
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
Forums
Discussions
Discussions
Discussions
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
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
10-16-2009 01:19 PM
10-16-2009 01:19 PM
ML350G3 SmartArray Controller Failure SA641 replaced with SA642
I had a failure with the SA641 and could not purchase a replacement as it was discontinued. I was told that the SA642 would be the replacement. It arrived today and I put it into the server. The card is posting and the Windows 2003 SBS server begins the GUI splash screen. After a few seconds it gets a STOP 0x0000007b and restarts.
I believe the issue is that the OS is not recognizing the SA642. All of my drives and data are intact.
How do I get the SA642 to boot the Ultra320 drives without a complete rebuild?
Thanks.
I believe the issue is that the OS is not recognizing the SA642. All of my drives and data are intact.
How do I get the SA642 to boot the Ultra320 drives without a complete rebuild?
Thanks.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2009 02:10 PM
10-16-2009 02:10 PM
Re: ML350G3 SmartArray Controller Failure SA641 replaced with SA642
This question would be better served in a Windows system administration section of these forums, as this seems to be strictly a Windows OS issue. I'll ask the forum moderators to move this thread there.
My Windows knowledge is badly rusty and somewhat out of date, but I understand that booting from Windows 2003 CD-ROM offers some recovery options.
There might be an automated recovery option that hopefully can insert the correct SA642 driver to the existing system.
http://support.microsoft.com/kb/325375
(see section titled "How to Repair Your Installation of Windows", near the end of the page)
MK
My Windows knowledge is badly rusty and somewhat out of date, but I understand that booting from Windows 2003 CD-ROM offers some recovery options.
There might be an automated recovery option that hopefully can insert the correct SA642 driver to the existing system.
http://support.microsoft.com/kb/325375
(see section titled "How to Repair Your Installation of Windows", near the end of the page)
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2009 08:32 PM
10-16-2009 08:32 PM
Re: ML350G3 SmartArray Controller Failure SA641 replaced with SA642
0x7b means INACCESSIBLE_BOOT_DEVICE. Have a look at http://support.microsoft.com/kb/324103/en-us
Most likely some UID has changed causing windows not to find the drive it's looking for. Sometimes this error is easily fixed by booting the windows CD, selecting recovery console and executing fixboot & fixmbr.
Most likely some UID has changed causing windows not to find the drive it's looking for. Sometimes this error is easily fixed by booting the windows CD, selecting recovery console and executing fixboot & fixmbr.
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP