Probleme bootcamp W10 & Mojave

  • Créateur du sujet Créateur du sujet LemmS
  • Date de début Date de début
L

LemmS

Membre enregistré
1 Mars 2019
5
0
45
Bonjour a tous,
Je dispose d'un IMAC avec Mojave & W10 (Bootcamp) tout fonctionnait très bien mais
je rencontre un soucis depuis une mise a jour W10 (je suppose)
Je n'arrive plus a booter sur W10 (il n'apparait plus au démarrage)
Quand je lance l'assistant Bootcamp il me fait un message d'erreur
Le disque de démarrage ne peut être ni partitionné, ni restauré en une seule partition.

Merci de votre aide :)

Ci-dessous diskutil list

Bloc de code: 
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         899.0 GB   disk0s2
   3:       Microsoft Basic Data BOOTCAMP                100.5 GB   disk0s3
   4:           Windows Recovery                         505.4 MB   disk0s4

/dev/disk1 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         24.0 GB    disk1
   1:                        EFI EFI                     314.6 MB   disk1s1
   2:                 Apple_APFS Container disk2         23.7 GB    disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +922.7 GB   disk2
                                 Physical Stores disk1s2, disk0s2
   1:                APFS Volume Macintosh HD            711.3 GB   disk2s1
   2:                APFS Volume Preboot                 42.8 MB    disk2s2
   3:                APFS Volume Recovery                517.0 MB   disk2s3
   4:                APFS Volume VM                      2.2 GB     disk2s4
 
Bonjour LemmS

LemmS a dit:
Quand je lance l'assistant Bootcamp il me fait un message d'erreur
Le disque de démarrage ne peut être ni partitionné, ni restauré en une seule partition.
Cliquez pour agrandir...

- ton intention en lançant l'Assistant BootCamp --> est-elle de lui faire supprimer les partitions dédiées actuellement à Windows > avant recréation d'une partition BOOTCAMP > et réinstallation de Windows 10 ?​
 
Bonjour macomaniac,
Si je ne peux pas récupérer le dual boot alors oui je vais supprimer pour réinstaller.
Je te remercie de ton aide
Cdt,
 
Si tu as besoin de commandes pour la suppression des 2 partitions Windows (disk0s3 & disk0s4) > et la récupération de leur espace au Conteneur apfs --> tu n'as qu'à demander.

- pour ce qui est du redémarrage de ton Windows 10 --> je ne saurais te dire.​
 
Je te remercie de bien vouloir me donner les commandes pour supprimer les 2 partitions et récupérer leur espace afin de réinstaller Windows correctement
Merci
 
Repasse d'abors un :
Bloc de code: 
diskutil list

  • et reposte le tableau de disques

=> il arrive en effet avec 2 disques internes comme ceux de ton iMac > que les index des disques (disk0 vs disk1) permutent suite à un redémarrage (ce sont des variables indiquant le rang dans le processus temporel d'attachement des disques au Système du Mac lors du boot). Il s'agit donc de s'assurer de l'index de disque du HDD qui porte les 2 partitions Windows à supprimer.
 
Bloc de code: 
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         899.0 GB   disk0s2
   3:       Microsoft Basic Data BOOTCAMP                100.5 GB   disk0s3
   4:           Windows Recovery                         505.4 MB   disk0s4

/dev/disk1 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         24.0 GB    disk1
   1:                        EFI EFI                     314.6 MB   disk1s1
   2:                 Apple_APFS Container disk2         23.7 GB    disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +922.7 GB   disk2
                                 Physical Stores disk1s2, disk0s2
   1:                APFS Volume Macintosh HD            711.5 GB   disk2s1
   2:                APFS Volume Preboot                 42.8 MB    disk2s2
   3:                APFS Volume Recovery                517.0 MB   disk2s3
   4:                APFS Volume VM                      2.2 GB     disk2s4
 
Le HDD est resté disk0.

Alors passe la commande (copier-coller - copie-la bien jusqu'au list final) :
Bloc de code: 
diskutil eraseVolume free null disk0s3 ; diskutil eraseVolume free null disk0s4 ; diskutil ap resizeContainer disk2 0b ; diskutil list

  • cette commande concaténée : a) supprime les 2 partitions Windows > b) récupère leur espace au Conteneur apfs global et spécifiquement à la partition apfs du HDD > affiche le tableau des disques

