Problèmes de partition de mon disque dur

jhe974

Nouveau membre
24 Décembre 2019
7
0
53
Bonsoir,
Je fais appel à vous pour m'aider à résoudre des problèmes avec mon disque dur. J'ai un MacBook Pro 15" de mi-2012 et je tourne sous OS CATALINA. J'ai voulu partitioner mon disque pour BOOTCAMP. Je l'ai fait avec diskutility ce qui ne faut pas faire. J'ai essayé avec le terminal de supprimer une partition de mon Mac de 150 go. Maintenant il n'apparaît plus nul part et mon disque dur de 750 go à la base ne me donne que 600 Go.

Ci-dessous le résultat des lignes de commandes de terminal :

Last login: Tue Dec 24 17:36:14 on ttys000
jhecs@MacBook-Pro-de-Johnny ~ % diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *750.2 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 448.0 GB disk0s2
3: Microsoft Basic Data BOOTCAMP 151.7 GB disk0s3

/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +448.0 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD - Données 11.8 GB disk1s1
2: APFS Volume Preboot 26.0 MB disk1s2
3: APFS Volume Recovery 525.4 MB disk1s3
4: APFS Volume VM 5.4 GB disk1s4
5: APFS Volume Macintosh HD 11.5 GB disk1s5

jhecs@MacBook-Pro-de-Johnny ~ % diskutil cs list
No CoreStorage logical volume groups found
jhecs@MacBook-Pro-de-Johnny ~ % df -H/
df: illegal option -- /
usage: df [-b | -H | -h | -k | -m | -g | -P] [-ailn] [-T type] [-t] [filesystem ...]
jhecs@MacBook-Pro-de-Johnny ~ % df -H /
Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
/dev/disk1s5 448G 12G 419G 3% 484011 4374525069 0% /
jhecs@MacBook-Pro-de-Johnny ~ %


De plus Time Machine me sauvegarde tous ces éléments alors que sur mon disque dur original j'ai Macintosh HD :
1577289601731.png



Merci de me dire s'il est encore possible de faire quelque chose pour arranger tout ça. Et tout fonctionne bien sur le mac

Merci à vous.
 

macomaniac

Ouroboros
Club MacG
20 Septembre 2012
77 092
23 712
Forêt de Fontainebleau
Bonjour jhe

Passe la commande (copier-coller) :
Bloc de code:
diskutil ap resizeContainer disk1 0b ; diskutil list internal

  • la commande récupère l'espace libre disponible au Conteneur apfs > puis affiche la configuration interne seule

