 |
|
Frequently Asked Questions
Show Part Numbers
Hide Part Numbers
1102174, 11910110, 2005555, 2501592, 2506121, 2506224, 3500700, 3500733, 3500736, 3500747,
3500793, 3500807, 3500828, 3500844, 3500856, 3500859, 3500871, 3500888, 3500914, 3500922,
3500935, 3500963, 3501015, 3501055, 3501070, 3501082, 3501125, 3501128, 3501129, 3501223,
3501224, 3501230, 3501263, 3501277, 3501278, 3501327, 3501328, 3501408, 3501410, 3501415,
3501417, 3501427, 3501428, 3501436, 3501611, 3501614, 3501615, 3501660, 3501662, 3501726,
3501744, 6000722, 6000726, 6000788, 6000839, 6000929, 6000930, 6000989, 6000990, 6001242,
6001268, 6001269, 6001454, 6001455, 6001525, 6001552, 6001565, 6001566, 6001567, 6001597,
6001792, 6001900, 6001924, 6002158, 6002158a, 6002199, 6002323, 6002432, 6002433, 6002500,
6002501, 6002643, 6002680, 6002745, 6002908, 6002908R, 6007993R, WME03-01037-07, WME05-01037-03, WME5182002228MA,
WME5201002264MC, WME5234000266M, WME5236000264M, WME523600264M, WME536000264M
Show Model(s)
Hide Models
Q: What steps can be taken if a SATA, SCSI or RAID adapter BIOS does not respond during startup?A:
- Are there any error messages that might exhibit additional information? Common error messages might cause a SATA, RAID or SCSI adapter to not respond during startup. Such messages include, but are not limited to, NVRAM Configuration Mismatch, Unresolved Configuration Mismatch, Startup unit request failed, and so forth. Each of these examples has been covered in other FAQs or locations on the Source, and as such will not be gone into in great depth on this FAQ. Follow normal documented troubleshooting steps in each of these instances.
- Are there multiple SCSI BIOS utilities in the server? One of them may be causing a conflict. Disable all SCSI BIOS utilities except one. Test, and if so follow normal troubleshooting to resolve the conflict, such as resetting defaults, checking SCSI IDs, and so forth.
- Does the SATA, SCSI or RAID adapter take a long time while enumerating a particular device? If so, try removing the device, and then test for resolution. If it now responds, you may a difficulty with that particular device. If so, follow normal troubleshooting steps for that device.
- Check the server BIOS Setup utility. The location you need to check will vary, depending on the motherboard the RAID / SCSI card is installed in. In general, it is located in the Boot section in an entry for the hard drive below boot device priority section. Is the card properly recognized in the Boot order menu?
- Try starting the server with just the RAID or SCSI card in the server. If it is still not responding, the card may be the cause of the difficulty.
- Try resetting the defaults on the card. For example, for an Adaptec SCSI card, press the F6 key from the SCSI BIOS, and then configure view host adapter settings menu resets the defaults. In the case of an LSI RAID card, from the BIOS, go to objects-adapter-factory defaults. This assumes that you are able to enter the BIOS.
- Try reseating the card, preferably in a different slot in case this issue is caused by a resource conflict.
- Try clearing the NVRAM of the motherboard or pulling the CMOS battery, and then letting the server sit for 5 minutes with no power. It may be a corrupt CMOS setting. If you unsure about the procedures for clearing NVRAM, consult the motherboard documentation or tools for the exact location for the Clear CMOS jumper.
- Try flashing the firmware on the card.
Note: In general, Gateway posts available firmware on the Gateway Web site only if it has been completely tested. If you have a firmware directly from the card's vendor, it will most likely work, but make sure that you are aware that the firmware has not been tested by Gateway.
|
|
|
United States
(change country or region)