10.12 Sierra problème fusion drive après échec Boot Camp

Bonjour benyo

Tu as 2 disques : SSD de 121 Go & HDD de 4 To > associés au niveau de leurs partitions principales par un Fusion Drive de type apfs. Un Conteneur collectif de 4,1 To en résulte > recelant une distribution à 5 volumes de Catalina.

- passe la commande (copier-coller) :​
Bloc de code: 
diskutil verifyVolume disk2
  • la commande vérifie l'apfs du Conteneur et de ses volumes

Poste le retour en copier-coller. Pour ton coller > utilise plutôt le 17è menu depuis la gauche (balises code) que le 6è (balises icode).
 
Merco MAcomaniac pour ta réponse rapide !

ci dessous le résultat de la commande que tu m'as indiqué:
Bloc de code: 
Imac:~ bdescham$ diskutil verifyVolume disk2
Started file system verification on disk2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l /dev/disk0s2
Checking the container superblock
Checking the fusion superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking the Fusion data structures
Checking volume
Checking the APFS volume superblock
The volume Macintosh HD - Données was formatted by diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking snapshot 1 of 2 (com.apple.TimeMachine.2021-12-05-135028.local)
Checking snapshot 2 of 2 (com.apple.TimeMachine.2021-12-05-145457.local)
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume Preboot was formatted by diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2)
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 (1412.141.1) and last modified by apfs_kext (1412.141.2)
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 diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2)
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.141.1) and last modified by apfs_kext (1412.141.2)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking snapshot 1 of 2 (com.apple.TimeMachine.2021-12-05-135028.local)
Checking snapshot 2 of 2 (com.apple.TimeMachine.2021-12-05-145457.local)
Checking the extent ref tree
Checking the fsroot tree
Verifying allocated space
warning: MT mapping (0x40000008aee42 -> 0xb58ea6, 3, C) is not completely referenced
warning: MT mapping (0x40000011a692d -> 0xe88c2c, 1, C) is not completely referenced
warning: MT mapping (0x40000011a692e -> 0xe88c47, 1, C) is not completely referenced
warning: MT mapping (0x40000011a69b8 -> 0xe8843b, 1, C) is not completely referenced
warning: MT mapping (0x40000012f9b98 -> 0xe88457, 1, C) is not completely referenced
warning: MT mapping (0x40000012f9bc8 -> 0xe88454, 1, C) is not completely referenced
warning: MT mapping (0x400000131ce9d -> 0xe88439, 1, C) is not completely referenced
warning: MT mapping (0x40000013e464b -> 0xe88458, 1, C) is not completely referenced
warning: MT mapping (0x40000013e46af -> 0xe88420, 1, C) is not completely referenced
warning: MT mapping (0x40000015a0edc -> 0xe8829f, 1, C) is not completely referenced
warning: MT mapping (0x4000001b6462e -> 0xb687f5, 1, C) is not completely referenced
warning: MT mapping (0x4000001d9eed7 -> 0xb505b9, 2, C) is not completely referenced
warning: MT mapping (0x4000008f07c20 -> 0xb68520, 1, C) is not completely referenced
warning: MT mapping (0x400000a293a61 -> 0x1af82fd, 7, C) is not completely referenced
warning: MT mapping (0x400000f2d9e7b -> 0x986555, 1, C) is not completely referenced
warning: MT mapping (0x4000011cf1b12 -> 0x9911dc, 325, C) is not completely referenced
warning: MT mapping (0x4000011e59b3f -> 0x9f305e, 155, C) is not completely referenced
warning: MT mapping (0x4000012ff01fc -> 0xb6a11a, 1, C) is not completely referenced
warning: MT mapping (0x4000013126d47 -> 0xb6acde, 1, C) is not completely referenced
warning: MT mapping (0x40000132252c1 -> 0xb6a1dc, 1, C) is not completely referenced
warning: MT mapping (0x4000013378549 -> 0xb69714, 1, C) is not completely referenced
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Finished file system verification on disk2
 
