An administrator adds a new SATA hard drive into a functional server and attempts to boot the server. The server will no longer boot into the operating system. The administrator checks all the connections and reboots the server. The server still will not load the operating system. Which of the following is the MOST probable cause?

Question

Accepted Answer

A. The BIOS is set with the wrong boot order. Adding a new hard drive can cause the system's BIOS/UEFI to re-evaluate or change the default boot order, or the new drive might be unintentionally prioritized, preventing the system from booting from the original operating system drive.

Answer

B. The jumpers have not been set on the hard drive. SATA drives typically do not use jumpers for master/slave configuration; jumpers were primarily used with older PATA/IDE drives.

Answer

C. The hard drive is not compatible with the system board. While hardware incompatibility can occur, an incorrect boot order is a more probable and common issue when a server stops booting after adding a drive.

Answer

D. The boot.ini file needs to be modified. The `boot.ini` file is a legacy boot configuration file for older Windows versions and would not be the first point of failure if the BIOS isn't even attempting to load from the correct boot device.

An administrator adds a new SATA hard drive into a functional server and attempts to boot the server. The server will no longer boot into the operating system. The administrator checks all the…

Question

Options

How the community answered

Why each option

Topics

Community Discussion