CompTIA Server+ (SK0-005)TroubleshootingMedium

A server is experiencing extremely slow boot times and applications are taking an unusually long time to launch. The server administrator notices that the disk activity LED is constantly illuminated during these periods, even when no major data transfers are expected. Performance monitoring tools show very high disk I/O wait times. Which of the following is the MOST likely cause?

  1. AMemory (RAM) exhaustion causing excessive swapping.
  2. BGPU driver issues.
  3. CInsufficient network bandwidth.
  4. DOverloaded CPU.
Show answer & explanation

Correct answer: A. Memory (RAM) exhaustion causing excessive swapping.

High disk activity and I/O wait times, especially during slow boot and application launches, are classic symptoms of memory exhaustion. When a server runs out of physical RAM, it starts using a portion of the hard drive (swap space or page file) to temporarily store data that would normally reside in RAM. This process, known as swapping or paging, is significantly slower than accessing RAM, leading to severe performance bottlenecks.

Why the other options are wrong

  • B. GPU driver issues are relevant for graphics-intensive tasks, not generally for server boot times or overall disk I/O performance.
  • C. Network bandwidth issues would affect network-dependent operations, not typically local disk I/O wait times or boot speed.
  • D. An overloaded CPU would show high CPU utilization, not necessarily high disk I/O wait times unless it's bottlenecked by disk access due to swapping.

Memory Exhaustion & Swapping

When a system runs out of physical RAM and resorts to using a portion of the hard drive (swap space) as virtual memory, leading to severe performance degradation.

  • Causes high disk I/O activity and long I/O wait times.
  • Results in significantly slower application launches and overall system responsiveness.
  • Indicates a need for more physical RAM or optimized memory usage.

Memory trick: Slow server, disk light glows, RAM's low, where swap space goes!

More Troubleshooting questions