macOS Big Sur Problème partionnement DD (Bootcamp W10)

SuperEndako · 14 Mai 2021

Bonjour à tous,

Je souhaite installer Windows 10 sur une nouvelle partition de mon Macbook pro 2016 en utilisant l'assistant Boot Camp.

Lorsque j'utilise l'assistant, j'ai un message d'erreur me disant qu'il est impossible de partitionner le disque. Le bouton S.O.S n'indique aucun problème.
Via l'utilitaire de disque, j'ai également tenté de créer une nouvelle partition en supprimant l'espace libre mais rien n'y fait.

Voici ci-dessous le résultat de la commande "diskutil list":

Bloc de code:

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI ⁨EFI⁩                     314.6 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         500.0 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨Macintosh HD - Données⁩  118.2 GB   disk1s1
   2:                APFS Volume ⁨Preboot⁩                 378.7 MB   disk1s2
   3:                APFS Volume ⁨Recovery⁩                622.1 MB   disk1s3
   4:                APFS Volume ⁨VM⁩                      1.1 GB     disk1s4
   5:                APFS Volume ⁨Macintosh HD⁩            15.3 GB    disk1s5
   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.3 GB    disk1s5s1

Avez-vous une idée du process à suivre pour solutionner cette situation ?

Merci beaucoup par avance,
Pierre.

macomaniac · 14 Mai 2021

Bonjour SuperEndako

Passe la commande expérimentale (copier-coller) :

Bloc de code:

diskutil ap resizeContainer disk1 400g fat32 BOOTCAMP 0b ; diskutil list internal

la commande rétrécit le Conteneur apfs à 400 Go > créer un partition de 100 Go avec un volume BOOTCAMP en FAT-32 > affiche la configuration interne

Poste le retour intégral de la commande. Si elle bloque => on saura pourquoi.

SuperEndako · 14 Mai 2021

Bonsoir @macomaniac,

Merci de votre réponse !

Voici le retour intégral de la commande :

Bloc de code:

% diskutil ap resizeContainer disk1 400g fat32 BOOTCAMP 0b ; diskutil list internal

Started APFS operation
Aligning shrink delta to 99 963 174 912 bytes and targeting a new physical store size of 400 000 000 000 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 139 586 437 120 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 /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
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111136562 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111136818 + 292)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111137110 + 64)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111137174 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111137430 + 124)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111137554 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111137810 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111138066 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111138322 + 448)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111138770 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111139026 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111139282 + 64)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111139346 + 1024)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111140370 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111140626 + 8)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111140634 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111140890 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111141146 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111141402 + 192)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111141594 + 512)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111142106 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111142362 + 448)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111142810 + 60)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111142870 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111143126 + 180)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111143306 + 64)
warning: apfs_fs_alloc_count is not valid (expected 28844369, actual 28851177)
Checking volume
Checking the APFS volume superblock
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
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
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
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking snapshot 1 of 1 (com.apple.os.update-86484A0ED1E166168381D22275FDFB3C663FF80B71E079FC06291D4699CBF462)
Checking the extent ref tree
Checking the fsroot tree
Checking the file extent tree
Checking volume
Checking the APFS volume superblock
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
Performing deferred repairs
error: missing/invalid physical extent (111136562 + 256) with refcnt 1
Skipped 26/26 repairs of this type in total
Deferred repairs failed
The volume /dev/disk0s2 could not be verified completely
Storage system check exit code is 0
Shrinking APFS Physical Store disk0s2 from 499 963 174 912 to 400 000 000 000 bytes
Shrinking APFS data structures
APFS Container Resize error code is 49174
Error: -69606: A problem occurred while resizing APFS Container structures
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI ⁨EFI⁩                     314.6 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         500.0 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨Macintosh HD - Données⁩  118.2 GB   disk1s1
   2:                APFS Volume ⁨Preboot⁩                 378.7 MB   disk1s2
   3:                APFS Volume ⁨Recovery⁩                622.1 MB   disk1s3
   4:                APFS Volume ⁨VM⁩                      1.1 GB     disk1s4
   5:                APFS Volume ⁨Macintosh HD⁩            15.3 GB    disk1s5
   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.3 GB    disk1s5s1

macomaniac · 14 Mai 2021

Il y a des erreurs qui affectent le fsroot tree (le segment apfs formateur du volume-Données). Le repartitionnement est bloqué à cause de ces erreurs.

- redémarre > les 2 touches ⌘R (command R) tenues pressées pour lancer l'OS de secours local. Tu obtiens une fenêtre affichant 4 Utilitaires macOS. Lance l'Utilitaire de disque > presse la pastille : "Présentation" > "Afficher tous les appareils" --> le Conteneur apfs est alors affiché. Sélectionne-le et fais un S.O.S. dessus pour tenter de réparer l'apfs.