Poste le retour intégral de la commande en copier-coller > en veillant à faire le coller dans une fenêtre de code (c'est plus lisible !) par le procédé suivant -->

- utilise le menu ...▾ (à droite de la bobine souriante) dans la barre de menus au-dessus du champ de saisie d'un message > sous-menu : </> Bloc de code => tu fais ton coller dans la fenêtre de code et Continuer.
 

jhe974

Nouveau membre
24 Décembre 2019
7
0
53
Bonsoir,

Ci-dessous le résultat :

Bloc de code:
Last login: Wed Dec 25 14:35:40 on ttys000
jhecs@MacBook-Pro-de-Johnny ~ % diskutil ap resizeContainer disk1 0b ; diskutil list internal
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
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *750.2 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         448.0 GB   disk0s2
   3:       Microsoft Basic Data BOOTCAMP                151.7 GB   disk0s3

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +448.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD - Données  234.9 GB   disk1s1
   2:                APFS Volume Preboot                 26.0 MB    disk1s2
   3:                APFS Volume Recovery                525.4 MB   disk1s3
   4:                APFS Volume VM                      5.4 GB     disk1s4
   5:                APFS Volume Macintosh HD            10.9 GB    disk1s5

jhecs@MacBook-Pro-de-Johnny ~ %

Merci pour la rapidité de la réponse.
 

macomaniac

Ouroboros
Club MacG
20 Septembre 2012
77 092
23 712
Forêt de Fontainebleau
Est-ce que l'actuelle partition BOOTCAMP de 151 Go est opérationnelle ? - ou bien est-ce qu'on peut la supprimer ?

- car je soupçonne de l'espace libre d'exister en-dessous de cette partition (en fin de disque donc). Ce qui fait que seule la suppression de cette partition => permettrait de récupérer tout l'espace libéré avec celui déjà libre.​
 

macomaniac

Ouroboros
Club MacG
20 Septembre 2012
77 092
23 712
Forêt de Fontainebleau
Passe la commande (copier-coller) :
Bloc de code:
diskutil eraseVolume free null disk0s3 ; diskutil ap resizeContainer disk1 0b ; diskutil list internal

  • la commande supprime la partition BOOTCAMP > récupère l'ensemble de l'espace libre disponible au Conteneur apfs > réaffiche la configuration interne seule

Poste le retour intégral de la commande.
 

jhe974

Nouveau membre
24 Décembre 2019
7
0
53
Le résultat (J'ai toujours dans diskutillity Macintosh HD et Macintosh HD - Données)

Bloc de code:
jhecs@MacBook-Pro-de-Johnny ~ % diskutil eraseVolume free null disk0s3 ; diskutil ap resizeContainer disk1 0b ; diskutil list internal
Started erase on disk0s3 BOOTCAMP
Unmounting disk
Finished erase on disk0
Started APFS operation
Aligning grow delta to 301,945,688,064 bytes and targeting a new physical store size of 749,946,617,856 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 749,945,589,760 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 - Données was formatted by diskmanagementd (1412.41.1) and last modified by apfs_kext (1412.61.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
warning: apfs_fs_alloc_count is not valid (expected 400382, actual 57753776)
Checking volume
Checking the APFS volume superblock
The volume Preboot was formatted by hfs_convert (945.260.7) and last modified by apfs_kext (1412.61.1)
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 diskmanagementd (945.260.7) and last modified by apfs_kext (1412.61.1)
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 apfs.util (945.260.7) and last modified by apfs_kext (1412.61.1)
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 Macintosh HD was formatted by diskmanagementd (1412.61.1) and last modified by apfs_kext (1412.61.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
warning: apfs_fs_alloc_count is not valid (expected 41379, actual 2655796)
Verifying allocated space
warning: overallocation detected on Main device: (0xc852e+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc858b+21) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc85ab+15) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc85bb+26) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc85f4+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc867f+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc868f+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc86a0+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc86f8+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc870e+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8719+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8790+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc87c4+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc87d3+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc889e+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc88bc+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8901+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc89c2+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc89d6+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc89da+6) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc89e1+2) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc89e8+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8a97+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8b39+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8c56+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8c85+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8cae+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8cb1+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8cb5+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8cc2+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8cfe+4) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8d04+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8d0b+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8d0f+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8d11+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8d19+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8d1c+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8d2b+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8d4a+6) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8d51+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8dc9+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8dce+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8df2+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8df4+1) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8e55+5) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8e5b+9) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8e66+3) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8e6a+14) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8e7a+3) bitmap address (0x852fe)
warning: overallocation detected on Main device: (0xc8e95+1) bitmap address (0x852fe)
Too many warnings of this type 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 448,000,929,792 to 749,946,617,856 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *750.2 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         749.9 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +749.9 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD - Données  236.5 GB   disk1s1
   2:                APFS Volume Preboot                 26.0 MB    disk1s2
   3:                APFS Volume Recovery                525.4 MB   disk1s3
   4:                APFS Volume VM                      5.4 GB     disk1s4
   5:                APFS Volume Macintosh HD            10.9 GB    disk1s5

jhecs@MacBook-Pro-de-Johnny ~ %

Toutefois j'ai retrouvé la totalité de mon disque dur.
 

macomaniac

Ouroboros
Club MacG
20 Septembre 2012
77 092
23 712
Forêt de Fontainebleau
Tu as récupéré tout l'espace-disque possible.

- par ailleurs : la division entre un volume-Système (Macintosh HD) & un volume-Utilisateur (Macintosh HD - Données) --> est une innovation de Catalina. Elle est montrée par le terminal et l'Utilitaire de disque > mais masquée à l'usage par le Finder.​