How to Troubleshoot Storage Drives and RAID Arrays for CompTIA A+ Core 1 (220-1101)

1. Why Storage Troubleshooting Matters on the A+ Exam

Storage issues are one of those classic A+ gotchas because you’ve gotta sort out hardware failure, firmware settings, Windows visibility quirks, and the whole data-risk side of the job. For Core 1 (220-1101), you’re mainly working with the storage hardware itself, the ports and interfaces it plugs into, the basics of BIOS or UEFI, and those foundational RAID concepts. That’s the lane you want to stay in. And yeah, some of the Windows tools spill over a little into Core 2, but the exam still wants the safest practical next step. It’s not looking for the most clever move in the room.

The big habit to build is actually pretty simple: protect the data first, then worry about convenience. On A+, the right answer is usually the least destructive option that still gets the job done, not the fastest or most aggressive move you could make.

2. Storage Devices, Interfaces, and What Actually Works Together

You’ll troubleshoot a whole lot faster when you know exactly what storage you’re looking at — the device type, the connector, the protocol, and how the controller handles it.

Legacy awareness still matters. PATA/IDE and parallel SCSI are older technologies you may see in exam questions. In bigger environments, you’ll hear more about SAS, which grew out of SCSI command sets, and eSATA, which is basically an older external SATA-style connector. You don’t need to be an enterprise storage wizard for A+, but you absolutely should recognize the names and know the basic job each one does.

M.2 compatibility is a frequent trap. An M.2 slot might support SATA, NVMe, or both, so don’t assume a drive is compatible just because it slides into the slot. That’s one of those little details that catches people out all the time. Keying matters too — B-key, M-key, and B+M-key help tell you what’ll physically fit and what’s actually compatible. And yeah, check the motherboard manual, because some M.2 slots share lanes with SATA ports or PCIe slots. That’s one of those annoying gotchas that shows up in the real world and makes your day a little worse. Using one slot can disable a SATA port or reduce PCIe bandwidth somewhere else, so it’s absolutely worth confirming before you start swapping parts around.

With NVMe, make sure the system can actually boot from it if that drive’s supposed to hold the operating system. Honestly, people overlook that part more often than you’d think. Older boards may still detect the drive as storage but won’t boot from it unless the firmware supports that boot path or gets updated. In smaller systems, some NVMe drives may need a heatsink or just better airflow, otherwise they can throttle when they heat up.

3. Core Concepts That Affect Diagnosis

When a user says, “it’s slow,” I immediately start thinking about throughput, latency, and IOPS. HDDs usually get hit hardest on latency because, well, there are moving parts in there doing mechanical work. SSDs respond faster, and NVMe SSDs can usually handle more operations at the same time than SATA drives. That’s a big reason they feel so much quicker in day-to-day use.

Fragmentation mostly affects HDDs, since the moving parts make scattered data more of a headache. Modern operating systems usually recognize SSDs and use optimization methods like TRIM instead of old-school full defragmentation. TRIM lets the OS tell the SSD which blocks aren’t being used anymore. TRIM support depends on the OS, the file system, the controller path, and whether the storage stack passes TRIM or UNMAP correctly — and some RAID or controller setups can limit that passthrough.

Bad sectors on HDDs and bad blocks or worn cells on SSDs aren’t the same failure pattern, but both can absolutely cause read/write errors and file corruption symptoms. SMART is useful for early warning, but it’s not magic and it’s definitely not perfect. A drive can fail without clear SMART warning, and a SMART “passed” result does not guarantee the drive is healthy. Always correlate SMART with symptoms, Event Viewer logs, and diagnostics.

Boot Mode, Partition Style, and File Systems

Partition style and file system are different layers. MBR and GPT are the ways the disk’s partition layout is defined. NTFS, FAT32, and exFAT are the file systems that tell the OS how data is organized inside a partition.

• GPT: modern partition style, supports large disks and is generally required for native UEFI Windows boot
• MBR: older partition style, commonly associated with legacy BIOS/CSM boot
• NTFS: standard Windows file system with permissions and large-file support
• FAT32: broad compatibility but a 4 GB maximum file size
• exFAT: common on removable media for large files and cross-platform use

If the firmware boot mode and partition style don’t match up, the system can fail to boot even when the disk itself is perfectly fine. A BIOS reset can cause that mess by changing UEFI or Legacy settings, Secure Boot behavior, or the controller mode. On boot drives, don’t forget about the EFI System Partition. If that piece is missing or damaged, you can still get a “No boot device” error even though the main Windows partition is sitting there just fine.