Poste l'ensemble de l'affichage retourné --> pour voir s'il n'y a pas eu de blocage en cours d'enchaînement.
 
Bloc de code: 
Started erase on disk0s3 BOOTCAMP
Unmounting disk
Finished erase on disk0
Started erase on disk0s4
Unmounting disk
Finished erase on disk0
Started APFS operation
Aligning grow delta to 100 993 273 856 bytes and targeting a new physical store size of 999 995 129 856 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 999 994 101 760 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 hfs_convert (945.200.129) and last modified by apfs_kext (945.241.4)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
warning: apfs_num_other_fsobjects (267) is not valid (268)
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.241.4)
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.241.4)
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.241.4)
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
The volume /dev/disk1s2 appears to be OK
Storage system check exit code is 0
Growing APFS Physical Store disk0s2 from 899 001 856 000 to 999 995 129 856 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         1000.0 GB  disk0s2

/dev/disk1 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         24.0 GB    disk1
   1:                        EFI EFI                     314.6 MB   disk1s1
   2:                 Apple_APFS Container disk2         23.7 GB    disk1s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.0 TB     disk2
                                 Physical Stores disk1s2, disk0s2
   1:                APFS Volume Macintosh HD            711.5 GB   disk2s1
   2:                APFS Volume Preboot                 42.8 MB    disk2s2
   3:                APFS Volume Recovery                517.0 MB   disk2s3
   4:                APFS Volume VM                      2.2 GB     disk2s4

ça fonctionne très bien, merci beaucoup de ton aide @macomaniac
Bon dimanche
 
Dernière édition par un modérateur:
Salut, moi je galère, je me permets de poster ici car c'est aussi sur Mojave et aussi pour W10 via bootcamp.

Soit avec bootcamp j'ai eu une erreur lorsqu'il essayait de copier les fichiers windows indiquant qu'il ne ne parvient pas à localiser le disque et la partition spécifiée <ImageInstall>. Soit quand j'essaye via une clé USB j'ai au même moment : la partition système EFI est en NTFS, formatez la en FAT32 puis redémarrez l'installation.

Voilà maintenant le bordel accumulé xD... :

Bloc de code: 
/dev/disk0 (internal):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                         121.3 GB   disk0

   1:                        EFI EFI                     314.6 MB   disk0s1

   2:                 Apple_APFS Container disk2         121.0 GB   disk0s2


/dev/disk1 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *2.0 TB     disk1

   1:                        EFI NO NAME                 209.7 MB   disk1s1

   2:                 Apple_APFS Container disk2         1.6 TB     disk1s2

   3:                        EFI NO NAME                 104.9 MB   disk1s5

   4:         Microsoft Reserved                         16.8 MB    disk1s6

   5:                        EFI NO NAME                 104.9 MB   disk1s7

   6:                        EFI NO NAME                 104.9 MB   disk1s8

   7:                        EFI NO NAME                 104.9 MB   disk1s9

   8:                        EFI NO NAME                 104.9 MB   disk1s10

   9:                        EFI NO NAME                 104.9 MB   disk1s12


/dev/disk2 (synthesized):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      APFS Container Scheme -                      +1.7 TB     disk2

                                Physical Stores disk0s2, disk1s2

   1:                APFS Volume Macintosh               702.0 GB   disk2s1

   2:                APFS Volume Preboot                 46.9 MB    disk2s2

   3:                APFS Volume Recovery                522.7 MB   disk2s3

   4:                APFS Volume VM                      2.1 GB     disk2s4


/dev/disk3 (disk image):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:                            CCCOMA_X64FRE_FR-FR... +5.4 GB     disk3
 
Bonjour spirius

Tu as décidé de collectionner les volumes NO NAME sur des partitions de type EFI ? :hilarious:

