PC Master Race

14925 readers

1 users here now

A community for PC Master Race.

Rules:

No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
Be respectful. Everyone should feel welcome here.
No NSFW content.
No Ads / Spamming.
Be thoughtful and helpful: even with ‘stupid’ questions. The world won’t be made better or worse by snarky comments schooling naive newcomers on Lemmy.

Notes:

PCMR Community Name - Our Response and the Survey

founded 1 year ago

MODERATORS

[email protected]

How to increase available shrink space? Advice needed (lemmy.world)

submitted 9 months ago by [email protected] to c/[email protected]

17 comments fedilink hide all child comments

There seems to be plenty of free space on the SSD but there are unmovable files. So I deleted pagefiles etc, which increased available shrink space from 34000ish MB to 79000ish MB before it somehow decreased back to 58459 MB. GParted Live on USB (with laptop safe boot option disabled) did not work, so I am wondering if there's a way to locate and delete the unmovable $DATA file in question. Besides, can y'all recommend some decent software that address this issue please? Thanks in advance :D

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

GParted and most Linux distros wont touch a hibernated Windows NTFS disk. Unfortunately by default Windows saves its kernel in hibernation files on shutdown to shave a few seconds off boot, this anti-fearure is called Fast Startup/Boot. When Windows hibernates it make gparted and other partitioning tools default to read only mode when mounting NTFS partition.

I believe you can run ntfsfix /dev/sda2 (replacing sda2 with the drive name, see fdisk -l for names of drives) to resolve this from a terminal in gparted and other OSes.

You can also try to disable Fast Startup.

For partitioning, EaseUS has a great partitioning tool (Windows only) that works well with Windows partitions, it fails with anything more advanced than Ext2.