Puis redémarre (Menu  > Redémarrer). De retour dans ta session > repasse la commande :

Bloc de code:

diskutil ap resizeContainer disk1 400g fat32 BOOTCAMP 0b ; diskutil list internal

et poste le retour.

SuperEndako · 14 Mai 2021

J'ai tenté de réparer le Conteneur Disk 2 avec l'OS de secours local en suivant vos instructions mais obtenu un message d'erreur :
"Impossible de procéder à la vérification ou à la répartition, car un ou plusieurs volumes sont verrouillés : (-69502)
L'opération a échoué"

Voici le résultat de la commande de retour sur ma session :

Bloc de code:

% diskutil ap resizeContainer disk1 400g fat32 BOOTCAMP 0b ; diskutil list internal

Started APFS operation
Aligning shrink delta to 99 963 174 912 bytes and targeting a new physical store size of 400 000 000 000 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 139 452 219 392 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 /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
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111136562 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111136818 + 292)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111137110 + 64)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111137174 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111137430 + 124)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111137554 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111137810 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111138066 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111138322 + 448)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111138770 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111139026 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111139282 + 64)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111139346 + 1024)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111140370 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111140626 + 8)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111140634 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111140890 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111141146 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111141402 + 192)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111141594 + 512)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111142106 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111142362 + 448)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111142810 + 60)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111142870 + 256)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111143126 + 180)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (111143306 + 64)
warning: apfs_fs_alloc_count is not valid (expected 28819823, actual 28826631)
Checking volume
Checking the APFS volume superblock
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
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
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
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking snapshot 1 of 1 (com.apple.os.update-86484A0ED1E166168381D22275FDFB3C663FF80B71E079FC06291D4699CBF462)
Checking the extent ref tree
Checking the fsroot tree
Checking the file extent tree
Checking volume
Checking the APFS volume superblock
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
Performing deferred repairs
error: missing/invalid physical extent (111136562 + 256) with refcnt 1
Skipped 26/26 repairs of this type in total
Deferred repairs failed
The volume /dev/disk0s2 could not be verified completely
Storage system check exit code is 0
Shrinking APFS Physical Store disk0s2 from 499 963 174 912 to 400 000 000 000 bytes
Shrinking APFS data structures
APFS Container Resize error code is 49174
Error: -69606: A problem occurred while resizing APFS Container structures
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI ⁨EFI⁩                     314.6 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         500.0 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨Macintosh HD - Données⁩  118.1 GB   disk1s1
   2:                APFS Volume ⁨Preboot⁩                 378.7 MB   disk1s2
   3:                APFS Volume ⁨Recovery⁩                622.1 MB   disk1s3
   4:                APFS Volume ⁨VM⁩                      1.1 GB     disk1s4
   5:                APFS Volume ⁨Macintosh HD⁩            15.3 GB    disk1s5
   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.3 GB    disk1s5s1

macomaniac · 14 Mai 2021

Passe la commande :

Bloc de code:

diskutil list

qui affiche un tableau détaillé de l'apfs

Poste le tableau. Il montrera si le volume-Données est chiffré par FileVault.

SuperEndako · 14 Mai 2021

Voici le résultat

Bloc de code:

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI ⁨EFI⁩                     314.6 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         500.0 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨Macintosh HD - Données⁩  118.1 GB   disk1s1
   2:                APFS Volume ⁨Preboot⁩                 378.7 MB   disk1s2
   3:                APFS Volume ⁨Recovery⁩                622.1 MB   disk1s3
   4:                APFS Volume ⁨VM⁩                      1.1 GB     disk1s4
   5:                APFS Volume ⁨Macintosh HD⁩            15.3 GB    disk1s5
   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.3 GB    disk1s5s1

macomaniac · 14 Mai 2021

Pardon : c'est la commande -->

Bloc de code:

diskutil ap list

qui affiche un tableau détaillé de l'apfs

Passe-la et poste le tableau.

SuperEndako · 14 Mai 2021

Pas de problème

Bloc de code:

% diskutil ap list

