When a PC feels slow, won't boot, or throws file system errors, storage is often the real culprit. For CompTIA A+ Core 2 (220-1202), Domain 1, Objective 1.5, you're expected to know the Windows disk management commands that support techs use to diagnose and correct these issues. That means working from the command line with tools that can confirm file system health, repair corruption, and prepare drives for use.
This article focuses on the commands most tied to the exam, mainly chkdsk, format, and diskpart. Along the way, you'll see safe habits and realistic examples, because disk work has a unique risk: one wrong target can erase the wrong data. If you build a careful routine now, you'll be faster on the exam and safer on the job.
Before you touch a disk, learn the basics that prevent data loss
A "disk," a "partition," and a "volume" sound similar, but they describe different layers. A disk is the physical drive (SSD or HDD) or a virtual drive. A partition is a defined chunk of that disk. A volume is what Windows mounts and shows with a drive letter, such as C: or D:. Often a volume maps to a partition, but Windows can present storage in more complex ways in some setups.
File systems sit on top of volumes. NTFS is the default for modern Windows system drives because it supports permissions, large files, and reliability features. FAT32 is older and widely compatible, but it has a 4 GB file-size limit and weaker security features. exFAT is common for removable storage because it supports large files and works well across platforms.
Before running any disk management command, use a short safety routine:
- Back up first if the data matters.
- Confirm the correct disk number and drive letter.
- Close apps that may lock files on the target volume.
- Run as admin when required, or commands may fail silently.
- Document what you changed (command, target, time, outcome).
Windows GUI tools (File Explorer, Disk Management) are fine for quick checks. Still, the exam expects comfort with command-line output, plus the discipline to verify targets before acting.
How to identify the right drive and avoid the wrong one
Drive letters feel stable, but they can shift when you add or remove USB devices. Disk numbers can also change across reboots or different ports. As a result, verify the target every time, even when you feel sure.
Start by checking in File Explorer for the drive letter, label, and capacity. Next, open Disk Management and match the same label and size to a disk and partition layout. Then compare those details against command output from tools like DiskPart (list disk, list volume). This cross-check takes seconds, yet it prevents the most common mistake in storage work: selecting the wrong device because two drives look similar.
Treat storage targets like medications in a hospital, check the label, check the dose (size), then confirm again before you act.
Common disk terms you will see in command output
Disk management tools use short status words that carry a lot of meaning. MBR and GPT describe partition styles. GPT is standard on modern UEFI systems and supports large drives and more partitions. MBR is older and often appears on legacy systems or older external media.
You'll also see operational states. Online means Windows can access the disk. Offline often appears after a policy change, a SAN-style signature conflict, or certain imaging tasks. Healthy is a good sign, while RAW usually means Windows can't interpret the file system. RAW does not automatically mean "empty," so don't format it if the user needs the data. Unallocated means no partition exists in that space. Finally, read-only can block writes and formats, which is common on some failing media or misconfigured devices.
The word active matters mainly for legacy BIOS boot with MBR. On modern UEFI systems, "active" is usually not part of normal boot repair, so don't set it unless you know the boot mode and the layout.
Run CHKDSK to find and fix file system errors
chkdsk (Check Disk) examines a volume's file system structure and, when asked, repairs logical issues. Support techs run it after sudden power loss, system crashes, repeated app hangs during file access, or when Windows reports "scan and repair drive." It also helps when a device is slow to read, because file system errors can force repeated retries.
At a high level, chkdsk answers two questions. First, "Is the file system consistent?" Second, "Are there bad sectors that Windows should avoid?" The tool can mark problem areas so the OS stops writing to them. It can also repair metadata problems, such as directory index errors. However, chkdsk can't fix a physically failing drive. If the disk keeps developing new bad sectors, replacement becomes the real fix.
A simple decision flow keeps you safe and efficient:
- Scan first when you're unsure, or when the user still needs quick access.
- Repair next if the scan reports errors.
- Schedule at reboot if you must check the system drive and Windows can't lock it.
When the target is C:, Windows often can't dismount it while running. In that case, chkdsk will offer to run on the next restart. Plan for downtime, because repairs can take a while, especially on large HDDs.
The CHKDSK switches you need for Core 2
For the exam, the key switches are /f and /r.