bonjour j'aimerai savoir comment fair avec boot camp j'ai ce probleme Le disque de démarrage doit êt

[mateo0302]

Verifying allocated space
warning: Overallocation Detected on Main device: (462052+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462055+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462058+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462060+2) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462063+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462066+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462069+2) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462076+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462080+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462085+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462089+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462095+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462097+2) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462106+2) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462109+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462118+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462120+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462123+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462126+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462129+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462137+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462140+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462145+3) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462161+2) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462164+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462167+2) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462170+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462174+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462177+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462179+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462184+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462189+2) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462197+2) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462207+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462217+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462225+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462228+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462233+2) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462244+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462247+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462249+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462255+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462258+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462260+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462264+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462268+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462271+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462275+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462280+1) bitmap address (17bc9)
warning: Overallocation Detected on Main device: (462284+1) bitmap address (17bc9)
too many warnings generated; suppressing subsequent ones

 

[mateo0302]

Performing deferred repairs
error: found file extent gap (id 17) at logical address 0+955146240
Deferred repairs failed
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                        *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.7 TB     disk1s2
   3:                  Apple_HFS Untitled                302.7 GB   disk1s3

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +2.8 TB     disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD            1.7 TB     disk2s1
   2:                APFS Volume Preboot                 42.9 MB    disk2s2
   3:                APFS Volume Recovery                509.8 MB   disk2s3
   4:                APFS Volume VM                      24.6 KB    disk2s4

[/code]

Je l'ai fait en trois fois car il y avait plus que 5000 caractères

 

[Membre supprimé 1060554]

Édit. Je reposte à la suite.

 

[Membre supprimé 1060554]

Il y a une erreur dans l'apfs du Fusion Drive qu'il faut tenter de réparer.

Redémarre > les 2 touches ⌘R (cmd R) pressées pour démarrer en mode secours. Tu obtiens un écran affichant une fenêtre de 4 Utilitaires macOS = écran de la session de secours.

- lance l'Utilitaire de disque. Dans l'angle supérieur gauche du panneau > fais un clic sur la pastille : "Présentation". Sélectionne : "Afficher tous les appareils" --> le Conteneur apfs est affiché.​

- sélectionne-le > presse le bouton : "S.O.S." --> afin de lancer une réparation.​

Cela fait > redémarre (Menu  > Redémarrer). Ta session d'utilisateur réouverte > passe la commande :

diskutil verifyVolume disk2

• qui vérifie l'apfs du Fusion Drive

Poste le retour.

 

[mateo0302]

Started file system verification on disk2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l /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.260.7)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking snapshot 1 of 7
Checking snapshot 2 of 7
Checking snapshot 3 of 7
Checking snapshot 4 of 7
Checking snapshot 5 of 7
Checking snapshot 6 of 7
Checking snapshot 7 of 7
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
error: found file extent gap (id 17) at logical address 955146240 (expected 0)
Verifying allocated space
Performing deferred repairs
error: found file extent gap (id 17) at logical address 0+955146240
Deferred repairs failed
The volume /dev/disk1s2 could not be verified completely
Storage system check exit code is 8
Error: -69716: Storage system verify or repair failed
Underlying error: 8

Et voila @macomaniac

 

[Membre supprimé 1060554]

L'apfs n'a pas pu être réparé.

