4 Diagnosing Storage Problems

Where storage problems can originate

Storage problems can originate in the storage device, its connection or controller, or the file system. Because their symptoms can overlap, use evidence to narrow down the cause and protect important data before attempting repairs.

Follow a safe diagnostic sequence

1. Protect the data first. If a drive makes unusual noises, disconnects, becomes very slow, or reports a critical health warning, back up data. If the drive seems to be failing, minimize use and seek recovery advice before running repairs. Repeated attempts to read a failing drive can make recovery harder.

2. Check basic conditions. Confirm that the drive has power and appears in the operating system’s disk utility or firmware settings. For an external drive, try a known-good cable, port, and power supply. Avoid disconnecting it while data is being written.

3. Record symptoms and timing. Note error messages, when the problem began, and any recent drops, power loss, updates, driver changes, or new storage hardware. Intermittent detection can point to a connection or controller problem as well as a failing device.

4. Check health and logs. Use the operating system’s health tools and, when available, the drive manufacturer’s diagnostic utility. Look for repeated I/O errors, resets, or unexpected removals in system logs.

5. Check the file system only after protecting data. File-system repair can change disk structures; it is not a substitute for a backup and does not prove the physical device is healthy.

Interpret symptoms as clues

Symptoms are clues, not conclusive diagnoses. Use them to choose further checks while considering that several different causes can produce similar signs.

• Drive is absent or appears and disappears: Possible causes include a loose or faulty cable, port, enclosure, power supply, controller, or drive. Try a known-good connection and check whether firmware or disk tools detect the drive consistently.

• Files or folders are missing, or the volume reports errors: Possible causes include file-system or partition damage, interrupted writes, bad sectors, or device trouble. Back up accessible files, run an appropriate file-system check, and review drive-health results.

• Slow reads, freezes, or repeated retries: Possible causes include a heavy workload, low free space, connection or controller issues, or failing media. Check disk activity and logs, test a different connection, and inspect health indicators.

• A volume appears unformatted or as RAW: Possible causes include file-system metadata damage, partition issues, or failed reads. Do not format it if the data matters; back up or seek recovery help, then investigate the device and partition state.

• Repairs work briefly, then errors return: An underlying device, connection, controller, power, driver, or firmware problem may remain. Treat recurring errors as a warning and check hardware and logs instead of repeatedly repairing the file system.

File-system corruption can result from interrupted software operations or unsuccessful reads and writes at the storage-device level.

Interpret drive-health indicators

Many drives report S.M.A.R.T. information. Depending on the drive and tool, this may include an overall health assessment or measures related to media errors, spare capacity, temperature, or remaining life. Interpret results in the context of the drive model and manufacturer’s guidance: a normal status does not guarantee that a drive will not fail, while a warning should be taken seriously.

Windows can show critical warnings and selected health information for supported NVMe drives under Settings > System > Storage > Disks & volumes > Properties. Examples include low spare capacity, degraded reliability, and read-only status. This Windows monitoring feature covers NVMe SSDs, not SATA SSDs or HDDs; use a suitable manufacturer tool or another supported diagnostic method for those devices.

Check and repair file-system errors

Unexpected shutdowns or device disconnections can leave file-system records inconsistent even when the storage hardware is sound. Conversely, file-system errors can indicate hardware or connection trouble, so a file-system check should be considered alongside other evidence.

On Windows, chkdsk checks a volume’s file-system structure. For example, chkdsk D: /scan scans an NTFS volume online. chkdsk D: /f attempts to fix logical errors and may require the volume to be locked or checked at restart. The /r option also searches for bad sectors and attempts to recover readable information; it can take a long time. Back up important data before repairs, and do not treat a successful repair as proof that drive hardware is healthy.

On macOS, Disk Utility’s First Aid checks and can repair certain formatting and directory-structure problems. It cannot detect or repair every disk problem. If it reports that a disk is about to fail, back up data and replace the disk rather than treating First Aid as a hardware fix.

Distinguish software from hardware clues

Evidence leans toward a software or file-system issue when the device is detected consistently, health checks report no warning, and a file-system scan finds errors that are repaired without recurring. Recent improper shutdowns, forced removal, or operating-system problems may also support this possibility.

Evidence leans toward a hardware, connection, or controller issue when the drive disappears intermittently, reports critical health warnings, produces repeated read/write errors, or errors return after file-system repair. Check connections and logs before concluding that the drive itself is faulty: storage resets or surprise removals can also result from a disrupted connection or storage subsystem. If possible, test with a known-good cable, port, enclosure, or compatible system. Persistent errors across different connections strengthen the case for device failure.

Rule of thumb: Repair file-system errors when data is protected and the device appears stable. Prioritize backup and replacement or professional recovery when health warnings or recurring hardware-level errors appear. File-system tools address logical structures; they cannot repair failing hardware.