Tu as 2 snapshots récents associés aussi bien au volume-Données qu'au volume-Système :
Bloc de code: 
Checking snapshot 1 of 2 (com.apple.TimeMachine.2021-12-05-135028.local)
Checking snapshot 2 of 2 (com.apple.TimeMachine.2021-12-05-145457.local)
  • peut-être susceptibles de verrouiller de l'espace de blocs et par là de proscrire un repartitionnement. Par ailleurs > tu as une série d'erreurs du spaceman (space_manager) qui gère l'allocation des blocs --> lesquelles peuvent proscrire un repartitionnement.

On va faire un test de repartitionnement --> afin de voir la réaction de l'apfs à cette opération. En cas d'échec --> la raison devrait se trouver alléguée. Passe la commande (copier-coller) :
Bloc de code: 
diskutil ap resizeContainer disk2 3t fat32 BOOTCAMP 0b ; diskutil list internal
  • la commande instruit un rétrécissement du Conteneur apfs à 3 To > et la création d'une partition BOOTCAMP de 1,1 To au format FAT-32 en queue du grand SSD > puis affiche la configuration interne résultante

Poste le retour complet de la commande.
 
on dirait que cela à fonctionné?
Bloc de code: 
Imac:~ bdescham$ diskutil ap resizeContainer disk2 3t fat32 BOOTCAMP 0b ; diskutil list internal
Started APFS operation
Aligning shrink delta to 1 121 700 343 808 bytes and targeting a new physical store size of 2 878 876 930 048 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 1 035 288 444 928 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk1s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /dev/disk0s2
Checking the container superblock
Checking the fusion superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking the Fusion data structures
Checking volume
Checking the APFS volume superblock
The volume Macintosh HD - Données was formatted by diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2)
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 285729, actual 242460257)
Checking volume
Checking the APFS volume superblock
The volume Preboot was formatted by diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2)
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 (1412.141.1) and last modified by apfs_kext (1412.141.2)
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 diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2)
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.141.1) and last modified by apfs_kext (1412.141.2)
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 42549, actual 2738923)
Verifying allocated space
warning: overallocation detected on Main device: (0x21e18c+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e18f+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e29c+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e2af+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e2d1+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e2e7+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e308+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e30f+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e32e+2) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e336+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e33a+2) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e33f+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e342+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e347+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e34d+2) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e357+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e35a+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e361+2) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e39f+2) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e3bb+9) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e3f7+8) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e485+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e487+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e48b+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e491+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e496+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e49f+6) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e4a6+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e4b3+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e4b9+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e4be+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e4ca+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e4dc+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e4e6+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e50a+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e526+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e54f+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e55b+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e578+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e593+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e59c+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e59e+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e5b8+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e5d1+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e5d6+2) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e5d9+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e5e8+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e5f0+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e5f5+1) bitmap address (0x20d4d8)
warning: overallocation detected on Main device: (0x21e5f9+1) bitmap address (0x20d4d8)
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
Shrinking APFS Physical Store disk1s2 from 4 000 577 273 856 to 2 878 876 930 048 bytes
Shrinking APFS data structures
Shrinking partition
Modifying partition map
512 bytes per physical sector
/dev/rdisk1s3: 2190282496 sectors in 34223164 FAT32 clusters (32768 bytes/cluster)
bps=512 spc=64 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=1328250880 drv=0x80 bsec=2190817280 bspf=267369 rdcl=2 infs=1 bkbs=6
Mounting disk
1 new disk created or changed due to APFS operation
Disk from APFS operation: disk1s3
Finished APFS operation
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         121.1 GB   disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         2.9 TB     disk1s2
   3:       Microsoft Basic Data BOOTCAMP                1.1 TB     disk1s3

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +3.0 TB     disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD - Données  993.1 GB   disk2s1
   2:                APFS Volume Preboot                 85.6 MB    disk2s2
   3:                APFS Volume Recovery                529.0 MB   disk2s3
   4:                APFS Volume VM                      2.1 GB     disk2s4
   5:                APFS Volume Macintosh HD            11.2 GB    disk2s5
 
Malgré des erreurs alléguées mais non bloquantes --> le repartitionnement s'est effectué sans problème. Tu as une partition BOOTCAMP de 1,1 To.

- passe la commande (copier-coller) :​
Bloc de code: 
diskutil eraseVolume free null disk1s3 ; diskutil ap resizeContainer disk2 0b ; diskutil list internal
  • la commande supprime la partition BOOTCAMP expérimentale > récupère son espace au Conteneur apfs > ré-affiche la configuration interne