APFS Container (1 found)
|
+-- Container disk1 4C156E8C-FC4F-46DD-9470-84A3D4F23F48
    ====================================================
    APFS Container Reference:     disk1
    Size (Capacity Ceiling):      499963174912 B (500.0 GB)
    Capacity In Use By Volumes:   135685271552 B (135.7 GB) (27.1% used)
    Capacity Not Allocated:       364277903360 B (364.3 GB) (72.9% free)
    |
    +-< Physical Store disk0s2 8E8FC6BB-9F95-42D7-B9A5-8AB907A86595
    |   -----------------------------------------------------------
    |   APFS Physical Store Disk:   disk0s2
    |   Size:                       499963174912 B (500.0 GB)
    |
    +-> Volume disk1s1 A5234B50-E9AC-3FB4-B345-9DDCA52BD5C4
    |   ---------------------------------------------------
    |   APFS Volume Disk (Role):   disk1s1 (Data)
    |   Name:                      Macintosh HD - Données (Case-insensitive)
    |   Mount Point:               /System/Volumes/Data
    |   Capacity Consumed:         118099247104 B (118.1 GB)
    |   Sealed:                    No
    |   FileVault:                 Yes (Unlocked)
    |
    +-> Volume disk1s2 04742F46-8149-462C-AF20-858F4D201942
    |   ---------------------------------------------------
    |   APFS Volume Disk (Role):   disk1s2 (Preboot)
    |   Name:                      Preboot (Case-insensitive)
    |   Mount Point:               /System/Volumes/Preboot
    |   Capacity Consumed:         378658816 B (378.7 MB)
    |   Sealed:                    No
    |   FileVault:                 No
    |
    +-> Volume disk1s3 7B141F81-ABEC-4F19-85BE-E7C8DBDB2297
    |   ---------------------------------------------------
    |   APFS Volume Disk (Role):   disk1s3 (Recovery)
    |   Name:                      Recovery (Case-insensitive)
    |   Mount Point:               Not Mounted
    |   Capacity Consumed:         622104576 B (622.1 MB)
    |   Sealed:                    No
    |   FileVault:                 No
    |
    +-> Volume disk1s4 2D1B8987-9C43-4AAA-B357-D788AF9C16A6
    |   ---------------------------------------------------
    |   APFS Volume Disk (Role):   disk1s4 (VM)
    |   Name:                      VM (Case-insensitive)
    |   Mount Point:               /System/Volumes/VM
    |   Capacity Consumed:         1074810880 B (1.1 GB)
    |   Sealed:                    No
    |   FileVault:                 No
    |
    +-> Volume disk1s5 14034122-0858-4105-8E52-5651665CD74A
        ---------------------------------------------------
        APFS Volume Disk (Role):   disk1s5 (System)
        Name:                      Macintosh HD (Case-insensitive)
        Mount Point:               Not Mounted
        Capacity Consumed:         15347961856 B (15.3 GB)
        Sealed:                    Broken
        FileVault:                 Yes (Unlocked)
        Encrypted:                 No
        |
        Snapshot:                  E7604D85-273D-433E-8C0A-D0B7D54F180F
        Snapshot Disk:             disk1s5s1
        Snapshot Mount Point:      /
        Snapshot Sealed:           Yes

macomaniac · 14 Mai 2021

Le volume Macintosh HD - Données est bien protégé par FileVault -->

- redémarre via ⌘R pour ouvrir la session de secours. Lance l'Utilitaire de disque. 2 actions préalables à la réparation : a) tu affiches tous les appareils (Présentation) > b) tu sélectionnes Macintosh HD - Données grisé (non monté car verrouillé par FileVault) > bouton : Monter > ton mot-de-passe de session dans le panneau qui le demande => Macintosh HD - Données doit être libellé en noir si remonté

- si oui => sélectionne alors seulement le Conteneur apfs et fais un S.O.S. dessus.

Redémarre enfin et de retour dans ta session --> repasse encore la commande :

Bloc de code:

diskutil ap resizeContainer disk1 400g fat32 BOOTCAMP 0b ; diskutil list internal

et poste le retour.

SuperEndako · 14 Mai 2021

Procédure suivie comme indiquée

Voici le résultat de la commande :

Bloc de code:

 % diskutil ap resizeContainer disk1 400g fat32 BOOTCAMP 0b ; diskutil list internal