Je note que tu as 7 snapshots (instantanés du volume Macintosh HD rétenteurs d'espace de blocs).

----------

Pour fermer le robinet des snapshots --> va à : Menu  > Préférences Système > Time Machine => décoche la case de l'option : "Sauvegarder automatiquement".

----------

Pour supprimer en lot les snapshots > passe la commande (copier-coller) :

sudo tmutil thinlocalsnapshots / 99000000000000 4 ; say 'ENFIN TERMINÉ LA PURGE'

• à validation > une demande de password s'affiche (commande sudo) --> tape ton mot-de-passe de session admin en aveugle - aucun caractère ne se montrant à la frappe - et revalide

• la commande supprime en lot les snapshots. Attends d'entendre une voix déclarer : "Enfin ! terminé la purge..." en signal de fin

Cela fait > redémarre une fois > de retour dans ta session > repasse la commande :

diskutil list

• qui affiche la configuration des disques

Poste le retour (on verra déjà si l'occupation de Macintosh HD a varié).

------------

note 1 : l'existence de snapshots peut bloquer un redimensionnement.

note 2 : il y a plein de problèmes divers --> on essaie de les régler.

 

[mateo0302]

/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.7 TB     disk1s2
   3:                  Apple_HFS Untitled                302.7 GB   disk1s3

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +2.8 TB     disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD            1.7 TB     disk2s1
   2:                APFS Volume Preboot                 42.9 MB    disk2s2
   3:                APFS Volume Recovery                509.8 MB   disk2s3
   4:                APFS Volume VM                      24.6 KB    disk2s4

Et voila @macomaniac

 

[Membre supprimé 1060554]

Bon : Macintosh HD est toujours occupé pour 1,7 To = zéro changement.

Passe encore la commande :

fdesetup status

• qui affiche le statut de FileVault (logiciel de chiffrement)

Poste le retour (c'est pour savoir si l'activation de FileVault pourrait jouer un rôle).

 

[mateo0302]

FileVault is Off.

Voila @macomaniac

 

[Membre supprimé 1060554]

Bon : une piste qui tourne court.

J'ai vu dans la vérification que l'apfs du volume VM (Virtual Memory : dédié à l'archivage de la RAM et du swap) --> recelait une erreur. Il n'a que 24 Ko d'occupation seulement - ce qui est anormal.

Passe la commande :

diskutil umount force disk2s4 ; diskutil ap deleteVolume disk2s4

• qui démonte VM (monté dans Macintosh HD at: /private/var/vm) > puis le supprime du Conteneur

Poste les retours.

 

[mateo0302]

Bon : une piste qui tourne court.

J'ai vu dans la vérification que l'apfs du volume VM (Virtual Memory : dédié à l'archivage de la RAM et du swap) --> recelait une erreur. Il n'a que 24 Ko d'occupation seulement - ce qui est anormal.

Passe la commande :

diskutil umount force disk2s4 ; diskutil ap deleteVolume disk2s4

• qui démonte VM (monté dans Macintosh HD at: /private/var/vm) > puis le supprime du Conteneur

Poste les retours.

Et voila @macomaniac

 

[Membre supprimé 1060554]

Tu as passé les commandes ? - si oui > quel a été le retour ?

 

[mateo0302]

Volume VM on disk2s4 force-unmounted
Started APFS operation
Deleting APFS Volume from its APFS Container
Unmounting disk2s4
Deleting Volume
Removing any Preboot and Recovery Directories
Finished APFS operation

désolé il y a eu un probleme @macomaniac

 

[Membre supprimé 1060554]

Alors à présent > redémarre une fois (ce qui recréera le volume VM dans l'opération).

- de retour dans ta session > repasse la commande :

diskutil list

• et poste le tableau des disques.

 

[mateo0302]

/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.7 TB     disk1s2
   3:                  Apple_HFS Untitled                302.7 GB   disk1s3

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +2.8 TB     disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD            1.7 TB     disk2s1
   2:                APFS Volume Preboot                 42.9 MB    disk2s2
   3:                APFS Volume Recovery                509.8 MB   disk2s3

Et voila @macomaniac

 

[Membre supprimé 1060554]

Tu as bien redémarré ? -- car je ne vois pas de recréation d'un volume VM...

 

[mateo0302]

/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.7 TB     disk0s2
   3:                  Apple_HFS Untitled                302.7 GB   disk0s3

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

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

Peut etre maintenant @macomaniac

/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.7 TB     disk0s2
   3:                  Apple_HFS Untitled                302.7 GB   disk0s3

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

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

peut etre maintenant @macomaniac

Et oui j'ai redemarre

 

[Membre supprimé 1060554]

Cette ligne -->

   4:                APFS Volume VM                      2.1 GB     disk2s4

• montre que le volume VM a été recréé et a une occupation de 2,1 Go (= normal). Ce volume doit être redevenu valide.

Repasse donc la commande :

diskutil verifyVolume disk2

• qui vérifie encore l'apfs

Poste le retour.

 

[mateo0302]

Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l /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.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.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
Verifying allocated space
The volume /dev/disk1s2 appears to be OK
Storage system check exit code is 0
Finished file system verification on disk2

Et voila @macomaniac

 

[Membre supprimé 1060554]

Hé ! hé ! --> après toutes ces manipulations --> il y a zéro erreurs dans l'apfs.

On revient donc au principal : la récupération de l'espace manquant - pris par une partition superflue. Repasse un :

diskutil list

• et reposte le tableau des disques --> que je sois sûr de l'index de disque du HDD.