10.14 Mojave Espace disque impossible a récupérer

[Lima33]

Bonjour à tous
Je vous explique ma problématique. J'ai voulu supprimer bootcamp de ma machine, et pour cela j'ai supprimé le conteneur qui lui était dédié sur mon disque. Je souhaitais ensuite récupérer cet espace sur mon premier conteneur qui contient mac os.
J'ai bien réussi à supprimer le conteneur bootcamp mais impossible de récupérer l'espace libéré par cette suppression.
Voici l'état de mon disque :

macbook-pro-de-lilian:~ lilian$ diskutil list

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *251.0 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk1 181.5 GB disk0s2

3: Microsoft Reserved 134.2 MB disk0s3


/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +181.5 GB disk1

Physical Store disk0s2

1: APFS Volume Macintosh HD 162.3 GB disk1s1

2: APFS Volume Preboot 45.4 MB disk1s2

3: APFS Volume Recovery 510.5 MB disk1s3

4: APFS Volume VM 1.1 GB disk1s4

J'ai bien un disque de 251 GB, et un containeur de 181 GB et impossible de l'agrandir avec la commande

macbook-pro-de-lilian:~ lilian$ diskutil ap resizeContainer disk1 0b

Started APFS operation

Error: -69519: The target disk is too small for this operation, or a gap is required in your partition map which is missing or too small, which is often caused by an attempt to grow a partition beyond the beginning of another partition or beyond the end of partition map usable space

Merci d'avance pour votre aide

Lilian

 

[Membre supprimé 1060554]

Bonjour Lima

C'est cette petite partition -->

3: Microsoft Reserved 134.2 MB disk0s3

• de 134 Mo qui a une fonction de blocage de la récupération de l'espace libre. Car la partition BOOTCAMP devait se situer en-dessous (partition disk0s4) et l'espace libre qui l'a remplacée est donc séparé de la partition apfs disk0s2 par la petite partition que j'ai mentionnée. Même si cette partition ne porte pas de volume visible > elle est enregistrée dans la table de partition GPT comme une section de disque de type Microsoft Reserved. Il faut donc supprimer cette partition => pour débloquer la récupération de l'ensemble de l'espace libre.

Action ! - passe la commande (copier-coller) :

diskutil eraseVolume free null disk0s3 ; diskutil ap resizeContainer disk1 0b ; diskutil list

• la commande supprime la partition-tampon > récupère l'espace libre au Conteneur apfs > réaffiche le tableau des disques

Poste le retour intégral de la commande (au cas où il y aurait eu un blocage à un point de l'enchaînement).

 

[Lima33]

Merci beaucoup macomaniac la suppression de la partition disk0s3 a effectivement résolu le problème.

macbook-pro-de-lilian:~ lilian$ diskutil eraseVolume free null disk0s3 ; diskutil ap resizeContainer disk1 0b ; diskutil list

Started erase on disk0s3

Unmounting disk

Finished erase on disk0

Started APFS operation

Aligning grow delta to 69 295 583 232 bytes and targeting a new physical store size of 250 790 436 864 bytes

Determined the maximum size for the targeted physical store of this APFS Container to be 250 789 408 768 bytes

Resizing APFS Container designated by APFS Container Reference disk1

The specific APFS Physical Store being resized is disk0s2

Verifying storage system

Using live mode

Performing fsck_apfs -n -x -l -S /dev/disk0s2

Checking the container superblock

Checking the EFI jumpstart record

Checking the space manager

Checking the space manager free queue trees

Checking the object map

Checking volume

Checking the APFS volume superblock

The volume Macintosh HD was formatted by hfs_convert (748.21.6) and last modified by apfs_kext (945.275.7)

Checking the object map

Checking the snapshot metadata tree

Checking the snapshot metadata

Checking the extent ref tree

Checking the fsroot tree

Checking volume

Checking the APFS volume superblock

The volume Preboot was formatted by newfs_apfs (748.21.6) and last modified by apfs_kext (945.275.7)

Checking the object map

Checking the snapshot metadata tree

Checking the snapshot metadata

Checking the extent ref tree

Checking the fsroot tree

Checking volume

Checking the APFS volume superblock

The volume Recovery was formatted by newfs_apfs (748.21.6) and last modified by apfs_kext (945.275.7)

Checking the object map

Checking the snapshot metadata tree

Checking the snapshot metadata

Checking the extent ref tree

Checking the fsroot tree

Checking volume

Checking the APFS volume superblock

The volume VM was formatted by newfs_apfs (748.21.6) and last modified by apfs_kext (945.275.7)

Checking the object map

Checking the snapshot metadata tree

Checking the snapshot metadata

Checking the extent ref tree

Checking the fsroot tree

Verifying allocated space

warning: Overallocation Detected on Main device: (1+63) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (64+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (128+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (192+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (256+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (320+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (384+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (448+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (512+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (576+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (640+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (704+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (768+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (832+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (896+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (960+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1024+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1088+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1152+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1216+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1280+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1344+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1408+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1472+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1536+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1600+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1664+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1728+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1792+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1856+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1920+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (1984+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2048+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2112+38) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2198+10) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2215+4) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2220+4) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2227+2) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2231+2) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2234+6) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2243+2) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2268+2) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2273+1) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2276+28) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2304+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2368+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2432+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2496+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2560+64) bitmap address (11bd674)

warning: Overallocation Detected on Main device: (2624+64) bitmap address (11bd674)

too many warnings generated; suppressing subsequent ones

The volume /dev/disk0s2 appears to be OK

Storage system check exit code is 0

Growing APFS Physical Store disk0s2 from 181 494 853 632 to 250 790 436 864 bytes

Modifying partition map

Growing APFS data structures

Finished APFS operation

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *251.0 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk1 250.8 GB disk0s2


/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +250.8 GB disk1

Physical Store disk0s2

1: APFS Volume Macintosh HD 164.3 GB disk1s1

2: APFS Volume Preboot 45.4 MB disk1s2

3: APFS Volume Recovery 510.5 MB disk1s3



4: APFS Volume VM 1.1 GB disk1s4


Encore merci pour ton aide

Lima

 

[Membre supprimé 1060554]

Content pour toi !