Partition: Gpart Resize

He couldn't just move files. He had to move the walls.

There it was: the problem. A tiny, choked block of dark grey representing the root directory ( /dev/nvme0n1p2 ), followed immediately by a massive, empty block of teal representing his /home directory ( /dev/nvme0n1p3 ). gpart resize partition

Elias leaned back in his chair, watching the system monitor graph flatline into a healthy, low-usage rhythm. He had resized the unresizable. He had edited the map, not the territory. He couldn't just move files

The window changed. A progress bar appeared. A tiny, choked block of dark grey representing

"It’s time," Elias whispered to the silent room. He reached for his bootable USB drive—the digital equivalent of a sterile operating room.

For months, Elias had lived in the "Red Zone." His root partition, a measly 100GB slice he’d allocated years ago when he thought 50GB was infinite, was choking. Log files gasped for space. Docker containers refused to spin up. Downloads aborted mid-stream. Meanwhile, sitting right next to it on the physical drive, the /home partition lounged in opulent luxury, empty and vast, consuming terabytes of potential space.

The room was silent, save for the whir of the cooling fans. One hour passed. Then two. The progress bar sat at 45%. Don't crash, Elias thought. Don't flicker.