Use this mental chain: physical disk → controller/interface → BIOS/UEFI → OS/driver → partition style → file system → volume/drive letter. A break anywhere in that chain can make a drive appear missing.

4. BIOS/UEFI Storage Checklist

Before blaming Windows, verify firmware.

• First, make sure the drive actually shows up in BIOS or UEFI. If it doesn’t show there, don’t race straight into Windows troubleshooting yet.
• Then check the boot order and make sure the intended boot disk is sitting at the top where it should be.
• After that, verify the controller mode — AHCI, RAID, or any vendor-specific mode like Intel RST or VMD. That setting matters more than a lot of people realize.
• And don’t skip the UEFI versus Legacy or CSM boot mode check.
• Review Secure Boot changes after resets or firmware updates
• Confirm onboard storage controllers and M.2 slots are enabled
• Check for lane-sharing notes that disable SATA ports when M.2 is populated
• If needed, review whether a BIOS update adds NVMe compatibility or boot support

AHCI versus RAID matters because Windows loads different storage drivers depending on how the controller presents the disk. Change that presentation, and Windows may react badly. If a system was installed in AHCI and then the firmware gets switched to RAID or RST/VMD mode, Windows can blue-screen, refuse to boot, or act like the drive vanished because the right controller driver isn’t in the boot path anymore.

5. Disk States in Windows and the Safest Next Step

A drive can show up in Device Manager but not Disk Management if the controller and driver are fine, but the disk itself isn’t being exposed the way it should be. The reverse can happen too: the disk is visible at a low level, but File Explorer can’t mount it because of partition or file system problems.

6. Practical Windows Tool Workflows

Disk Management is your first Windows stop for offline disks, unallocated space, RAW partitions, and missing drive letters. Use it to inspect the situation before you touch anything.

diskpart is powerful and dangerous. Safe inspection commands include:

• diskpart
• list disk
• select disk X
• detail disk
• list volume
• attributes disk

Low-risk actions, only after positive identification, may include online disk or assign. Avoid destructive commands such as clean, convert, create partition, and format unless you are completely sure of disk identity and data status.

CHKDSK is for logical file-system repair, not hardware repair. chkdsk /f fixes file-system errors. chkdsk /r locates bad sectors and implies /f, but it is more intensive. On unstable or failing drives, CHKDSK can put extra stress on the disk and change metadata, so if the data matters, back it up or image it first. Seriously, slow down and think it through.

TRIM check: fsutil behavior query DisableDeleteNotify. A result of 0 means TRIM notifications are enabled; 1 means disabled. Even if enabled in Windows, controller or RAID passthrough still matters.

7. Diagnostics and Evidence Gathering

Use multiple sources of evidence.

• SMART/health tools: useful for warning signs, but not definitive
• Vendor-specific manufacturer diagnostics: short tests for quick health checks, extended tests for deeper media checks
• Trusted third-party SMART/health tools: useful for attribute visibility and trend checking
• Event Viewer: helps distinguish media, controller, and file-system problems

In Event Viewer, check Windows Logs > System and look for sources such as Disk, Ntfs, storahci, stornvme, or vendor controller drivers such as iaStor. Practical examples include disk timeout or reset events, NTFS corruption warnings, controller communication errors, and bad-block messages. Those clues help you figure out whether you’re dealing with a cable or controller path problem, or a drive that’s actually failing.

If SMART warns you but the drive still works, treat it seriously. Verify the warning, back it up right away, reduce unnecessary writes, run the right diagnostics, and start planning the replacement. And no, don’t treat a SMART warning like a polite recommendation.

8. Standalone Storage Troubleshooting Scenarios — the stuff you’ll actually see on calls and tickets

For a new SATA or NVMe drive, I like a repeatable check: confirm the physical install, verify power or slot seating, confirm motherboard support, check BIOS detection, and then inspect Disk Management. If it is a new blank disk, initialize and partition only after positive identification.

9. External and Removable Storage

External drives add more places for things to go wrong — the USB port, the cable, the enclosure, the bridge chip, and the power source. There’s usually a little more going on there than people think. If an external HDD clicks or keeps disconnecting, the problem might actually be the enclosure or a power issue over USB instead of the disk itself.

Check these in order, nice and methodically:

• Start with a known-good cable and try a different USB port.
• Use a powered hub or the correct power adapter if the device needs one.
• Check Device Manager for USB/storage detection
• Check Disk Management for offline, RAW, or no-letter states
• Think about file system compatibility if the drive moves between Windows, macOS, and Linux. Honestly, that can be the entire problem right there.

