Parted is a command-line disk partitioning tool for creating, deleting, moving and resizing partitions on storage devices. It works with partition tables such as GPT and MBR, and can be used during disk setup or recovery to change layout before a filesystem is created or adjusted.
What Parted does and where it fits
Parted is a low-level disk partitioning utility, so its purpose is to define and reshape the storage layout before a filesystem or operating system uses the disk. It is typically used during installation, recovery, migration, or storage reconfiguration, where partition boundaries and partition-table correctness matter more than filesystem content.
Because it operates at the partition-table layer, Parted changes the structure that other tooling later depends on. A mistake here can affect bootability, data placement, and the ability of the system to recognise or mount volumes correctly.
Partition tables, layouts, and resize operations
Parted works with common partition-table schemes such as GPT and MBR. That means it can create partitions from unused space, remove stale entries, move boundaries, and resize partitions when the underlying storage design needs to change. The tool is useful when a system has outgrown an original layout or when a recovery workflow needs the disk structure rebuilt carefully.
The key concept is that partitioning is not the same as formatting. Parted defines where partitions begin and end; filesystems, volume managers, and operating systems then use that structure. A partition table that is valid but poorly planned can still create operational problems later, especially if boot partitions, encryption layers, or recovery partitions are positioned badly.
Why partitioning tools are sensitive operations
Partitioning utilities are powerful because they act directly on storage metadata. That makes them inherently consequential: the wrong device, offset, or resize decision can destroy data or make an installed system unbootable. Even when the intention is safe maintenance, the scope of change is broad because one partition table often underpins many higher-level services.
In practice, this is why partitioning is usually done with the system in a controlled state, with a clear inventory of attached disks and a strong check on which device is being modified. The risk is not only accidental deletion, but also partial changes that leave a layout inconsistent with the way the operating system expects to find it.
Using Parted in installation and recovery workflows
Parted is most valuable when a machine is being prepared, rebuilt, or repaired. In those cases it helps operators establish the storage foundation before a filesystem is created, restored, or expanded. That makes it part of the infrastructure setup path rather than an everyday end-user utility.
Because it is often used under time pressure during recovery, the main operational discipline is validation: confirm the target disk, confirm the intended partition map, and confirm that the resulting layout matches the boot and storage design the system requires. A clean partition table is only useful if the rest of the storage stack is ready to consume it correctly.
Risk and Threat Considerations
Partitioning mistakes can cause immediate availability loss, data loss, or a failed boot sequence, and those failures are especially disruptive on systems that host critical services or recovery images. The same capability that makes Parted useful for repair also makes it dangerous when used against the wrong disk or with an incorrect resize plan.
Failure mechanism: A partition-table change can overwrite the wrong storage metadata, invalidate expected offsets, or leave a disk layout inconsistent with the system's boot, encryption, or volume assumptions.
Impact: The result can be lost data, inaccessible volumes, a non-booting host, or a recovery process that cannot complete without additional repair work.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | CM-8 — System Component Inventory | Parted use depends on knowing exactly which disk is being changed. |
| CM-3 — Configuration Change Control | Partition edits are high-impact configuration changes to storage metadata. | |
| SI-2 — Flaw Remediation | Partition-table repair and rebuild workflows support restoring broken storage layouts. | |
| Recommendation — Maintain an accurate disk inventory before applying partition changes. Require approval and rollback planning before changing partition layouts. Validate repaired layouts promptly so damaged storage structures do not persist. | ||
| CIS Controls v8 | CIS-11 — Data Recovery | Parted is often used in recovery scenarios where restoring storage structure matters. |
| CIS-4 — Secure Configuration of Enterprise Assets and Software | Partition layouts are part of secure and reliable system configuration. | |
| Recommendation — Use recovery procedures that preserve and verify the intended partition structure. Standardize approved disk layouts and verify them during build and rebuild. | ||
Practitioner Guidance
Why practitioners should care: Treat Parted as a change-control tool, not just a convenience utility. Its output affects every later storage-layer operation, so the operator needs to reason about the whole disk layout, not only the partition being edited.
What to watch for: Confirm device identity before every destructive action, and validate the final table after any resize or move. Where possible, pair the partitioning step with a documented storage plan so that boot, data, and recovery partitions remain aligned with operational intent.
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 3, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org