• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1002
  • Last Modified:

Windows 2003 Enterprise Does Not Recognize Hard Drive in Server

I am rebuilding my primary server with a new 300 GB SCSI U320 boot drive, but I cannot get Win2003 Enterprise Edition to recognize the new drive.

 Disks are RAID 0 and RAID 5 via Intel MegaRAID Elite 1650, which provides BIOS controlled RAID - so, in theory, no drivers need to be loaded via F6 at start of boot.  All old drives have been pulled temporarily while I am trying to diagnose the problem, the RAID configuration cleared, and only the new drive appears in the RAID array list (as RAID 0).

After failing with Win2003, I dropped back to Win2000 (same result), and to Windows 98.  From DOS I was able to allocate a primary partition (8GB FAT32), make it active, and format it as a system disk, and boot from it.  From there I was able to load Windows 98.

Not surprisingly, Windows 98 will not boot up, but I can boot to a DOS prompt and display the contents of the C: drive.  So, the drive is clearly present and accessible via BIOS.  No drivers were added to the DOS configuration.

However, when I try to boot up either Win2000 or Win2003 Enterprise I continue to get "Setup did not find any hard drives installed in your computer."  I've tried it both with and without providing the MegaRAID Elite 1650 drivers via F6 when Setup initializes.

This really has me stumped.  I'm only in this mess because my primary hard drive crashed on me and my backup image drive did not spin up.  I'm been running this configuration for years, with 3 primary partitions: partition 0 for DOS, partition 1 for Win2000, and partition 2 for Windows 2003 Small Business Server, and using System Commander as a boot manager though I only used DOS/Win2000 to recover from problems, of which there have been precious few.  The old hard drive was 73 GB  and the new one 300 GB, but I formatted only an 8GB partition for Windows 98 in case there was a problem with the 300 GB disk. (I read somewhere that there could be a problem with an initial load past 70 GB, which I suppose could still be a problem since the free space will be ~292GB after partition 0.)

Other than using my one remaining backup 73 GB drive and/or reloading Win2003 Small Business Server, I am now out of ideas. I would prefer not to reuse the backup drive because there may be useful data on that drive that is not backed up elsewhere. I would prefer not to go back to Win2003 SBS because I need Enterprise Edition so I can address past 4 GB of memory (assuming that SBS will even load, of course).

All suggestions gratefully received.



0
donestes
Asked:
donestes
  • 5
  • 5
  • 4
  • +1
1 Solution
 
5g6tdcv4Commented:
However, when I try to boot up either Win2000 or Win2003 Enterprise I continue to get "Setup did not find any hard drives installed in your computer."  I've tried it both with and without providing the MegaRAID Elite 1650 drivers via F6 when Setup initializes.



You must have the wrong driver........
are their scsi drivers that need to be installed?
0
 
donestesAuthor Commented:
The MegaRAID does not need drivers (even though they are available) because it is BIOS controlled.  That is why DOS can access the drives without adding any SCSI drivers to the configuration.  I bought it specifically for that feature - OS independence.  If DOS doesn't need the drivers, why would Win2000/2003?

That said, I tried to load both Win2000 and Win2003 both with and without the MegaRAID drivers - and neither worked.  In fact, when I provided the drivers to Win2003 Enterprise it came back and said that the built in driver was newer than the driver I was trying to load.  That gave me the impetus to try it both with and without the MegaRAID driver.

The prior working configuration did not have the drivers either - but the example was on the drive that crashed and on the backup that did not spin up.
0
 
donestesAuthor Commented:
New information: I tried loading Win2003 Small Business Server (the same version that I had been running) and it also did not recognize the disks.  However, I tried to load Win2008 Server it did recognize the disks, but only after I loaded the MegaRAID driver.  
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
noxchoCommented:
Man, your problem is driver. Sure OS needs the controller driver. Your RAID controller is on motherboard and there is no RAID that can be built without RAID controller chip.
Load the driver during Win 2003 installation and check if it changes the situation. Your understanding that BIOS controller RAID does not need driver is wrong.
0
 
