Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1249
  • Last Modified:

Windows Server 2003 BSOD with RAID Enabled

I have a Proliant ML150 G3 Server and had RAID 1 (Mirroring) enabled via the on-board RAID controller. My motherboard went bad and was replaced. When I booted up with the new motherboard I get a BSOD (Error ID 0x0000007B) with RAID enabled. If I change to compatibility mode for the drive, it boots fine. I assume there is a problem with the HDD controller driver, but How can I replace the RAID HDD driver if I cannot boot into windows under RAID? Safe mode gets the same error. I would like to put the server back on RAID. right now its running on compatibility mode.
0
icsbudapest
Asked:
icsbudapest
  • 8
  • 5
  • 4
3 Solutions
 
losipCommented:
Now that you have the server running, I would expect that the ProLiant Support Pack (PSP) for Microsoft Windows Server 2003 Version 7.50A (or later) would install the correct drivers.  You can find this at http://h18023.www1.hp.com/support/files/server/us/locate/3376.html or from the SmartStart 7.50 CD. This PSP contains device drivers, management agents, and utilities supported under Windows Server 2003 and is worth running anyway to ensure you have the latest support.
0
 
tstritofCommented:
Hi,

the first thing to check - is your new on-board controller aware of the mirror? Does it show the mirrored array and proper logical volume or does it show 2 non-redundant arrays?

You can use the Proliant Essentials CD that came with your server to inspect the state of the mirror without booting to windows.

If everything is OK with your RAID1 array and you think that windows crash due to driver issue you can add the appropriate drivers to existing windows installation using a recovery console. If that fails and if you have the valid system state back up then you may try restoring the system state.

Regards,
Tomislav
0
 
tstritofCommented:
@ losip: sorry for "butting-in", I'm a bit slow typing... :) I see you have already started alog the similar path so I'll be "butting-out".

Regards,
Tomislav
0
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

 
icsbudapestAuthor Commented:
Another question. Assuming I get the correct driver and windows boots with raid enabled, I can run server/reboot while the RAID Array is rebuilding. Correct?
0
 
losipCommented:
Good question and I don't know the answer for sure.  You can with the high end SmartArray controllers which are autonomous processors but I'm not sure that the integrated Promise array chip on the ML150G3 supports that.  I don't think I'd risk it, personally.  There is more information about the controller at: http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c00771065/c00771065.pdf
0
 
losipCommented:
Re-reading your comment: in my response above, I was referring to rebooting the server while the array was rebuilding.  You can certainly run the server.
0
 
icsbudapestAuthor Commented:
I installed the PSP package and it still BSODs on startup. If I go into the RAID controller on startup, everything looks fine. It must be a windows thing. Also, the BSOD comes up after windows logo appears.
0
 
icsbudapestAuthor Commented:
I'm beginning to think the replacement motherboard might be a different generation ML150? Maybe they modified the RAID chip in later Generations and that is why it is crashing? Just thinking out loud. I wish it were easier to track down info on HP individual parts. :(
0
 
tstritofCommented:
Maybe this can help you a bit HP Part Surfer.

Regards,
Tomislav
0
 
icsbudapestAuthor Commented:
The part checks out. Its G3. I tried just installing the RAID controller driver. It wont install because "hardware is not present," obviously, if its disabled in BIOS windows thinks it doesn't exist. This explains why the software package didn't install it either.
0
 
losipCommented:
If it's disabled in BIOS, you won't get the "Press F8 key" prompt during POST.  I take it that this works since you say " If I go into the RAID controller on startup, everything looks fine".  Therefore, it does sounds like a Windows driver issue but can we just clarify exactly what you see in the BIOS / Advanced / Harddisk Configuration?  And, can you confirm that you do get asked to press F8 and when you do so, you see that a RAID array exists?
0
 
icsbudapestAuthor Commented:
If it is disabled in BIOS, I do not get the "Press 8 Key" and windows starts normally. However, I can not install a driver for the non-existent hardware. (Hardisk: Enhanced, RAID:disabled, AHCI:Disabled)

If it is enabled in BIOS I do get the "press f8 key" prompt and I can go into the controller settings and add an array etc. The controller sees all the disks and seems to function properly, but I get the BSOD when trying to boot windows. (Harddisk: Enhanced, RaiD:Enabled)

0
 
losipCommented:
What I would do at this stage is to try the early stages of a fresh install of WS03.  Now, this could be tricky because WS03 demands disk controller drivers from a floppy disk and the ML150G3 doesn't have one but I <think> the early stages on setup let you use a USB floppy.  If you can rig that up, can create a disk with the driver on it and get to the installation stage where it can see the array, I think you would then stand a good chance of not getting the BSOD.

I guess the official way is to boot from the SmartStart CD and get to the early point of OS installation when it's asking where to install Windows but I couldn't be sure at what point it would interfere with your existing installation
0
 
tstritofCommented:
Just a suggestion - if you take that path you could also slipstream the RAID controller driver (if you have it) into standard Windows installation image (if you have it) and create a custom boot disk with a tool like nLite. I remember having USB drive issues with ML 110 G3 and ML 150 G3 models (but HP may have fixed it in newer versions of their USB boot disk tools).
0
 
icsbudapestAuthor Commented:
Thanks for the suggestions. I've run out of time today but will get back to this soon. I will set up more frequent backups until then. I don't remember how I did this originally. (It ran fine for about 2-3 years.) I might have a slip-streamed install cd here somewhere. I'll leave this topic open until I try these suggestions.
0
 
icsbudapestAuthor Commented:
I think the solution would be along the lines of what "losip" commented last. However, rather then solve this problem directly I decided to use this opportunity to upgrade the OS from 2003 to 2008. Something I have wanted to do anyway. Unfortunately, this leaves the possible solution unconfirmed.
0
 
icsbudapestAuthor Commented:
I ended up giving up on the repair and just upgraded rather then solve the driver problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 8
  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now