A common exam trap is a USB drive that shows up in Device Manager but never appears in File Explorer. The safest next step is usually Disk Management, not formatting.

10. RAID Basics and Safe RAID Troubleshooting — where one bad move can get expensive

RAID improves availability, performance, or both, but RAID is not backup.

Manage RAID in the correct layer: hardware RAID utility, firmware RAID utility, or OS software RAID tool, depending on implementation. Some consumer “RAID” solutions are firmware-assisted, not true dedicated hardware RAID.

If an array is degraded, it is still functioning but has lost redundancy. If it is failed, stop and protect data. For replacement, use a disk with the same interface/protocol and equal or larger usable capacity, and make sure it meets controller requirements. In enterprise systems, firmware qualification or sector-format compatibility may matter.

A safe RAID workflow looks like this: confirm the backup, identify the failed member by bay or slot and serial number if you can, verify hot-swap support, replace only the failed disk, watch the rebuild, and then confirm the array is healthy afterward. Keep an eye out for foreign configuration or import prompts, and don’t accept them casually unless you really understand the controller state. That’s one of those prompts that deserves a pause.

If a RAID 5 rebuild fails, or a second disk starts throwing errors during the rebuild, that’s a strong sign you should escalate. Rebuilds are hard on the array, and a shaky second disk can turn a degraded setup into a failed one pretty quickly.

11. Security and Data Protection Awareness — because storage problems aren’t always just storage problems

If a volume is encrypted with BitLocker or device encryption, the drive can be perfectly healthy and still be inaccessible without the recovery key. Healthy hardware doesn’t always mean accessible data. Before you replace hardware or start changing motherboard or firmware settings, check the encryption status first. It’s a small step that can save you a lot of grief.

Also remember:

• Formatting does not securely erase data
• Secure erase and sanitization are different from normal formatting
• Failed drives containing sensitive data may require documented handling or disposal procedures

On real support calls, chain-of-custody and escalation matter when the data is regulated or highly sensitive.

12. When to Stop and Escalate

Stop and protect data first if you see any of these:

• Clicking or grinding HDD
• SMART failure with important data still present
• Former data disk now showing unallocated or RAW
• RAID degraded with uncertainty about the failed member
• RAID rebuild failure or multiple member errors
• Suspected controller failure
• Sensitive or encrypted data that you’re not authorized to handle

CompTIA’s troubleshooting process still applies here: identify the problem, establish a theory of probable cause, test that theory, build and carry out a plan, verify full functionality and preventive measures, and document what you found and what you did. In storage scenarios, “if necessary, escalate” belongs in your thinking any time the next action could cause data loss.

13. Exam Prep: Best-Next-Step Thinking

Memorize these distinctions:

• Detected in BIOS/UEFI ≠ usable in Windows
• Visible in Windows ≠ visible in File Explorer
• Offline ≠ undetected
• Unallocated ≠ failed
• Degraded RAID ≠ failed RAID
• M.2 ≠ NVMe
• UEFI/GPT and Legacy BIOS/MBR are common boot pairings

Quick exam rule: choose the least destructive correct action first. Formatting, initializing, converting, rebuilding, and reinstalling are rarely the first best answer unless the scenario clearly says the disk is new, blank, or data is already protected.

Mini-question 1: BIOS sees a disk, but File Explorer does not. What first? Check Disk Management. Why not format? Because the disk may only be offline, unallocated, RAW, or missing a drive letter.

Mini-question 2: A RAID 1 array is degraded. What first? Verify backup and identify the failed member in the RAID utility. Why not pull a drive immediately? Because removing the wrong disk can fail the array.

Mini-question 3: A PC shows “No boot device” after a BIOS reset. What first? Check boot order, UEFI/Legacy mode, Secure Boot state, and AHCI/RAID mode. Why not replace the SSD immediately? Because the disk may be healthy and only presented differently.

Mini-question 4: A USB drive appears in Device Manager but not File Explorer. What first? Check Disk Management for a missing letter, RAW state, or offline status. Why not assume the port is bad? Because enumeration already occurred.

14. Final Takeaways

For A+ storage questions, think in order: Physical → Firmware → OS → Volume. Use BIOS/UEFI to confirm detection and boot settings, Disk Management to inspect state, Device Manager for controller issues, SMART and diagnostics for health, Event Viewer for evidence, and RAID utilities for arrays. If the symptoms point to possible data loss, slow down. The safest correct answer is usually the right one on the exam and in the field.