johnpsph
join:2003-11-16
Saint Louis, MO
 ·Charter Pipeline
edit:
May 11th, @06:55PM
| [motherboard] Computer can't see RAID drives with NIC insta
So I have a computer with the following specs:
Intel D945GCCRL Mobo
Intel Core 2 Duo 1.8Ghz
1.5GB RAM
StarTech PEXSATA22 PCI Express SATA II Controller
2x 80GB SATA II drives in RAID 1 array
Everything works perfects in the setup listed above. However, I would like to add a second NIC, so I've tried installing THREE different PCI NIC's, and get the same problem every time:
When I boot, I normally get the Intel boot screen, then a screen that displays my RAID Controller model and array. After I install any of the NIC's, I just get a screen showing the controller, but it can't see the hard drives. I've tried using different PCI slots, but to no avail. I'm really frustrated and at my wit's end, so if anyone can offer some advice, I'd really appreciate it. Thanks |
|
yuutomo
The Wonder Kitter
Premium
join:2001-08-27
Missoula, MT | well, there's questions that need to be asked and answered before we move onto the current issue.
1. why are you installing a NIC when the mobo has one? |
|
johnpsph
join:2003-11-16
Saint Louis, MO | I'm using the box as a server 2003 lab machine and want dual NICS |
|
kba4
join:2001-10-23
Akron, OH
·RoadRunner Cable
edit:
May 12th, @02:20PM
| reply to johnpsph
sounds like an IRQ issue. You may be able to fix it fastest by going to the BIOS and checking that the IRQ numbers are far apart from one another.
windows may also have a way to change this too.
the problem is most likely that the RAID card is using a dedicated range of RAM addresses while the NIC doesn't need a dedicated range, though it's configured by default to use it anyway. |
|
johnpsph
join:2003-11-16
Saint Louis, MO | Thanks so much for your reply, but I honestly have no idea how to go about applying the BIOS fix you've suggested. Could you give me a bit more detail, or point me to a page? Thanks |
|
kba4
join:2001-10-23
Akron, OH
·RoadRunner Cable
| reply to johnpsph
a few links that may work for you before we go into IRQ's, and while I research just how to access the IRQ settings on your board.
»support.intel.com/support/mother···tm#ctrli
Intel PDF - Scroll down to page 43 |
|
johnpsph
join:2003-11-16
Saint Louis, MO | THanks again for the reply. To be honest, this mobo has a really bad BIOS interface, I looked through and didn't see anything on IRQ settings. |
|
kba4
join:2001-10-23
Akron, OH
·RoadRunner Cable
| reply to johnpsph
on page 70 of the Intel PDF I linked, it says that PCI devices (both on-board and add-in) are auto-configured at boot. so what you must do is find the setting that changes the available IRQ's. this gets kind of technical, a little above my current level of education on the matter, but basically you'll need to find out how much memory your PCI NIC needs to function (look in manual or on the website) and set that amount as the range to disclude in the available IRQ in BIOS. Now you need to manually install the NIC in windows, which again is above me, though it should be pretty straight-forward. what I do know is that you can go to Add Hardware (in XP, and I'm hoping 2k3 too) and enter in the information when asked.
I hope this works, otherwise both of us need to go to A+ Cert for a refresher  |
|
HRM
God Bless America
Premium,MVM
join:2002-02-03
Darien, CT
clubs:  
 ·Vonage
| reply to johnpsph
This is an odd situation. I might try taking out one drive and the SATA controller and see if you can get the NIC installed, then replace the controller.
This may totally hose things, but once it gets into windows and is detected, maybe it will get past this issue. |
|
johnpsph
join:2003-11-16
Saint Louis, MO | Ouch. That worked, but when I set it back up with the raid, I ended up with the same problem, and I couldn't boot windows, so i had to reinstall |
|
kba4
join:2001-10-23
Akron, OH
·RoadRunner Cable
| let us know if and when it's working, my experience with 2k3 (and 2k) server is hit and miss for some things. for instance, running RRaS to share the net on a domain can sometimes work only when the NIC's (two are required) are initialized in a certain particular order. I've never found the actual rhyme or reason to it, and always had to use trial and error: Stop RRaS, open Network Connections and Disable one and then both adapters, Start RRaS, Enable one and then the other adapter... rinse repeat sometimes 100x or more and eventually it works. thankfully the reboots are far and few between with 2k3 but 2k needed them at almost every windows update! ah well... |
|
johnpsph
join:2003-11-16
Saint Louis, MO | Well, I'm just finally getting 2k3 reinstalled, and I'm also updating the BIOS to see if that might help. Otherwise, i'm pretty much at a dead end, so I could still really use some help |
|
kba4
join:2001-10-23
Akron, OH
·RoadRunner Cable
| not that I can promise anything but others that may read this thread could use all the info possible to solve the problem here. post the NIC's you've tried (brand, model), maybe there's something in common with them all. What I'm getting at is, perhaps an investment in a higher-end NIC, something made by 3COM or Intel, would be worthwhile. of course without knowing much about your past attempts, it's hard to say.
also, let's not rule out the other things entirely: RAM, mobo, HDD's- these can all potentially create problems of their own too.
--
when will these humans realize their insignifigance in the universe? |
|
HRM
God Bless America
Premium,MVM
join:2002-02-03
Darien, CT
clubs:
·Vonage
edit:
May 13th, @06:01AM
| reply to johnpsph
THis is the kind of a thing that a bios update might address. Sorry about the reinstall, but you tried everything else. It seems a really severe hardware conflict.
THe only thing I can think of is trying some sort of USB nic that can be introduced after windows is going.
A common chipset might be the cause. Finding out what your nics have in common would be good to start on that path as suggested.
EDIT: I realise now that after you got the NIC, maybe you should have just tried to install the controler, without hooking the drives to it. I don't think it would have mattered since you can't get into windows at all with it all assembled. |
|
johnpsph
join:2003-11-16
Saint Louis, MO | Sadly, updating the BIOS did nothing to help. I'm beginnging to wonder if either my NIC(s) or RAID controller are to blame |
|
HRM
God Bless America
Premium,MVM
join:2002-02-03
Darien, CT
clubs: | There sure is a conflict there in the most basic sense. You should be able to google the NIC chipset and/or the controller and find others with issues. Probably many before you have found this issue. Someone may even know the answer. |
|
sdgthy
@algx.net | reply to johnpsph
Have you tried different slots? |
|
johnpsph
join:2003-11-16
Saint Louis, MO | Yup, tried both slots. |
|
sdgthy
@algx.net
| Wow, really does have just two PCI slots: »www.intel.com/products/motherboa···ndex.htm
And I thought my Supermicro H8SSLi was lacking in slots...
This sounds like an IRQ problem. You might check what IRQs each is trying to use with only one of each installed. Another can be if the add-in board ROM can't be loaded, that can be solved by disabling the option to boot from a RAID card if you're not booting from it, or disabling booting from the network of a NIC (PXE). You can also trying disabling anything in the BIOS that you are not using floppy, PATA, serial, etc. The latter may free up IRQs. |
|
kba4
join:2001-10-23
Akron, OH
·RoadRunner Cable
| reply to johnpsph
just a thought: you're using rather basic components to run a server. I'll admit, I've gotten server 2k and 2k3 up and running on low-end components but I wouldn't expect this to always be the case. the people who buy server typically spend a grand or so on software alone, and the hardware can run into the $2-3K range just for a basic system. |
|
