troubleshooting practice questions

Replace the failed disk and restore from backup

Why wrong: Restoring from backup is time-consuming and should only be done if the rebuild fails; not the best practice.

Replace the failed disk and perform a manual rebuild from backup

Why wrong: Manual rebuild from backup is slower and riskier than automatic rebuild, and should only be done if automatic fails.

Delete the logical drive and recreate the array

Why wrong: This would cause data loss and is not necessary when a simple disk replacement can restore the array.

Operating system files

Why wrong: Missing or corrupt OS files would typically generate a different error, such as 'Missing operating system' or a blue screen.

SATA cable connections

Why wrong: While loose cables can cause boot issues, the drives are spinning and detected by the controller, so cables are likely fine.

RAID array status

Why wrong: The technician already verified the drives appear in the RAID controller, so the array status is likely healthy; if it were degraded, the drives might not appear.

Add a second disk to the RAID 5 array (convert to RAID 6).

Why wrong: Converting to RAID 6 would add parity overhead and not reduce latency; it might even increase it.

Increase the VM's memory allocation.

Why wrong: Memory allocation does not affect disk latency directly; this would not resolve a storage I/O bottleneck.

Change the virtual disk type from thin to thick.

Why wrong: Changing disk type affects space allocation, not I/O latency; the underlying storage device remains the same.

The UPS battery is depleted

Why wrong: The UPS battery status does not affect the server's ability to power on if utility power is present; the server powers on momentarily.

One of the power supplies has failed

Why wrong: A failed power supply would not allow the server to power on even briefly; it would remain off or show error LEDs.

The CMOS battery is dead

Why wrong: A dead CMOS battery would only reset BIOS settings and may cause a date/time error, not a failure to POST.

Shrink the existing partition and extend it onto an additional drive

Why wrong: This is not directly supported on a basic disk and would require conversion to dynamic disk, which often requires a reboot.

Add a new drive, initialize it, and configure a RAID 1 mirror with the existing drive

Why wrong: Mirroring does not increase usable space and may require a reboot to convert to dynamic disk.

Replace the current system drive with a larger one and restore from backup

Why wrong: This causes significant downtime and is not the best solution when a non-disruptive option exists.

The new replacement drive is faulty.

Why wrong: If the new drive were faulty, the rebuild would likely have failed or shown errors.

The motherboard has a faulty PCIe slot for the RAID controller.

Why wrong: Faulty PCIe slot would cause the controller to disappear or cause I/O errors, not parity errors.

The RAID controller cache module has failed.

Why wrong: Cache failure would cause write errors or performance issues, not parity errors on a mirrored pair.

Check network cables and switch connections.

Why wrong: Network issues typically cause connectivity problems, not random system crashes, so this step is premature.

Reinstall the operating system.

Why wrong: Reinstalling the OS is a last resort after hardware issues have been thoroughly checked, as it may not fix hardware failures.

Replace the CPU with a known good one.

Why wrong: CPU failures are less common than memory issues; replacing the CPU is invasive and should be done after memory is cleared.

Run a filesystem check utility from a recovery disk.

Why wrong: A filesystem check would only help if the error were due to filesystem corruption, not a missing boot device.

Replace the hard drive with a known good one.

Why wrong: Replacing the drive is drastic and should not be the first step without verifying other possibilities.

Reseat the hard drive data and power cables.

Why wrong: Reseating cables is reasonable but less likely than a boot order change after a power outage.

Power supply status

Why wrong: Incorrect. Power supply issues typically cause shutdowns or instability, not slow queries with normal resource metrics.

Database index fragmentation

Why wrong: Incorrect. Index fragmentation affects disk I/O, but disk latency is normal, so this is not the immediate issue.

Operating system patch level

Why wrong: Incorrect. While patches can affect performance, the symptom is slow queries with normal CPU/memory/disk, so network is more likely.

Disable hyper-threading on the host

Why wrong: Incorrect. Disabling hyper-threading reduces logical CPUs, which can increase ready time and degrade performance further.

Increase the number of vCPUs for the VM

Why wrong: Incorrect. Increasing vCPUs can worsen ready time because it leads to more contention for physical cores.

Migrate the VM to a different host

Why wrong: Incorrect. While migration might help temporarily, it does not address the root cause of over-provisioning on the host.

Disk fragmentation