Poste le retour.
 
et voilà:
Bloc de code: 
Imac:~ bdescham$ diskutil eraseVolume free null disk1s3 ; diskutil ap resizeContainer disk2 0b ; diskutil list internal
Started erase on disk1s3 BOOTCAMP
Unmounting disk
Finished erase on disk1
Started APFS operation
Aligning grow delta to 1 121 700 343 808 bytes and targeting a new physical store size of 4 000 577 273 856 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 4 000 576 245 760 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk1s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /dev/disk0s2
Checking the container superblock
Checking the fusion superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking the Fusion data structures
Checking volume
Checking the APFS volume superblock
The volume Macintosh HD - Données was formatted by diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2)
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 300000, actual 242474528)
Checking volume
Checking the APFS volume superblock
The volume Preboot was formatted by diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2)
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 (1412.141.1) and last modified by apfs_kext (1412.141.2)
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 diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.2)
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.141.1) and last modified by apfs_kext (1412.141.2)
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 42549, actual 2738923)
Verifying allocated space
warning: overallocation detected on Main device: (0x21e18c+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e18f+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e29c+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e2af+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e2d1+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e2e7+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e308+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e30f+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e32e+2) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e336+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e33a+2) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e33f+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e342+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e347+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e34d+2) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e357+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e35a+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e361+2) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e3a0+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e3bb+9) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e3f7+8) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e485+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e487+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e48b+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e491+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e496+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e49f+6) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e4a6+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e4b3+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e4b9+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e4be+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e4ca+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e4dc+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e4e6+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e50a+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e526+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e54f+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e55b+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e578+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e593+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e59c+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e59e+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e5b8+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e5d1+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e5d6+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e5d9+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e5e8+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e5f0+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e5f5+1) bitmap address (0x13d1d70)
warning: overallocation detected on Main device: (0x21e5f9+1) bitmap address (0x13d1d70)
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 disk1s2 from 2 878 876 930 048 to 4 000 577 273 856 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         121.1 GB   disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         4.0 TB     disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +4.1 TB     disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD - Données  993.2 GB   disk2s1
   2:                APFS Volume Preboot                 85.6 MB    disk2s2
   3:                APFS Volume Recovery                529.0 MB   disk2s3
   4:                APFS Volume VM                      2.1 GB     disk2s4
   5:                APFS Volume Macintosh HD            11.2 GB    disk2s5
 
Retour à la case départ sans problème.

- comme l'Assistant BootCamp est susceptible en cas de détections d'erreurs (même non bloquantes) --> voici ce que te conseille. Redémarre > les 2 touches ⌘R (command R) tenues pressées pour ouvrir la session de secours. Quand tu as son écran > lance l'Utilitaire de disque. Presse la pastille : "Présentation" et coche : "Afficher tous les appareils". Le Conteneur apfs est alors affiché. Sélectionne-le et fais un S.O.S. pour tenter de réparer les erreurs de l'apfs (on ne peut pas réparer en étant démarré sur macOS). Puis redémarre (Menu  > Redémarrer) > ta session réouverte => relance les opérations avec l'Assistant BootCamp.​
​
Tu n'auras qu'à dire si le repartitionnement est débloqué avec ce logiciel.
 
Bonjour à tous,
Je reviens car malheureusement j'ai un problème similaire à mes précédents messages...

En utilisant l'assistant bootcamp pour supprimer la partition windows que j'avais réussi à installer grâce à l'aide de @macomaniac, celle-ci a de nouveau disparue et je n'arrive plus a y accéder ni à la supprimer pour en "récupérer" les Go.

J'ai essayé les mêmes commandes qu'auparavant et cela ne marche pas non plus, les voici :

Bloc de code: 
diskutil list
Résultat :
Bloc de code: 
/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         185.0 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +185.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD - Données  116.4 GB   disk1s1
   2:                APFS Volume Preboot                 219.4 MB   disk1s2
   3:                APFS Volume Recovery                529.0 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4
   5:                APFS Volume Macintosh HD            11.2 GB    disk1s5

