Drive & RAID Issues pt.1

CompTIA A+ Core 1 (220-1201) Objective 5.2 focuses on hardware and system symptoms that show up in real support tickets. On the exam, you often win points by spotting the symptom first, then choosing the best next step (not the most advanced fix). That pattern matters because many issues share the same surface signs.

This post helps you recognize drive and RAID issues early, such as slow reads, missing volumes, or failed arrays, and connect them to likely causes. It also covers overheating warnings, a burning smell, and random shutdowns, which often point to airflow, fan, or power problems that need fast action.

You'll also review application crashes and unusual noise, since both can signal failing storage, unstable memory, or a stressed power supply. Finally, we'll address swollen capacitors and inaccurate system date/time, including what each symptom suggests and what to check first so you don't waste time or risk more damage.

Start with a safe, repeatable troubleshooting routine (before you touch anything)

Hardware symptoms can feel random, yet a consistent routine keeps you calm and accurate. First, protect data and prevent damage. Then, gather facts before swapping parts. This matters on the CompTIA A+ 220-1201 exam because many answer choices look reasonable, but only one reflects the best next step.

A good baseline flow is simple: observe the symptom, record what changed, confirm whether the issue happens before Windows loads, and only then test one variable at a time. Treat the system like a crime scene. If you start moving "evidence" too early, you lose the story of what failed first.

If you can't explain what you changed, you can't trust the result. Change one thing, then re-test.

Quick triage questions that narrow the cause fast

Before you open the case, ask a short set of questions and write the answers down. These questions quickly separate power, heat, storage, and firmware problems.

When did it start, and how often does it happen? If failures cluster after long uptime, heat or memory issues rise on the list. If it fails instantly, suspect power, shorting, or firmware settings.
What changed right before it started (update, new drive, RAM, move, cleaning)? A BIOS update can trigger boot problems. A moved desktop can loosen a SATA cable. A new drive can expose a weak PSU under load.
Does it happen under load, like gaming, backups, or stress tests? Load-related shutdowns often point to overheating, a failing fan, or unstable power delivery.
Does it happen in BIOS/UEFI, or only inside Windows? If it freezes in BIOS, Windows drivers are not the cause. That pattern points to hardware, thermal problems, or firmware instability.
Is data missing, are drives "gone", or is a RAID degraded? Missing volumes suggest cable, port, controller, or RAID metadata issues. A degraded array suggests a member drive fault or a controller reporting errors.
Do you hear beep codes, see diagnostic LEDs, or get SMART warnings? Beeps and board LEDs can indicate CPU, RAM, or GPU faults. SMART alerts point toward a failing drive.
Was there a recent power outage or surge? After outages, you may see corrupted files, RAID rebuilds, BIOS time resets, or damaged PSUs and surge protectors.

A fast way to interpret answers is to think in layers. Power and heat often create sudden shutdowns and resets. Storage faults often create slow boots, missing files, and crashes during reads or writes. Firmware issues often show up before the OS loads, along with time and boot-order problems.

Safety first when you notice heat, a burning smell, or swelling parts

When you notice strong heat, a burning smell, repeated shutdowns, or bulging capacitors, stop troubleshooting like it's a normal ticket. At that point, your priority shifts to safety and preventing more damage.

Start with immediate actions:

