M26 - Disk Management: CLI
Disk Management: CLI
Inspect storage devices and mount points from the command line, and understand which commands are observational versus potentially destructive.
- Inspect disks, volumes, and mount points from the CLI.
- Recognize the difference between read-only inspection commands and change-making commands.
- Understand why formatting and repair tools deserve extra caution.
Why This Matters
The CLI is often the clearest place to inspect storage on remote systems or servers without a desktop environment.
But storage commands vary widely in risk. Some merely show information. Others can destroy data or alter the filesystem state.
1. Start With Inspection Commands
Get-Disk Get-Volume
lsblk df -h mount
These commands help you answer:
- what devices are present
- what filesystems are mounted
- where they are mounted
- how full they are
2. Treat Change-Making Commands Differently
Some commands go beyond inspection.
Examples include:
- partition editors
- formatting commands
- filesystem repair tools
- commands that alter mount configuration
Storage Caution Rule
If the command can repartition, format, or repair a filesystem, do not run it until you know exactly which device you are targeting and why.
3. Why the CLI Still Matters
The CLI is useful because it gives precise names and states that GUIs may hide or simplify.
That precision matters when:
- you are on a server
- you are documenting storage state
- you need an exact mounted filesystem or device name
What to Ignore for Now
- advanced SMART diagnostics
- complex partition-table editing
- destructive repair workflows
The goal here is to build inspection discipline first.
Before You Move On
You are ready for the storage lab when you can:
- inspect storage from the CLI
- distinguish safe observation from risky modification
- explain why exact device targeting matters
Next, we use a safer external-drive style scenario to practice the storage workflow.