Why wrong: Incorrect. Fragmentation increases seek times but typically does not cause queue lengths above 10 on modern RAID arrays.

Slow network link

Why wrong: Incorrect. A slow network link would affect network throughput, not disk I/O wait times and queue length.

Overloaded CPU

Why wrong: Incorrect. High CPU utilization does not directly cause high disk I/O wait; it might indicate a bottleneck elsewhere.

Memory leak in an application

Why wrong: Incorrect. While a memory leak could cause high usage, the exhibit does not indicate a specific application; the most direct interpretation is insufficient memory.

Virtual memory is misconfigured

Why wrong: Incorrect. Virtual memory settings appear normal; the issue is lack of physical memory, not a configuration problem.

Page file is too small

Why wrong: Incorrect. The page file size (16,384 MB) is equal to physical memory; that is typically sufficient.

Corrupted file system

Why wrong: Incorrect. File system corruption would show event IDs like 55 or 26, not a controller error.

Loose data cable

Why wrong: Incorrect. While loose cables can cause errors, event ID 11 typically points to a controller-level issue rather than a cable connection.

Failed hard disk drive

Why wrong: Incorrect. A disk failure usually generates different event IDs (e.g., 7, 50), and the error points to the controller.

The memory module is not seated properly

Why wrong: While improper seating can cause errors, the beep code for a memory error often points to incompatibility first; seating issues usually cause no beep or a different code.

The BIOS is not updated to support the new memory

Why wrong: BIOS updates are rarely required for standard memory; this is a less common cause of POST memory errors.

The memory is installed in the wrong slot

Why wrong: Most server motherboards support single-module configurations, so slot order rarely prevents boot. The beep code would be different if it were slot-related.

The server is drawing too much power

Why wrong: Overload would cause a system crash or shutdown, but the power supply LED would likely remain green until failure.

The power cord is unplugged

Why wrong: An unplugged cord results in no LED; an amber LED means the supply is powered but has an internal fault.

The server is overheating

Why wrong: Overheating typically triggers a system shutdown with both power supplies still operational; the amber LED is a specific power supply fault indicator.

The hard drive data cable is loose

Why wrong: A loose cable would often result in the drive not being detected at all, not just a boot error. The error specifically mentions hard disk (3F0), suggesting it is detected.

The boot sector is corrupted

Why wrong: A corrupt boot sector typically produces an error like 'Missing operating system' rather than 'Boot device not found'.

The hard drive has failed

Why wrong: A failed drive would typically not be listed as 'Hard Disk: (3F0)'; that identifier suggests the drive is recognized but not bootable.

Replace the CMOS battery

Why wrong: A dead CMOS battery affects BIOS settings and time, but does not prevent the system from POSTing and booting.

Flash the BIOS firmware

Why wrong: BIOS corruption is rare and typically shows symptoms like boot loops or incorrect hardware detection; it is not the primary suspect after reseating components.

Replace the power supply

Why wrong: A failing power supply typically causes random shutdowns or failure to power on, not a complete lack of POST with fans spinning.

Incorrect DNS server configuration

Why wrong: DNS is for name resolution; ping uses IP addresses, so DNS misconfiguration does not affect direct ping to gateway.

Incorrect subnet mask

Why wrong: An incorrect subnet mask would likely cause the server to calculate the wrong network address, potentially making it think the gateway is on a different subnet, but self-ping would still work. However, this is less common than physical issues after a move.

Duplicate IP address on the network

Why wrong: A duplicate IP address typically causes intermittent connectivity and an error message from the OS, not a consistent inability to ping the gateway.

Move the server to a cooler location in the data center

Why wrong: The ambient temperature is within acceptable range, so moving the server would not significantly improve cooling.

Reinstall the CPU heat sink with more thermal paste

Why wrong: The thermal paste has already been replaced; adding more or reapplying is unlikely to resolve the issue.

Replace the power supply unit

Why wrong: The PSU fan is integrated, but the logs point to CPU temperature, not power supply failure. Replacing PSU would not address the root cause.

Failed CPU

Why wrong: A failed CPU would prevent the system from completing POST, so the error would not appear.

Incorrect memory timings

Why wrong: Memory timing issues usually cause POST beep codes or instability, not an 'OS not found' error.

Overheating

Why wrong: Thermal issues typically cause shutdowns during POST or early boot stages, not a clean 'OS not found' message.