Why does my NVMe partition still show its full size after shrinking it with GParted?

0
0
Asked By MellowPine42 On

I have a 1 TB NVMe SSD running Kubuntu 24.04 with an ext4 filesystem. I booted from a Ventoy USB containing GParted and resized the partition to about 512 GB, then applied the changes with the green checkmark. GParted reported no errors, but after rebooting, the system still shows the partition as roughly 931.5 GB. This is my first time partitioning an NVMe drive, so I'm wondering whether NVMe devices require anything different or whether I missed a filesystem-resize step.

3 Answers

Answered By QuietHarbor88 On

A partition and the filesystem inside it are separate things. Shrinking only the partition while leaving ext4 at its original size can make the filesystem think it still extends to the end of the disk. For ext4, the filesystem must be shrunk first, followed by the partition. GParted normally performs both operations when you use its resize function, provided the partition is unmounted and the operation completes successfully.

VioletCrane6 -

resize2fs is commonly used for ext4, but don’t run it blindly while the filesystem is mounted. Boot from the live USB, verify the correct NVMe partition, and let GParted handle the filesystem and partition resize if possible.

Answered By AmberTelescope5 On

Before doing anything destructive, verify what the system sees with lsblk -f and sudo fdisk -l. If the partition is about 512 GB but a file manager still reports about 931 GB, check whether you’re viewing the disk rather than the partition, or whether the filesystem still needs resizing. If the partition really is still full-sized, review GParted’s pending operations and its log to confirm the change was applied to the intended drive.

Answered By CopperSparrow7 On

NVMe does not require any special partitioning procedure. Linux exposes NVMe drives as ordinary block devices, so GParted handles them the same way as SATA, SCSI, and older IDE disks. Also, the device name would normally look like /dev/nvme0n1p1—not /dev/nvme01p01.

LunarQuilt3 -

Check the partition table from a terminal with lsblk or sudo fdisk -l. If the partition still ends near the end of the disk, the change was not actually committed or you may have selected the wrong device.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.