10.12 Sierra impossible de fusionner deux partitions sous sierra

[Jabaloo]

Et voici dans un premier temps !

-bash-3.2# diskutil repairVolume disk2

Started file system repair on disk2
Repairing storage system
Performing fsck_apfs -y -x /dev/disk0s2
Checking the container superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking volume
Checking the APFS volume superblock
The volume DISQUE DUR HD 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 snapshot 1 of 4
error: directory valence check: directory (oid 0xe002e): nchildren (6) does not match drec count (0)
warning: snapshot fsroot tree corruptions are not repaired; they'll go away once the snapshot is deleted
Checking snapshot 2 of 4
error: directory valence check: directory (oid 0xe002e): nchildren (6) does not match drec count (0)
Checking snapshot 3 of 4
error: directory valence check: directory (oid 0xe002e): nchildren (6) does not match drec count (0)
Checking snapshot 4 of 4
error: directory valence check: directory (oid 0xe002e): nchildren (6) does not match drec count (0)
Checking the extent ref tree
Checking the fsroot tree
error: directory valence check: directory (oid 0xe002e): nchildren (6) does not match drec count (0)
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
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
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
Performing deferred repairs
error: nchildren of inode object (id 917550) does not match expected value
Restarting after deferred repairs
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 DISQUE DUR HD 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 snapshot 1 of 4
error: directory valence check: directory (oid 0xe002e): nchildren (6) does not match drec count (0)
Checking snapshot 2 of 4
error: directory valence check: directory (oid 0xe002e): nchildren (6) does not match drec count (0)
Checking snapshot 3 of 4
error: directory valence check: directory (oid 0xe002e): nchildren (6) does not match drec count (0)
Checking snapshot 4 of 4
error: directory valence check: directory (oid 0xe002e): nchildren (6) does not match drec count (0)
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
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record

 

[Jabaloo]

et voila le reste !

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
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Finished file system repair on disk2
-bash-3.2#

 

[Membre supprimé 1060554]

Il y a eu 2 passes de réparation --> apparemment la 2è passe a réussi a obtenir un code de sortie de la vérification = 0 (comme zéro faute).

Enchaîne avec la commande :

diskutil ap resizeContainer disk2 0b ; diskutil list

• le 0 de 0b = zéro ; mets bien un point-virgule ; entre 0b et diskutil

• la commande récupère l'espace libre au Conteneur apfs > puis affiche le tableau des disques

Poste l'affichage d'ensemble retourné par la commande.

 

[Jabaloo]

-bash-3.2# diskutil ap resizeContainer disk2 0b ; diskutil list
Started APFS operation
Aligning grow delta to 59 685 384 192 bytes and targeting a new physical store size of 250 685 575 168 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 250 684 547 072 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Performing fsck_apfs -n -x -S /dev/disk0s2
Checking the container superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking volume
Checking the APFS volume superblock
The volume DISQUE DUR HD 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
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
warning: directory valence check: directory (oid 0xe002e): orphan directory record
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

 

[Jabaloo]

