Problème fsroot tree suite suppression partition BOOTCAMP

Il semble avoir créer la partition TEMP en plus de la BOOTCAMP
Bloc de code: 
Started APFS operation
Aligning shrink delta to 350 000 001 024 bytes and targeting a new physical store size of 2 328 876 929 024 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 963 280 633 856 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /dev/disk1s2
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 was formatted by diskmanagementd (945.260.7) and last modified by apfs_kext (945.260.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 hfs_convert (945.200.129) and last modified by apfs_kext (945.260.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 diskmanagementd (945.200.129) and last modified by apfs_kext (945.260.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 apfs.util (945.200.129) and last modified by apfs_kext (945.260.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 Tier2 device: (1125900370066688+64) bitmap address (2a17f)
warning: Overallocation Detected on Tier2 device: (1125900370066752+64) bitmap address (2a17f)
warning: Overallocation Detected on Tier2 device: (1125900370066816+64) bitmap address (2a17f)
warning: Overallocation Detected on Tier2 device: (1125900370066880+59) bitmap address (2a17f)
warning: Overallocation Detected on Tier2 device: (1125900443661563+5) bitmap address (2aa45)
warning: Overallocation Detected on Tier2 device: (1125900443661568+64) bitmap address (2aa45)
warning: Overallocation Detected on Tier2 device: (1125900443661632+64) bitmap address (2aa45)
warning: Overallocation Detected on Tier2 device: (1125900443661696+64) bitmap address (2aa45)
warning: Overallocation Detected on Tier2 device: (1125900443661760+64) bitmap address (2aa45)
warning: Overallocation Detected on Tier2 device: (1125900443661824+64) bitmap address (2aa45)
warning: Overallocation Detected on Tier2 device: (1125900443661888+64) bitmap address (2aa45)
warning: Overallocation Detected on Tier2 device: (1125900443661952+64) bitmap address (2aa45)
warning: Overallocation Detected on Tier2 device: (1125900443662016+33) bitmap address (2aa45)
The volume /dev/disk1s2 appears to be OK
Storage system check exit code is 0
Shrinking APFS Physical Store disk0s2 from 2 678 876 930 048 to 2 328 876 929 024 bytes
Shrinking APFS data structures
Shrinking partition
Modifying partition map
Initialized /dev/rdisk0s5 as a 326 GB case-insensitive HFS Plus volume with a 32768k journal
Mounting disk
1 new disk created or changed due to APFS operation
Disk from APFS operation: disk0s5
Finished APFS operation
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         2.3 TB     disk0s2
   3:                  Apple_HFS TEMP                    349.9 GB   disk0s5
   4:       Microsoft Basic Data BOOTCAMP                321.5 GB   disk0s3
 
Allez ! encore une tranche... Passe la commande :
Bloc de code: 
diskutil ap resizeContainer disk2 2120g jhfs+ BROL 0b ; diskutil list disk0

  • la commande rétrécit le Conteneur à 2,12 To et crée une partition BROL de 330 Go environ

Poste le retour.
 
Ca a été la tranche de trop...
Bloc de code: 
Started APFS operation
Aligning shrink delta to 329 999 998 976 bytes and targeting a new physical store size of 1 998 876 930 048 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 963 280 633 856 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /dev/disk1s2
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 was formatted by diskmanagementd (945.260.7) and last modified by apfs_kext (945.260.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 hfs_convert (945.200.129) and last modified by apfs_kext (945.260.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 diskmanagementd (945.200.129) and last modified by apfs_kext (945.260.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 apfs.util (945.200.129) and last modified by apfs_kext (945.260.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 Tier2 device: (1125900370066688+64) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900370066752+64) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900370066816+64) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900370066880+59) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900443661563+5) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661568+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661632+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661696+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661760+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661824+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661888+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661952+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443662016+33) bitmap address (4418)
The volume /dev/disk1s2 appears to be OK
Storage system check exit code is 0
Shrinking APFS Physical Store disk0s2 from 2 328 876 929 024 to 1 998 876 930 048 bytes
Shrinking APFS data structures
APFS Container Resize error code is 49187
Error: -69606: A problem occurred while resizing APFS Container structures
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         2.3 TB     disk0s2
   3:                  Apple_HFS TEMP                    349.9 GB   disk0s5
   4:       Microsoft Basic Data BOOTCAMP                321.5 GB   disk0s3
 
Alors plus modeste -->
Bloc de code: 
diskutil ap resizeContainer disk2 2220g jhfs+ BROL 0b ; diskutil list disk0

  • poste le retour.
 
...
Bloc de code: 
Started APFS operation
Aligning shrink delta to 230 000 001 024 bytes and targeting a new physical store size of 2 098 876 928 000 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 963 280 633 856 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /dev/disk1s2
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 was formatted by diskmanagementd (945.260.7) and last modified by apfs_kext (945.260.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 hfs_convert (945.200.129) and last modified by apfs_kext (945.260.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 diskmanagementd (945.200.129) and last modified by apfs_kext (945.260.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 apfs.util (945.200.129) and last modified by apfs_kext (945.260.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 Tier2 device: (1125900370066688+64) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900370066752+64) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900370066816+64) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900370066880+59) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900443661563+5) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661568+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661632+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661696+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661760+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661824+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661888+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661952+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443662016+33) bitmap address (4418)
The volume /dev/disk1s2 appears to be OK
Storage system check exit code is 0
Shrinking APFS Physical Store disk0s2 from 2 328 876 929 024 to 2 098 876 928 000 bytes
Shrinking APFS data structures
APFS Container Resize error code is 49187
Error: -69606: A problem occurred while resizing APFS Container structures
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         2.3 TB     disk0s2
   3:                  Apple_HFS TEMP                    349.9 GB   disk0s5
   4:       Microsoft Basic Data BOOTCAMP                321.5 GB   disk0s3
 
Encore une tentative plus modeste -->
Bloc de code: 
diskutil ap resizeContainer disk2 2300g jhfs+ BROL 0b ; diskutil list disk0

  • poste le retour.
 
Pas mieux....
Tu n'aurais pas quelque chose de plus...radical ?

Bloc de code: 
Started APFS operation
Aligning shrink delta to 150 000 001 024 bytes and targeting a new physical store size of 2 178 876 928 000 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 963 280 633 856 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /dev/disk1s2
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 was formatted by diskmanagementd (945.260.7) and last modified by apfs_kext (945.260.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 hfs_convert (945.200.129) and last modified by apfs_kext (945.260.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 diskmanagementd (945.200.129) and last modified by apfs_kext (945.260.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 apfs.util (945.200.129) and last modified by apfs_kext (945.260.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 Tier2 device: (1125900370066688+64) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900370066752+64) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900370066816+64) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900370066880+59) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900443661563+5) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661568+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661632+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661696+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661760+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661824+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661888+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661952+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443662016+33) bitmap address (4418)
The volume /dev/disk1s2 appears to be OK
Storage system check exit code is 0
Shrinking APFS Physical Store disk0s2 from 2 328 876 929 024 to 2 178 876 928 000 bytes
Shrinking APFS data structures
APFS Container Resize error code is 49187
Error: -69606: A problem occurred while resizing APFS Container structures
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         2.3 TB     disk0s2
   3:                  Apple_HFS TEMP                    349.9 GB   disk0s5
   4:       Microsoft Basic Data BOOTCAMP                321.5 GB   disk0s3
 
Le plus radical consisterait à supprimer le Fusion Drive > puis le recréer > et tester un repartitionnement avant réinstallation d'OS.

- est-ce qu'une partition BOOTCAMP de 671 Go te conviendrait (dans l'état actuel des lieux) ?​
 