Started APFS operation
Aligning shrink delta to 99 963 174 912 bytes and targeting a new physical store size of 400 000 000 000 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 139 418 664 960 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 /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
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
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
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
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
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking snapshot 1 of 1 (com.apple.os.update-86484A0ED1E166168381D22275FDFB3C663FF80B71E079FC06291D4699CBF462)
Checking the extent ref tree
Checking the fsroot tree
Checking the file extent tree
Checking volume
Checking the APFS volume superblock
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
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Shrinking APFS Physical Store disk0s2 from 499 963 174 912 to 400 000 000 000 bytes
Shrinking APFS data structures
Shrinking partition
Modifying partition map
4096 bytes per physical sector
/dev/rdisk0s3: 24399000 sectors in 3049875 FAT32 clusters (32768 bytes/cluster)
bps=4096 spc=8 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=97733120 drv=0x80 bsec=24404992 bspf=2979 rdcl=2 infs=1 bkbs=6
Mounting disk
1 new disk created or changed due to APFS operation
Disk from APFS operation: disk0s3
Finished APFS operation
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI ⁨EFI⁩                     314.6 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         400.0 GB   disk0s2
   3:       Microsoft Basic Data ⁨BOOTCAMP⁩                100.0 GB   disk0s3

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +400.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨Macintosh HD - Données⁩  118.1 GB   disk1s1
   2:                APFS Volume ⁨Preboot⁩                 378.7 MB   disk1s2
   3:                APFS Volume ⁨Recovery⁩                622.1 MB   disk1s3
   4:                APFS Volume ⁨VM⁩                      1.1 GB     disk1s4
   5:                APFS Volume ⁨Macintosh HD⁩            15.3 GB    disk1s5
   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.3 GB    disk1s5s1

macomaniac · 14 Mai 2021

L'erreur a été réparée et voici le résultat -->

Bloc de code:

   3:       Microsoft Basic Data ⁨BOOTCAMP⁩                100.0 GB   disk0s3

partition BOOTCAMP créée.

Passe la commande :

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 son espace au Conteneur > affiche la configuration interne

Poste le retour.

----------

Note : pour réparer un système de fichiers > il faut que tous les volumes qui en dépendent soient démontés. Ce qui ne se peut que dans la session de secours. Car avec les OS apfs > démarrer en mode secours local fait démarrer sur un clone exécuté à la volée de l'OS de secours du volume Recovery => dans une image-disque en RAM. Le Mac étant alors démarré sur la RAM en indépendance du disque interne => tous les volumes du Conteneur peuvent être démontés et l'apfs réparé.

SuperEndako · 15 Mai 2021

Merci beaucoup pour les explications, je comprends mieux !

Voici le résultat de la commande :

Bloc de code:

% 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 99 963 174 912 bytes and targeting a new physical store size of 499 963 174 912 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 499 962 146 816 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 /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
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
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
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
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
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking snapshot 1 of 1 (com.apple.os.update-86484A0ED1E166168381D22275FDFB3C663FF80B71E079FC06291D4699CBF462)
Checking the extent ref tree
Checking the fsroot tree
Checking the file extent tree
Checking volume
Checking the APFS volume superblock
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
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Growing APFS Physical Store disk0s2 from 400 000 000 000 to 499 963 174 912 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI ⁨EFI⁩                     314.6 MB   disk0s1
   2:                 Apple_APFS ⁨Container disk1⁩         500.0 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume ⁨Macintosh HD - Données⁩  118.1 GB   disk1s1
   2:                APFS Volume ⁨Preboot⁩                 378.7 MB   disk1s2
   3:                APFS Volume ⁨Recovery⁩                622.1 MB   disk1s3
   4:                APFS Volume ⁨VM⁩                      1.1 GB     disk1s4
   5:                APFS Volume ⁨Macintosh HD⁩            15.3 GB    disk1s5
   6:              APFS Snapshot ⁨com.apple.os.update-...⁩ 15.3 GB    disk1s5s1

macomaniac · 15 Mai 2021

Ton apfs a retrouvé l'élasticité requise.

- tu n'as qu'à relancer l'Assistant BootCamp pour ton installation de Windows.

SuperEndako · 19 Mai 2021

Bonjour @macomaniac,

Désolé pour la réponse tardive, je viens seulement de retrouver mon mac.
J'ai relancé l'assistant et tout a fonctionné correctement !!

Merci beaucoup pour l'aide et les explications tout au long du process !!!

Passe une bonne journée

macomaniac · 19 Mai 2021

Content pour toi !

Rechercher

Rechercher

macOS Big Sur Problème partionnement DD (Bootcamp W10)

SuperEndako

Membre enregistré

macomaniac

Ouroboros

SuperEndako

Membre enregistré

macomaniac

Ouroboros

SuperEndako

Membre enregistré

macomaniac

Ouroboros

SuperEndako

Membre enregistré

macomaniac

Ouroboros

SuperEndako

Membre enregistré

macomaniac

Ouroboros

SuperEndako

Membre enregistré

macomaniac

Ouroboros

SuperEndako

Membre enregistré

macomaniac

Ouroboros

SuperEndako

Membre enregistré

macomaniac

Ouroboros

Sujets similaires