Passe la commande (copier-coller direct - déroule-la bien jusqu'au list final pour la copier toute) :
Bloc de code: 
diskutil eraseVolume free null disk0s5 ; diskutil eraseVolume free null disk0s6 ; diskutil eraseVolume free null disk0s7 ; diskutil eraseVolume free null disk0s8 ; diskutil eraseVolume free null disk0s9 ; diskutil eraseVolume free null disk0s10 ; diskutil eraseVolume free null disk0s12 ; diskutil ap resizeContainer disk2 0b ; diskutil list

  • cette commande concaténée : a) supprime toutes les petites partitions situées sur le HDD en-dessous de la partition apfs > b) récupère l'ensemble de l'espace libre disponible au Conteneur apfs > c) réaffiche le tableau des disques

Poste l'ensemble de l'affichage retourné --> que je puisse vérifier s'il n'y a pas eu de blocage à un moment donné de l'enchaînement.
 
spiriusmac:~ spirius$ diskutil eraseVolume free null disk0s5 ; diskutil eraseVolume free null disk0s6 ; diskutil eraseVolume free null disk0s7 ; diskutil eraseVolume free null disk0s8 ; diskutil eraseVolume free null disk0s9 ; diskutil eraseVolume free null disk0s10 ; diskutil eraseVolume free null disk0s12 ; diskutil ap resizeContainer disk2 0b ; diskutil list
Unable to find disk for disk0s5
Unable to find disk for disk0s6
Unable to find disk for disk0s7
Unable to find disk for disk0s8
Unable to find disk for disk0s9
Unable to find disk for disk0s10
Unable to find disk for disk0s12
Started APFS operation
Aligning grow delta to 270 919 581 696 bytes and targeting a new physical store size of 1 878 901 370 880 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 1 878 901 370 880 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 was formatted by hfs_convert (945.200.129) and last modified by apfs_kext (945.250.134)
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.250.134)
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.250.134)
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.250.134)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Verifying allocated space
 
warning: Overallocation Detected on Main device: (461649+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461651+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461654+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461659+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461661+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461665+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461670+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461674+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461681+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461686+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461694+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461696+3) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461704+3) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461709+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461711+3) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461715+4) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461720+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461724+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461726+3) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461730+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461733+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461735+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461738+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461741+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461743+4) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461749+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461752+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461755+5) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461760+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461762+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461766+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461769+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461774+4) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461779+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461781+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461783+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461789+3) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461800+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461810+3) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461814+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461818+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461820+3) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461824+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461826+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461829+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461832+5) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461838+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461841+2) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461844+1) bitmap address (51cb)
warning: Overallocation Detected on Main device: (461846+2) bitmap address (51cb)
too many warnings generated; suppressing subsequent ones
The volume /dev/disk0s2 appears to be OK
 
Storage system check exit code is 0
Growing APFS Physical Store disk1s2 from 1 607 981 789 184 to 1 878 901 370 880 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 121.3 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk2 121.0 GB disk0s2

/dev/disk1 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk1
1: EFI NO NAME 209.7 MB disk1s1
2: Apple_APFS Container disk2 1.9 TB disk1s2
3: EFI NO NAME 104.9 MB disk1s5
4: Microsoft Reserved 16.8 MB disk1s6
5: EFI NO NAME 104.9 MB disk1s7
6: EFI NO NAME 104.9 MB disk1s8
7: EFI NO NAME 104.9 MB disk1s9
8: EFI NO NAME 104.9 MB disk1s10
9: EFI NO NAME 104.9 MB disk1s12

/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +2.0 TB disk2
Physical Stores disk0s2, disk1s2
1: APFS Volume Macintosh 702.1 GB disk2s1
2: APFS Volume Preboot 46.9 MB disk2s2
3: APFS Volume Recovery 522.7 MB disk2s3
4: APFS Volume VM 2.1 GB disk2s4

/dev/disk3 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: CCCOMA_X64FRE_FR-FR... +5.4 GB disk3

VOILA
 
