Added Adaptec 29160 SCSI card to GW ALR7200 server win 2k sp4 - "Device cannot start, (Code 10)" need help
Hope someone knows what I obviously overlooked:
We have a Win 2000 sp4 server. Platform is a GW ALR 7200 Server with 1 GB Ram and a single processor.
Everything was working fine, I installed the new card as per instructions (in 32 bit PCI slot, have no 64s available) and no matter what combination of BIOS and Driver combinations I use I cannot get the device to start.
The system has listed in the Device Manager 3 additional Adaptec family controllers:
The following is from the Hardware Manager screen
AHA-2940U2/U2W PCI SCSI Controller
AHA-2940U2/U2W PCI SCSI Controller
AIC-7892 Ultra 160/m PCI SCSI Card
SCSI Card 29160 Ultra 160 SCSI
The last device has the yellow ! (of death??) on it and the properties say "This device cannot start (Code 10)" and give no additional information.
During the system boot, I see the BIOS for hte first 2 controllers and the last controller and all the attached devices are recognized. The problems start after windows boots up (no error messages during boot, just no device)
I have been all over the Adaptec support site, but thought I would ask real experts before going to them directly.
BACKGROUND: (not necessarily part of the problem, skip if you like)
The internal tape drive has failed and rather than replacing it and buying 3 new drives for each of the 3 new servers we are bringing on line, we opted to move up and get a tape library. This server runs Exchange Server 2000 and will also be the Back-Up server running Veritas with remote agents for the other 3 machines. This set up was chosen after a consultant who charges enough to pretend to know indicated that the Veritas Remote backup agent has problems opening the mail stores on a remote Exchange server. the logical choice is to have the exchange server be the backup server as well - our mail traffic falls off conciderably at night - with the exception of MyDoom of course. This same consultant was also trying to talk us out of remotely backing up any servers stating that network traffic etc would cause too much delay etc. the eventual plan will be to ahve all the servers being backup on a seperate Gigabit ether network segment dedicated to this function - this should be more than enough (yes, no, maybe? discuss?)
Sorry for the lengthy post, wanted to get all the info out there on the first go. I've been struggling withthis for a while and in the mean time, there are no backups being made of the exchange server - a defenite recepiet for disaster!!
Thank you all in advance for any help - points go to whomever gets the card to be recognized by Win-2K (split points are defenitely possible)
We have a Win 2000 sp4 server. Platform is a GW ALR 7200 Server with 1 GB Ram and a single processor.
Everything was working fine, I installed the new card as per instructions (in 32 bit PCI slot, have no 64s available) and no matter what combination of BIOS and Driver combinations I use I cannot get the device to start.
The system has listed in the Device Manager 3 additional Adaptec family controllers:
The following is from the Hardware Manager screen
AHA-2940U2/U2W PCI SCSI Controller
AHA-2940U2/U2W PCI SCSI Controller
AIC-7892 Ultra 160/m PCI SCSI Card
SCSI Card 29160 Ultra 160 SCSI
The last device has the yellow ! (of death??) on it and the properties say "This device cannot start (Code 10)" and give no additional information.
During the system boot, I see the BIOS for hte first 2 controllers and the last controller and all the attached devices are recognized. The problems start after windows boots up (no error messages during boot, just no device)
I have been all over the Adaptec support site, but thought I would ask real experts before going to them directly.
BACKGROUND: (not necessarily part of the problem, skip if you like)
The internal tape drive has failed and rather than replacing it and buying 3 new drives for each of the 3 new servers we are bringing on line, we opted to move up and get a tape library. This server runs Exchange Server 2000 and will also be the Back-Up server running Veritas with remote agents for the other 3 machines. This set up was chosen after a consultant who charges enough to pretend to know indicated that the Veritas Remote backup agent has problems opening the mail stores on a remote Exchange server. the logical choice is to have the exchange server be the backup server as well - our mail traffic falls off conciderably at night - with the exception of MyDoom of course. This same consultant was also trying to talk us out of remotely backing up any servers stating that network traffic etc would cause too much delay etc. the eventual plan will be to ahve all the servers being backup on a seperate Gigabit ether network segment dedicated to this function - this should be more than enough (yes, no, maybe? discuss?)
Sorry for the lengthy post, wanted to get all the info out there on the first go. I've been struggling withthis for a while and in the mean time, there are no backups being made of the exchange server - a defenite recepiet for disaster!!
Thank you all in advance for any help - points go to whomever gets the card to be recognized by Win-2K (split points are defenitely possible)
This could help http://www.eventid.net/display.asp?eventid=9&eventno=2059
CODE 10
If the device has a "FailReasonString" value in its hardware key, that string is displayed as the error message. The driver or enumerator places this registry string value there. If there is no "FailReasonString" in the hardware key, the following generic error message is displayed:
This device is either not present, not working properly, or does not have
all the drivers installed. (Code 10)
Try upgrading the device drivers for this device.
Solution button: Update Driver
To resolve this error code, make sure the device is connected to the computer correctly. For example, make sure all cables are plugged in fully and that all adapter cards are properly seated. Follow the suggested solution button and update the device driver. It may be possible to remove the device and redetect it using the Add New Hardware wizard.
CODE 10
If the device has a "FailReasonString" value in its hardware key, that string is displayed as the error message. The driver or enumerator places this registry string value there. If there is no "FailReasonString" in the hardware key, the following generic error message is displayed:
This device is either not present, not working properly, or does not have
all the drivers installed. (Code 10)
Try upgrading the device drivers for this device.
Solution button: Update Driver
To resolve this error code, make sure the device is connected to the computer correctly. For example, make sure all cables are plugged in fully and that all adapter cards are properly seated. Follow the suggested solution button and update the device driver. It may be possible to remove the device and redetect it using the Add New Hardware wizard.
ASKER
1stITMAN - the event log shows nothing and I have updated the driver, but it wont hurt to try that again. I will go find the most pu to date drive out there.
Any thoughts on a need to flash teh BIOS on the server box? The box is circa 1998/2000 erra and I'm sure that the BIOS has not been updated. Thoughts?
Any thoughts on a need to flash teh BIOS on the server box? The box is circa 1998/2000 erra and I'm sure that the BIOS has not been updated. Thoughts?
Well its a good idea to update the bios!
ASKER
This is odd behavior:
I go through the process of updating the device driver and when you get to the point where you tell it that you "have disk", browse to the .inf file, select it, click ok and then it returns to the select model window...the window remains blank. I cannot get the server to show me an option of selecting the new device driver. I went back and downloded the entire driver package from Adaptec again - nothing.
Has anyone ever seen this happen before?
I go through the process of updating the device driver and when you get to the point where you tell it that you "have disk", browse to the .inf file, select it, click ok and then it returns to the select model window...the window remains blank. I cannot get the server to show me an option of selecting the new device driver. I went back and downloded the entire driver package from Adaptec again - nothing.
Has anyone ever seen this happen before?
I would uninstall then then try agian!
ASKER
Did that - same thing.
I'm going for the BIOS flash now (I hate doing this, always makes me nervous) currently is on version 4.x.x dated 1998 and the current version is 6.x.x dated 2000 - might as well.
I'll report back after I recover from total oblivion - wish me luck
I'm going for the BIOS flash now (I hate doing this, always makes me nervous) currently is on version 4.x.x dated 1998 and the current version is 6.x.x dated 2000 - might as well.
I'll report back after I recover from total oblivion - wish me luck
ASKER
This just gets better and better.
"unable to allocate ROM memory - upgrade aborted"
"unable to allocate ROM memory - upgrade aborted"
Ok did you follow the correct steps to flash the bios, you may have goosed it. Damn!!
Well Try restting the Bios take battery out for about 10 mins and put it back in and boot.
Can you still boot the server!!
Well Try restting the Bios take battery out for about 10 mins and put it back in and boot.
Can you still boot the server!!
ASKER
The server still boots. I printeddown the Gateway instructions for their flash prog and followed
1) enter bios and write down all settings (sure why not)
2) reboot to floppy
3) at promt type PROGBIOS<CR>
so on and so forth. I've done BIOS flashes manytimes, I'm just not comfortable with any opperation that can disable the computer indefinitely if it goes wrong - never had one go wrong either - but then I read and follow the Surgeon General's warnings too, what can I say...
Server is happily still living in 1998 and stubbornly refuses to come up to the 21 centry no matter how much I beg opr threaten it to do so.
I suppose I could pull the battery on the BIOS, but I'm not sure what that would gain me at this point other than ensuring that I have to reenter any non default values.
I was thinking that perhaps I need to have a dos driver for the existing (AHA-2940U2/U2W PCI SCSI Controller) controller with the HDDs on it for hte floppy boot. I suppose that this wouldn't be too hard to create, the Win 98 boot disk threw up a complaint that it couldn't find C:\ followed by some things to cause this, and then it actually said that it wrote some files to C:\ which surprised me and then gave me the A:> prompt.
I followed the instructions as printed and then got the unable to allocate ROM memory error (or whatever I wrote above) I was thikning that I could try pulling down the flash program again from Gateway, but not sure that that will do anything, there were no errors when I grabbed it the first time.
suggestions?
1) enter bios and write down all settings (sure why not)
2) reboot to floppy
3) at promt type PROGBIOS<CR>
so on and so forth. I've done BIOS flashes manytimes, I'm just not comfortable with any opperation that can disable the computer indefinitely if it goes wrong - never had one go wrong either - but then I read and follow the Surgeon General's warnings too, what can I say...
Server is happily still living in 1998 and stubbornly refuses to come up to the 21 centry no matter how much I beg opr threaten it to do so.
I suppose I could pull the battery on the BIOS, but I'm not sure what that would gain me at this point other than ensuring that I have to reenter any non default values.
I was thinking that perhaps I need to have a dos driver for the existing (AHA-2940U2/U2W PCI SCSI Controller) controller with the HDDs on it for hte floppy boot. I suppose that this wouldn't be too hard to create, the Win 98 boot disk threw up a complaint that it couldn't find C:\ followed by some things to cause this, and then it actually said that it wrote some files to C:\ which surprised me and then gave me the A:> prompt.
I followed the instructions as printed and then got the unable to allocate ROM memory error (or whatever I wrote above) I was thikning that I could try pulling down the flash program again from Gateway, but not sure that that will do anything, there were no errors when I grabbed it the first time.
suggestions?
ASKER
"Cannot allocate memory for ROM file"
the server has 1 GB of RAM and is being booted into Win 98. I'm going to guess that this is the problem. Any suggestions on a better boot disk to use? I'd rather not pull out RAM just to do this...but if I have to then I have to.
the server has 1 GB of RAM and is being booted into Win 98. I'm going to guess that this is the problem. Any suggestions on a better boot disk to use? I'd rather not pull out RAM just to do this...but if I have to then I have to.
Ok I thought there was something wrong with your bios thats why i asked you pull the battery out, So i guess its booting fine then.
Now Im thinking is it an IRQ conflict?
Do you need all the cards in ther server.
OK you see when addind a scsi card you have a bios for it and on boot it detects anything connected to it, so if its detecting devices then that is fine, it when it is in the OS then the problems start , correct!!
Now Im thinking is it an IRQ conflict?
Do you need all the cards in ther server.
OK you see when addind a scsi card you have a bios for it and on boot it detects anything connected to it, so if its detecting devices then that is fine, it when it is in the OS then the problems start , correct!!
ASKER
Correct. the problems start in the OS.
The deal with those other cards is that they are embedded in the motherboard. Since the second card only has the now defunked tape drive on it, I was thinking of disabling that one, or removing it. However, according to Adaptec, you can have as many SCSI cards as you have slots to plug them into.
I had thought about an IRQ conflict, but checking everythign else in the system tha I can check, nothing is using the same IRQ.
For Today's fun and excitement I was thinking about reseating the card (just for kicks since it seems to be fine during it's BIOS boot up) and then pulling out 3 sticks of RAM - getting me back to 256MB - and trying the BIOS FLASH for the server again....I seem to recall that Win98 will not address a full GB of RAM, and I don'thave any NT based floppy boot disk sets, and they don't come up in command line anyway. Probably need to find a Dr. DOS or something like that. (Linux would be nice)
The deal with those other cards is that they are embedded in the motherboard. Since the second card only has the now defunked tape drive on it, I was thinking of disabling that one, or removing it. However, according to Adaptec, you can have as many SCSI cards as you have slots to plug them into.
I had thought about an IRQ conflict, but checking everythign else in the system tha I can check, nothing is using the same IRQ.
For Today's fun and excitement I was thinking about reseating the card (just for kicks since it seems to be fine during it's BIOS boot up) and then pulling out 3 sticks of RAM - getting me back to 256MB - and trying the BIOS FLASH for the server again....I seem to recall that Win98 will not address a full GB of RAM, and I don'thave any NT based floppy boot disk sets, and they don't come up in command line anyway. Probably need to find a Dr. DOS or something like that. (Linux would be nice)
ASKER
sorry - the first 2 ar embeded, the third is the RAID card, I suppose that I could move the RAID controller to the new card.....
Go here for dos boot disks http://www.bootdisk.com/
ASKER
That's where I got he win 98 disk...I'll look for others
ASKER
Any idea id Dr Dos 7.x will handle the gig of ram?
No I idea
should do it only dos
should do it only dos
ASKER
So far nothing seems to have worked. I have not yet resorted to pulling out some RAM and trying the BIOS FLASH again. Still hoping that someone has had this problem and resolved it
Thanks
Thanks
ASKER
Although this problem never got resolved, I'm going to close this question out as I have pulled the card out of hte server in question and will try to install it in a different server. The need to have the card and the associated tape library online has reached a point where I no longer have the luxury of making it work on this server.
The BIOS flash was never accomplished.
I would like to give the points to 1stITMAN for taking a stab at the issue - and for being the only one, but I don't know if this would be the correct thing to do.
The BIOS flash was never accomplished.
I would like to give the points to 1stITMAN for taking a stab at the issue - and for being the only one, but I don't know if this would be the correct thing to do.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This issue was never resolved. I pulled the card out of the system in question and in stalled it into a new Dual Opteron server and it is working fine (Tyan S2882G3NR Rev.2A motherboard) the tape library hokedup to it is happily backing up data to it's hearts content.
Download latest drivers from adaptec and install that.
Are you getting any errors in teh event viewer plz check and post