Shut down the system (don't keep "testing" while it smells hot).
Disconnect power from the wall and from the device (remove laptop AC and battery if it's removable).
Let it cool before you touch internal parts. Hot VRMs, GPUs, and heatsinks can burn skin.
Don't open a power supply. PSUs hold charge, even when unplugged.
Don't sniff closely to "confirm" the smell. If something burned, treat it as a hazard.
Inspect connectors and plastics for melting, discoloration, or warped shapes. Check the 24-pin ATX plug, PCIe GPU power plugs, SATA power, and fan headers.
Use a known-good outlet or UPS before further tests. A failing outlet or cheap power strip can cause repeat faults.

Fire risk is real because failing components can arc, overheat, and damage nearby parts. Continued use can also destroy drives and boards because heat speeds up wear, while unstable power corrupts writes and stresses controllers. In other words, one ignored smell can become a dead motherboard, a dead SSD, and a lost RAID set.

Heat and unstable power don't just "crash" systems, they can corrupt data mid-write and turn a small fault into a full failure.

Tools and built-in checks you should know for the exam

Once the system is safe to test, use tools that confirm or rule out common causes. On the exam, you often choose a tool based on what it can reveal, not because it is the most advanced option.

Here are core checks worth knowing:

SMART status (drive health): Shows indicators like reallocated sectors and wear level. A bad SMART report supports drive replacement planning.
Vendor SSD tools: Report firmware versions, health, temperature, and sometimes run diagnostics. They also help confirm if a firmware update applies.
Disk Management (Windows): Confirms whether Windows sees the disk, its partitions, and file system state. It helps spot offline disks, missing volumes, or unallocated space.
Event Viewer: Finds disk, controller, and unexpected shutdown events. Look for disk timeouts, NTFS errors, and repeated storage warnings near crash times.
Reliability Monitor: Gives a timeline view of crashes, driver failures, and updates. It helps you correlate the first failure with a change.
Task Manager: Shows CPU, memory, disk, and GPU load. High disk active time with low throughput often hints at drive trouble.
Windows Memory Diagnostic: Screens for memory errors that can cause random app crashes and corrupted installs.
BIOS/UEFI hardware monitor: Confirms temperatures, fan speeds, and sometimes voltages. If temps spike in BIOS, you have a cooling issue independent of Windows.
Multimeter or PSU tester concepts: High level idea only. You use them to check whether rails and power-good signals look normal, which supports diagnosing random restarts and no-boot faults.

Used together, these checks create a trustworthy picture. You move from symptoms to evidence, then to the simplest corrective action that fits what you found.

Drive and RAID issues, the signs, the likely cause, and the best next step

Drive and RAID faults rarely start with a clean error message. More often, you see slow boots, missing volumes, random freezes during file access, or a RAID alert that appears after a restart. For the CompTIA A+ 220-1201 exam, the best answers usually focus on safe confirmation steps first, because the wrong action can turn a recoverable problem into data loss.

Treat storage problems like a weak bridge. You can still cross it for a moment, but every extra trip raises the risk. Your next step should protect data, confirm what the firmware and OS can see, and then decide whether you are dealing with cables, settings, a failing drive, or a RAID member that dropped out.

When a drive is missing, unallocated, or won't boot

Start by separating three similar symptoms, because they point to different causes. A drive can be physically missing (not detected), logically missing (seen but no volume), or present but not bootable (seen, yet the system won't start). Each case has a simple first check that saves time.

For a drive that is not detected, begin with the basics inside the case. Reseat the data cable and the power cable. Then try a different SATA port, because a single port can fail or get disabled. If you have a spare cable, swap it in, since bad SATA cables are common and cheap. On laptops, re-seat the M.2 drive and confirm the screw and standoff fit, because a loose M.2 can disconnect under heat.

Next, confirm detection in BIOS/UEFI. If firmware doesn't see the drive, the OS will not fix it. While you are there, check storage mode and related settings:

UEFI vs. Legacy/CSM: A system installed in UEFI mode often won't boot if you flip to legacy, and the reverse is also true.
Boot order and boot device: After updates or resets, firmware may try a USB device, a network boot, or the wrong drive.
Correct disk selection: On multi-drive systems, confirm the OS drive is still set as the primary boot choice.

If BIOS/UEFI sees the drive but Windows shows it as unallocated or the volume is missing, think in terms of partition and file system structures. A damaged partition table can make a disk look empty even when data still exists. Similarly, a corrupted boot record or boot configuration can stop booting while the drive remains readable. At a high level, those patterns suggest logical corruption, not an unplugged drive.

A practical exam mindset: first confirm the drive is detected in BIOS/UEFI, then verify the boot mode and boot order, and only then suspect partition or boot record damage.

How to read SMART warnings and other early failure clues

SMART (Self-Monitoring, Analysis, and Reporting Technology) is the drive's internal health reporting system. It tracks error counts and wear indicators that often rise before a full failure. SMART does not predict every failure, but it gives you evidence when a drive starts to degrade.

Some SMART attributes matter more than others in day-to-day support. The following are common red flags because they often correlate with real media damage or a drive that can't reliably read data:

Reallocated sectors (HDD): The drive moved bad sectors to spares. A growing count suggests the surface is failing.
Pending sectors (HDD): The drive struggles to read sectors and marks them for re-test. This can cause freezes and file corruption.
Wear level / percentage used (SSD): NAND flash has a limited write life. A high wear reading means the drive is closer to end-of-life.
Media and data integrity errors (SSD): Repeated internal errors can signal failing NAND or controller issues.
High CRC errors (often cable related): On SATA devices, CRC errors can point to a bad cable or noisy connection, not the drive itself. Still, repeated CRC errors are not normal and deserve action.

Besides SMART, watch for early behavior clues. Frequent file system checks, slow file copies that stop and resume, and repeated disk warnings in Event Viewer often appear before a drive fails completely. Another clue is heat. Drives that run hot for long periods tend to degrade faster, especially in small cases with poor airflow.

A simple rule keeps you safe and matches exam logic: if SMART warns, or if storage errors repeat, back up now and plan a replacement. Don't wait for a drive to "prove" it is dead. Also, remember that SSDs can fail with no sound at all. You may only see sudden read-only behavior, missing volumes, or boot failures.

Unusual drive noise and what it usually means

Noise matters most for traditional hard drives, because they have moving parts. When the sound changes, the mechanism often changed too. That does not guarantee failure, but it raises the odds enough that you should act carefully.

Here are common sounds and what they usually suggest:

Clicking or repeated ticking (HDD): Often called "click of death." The heads may fail to read servo data or return to position, which can happen with mechanical wear or surface damage.
Grinding or scraping (HDD): This can indicate physical contact or bearing problems. Treat it as urgent because continued use can destroy the platters.
A steady whir or gentle hum (HDD): Often normal spindle noise, especially during spin-up. However, a rising pitch over time can hint at bearing wear.
Beep, whine, or chirp (sometimes power related): Some drives and enclosures emit tones during power problems. Coil whine from a PSU or GPU can also be mistaken for drive noise, so confirm the source by listening near the case panels and bays.

Noise becomes more meaningful when paired with performance symptoms. A new clicking sound plus slow boots, long application loads, or freezes during file access often points to imminent failure. In that situation, your priority is data protection, not diagnosis.

Avoid actions that increase wear or force repeated reads. Don't keep rebooting "to see if it comes back." Each boot can trigger more head movement and more retries. Also, don't run heavy surface scans if the data is at risk, since long tests can push a failing drive over the edge. Instead, back up what you can, then plan the next step based on what the system detects and what SMART reports.

RAID symptoms you must recognize, degraded arrays, failed rebuilds, and wrong disk order

RAID adds performance or uptime by combining disks into a set, but it also adds complexity. For troubleshooting, the key is to recognize whether the array is still working with reduced protection, or if it has failed.

In simple terms, degraded means the RAID set still runs, but it lost redundancy (for example, one disk in RAID 1, 5, or 10 dropped out). Failed means the array can't present the volume, so the system may not boot or the data may be inaccessible. On the exam, expect prompts like "RAID array is degraded," "rebuild started then failed," or "one disk shows as missing."

Common causes follow predictable patterns:

Single disk failure: Typical for RAID 1, RAID 5, and RAID 10. The array degrades, then needs a rebuild after replacement.
Multiple disk failures: Can push RAID 5 or RAID 10 into a failed state, depending on which disks fail and the RAID level.
Unplugged cable or loose backplane connection: A healthy disk can drop from the set if power or data disconnects.
Controller or firmware issues: A RAID controller can misreport drives, especially after updates or power events.
Battery-backed cache problems: A failed cache battery can force write cache changes, cause warnings, or risk data inconsistency after sudden power loss.

RAID reduces downtime, but RAID is not a backup. It does not protect against deletion, ransomware, file corruption, or fire. That idea appears often in CompTIA objectives because it guides safe decision-making.

First steps should be cautious and evidence-based. Check the RAID management tool or controller BIOS for alerts.