5g6tdcv4Commented:
"However, I tried to load Win2008 Server it did recognize the disks, but only after I loaded the MegaRAID driver.  "
Ok with that being said what makes you think server 2003 is going to work with the RAID without drivers if server 2008 needed you to put them in?


"In fact, when I provided the drivers to Win2003 Enterprise it came back and said that the built in driver was newer than the driver I was trying to load."

If the driver you are trying to F6 install is older than the driver that is on the 2003 install media, you need to find a newer one
0
 
donestesAuthor Commented:
There is a RAID controller on the motherboard, but I am not using that.  The backplane is connected to the Intel MegaRAID card not to the built-in RAID connector on the motherboard.  If your assertion were true, then how would DOS be able to recognize the drive without a driver configured?  I specifically bought this card when configuring the system so that I did not need a driver to get to it from DOS.

Regardless, I tried loading the MegaRAID driver via the F6 prompt and it did not work with either Win2000 or Win2003, but it DID work with Win2008.  So, the question reduces to:

Why does neither Win2000 nor Win2003 recognize the disk as being present when the driver is loaded, particularly since it did so when I originally configured the system? I must be missing a step in the process.

I suspect at this point that there has to be an NTFS partition present on the disk for it to detect it, which I will prove or disprove in the next couple of hours.
0
 
D_VanteCommented:
Have you tried downloading the latest driver from intel
0
 
5g6tdcv4Commented:
if you hook up your backup drive to the raid controller does the 2003 install see it?
0
 
5g6tdcv4Commented:
also I am assuming you have created the raid array using the RAID utility.
What type of RAID are you creating to boot off of? How many disks are going to be in said array?
or are you only using the controller to "pass through" the scsi drive as a single master for boot?
0
 
donestesAuthor Commented:
When I inserted the backup boot drive the MegaRAID controller could see that a drive was in the slot but it reported it as "Failed" thus the conclusion that it did not spin up.

The RAID was configured for 6 drives: 2 RAID 0 (1 system boot drive and 1VMWare virtual machine drive) and 4 configured as RAID 5.  I pulled all the drives except the new 300 GB drive, cleared the configuration, and declared a single drive RAID 0 array.  So, yes, it is being used as a pass through.

I am using the version 6.41 driver which is the only MegaRAID driver I had in my driver repository, and which I therefore concluded had to be the same driver that I had used with Win2003 previously.  I did not use the newer 6.51 driver in order to minimize the number of variables changing.  I agree this is worth a try at some point in the debugging process, but if it did work while we are changing other variables then we would not know which variable was the one that fixed the problem.

Correction: I had said Intel MegaRAID - I should have said LSI Logic MegaRAID 1650.
0
 
5g6tdcv4Commented:
slap the 300 gb in, start the 2k3 install F6 the driver and see if the new one works. That is only one variable and could be the easiest and shortest solution
0
 
noxchoCommented:
Is your driver unpacked? And is this driver for exact bit version of your Win 2003? I mean is it 64bit or x86?
0
 
D_VanteCommented:
Agree. Drivers are usually backwards compatible
0
 
donestesAuthor Commented:
Driver is unpacked, and is x86 not x64.

Test with the Win2008 allocated logical disk on Drive 0 did not work, so that is not it.  (I did F6 load the 6.41 driver). No joy.

On the test load with 6.51 driver, Win2003 comes up to say

"The driver you provided seems to be newer than the Windows default driver.

"Windows already has a driver for 'LSI MegaRAID products for Windows 2003 (x86)'"

I used the newer 6.51 driver.  This time it recognize that the disk was present.

So, the problem is solved, and I guess we'll just never know what was different about the procedure I followed when I set up Win2003 Small Business Server several years ago (and it worked with the 6.41 driver) and what I did differently this time so that the 6.41 driver did not work.
0
 
D_VanteCommented:
Are you using server 2003 r2?
0
 
D_VanteCommented:
Are you using server 2003 r2?
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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