Hardware problems 60
Network controller stopped working when an expansion board was added
Action
:
1.
Be sure no loose connections (on page
19
) exist.
2.
Be sure the server and operating system support the controller. Refer to the server and operating system
documentation.
3.
Be sure the new expansion board has not changed the server configuration, requiring reinstallation of
the network driver.
a.
Uninstall the network controller driver for the malfunctioning controller in the operating system.
b.
Restart the server and run RBSU. Be sure the server recognizes the controller and that resources are
available for the controller.
c.
Restart the server, and then reinstall the network driver.
4.
Refer to the operating system documentation to be sure the correct drivers are installed.
5.
Refer to the operating system documentation to be sure that the driver parameters match the
configuration of the network controller.
Problems are occurring with the network interconnect blades
Action
: Be sure the network interconnect blades are properly seated and connected.
Expansion board problems
System requests recovery method during expansion board replacement
When replacing an expansion board on a BitLocker™-encrypted server, always disable BitLocker™ before
replacing the expansion board. If BitLocker™ is not disabled, the system requests the recovery method
selected when BitLocker™ was configured. Failure to provide the correct recovery password or passwords
results in loss of access to all encrypted data.
Be sure to enable BitLocker™ after the installation is complete.
For information on BitLocker™, see BitLocker™ for Servers on the Microsoft website
(
http://www.microsoft.com
).