Verifying allocated space
warning: Overallocation Detected on Main device: (34+2) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (41+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (262+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (506+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (2813+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (3027+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (3030+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (3084+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (3193+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (4322+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (4703+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (4837+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (4914+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (7875+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (7892+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (7905+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (7932+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (7938+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8079+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8082+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8084+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8121+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8153+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8186+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8189+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8197+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8260+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8393+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8419+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8451+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8571+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8583+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8619+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8628+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8637+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8649+2) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8661+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8665+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8685+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8733+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8747+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8758+1) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8762+2) bitmap address (cdc9b)
warning: Overallocation Detected on Main device: (8845+1) bitmap address (cdc9b)
too many warnings generated; suppressing subsequent ones

 

[Jabaloo]

Et pour finir

The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Growing APFS Physical Store disk0s2 from 191 000 190 976 to 250 685 575 168 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         251.0 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk2         250.7 GB   disk0s2

/dev/disk1 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +2.1 GB     disk1
   1:                  Apple_HFS macOS Base System       2.0 GB     disk1s1

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +250.7 GB   disk2
                                 Physical Store disk0s2
   1:                APFS Volume DISQUE DUR HD           166.2 GB   disk2s1
   2:                APFS Volume Preboot                 47.2 MB    disk2s2
   3:                APFS Volume Recovery                522.7 MB   disk2s3
   4:                APFS Volume VM                      1.1 GB     disk2s4

/dev/disk3 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +5.2 MB     disk3

/dev/disk4 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk4

/dev/disk5 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk5

/dev/disk6 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk6

/dev/disk7 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk7

/dev/disk8 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk8

/dev/disk9 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk9

/dev/disk10 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +12.6 MB    disk10

/dev/disk11 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +4.2 MB     disk11

/dev/disk12 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +1.0 MB     disk12
/dev/disk13 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk13

/dev/disk14 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk14

/dev/disk15 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk15

/dev/disk16 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +1.0 MB     disk16

/dev/disk17 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +6.3 MB     disk17

/dev/disk18 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +6.3 MB     disk18

/dev/disk19 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +524.3 KB   disk19

/dev/disk20 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            untitled               +2.1 MB     disk20

 

[Membre supprimé 1060554]

Comme tu as pu le constater > il y a encore des erreurs (mais non invalidantes) dans le système de fichiers apfs.

Qui n'ont pas bloqué la récupération d'espace comme tu peux le voir ici -->

/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         251.0 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk2         250.7 GB   disk0s2

• ton problème spécifique est donc résolu.

Tu peux redémarrer (Menu  > Disque de démarrage) > choisir DISQUE DUR HD > redémarrer dessus. Ce qui va te ramener à ta session habituelle d'utilisateur.

 

[Jabaloo]

Oui mon problème est résolu, merci grandement pour votre aide et votre précieux temps !

J'ai une autre question si ce n'est trop vous demander, est il possible d'installer windows avec Boot Camp sur un disque dur externe ?

 

[Membre supprimé 1060554]

En ce qui concerne ta question d'une installation externe de Windows -->

- il vaudra mieux que tu attendes un avis de Locke qui connaît le sujet. Pour ma part > je n'ai jamais utilisé Windows ni ne l'utiliserai jamais > ce qui fait que mon expertise à ce sujet est aussi mince que mon intérêt ​

=> tu pourrais envisager de créer un nouveau sujet > sur le forum Windows sur Mac.

 

[Jabaloo]

Très bien c'est ce que je vais faire.
Je vous remercie encore pour votre aide et votre temps.

 

[Locke]

J'ai une autre question si ce n'est trop vous demander, est il possible d'installer windows avec Boot Camp sur un disque dur externe ?

Une grosse lecture à faire... https://forums.macg.co/threads/installation-de-windows-10-1803.1310171/ ...et en particulier la réponse #2. Donc, en clair il faut d'abord passer impérativement par une installation dans le disque dur interne et utiliser Winclone et un disque dur exclusivement en Thunderbolt. Toute autre tentative sera vouée à un échec et je précise encore une fois : il n'y a pas d'autre alternative.

 

[theobelrep]

Bonjour à tous !

J'ai en possession un iMac et j'ai voulu faire la manipulation pour installer BootCamp, manque de bol, j'ai installé la mauvaise version de windows (je voulais windows 10, et j'ai installer le windows 8),
Connaissant pourtant la manipulation pour retirer la partition BootCamp afin de la réinstaller sous Windows 10, j'ai malheureusement supprimé la partition BootCamp via l'utilitaire de disque.. De ce fait, BootCamp ne reconnais plus la partition et je me retrouve avec deux partitions.

Essayant à plusieurs reprise de solutionner le problème avec ce forum, je ne sais pas comment j'ai pu le faire mais j'ai maintenant 4 partitions différentes (dont Macintosh HD qui est la principale).

Est-ce que vous auriez la solution afin de rendre mon iMac comme sorti d'usine avec seulement une seule partition avec toute la capacité de stockage récupérée ?

Je vous en remercie d'avance.

 

[Membre supprimé 1060554]

Bonsoir theobelrep

Voici comment tu vas pouvoir fournir les informations de base -->

- va à : Applications > Utilitaires > lance le «Terminal». Dans la fenêtre ouverte > saisis la commande (informative) :

diskutil list

et ↩︎ (presse la touche "Entrée" du clavier pour exécuter la commande)

• tu vas voir s'afficher le tableau des disques attachés au Mac (en interne / externe) > avec leurs paramètres de tables de partition > partitions > Conteneur CoreStorage si présent > Conteneur apfs si présent

Poste ce tableau ici en copier-coller (pas de capture) > mais attention ! > avant de faire ton coller -->

• dans cette page de MacGé > presse le bouton
  
  ici :
  
  
  menu  : </> Code > par ⌘V colle dans la fenêtre Code > presse le bouton Insérer (ce procédé permet un affichage fenêtré qui économise l'espace de page en respectant la mise en forme des tableaux du «Terminal» --> d'où une plus grande lisibilité)

=> ces informations montreront la configuration du disque.

Note : il n'y a que les tableaux du Terminal qui me sont explicites > les affichages graphiques de l'Utilitaire de disque m'embrouillent.

 

[theobelrep]

diskutil list
/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         1.4 TB     disk1s2
   3:       Microsoft Basic Data                         615.6 GB   disk1s3
   4:                 Apple_APFS Container disk3         268.4 MB   disk1s4
   5:                 Apple_APFS Container disk4         993.6 GB   disk1s5

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

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +268.4 MB   disk3
                                 Physical Store disk1s4

/dev/disk4 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +993.6 GB   disk4
                                 Physical Store disk1s5

imac-de-theo:~ theobelrepayre$

 

[Membre supprimé 1060554]

Passe la commande (copier-coller direct - copie-la bien jusqu'au list final) -->

diskutil ap deleteContainer disk3 ; diskutil ap deleteContainer disk4 ; diskutil eraseVolume free null disk1s3 ; diskutil eraseVolume free null disk1s4 ; diskutil eraseVolume free null disk1s5 ; diskutil ap resizeContainer disk2 0b ; diskutil list

• cette commande concaténée : a) supprime le Conteneur du bas disk3 (ce qui reformate un volume Untitled sur la partition disk1s4) > b) supprime le Conteneur du bas disk4 (ce qui reformate un volume Untitled sur la partition disk1s5) > c) supprime la partition disk1s3 > d) supprime la partition disk1s4 > e) supprime la partition disk1s5 > f) récupère l'ensemble de l'espace libéré au Conteneur disk2 du Fusion Drive > g) réaffiche le tableau des disques

Poste l'ensemble de l'affichage retourné (en plusieurs message si nécessaire) --> que je voie s'il n'y a pas eu de blocage à un moment donné de l'enchaînement (et si oui lequel).

 

[theobelrep]

diskutil list
/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         3.0 TB     disk1s2

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

imac-de-theo:~ theobelrepayre$

 

[theobelrep]

Tout est rentré dans l'ordre ! Merci infiniment @macomaniac ! Du génie

 

[theobelrep]

Je devrai pouvoir réinstaller BootCamp sans problème je pense.

 

[Membre supprimé 1060554]

Content pour toi !

 

[Membre supprimé 1060554]

Note : tu peux relancer l'Assistant BootCamp, en effet.