F5F Stay Refreshed Software Operating Systems MacOS: Unable to assign additional free space to the primary drive.

MacOS: Unable to assign additional free space to the primary drive.

MacOS: Unable to assign additional free space to the primary drive.

Pages (2): 1 2 Next
H
HotMilkTea
Member
204
05-31-2016, 09:20 PM
#1
I have a Boot Camp section that I wanted to reduce in size, giving more room inside my main macOS installation. I went through this guide, but the final part is giving me trouble. After using the MiniTool Partition Wizard to shrink it, the available space shows up in Disk Utility. Then I ran these commands: df -h diskutil apfs list sudo diskutil apfs resizeContainer disk0s2 0. But when I tried the command “sudo diskutil apfs resizeContainer disk0s2 0”, the Terminal returned this message:

"Started APFS operation Aligning grow delta to 79.263.285.248 bytes and targeting a new physical store size of 429.316.349.952 bytes Determined the maximum size for the targeted physical store of this APFS Container to be 429.316.349.952 bytes Resizing APFS Container designated by APFS Container Reference disk1"

That’s what I see now.
H
HotMilkTea
05-31-2016, 09:20 PM #1

I have a Boot Camp section that I wanted to reduce in size, giving more room inside my main macOS installation. I went through this guide, but the final part is giving me trouble. After using the MiniTool Partition Wizard to shrink it, the available space shows up in Disk Utility. Then I ran these commands: df -h diskutil apfs list sudo diskutil apfs resizeContainer disk0s2 0. But when I tried the command “sudo diskutil apfs resizeContainer disk0s2 0”, the Terminal returned this message:

"Started APFS operation Aligning grow delta to 79.263.285.248 bytes and targeting a new physical store size of 429.316.349.952 bytes Determined the maximum size for the targeted physical store of this APFS Container to be 429.316.349.952 bytes Resizing APFS Container designated by APFS Container Reference disk1"

That’s what I see now.

D
DragonHeart_
Junior Member
7
05-31-2016, 09:53 PM
#2
It seems you need to perform maintenance on the .2 volume, which often requires disabling parts to reduce its size—though the changes won’t be huge. If this involves a mechanical HDD, I’d note that recurring errors could indicate issues, and the drive might be showing signs of wear.
D
DragonHeart_
05-31-2016, 09:53 PM #2

It seems you need to perform maintenance on the .2 volume, which often requires disabling parts to reduce its size—though the changes won’t be huge. If this involves a mechanical HDD, I’d note that recurring errors could indicate issues, and the drive might be showing signs of wear.

M
metalstone28
Member
98
06-01-2016, 03:34 PM
#3
Hi, sorry about the situation. It seems the disk might not be functioning properly. Maybe TimeMachine was active and affected the diskutil process... In any case, I recommend backing up all your files and installing a fresh version of macOS from the official OSX base or recovery options. The steps for these depend on whether you're using an Intel or Apple Silicon chip. Once installed, you can use the disk utility to handle disks and partitions.
M
metalstone28
06-01-2016, 03:34 PM #3

Hi, sorry about the situation. It seems the disk might not be functioning properly. Maybe TimeMachine was active and affected the diskutil process... In any case, I recommend backing up all your files and installing a fresh version of macOS from the official OSX base or recovery options. The steps for these depend on whether you're using an Intel or Apple Silicon chip. Once installed, you can use the disk utility to handle disks and partitions.

I
iiCatherineii
Member
159
06-08-2016, 03:01 AM
#4
Thanks for the helpful suggestions. The device is an Intel 16 MBPCM from 2019 with a 500GB SSD. It seems the problem might be related to the free space created by MiniTool Partition. Since SSDs don’t need defragmentation, trying to boot into Windows and defragment the unused space could help. I’d like to avoid reinstalling or erasing anything. Any other ideas?
I
iiCatherineii
06-08-2016, 03:01 AM #4

Thanks for the helpful suggestions. The device is an Intel 16 MBPCM from 2019 with a 500GB SSD. It seems the problem might be related to the free space created by MiniTool Partition. Since SSDs don’t need defragmentation, trying to boot into Windows and defragment the unused space could help. I’d like to avoid reinstalling or erasing anything. Any other ideas?

F
Frontline107
Junior Member
17
06-08-2016, 05:28 AM
#5
Store crucial documents on a separate external storage device. Turn off the time machine feature, remove any saved backups from the time machine, and run the diskutil utility again. Should the process encounter failure and cause file system damage, reinstall the operating system.
F
Frontline107
06-08-2016, 05:28 AM #5

Store crucial documents on a separate external storage device. Turn off the time machine feature, remove any saved backups from the time machine, and run the diskutil utility again. Should the process encounter failure and cause file system damage, reinstall the operating system.

_
_HardGamer_
Member
181
06-08-2016, 09:14 AM
#6
Choose your Macintosh HD drive and run a "SOS" to verify the filesystem. It detected an error and will stop until resolved.
_
_HardGamer_
06-08-2016, 09:14 AM #6

Choose your Macintosh HD drive and run a "SOS" to verify the filesystem. It detected an error and will stop until resolved.

C
Creeperman3
Senior Member
454
06-10-2016, 08:56 AM
#7
C
Creeperman3
06-10-2016, 08:56 AM #7

H
HetYoshiTeam
Member
164
06-12-2016, 06:30 AM
#8
APFS has been around for about four years, making it relatively recent compared to older file systems.
H
HetYoshiTeam
06-12-2016, 06:30 AM #8

APFS has been around for about four years, making it relatively recent compared to older file systems.

K
Koollojoe
Posting Freak
830
06-12-2016, 12:15 PM
#9
Really? I was under the impression it was significantly older than I remembered. My recollection about it being initially created for something else might be incorrect too. It seems the problem could stem from adapting an earlier version meant for a different function. I felt there was a lot of “why” surrounding APFS, and it mostly came down to “well, we got it.”
K
Koollojoe
06-12-2016, 12:15 PM #9

Really? I was under the impression it was significantly older than I remembered. My recollection about it being initially created for something else might be incorrect too. It seems the problem could stem from adapting an earlier version meant for a different function. I felt there was a lot of “why” surrounding APFS, and it mostly came down to “well, we got it.”

O
Okunino
Posting Freak
845
07-02-2016, 07:48 PM
#10
It could refer to HFS+ and APFS being tailored for SSD performance
O
Okunino
07-02-2016, 07:48 PM #10

It could refer to HFS+ and APFS being tailored for SSD performance

Pages (2): 1 2 Next