Pas de sauvegarde TM bloquante, et la sauvegarde auto est bien désactivée dans les préférences :
Bloc de code: 
diskutil ap listSnaps disk1s1
Résultat :
Bloc de code: 
No snapshots for disk1s1


Bloc de code: 
diskutil ap resizeContainer disk1 200g fat32 BOOTCAMP 0b ; diskutil list internal
Résultat :
Bloc de code: 
Started APFS operation
Aligning grow delta to 14 999 998 464 bytes and targeting a new physical store size of 200 000 000 000 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 250 789 408 768 bytes
Error: -69604: You cannot create new partitions with a grow request
/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         185.0 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +185.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD - Données  117.0 GB   disk1s1
   2:                APFS Volume Preboot                 219.4 MB   disk1s2
   3:                APFS Volume Recovery                529.0 MB   disk1s3
   4:                APFS Volume VM                      2.1 GB     disk1s4
   5:                APFS Volume Macintosh HD            11.2 GB    disk1s5


Bloc de code: 
diskutil ap resizeContainer disk1 0b ; diskutil list internal
Résultat :
Bloc de code: 
Started APFS operation
Aligning grow delta to 65 790 435 328 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
warning: container has been mounted by APFS version 1677.81.1, which is newer than 1412.141.1
warning: disabling overallocation repairs by default; use -o to override
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 hfs_convert (748.41.3) and last modified by apfs_kext (1412.141.1)
Checking the object map
error: omap entry (oid 0x24031d): invalid ov_paddr (1152921504607434057)
Object map is invalid
The volume /dev/disk0s2 could not be verified completely
Storage system check exit code is 8
Error: -69716: Storage system verify or repair failed
/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         185.0 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +185.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD - Données  117.0 GB   disk1s1
   2:                APFS Volume Preboot                 219.4 MB   disk1s2
   3:                APFS Volume Recovery                529.0 MB   disk1s3
   4:                APFS Volume VM                      2.1 GB     disk1s4
   5:                APFS Volume Macintosh HD            11.2 GB    disk1s5


Et enfin suite au message "Error: -69604: You cannot create new partitions with a grow request" j'ai essayer avec 180 Go :
Bloc de code: 
diskutil ap resizeContainer disk1 180g fat32 BOOTCAMP 0b ; diskutil list internal
Résultat :
Bloc de code: 
Started APFS operation
Aligning shrink delta to 5 000 003 584 bytes and targeting a new physical store size of 179 999 997 952 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 137 019 523 072 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
warning: container has been mounted by APFS version 1677.81.1, which is newer than 1412.141.1
warning: disabling overallocation repairs by default; use -o to override
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 hfs_convert (748.41.3) and last modified by apfs_kext (1412.141.1)
Checking the object map
error: omap entry (oid 0x24031d): invalid ov_paddr (1152921504607434057)
Object map is invalid
The volume /dev/disk0s2 could not be verified completely
Storage system check exit code is 8
Error: -69716: Storage system verify or repair failed
/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         185.0 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +185.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD - Données  117.0 GB   disk1s1
   2:                APFS Volume Preboot                 219.4 MB   disk1s2
   3:                APFS Volume Recovery                529.0 MB   disk1s3
   4:                APFS Volume VM                      2.1 GB     disk1s4
   5:                APFS Volume Macintosh HD            11.2 GB    disk1s5

J'ai regardé sur d'autres topics mais je n'ai pas trouvé la solution.
Est-il possible de m'aider à nouveau, je ne sais plus quoi faire à présent...

En vous remerciant pour votre aide.
 

Sujets similaires

H
10.14 Mojave problème de démarrage de mon imac 27 sous fusion drive
Réponses
22
Affichages
2K
macOS
Locke
Locke
M
macOS Monterey Fusion Drive : données récupérables ? (erreur 119930868)
Réponses
11
Affichages
2K
macOS
Invité
Invité
K
macOS Monterey Boot sur disque externe plus possible
Réponses
0
Affichages
619
macOS
k_man
K
Aski
macOS Ventura No CoreStorage logical volume groups found
Réponses
6
Affichages
843
macOS
Locke
Locke
Herve1
10.13 High Sierra Problème Disque dur MBP 2010
Réponses
13
Affichages
1K
macOS
Sly54
Sly54
Haut Bas