Je me pose la question de savoir si ce n'est pas à cause de l'ancienne partition BOOTCAMP qui était présente sur le disque lors de la mise à jour vers Mojave. Cette dernière devait faire aux alentours de 700 Go et il semble qu'on ne puisse pas créer une partition plus grande que cette valeur justement.
 
Je ne peux pas te dire à quoi c'est dû. Tu as un disque de très grande capacité (3 To) et pas mal de données qui débordent du SSD sur ce disque. Je ne sais pas si le Fusion Drive apfs a des limites de partitionnement autour de la barre des 2,2 To pour le HDD ou s'il y a une erreur interne de l'apfs tel qu'il s'est installé.

Peut-être que le kernel qui prend en charge ces partitionnements et leurs volumes --> se trouve-t-il tant soit peu à la ramasse.

Pour vérifier cette dernière conjecture > redémarre une fois > ta session réouverte > repasse la commande :
Bloc de code: 
diskutil ap resizeContainer disk2 2300g jhfs+ BROL 0b ; diskutil list

  • et poste le retour.
 
Je poste en deux fois
Bloc de code: 
Started APFS operation
Aligning shrink delta to 150 000 001 024 bytes and targeting a new physical store size of 2 178 876 928 000 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 963 347 742 720 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 was formatted by diskmanagementd (945.260.7) and last modified by apfs_kext (945.260.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 hfs_convert (945.200.129) and last modified by apfs_kext (945.260.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 diskmanagementd (945.200.129) and last modified by apfs_kext (945.260.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 apfs.util (945.200.129) and last modified by apfs_kext (945.260.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 Tier2 device: (1125900370066688+64) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900370066752+64) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900370066816+64) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900370066880+59) bitmap address (3b52)
warning: Overallocation Detected on Tier2 device: (1125900443661563+5) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661568+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661632+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661696+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661760+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661824+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661888+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443661952+64) bitmap address (4418)
warning: Overallocation Detected on Tier2 device: (1125900443662016+33) bitmap address (4418)
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Shrinking APFS Physical Store disk1s2 from 2 328 876 929 024 to 2 178 876 928 000 bytes
Shrinking APFS data structures
APFS Container Resize error code is 49187
Error: -69606: A problem occurred while resizing APFS Container structures
 