Tu as oublié de poster le retour dans une fenêtre de code. En ce qui me concerne > j'ai fait un lapsus sur l'index du disque concerné (car tu as 2 disques internes : un SSD & un HDD associés en mode Fusion Drive) --> j'ai mis disk0-- alors qu'il fallait disk1--. On est donc à égalité en terme de bévue :hilarious:.

Qu'à cela ne tienne ! Voici ma commande éditée avec le bon index de disque -->
Bloc de code: 
diskutil eraseVolume free null disk1s5 ; diskutil eraseVolume free null disk1s6 ; diskutil eraseVolume free null disk1s7 ; diskutil eraseVolume free null disk1s8 ; diskutil eraseVolume free null disk1s9 ; diskutil eraseVolume free null disk1s10 ; diskutil eraseVolume free null disk1s12 ; diskutil ap resizeContainer disk2 0b ; diskutil list

  • repasse-la en copier-coller > puis poste le retour en veillant bien (pour la lisibilité et la réduction de place du tableau) --> à coller dans une fenêtre de code comme je l'avais décrit.
 
Malgré les balises codes j'ai ça :
 

Fichiers joints

  • Capture d’écran 2019-05-11 à 16.25.33.jpg
    Capture d’écran 2019-05-11 à 16.25.33.jpg
    256,5 KB · Affichages: 221
Bloc de code: 
spiriusmac:~ spirius$ diskutil eraseVolume free null disk1s5 ; diskutil eraseVolume free null disk1s6 ; diskutil eraseVolume free null disk1s7 ; diskutil eraseVolume free null disk1s8 ; diskutil eraseVolume free null disk1s9 ; diskutil eraseVolume free null disk1s10 ; diskutil eraseVolume free null disk1s12 ; diskutil ap resizeContainer disk2 0b ; diskutil list
Started erase on disk1s5 NO NAME
Unmounting disk
Finished erase on disk1
Started erase on disk1s6
Unmounting disk
Finished erase on disk1
Started erase on disk1s7 NO NAME
Unmounting disk
Finished erase on disk1
Started erase on disk1s8 NO NAME
Unmounting disk
Finished erase on disk1
Started erase on disk1s9 NO NAME
Unmounting disk
Finished erase on disk1
Started erase on disk1s10 NO NAME
Unmounting disk
Finished erase on disk1
Started erase on disk1s12 NO NAME
Unmounting disk
Finished erase on disk1
Started APFS operation
Aligning grow delta to 121 287 806 976 bytes and targeting a new physical store size of 2 000 189 177 856 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 2 000 188 149 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 was formatted by hfs_convert (945.200.129) and last modified by apfs_kext (945.250.134)
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.250.134)
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.250.134)
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.250.134)
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
 
Bloc de code: 
warning: Overallocation Detected on Main device: (461649+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461651+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461654+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461659+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461661+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461665+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461670+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461674+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461681+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461686+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461694+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461696+3) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461704+3) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461709+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461711+3) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461715+4) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461720+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461724+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461726+3) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461730+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461733+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461735+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461738+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461741+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461743+4) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461749+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461752+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461755+5) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461760+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461762+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461766+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461769+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461774+4) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461779+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461781+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461783+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461789+3) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461800+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461810+3) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461814+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461818+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461820+3) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461824+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461826+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461829+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461832+5) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461838+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461841+2) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461844+1) bitmap address (147a9)
warning: Overallocation Detected on Main device: (461846+2) bitmap address (147a9)
 

Sujets similaires

S
Boot Camp effacé avec utilitaire de disques
Réponses
10
Affichages
2K
Windows sur Mac
stephnadege
S
P
Supprimer partition Windows sans l'OS (Boot camp)
Réponses
23
Affichages
3K
Windows sur Mac
prohibition
P
J
prob bootcamp et partition
Réponses
7
Affichages
2K
Windows sur Mac
juko
J
Aski
macOS Ventura No CoreStorage logical volume groups found
Réponses
6
Affichages
805
macOS
Locke
Locke
O
macOS Monterey Aide Fusion Partitions
Réponses
8
Affichages
1K
macOS
Locke
Locke
Haut Bas