Bloc de code: 
/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                        *3.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         2.3 TB     disk1s2
   3:                  Apple_HFS TEMP                    349.9 GB   disk1s3
   4:       Microsoft Basic Data BOOTCAMP                321.5 GB   disk1s4

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +2.5 TB     disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD            933.9 GB   disk2s1
   2:                APFS Volume Preboot                 50.6 MB    disk2s2
   3:                APFS Volume Recovery                509.7 MB   disk2s4
   4:                APFS Volume VM                      2.1 GB     disk2s5

/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS Sauvegarde mac          2.0 TB     disk3s2

/dev/disk4 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *32.0 GB    disk4
   1:               Windows_NTFS WinInstall              32.0 GB    disk4s1
 
Échec encore. Passe la commande (copie-la bien jusqu'au disk1 final) :
Bloc de code: 
diskutil eraseVolume free null disk1s4 ; diskutil resizeVolume disk1s3 0b ; diskutil eraseVolume fat32 BOOTCAMP disk1s3 ; diskutil list disk1

  • la commande supprime la partition BOOTCAMP > récupère son espace à la partitoin TEMP > reformate la partition augmentée en FAT-32 avec un volume BOOTCAMP > réaffiche la configuration du HDD

Poste le retour.
 
Bloc de code: 
Started erase on disk1s4 BOOTCAMP
Unmounting disk
Finished erase on disk1
Resizing to full size (fit to fill)
Started partitioning on disk1s3 TEMP
Verifying the disk
Verifying file system
Volume was successfully unmounted
Performing fsck_hfs -fn -x /dev/rdisk1s3
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
The volume TEMP appears to be OK
File system check exit code is 0
Restoring the original state found as mounted
Resizing
Modifying partition map
Growing file system
Finished partitioning on disk1s3 TEMP
/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         2.3 TB     disk1s2
   3:                  Apple_HFS TEMP                    671.4 GB   disk1s3
Started erase on disk1s3 TEMP
Unmounting disk
Erasing
4096 bytes per physical sector
/dev/rdisk1s4: 1310950784 sectors in 20483606 FAT32 clusters (32768 bytes/cluster)
bps=512 spc=64 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=254031872 drv=0x80 bsec=1311270912 bspf=160032 rdcl=2 infs=1 bkbs=6
Mounting disk
Finished erase on disk1s4 BOOTCAMP
/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         2.3 TB     disk1s2
   3:       Microsoft Basic Data BOOTCAMP                671.4 GB   disk1s4
 
Voici le mieux qu'on ait pu faire -->
Bloc de code: 
   3:       Microsoft Basic Data BOOTCAMP                671.4 GB   disk1s4

  • tu n'as qu'à essayer d'installer Windows-10 à cette destination (il faut que tu aies un volume externe démarrable d'installation de Windows).
 
En tout état de cause, et même si la finalité n'est pas totalement atteinte, je te remercie grandement pour l'aide qui tu m'as apportée.

Je te prie de m'excuser d'avoir pris autant de ton temps (surtout quand je vois que tu le fais très très fréquemment avec les autres membres du forum).
 
Tu n'auras qu'à dire si tu as pu installer Windows dans le volume BOOTCAMP.

- sinon > il faudrait reprendre les opérations à la base : suppression du Fusion Drive etc.​
 

Sujets similaires

Ulgalas
Partition bootcamp disparue suite à desinstallation
Réponses
6
Affichages
3K
Windows sur Mac
Locke
Locke
M
Probleme lancement bootcamp
Réponses
2
Affichages
2K
Windows sur Mac
Mrg91
M
Q
bootcamp problème installation
Réponses
1
Affichages
2K
Windows sur Mac
Locke
Locke
P
Partition Bootcamp impossible
Réponses
84
Affichages
9K
Windows sur Mac
Danielmorphee
D
P
10.14 Mojave SSD APFS : fsroot tree is invalid
Réponses
16
Affichages
3K
macOS
pignon_61
P
Haut Bas