Problème de partitionnement de disque pour installation de Windows

[Duodecim]

Bonjour macomaniac ! Merci pour ta réponse rapide ! J'ai fait le test, il semble y avoir pas mal de problèmes. Voilà ce que j'ai obtenu :

Started file system verification on disk2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l /dev/disk0s2
Checking the container superblock
Checking the fusion superblock
Checking the EFI jumpstart record
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking the Fusion data structures
Checking volume
Checking the APFS volume superblock
The volume Macintosh HD - Données was formatted by hfs_convert (945.200.129) and last modified by apfs_kext (1412.41.1)
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 (1412.41.1)
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 (1412.41.1)
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 (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume Macintosh HD was formatted by diskmanagementd (1412.41.1) and last modified by apfs_kext (1412.41.1)
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: MT mapping (0x4000004b8f309 -> 0xac226, 1, C) is not completely referenced
warning: MT mapping (0x4000004bbcd66 -> 0xac9d5, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc515f -> 0xa8082, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc51af -> 0x340028, 4, C) is not completely referenced
warning: MT mapping (0x4000004bc51b3 -> 0x475199, 5, C) is not completely referenced
warning: MT mapping (0x4000004bc551a -> 0xa8117, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc58e6 -> 0xa814d, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5906 -> 0xa814e, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5915 -> 0x340070, 4, C) is not completely referenced
warning: MT mapping (0x4000004bc5919 -> 0xa814f, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc594d -> 0x5c0078, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc59a2 -> 0xa8163, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc59aa -> 0x5c007b, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc59ad -> 0x338080, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc59ca -> 0x338086, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc5a23 -> 0xa8169, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5a4f -> 0xa8171, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5a52 -> 0x5c008a, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc5a5d -> 0x338096, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc5a65 -> 0x5c0093, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc5a70 -> 0x3400ac, 4, C) is not completely referenced
warning: MT mapping (0x4000004bc5a74 -> 0x5c0096, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc5a77 -> 0xa8176, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5af0 -> 0xa81a6, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5bc5 -> 0x3400cc, 4, C) is not completely referenced
warning: MT mapping (0x4000004bc5bcc -> 0x47935d, 5, C) is not completely referenced
warning: MT mapping (0x4000004bc5c09 -> 0x3400d8, 4, C) is not completely referenced
warning: MT mapping (0x4000004bc5c0d -> 0x479383, 9, C) is not completely referenced
warning: MT mapping (0x4000004bc5c19 -> 0xa81d8, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc5c66 -> 0x3380b8, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc5c68 -> 0xa81da, 4, C) is not completely referenced
warning: MT mapping (0x4000004bc5e07 -> 0xa8252, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc5e0d -> 0xa8259, 5, C) is not completely referenced
warning: MT mapping (0x4000004bc5e36 -> 0xa8260, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc5eac -> 0xa8265, 5, C) is not completely referenced
warning: MT mapping (0x4000004bc5eb5 -> 0xa826b, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc5ec5 -> 0xa826f, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5ec8 -> 0xa8271, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5ecb -> 0xa8275, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc600c -> 0xa82a2, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc6094 -> 0xa803e, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc6095 -> 0xa804b, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc6096 -> 0xa804d, 1, C) is not completely referenced
warning: MT mapping (0x4000004bca6e8 -> 0xa8090, 1, C) is not completely referenced
warning: MT mapping (0x4000004bca708 -> 0x340088, 4, C) is not completely referenced
warning: MT mapping (0x4000004bca70c -> 0x47abee, 9, C) is not completely referenced
warning: MT mapping (0x4000004bca76c -> 0xa8094, 1, C) is not completely referenced
warning: MT mapping (0x4000004bca786 -> 0xa809b, 1, C) is not completely referenced
warning: MT mapping (0x4000004bca789 -> 0x5c0024, 3, C) is not completely referenced
warning: MT mapping (0x4000004bca78c -> 0xa80a0, 1, C) is not completely referenced
Too many warnings of this type generated; suppressing subsequent ones
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Finished file system verification on disk2

 

[Membre supprimé 1060554]

Il y a un problème d'allocation d'espace de blocs -->

- passe la commande :​

fdesetup status

• qui affiche le statut de FileVault

Poste le retour (c'est pour savoir s'il y aura des volumes verrouillés si tu ouvres la session de secours).

 

[Duodecim]

Le Terminal m'indique :

FileVault is Off.

 

[Membre supprimé 1060554]

FileVault désactivé -->

- redémarre > les 2 touches ⌘R (cmd R) tenues pressées pour ouvrir la session de secours (écran affichant une fenêtre de 4 Utilitaires macOS).​

- lance l'Utilitaire de disque. Presse la pastille : "Présentation" (angle gauche supérieur du panneau) > "Afficher tous les appareils" => le Conteneur apfs global est affiché.​

- sélectionne le Conteneur global > fais un S.O.S. dessus.​

Cela fait > quitte l'Utilitaire de disque & redémarre (Menu  > Redémarrer) -->

- ta session ré-ouverte > repasse la commande :​

diskutil verifyVolume disk2

• et re-poste l'affichage de la vérification => qu'on voie s'il y a eu réparation de l'allocation des blocs.

 

[Duodecim]

J'ai fait tout ce que tu as indiqué, toutefois, le conteneur dans l'Utilitaire de disque était le disk3, et non le disk2. Voilà le résultat de la vérification du disk2, identique me semble-t-il à tout à l'heure :

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 - Données was formatted by hfs_convert (945.200.129) and last modified by apfs_kext (1412.41.1)
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 (1412.41.1)
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 (1412.41.1)
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 (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume Macintosh HD was formatted by diskmanagementd (1412.41.1) and last modified by apfs_kext (1412.41.1)
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: MT mapping (0x40000002edcf0 -> 0xa98bd, 1, D) is not completely referenced
warning: MT mapping (0x4000004b8f309 -> 0xac226, 1, C) is not completely referenced
warning: MT mapping (0x4000004bbcd66 -> 0xac9d5, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc515f -> 0xa8082, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc51af -> 0x340028, 4, C) is not completely referenced
warning: MT mapping (0x4000004bc51b3 -> 0x475199, 5, C) is not completely referenced
warning: MT mapping (0x4000004bc551a -> 0xa8117, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc58e6 -> 0xa814d, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5906 -> 0xa814e, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5915 -> 0x340070, 4, C) is not completely referenced
warning: MT mapping (0x4000004bc5919 -> 0xa814f, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc594d -> 0x5c0078, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc59a2 -> 0xa8163, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc59aa -> 0x5c007b, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc59ad -> 0x338080, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc59ca -> 0x338086, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc5a23 -> 0xa8169, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5a4f -> 0xa8171, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5a52 -> 0x5c008a, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc5a5d -> 0x338096, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc5a65 -> 0x5c0093, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc5a70 -> 0x3400ac, 4, C) is not completely referenced
warning: MT mapping (0x4000004bc5a74 -> 0x5c0096, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc5a77 -> 0xa8176, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5af0 -> 0xa81a6, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5bc5 -> 0x3400cc, 4, C) is not completely referenced
warning: MT mapping (0x4000004bc5bcc -> 0x47935d, 5, C) is not completely referenced
warning: MT mapping (0x4000004bc5c09 -> 0x3400d8, 4, C) is not completely referenced
warning: MT mapping (0x4000004bc5c0d -> 0x479383, 9, C) is not completely referenced
warning: MT mapping (0x4000004bc5c19 -> 0xa81d8, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc5c66 -> 0x3380b8, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc5c68 -> 0xa81da, 4, C) is not completely referenced
warning: MT mapping (0x4000004bc5e07 -> 0xa8252, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc5e0d -> 0xa8259, 5, C) is not completely referenced
warning: MT mapping (0x4000004bc5e36 -> 0xa8260, 2, C) is not completely referenced
warning: MT mapping (0x4000004bc5eac -> 0xa8265, 5, C) is not completely referenced
warning: MT mapping (0x4000004bc5eb5 -> 0xa826b, 3, C) is not completely referenced
warning: MT mapping (0x4000004bc5ec5 -> 0xa826f, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5ec8 -> 0xa8271, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc5ecb -> 0xa8275, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc600c -> 0xa82a2, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc6094 -> 0xa803e, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc6095 -> 0xa804b, 1, C) is not completely referenced
warning: MT mapping (0x4000004bc6096 -> 0xa804d, 1, C) is not completely referenced
warning: MT mapping (0x4000004bca6e8 -> 0xa8090, 1, C) is not completely referenced
warning: MT mapping (0x4000004bca708 -> 0x340088, 4, C) is not completely referenced
warning: MT mapping (0x4000004bca70c -> 0x47abee, 9, C) is not completely referenced
warning: MT mapping (0x4000004bca76c -> 0xa8094, 1, C) is not completely referenced
warning: MT mapping (0x4000004bca786 -> 0xa809b, 1, C) is not completely referenced
warning: MT mapping (0x4000004bca789 -> 0x5c0024, 3, C) is not completely referenced
Too many warnings of this type generated; suppressing subsequent ones
The volume /dev/disk1s2 appears to be OK
Storage system check exit code is 0
Finished file system verification on disk2

 

[Membre supprimé 1060554]

Oui : toujours le même problème.

- il manque 130 Go au Conteneur du Fusion Drive. Espace libre de bas de HDD sans doute. Passe la commande test (copier-coller) :​

diskutil ap resizeContainer disk2 0b ; diskutil list

• qui récupère l'espace libre > puis réaffiche le tableau des disques

Poste le retour intégral => que je voie si ton Conteneur est extensible en taille.

 

[Duodecim]

Voilà ce que j'ai :

Started APFS operation
Aligning grow delta to 129 680 216 064 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 - Données was formatted by hfs_convert (945.200.129) and last modified by apfs_kext (1412.41.1)
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 (1412.41.1)
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 (1412.41.1)
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 (1412.41.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
Checking volume
Checking the APFS volume superblock
The volume Macintosh HD was formatted by diskmanagementd (1412.41.1) and last modified by apfs_kext (1412.41.1)
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
Growing APFS Physical Store disk0s2 from 870 314 913 792 to 999 995 129 856 bytes
Modifying partition map
Growing APFS data structures
APFS Container Resize error code is 49180
A problem occurred; undoing all changes
Modifying partition map
Error: -69606: A problem occurred while resizing APFS Container structures
/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         870.3 GB   disk0s2

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

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +898.0 GB   disk2
                                 Physical Stores disk1s2, disk0s2
   1:                APFS Volume Macintosh HD - Données  497.2 GB   disk2s1
   2:                APFS Volume Preboot                 81.9 MB    disk2s2
   3:                APFS Volume Recovery                528.5 MB   disk2s3
   4:                APFS Volume VM                      2.1 GB     disk2s4
   5:                APFS Volume Macintosh HD            10.7 GB    disk2s5

 

[Membre supprimé 1060554]

Voici la sanction -->

APFS Container Resize error code is 49180
A problem occurred; undoing all changes
Modifying partition map
Error: -69606: A problem occurred while resizing APFS Container structures

• une erreur interne à l'apfs => proscrit toute modification de la taille actuelle du Conteneur apfs (aussi bien en augmentation qu'en diminution). Erreur non réparable.

Tu as dans les 508 Go de données (Système et utilisateur). Il te faudrait un DDE USB > avec dans les 550 Go d'espace disponible (et un format apfs du volume d'accueil) => pour cloner la distribution Catalina > démarrer sur le clone > supprimer l'apfs interne (= le Fusion Drive) > recréer le Fusion Drive apfs sans errreur > cloner à rebours la distribution du clone => dans le nouveau Conteneur du Fusion Drive.

 

[Duodecim]

Je souhaiterais repartir sur une installation propre. Est-ce qu'il est possible de booter macOS Catalina sur une clé USB de 64 Go que je formaterai en APFS ? Autre question : comment supprimer un FD et le recréer ensuite via l'Utilitaire de disque ? Merci pour le temps que tu passes à m'expliquer tout ça, c'est épineux…

 

[Membre supprimé 1060554]

Tu veux supprimer toutes les données sans les sauvegarder ?

- si c'était le cas > il est faclie de démarrer sur l'OS de secours > supprimer / recréer le Fusion Drive (via la terminal de cette session) > puis réinstaller Catalina.​

 

[Duodecim]

Mes données sont déjà toutes sauvegardées, il y a 300-350 Go de projet Final Cut Pro X qui sont dans mon gros disque dur. Comme ça, ça m'évite de faire la procédure du clonage et tout, tout en repartant sur de bonnes bases. J'ai tenté de supprimer mon Fusion Drive, avec en message d'erreur :

No CoreStorage logical volume groups found

J'ai essayé de chercher sur le forums des manipulations, mais aucune ne semble correspondre à mon cas et je n'ai pas envie de faire des commandes sur le Terminal au hasard…

 

[Membre supprimé 1060554]

Est-ce que tu es dans une session de secours actuellement ou dans ta session habituelle d'utilisateur ?

 

[Duodecim]

J’ai allumé l’ordinateur et mis le mode Récupération via Cmd+R, puis j’ai ouvert le Terminal via l’onglet Utilitaires, en haut.

 

[Membre supprimé 1060554]

Passe la commande :

diskutil list internal

• qui affiche la configuration des disques internes seule

Voici comment tu vas pouvoir poster ici ce tableau sans avoir besoin de prendre de photo -->

• tu sélectionnes le tableau > ⌘C pour le copier dans le presse-papier > ⌘Q pour quitter le «Terminal» > option  : "Obtenir de l'aide en ligne" (dans la fenêtre des 4 Utilitaires) > ce qui lance un navigateur «Safari»

• page Apple par défaut > un clic sur l'adresse de haut de page pour l'éditer > saisis  : macgénération (tout court  : c'est une barre de recherche Google) et valide > tu atteins le site MacGé > Forums > te connectes > ce fil

• utilise le menu ...▾ (à droite de la bobine souriante) dans la barre de menus au-dessus du champ de saisie d'un message > sous-menu : </> Bloc de code => tu fais ton coller dans la fenêtre de code et Continuer.

Note 1 : si tu ne peux pas poster via le Safari de la session de secours (ça arrive) --> poste une photo du tableau (à partir du commencement = le disque /dev/disk0 ou disque physique interne) - tu as un bouton : "Joindre un fichier" en bas de cette page.

Note 2 : dans la session de secours > les applications se lancent en mode "alternatif" et pas parallèle. Il faut quitter le Terminal pour lancer Safari. Vice-versa > quitter Safari pour récupérer l'écran général de la session de secours et pouvoir relancer le Terminal. Aucun redémarrage n'est requis.

 

[Duodecim]

Voici ce que j'ai obtenu via la commande que tu m'as donnée :

/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 disk3         870.3 GB   disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *28.0 GB    disk1
   1:                        EFI EFI                     314.6 MB   disk1s1
   2:                 Apple_APFS Container disk3         27.7 GB    disk1s2

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +898.0 GB   disk3
                                 Physical Stores disk1s2, disk0s2
   1:                APFS Volume Macintosh HD - Données  385.9 GB   disk3s1
   2:                APFS Volume Preboot                 81.9 MB    disk3s2
   3:                APFS Volume Recovery                528.5 MB   disk3s3
   4:                APFS Volume VM                      2.1 GB     disk3s4
   5:                APFS Volume Macintosh HD            11.0 GB    disk3s5

 

[Membre supprimé 1060554]

Passe la commande :

diskutil ap deleteContainer disk3 ; diskutil list internal

• la commande supprime le Fusion Drive (ce qui reformate 2 volumes Untitled standards sur les 2 partitions principales des 2 disques) > puis réaffiche la configuration des disques internes

Poste le retour.

 

[Duodecim]

Voici le résultat :

Started APFS operation on disk3
Deleting APFS Container with all of its APFS Volumes
Unmounting Volumes
Unmounting Volume "Macintosh HD - Données" on disk3s1
Unmounting Volume "Preboot" on disk3s2
Unmounting Volume "Recovery" on disk3s3
Unmounting Volume "VM" on disk3s4
Unmounting Volume "Macintosh HD" on disk3s5
Deleting Volumes
Deleting Container
Wiping former APFS disks
Switching content types
Reformatting former APFS disks
Initialized /dev/rdisk1s2 as a 26 GB case-insensitive HFS Plus volume with a 8192k journal
Mounting disk
Initialized /dev/rdisk0s2 as a 931 GB case-insensitive HFS Plus volume with a 81920k journal
Mounting disk
2 new disks created or changed due to APFS operation
Disk from APFS operation: disk1s2
Disk from APFS operation: disk0s2
Finished APFS operation on disk3
/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_HFS Untitled 2              999.9 GB   disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *28.0 GB    disk1
   1:                        EFI EFI                     314.6 MB   disk1s1
   2:                  Apple_HFS Untitled                27.6 GB    disk1s2

 

[Membre supprimé 1060554]

Parfait. Après la destruction > la reconstruction.

- passe la commande :​

diskutil ap create disk1s2 disk0s2 "Macintosh HD" ; diskutil list internal

• tu peux la passer en copier-coller à rebours : tu la copies ici avec Safari > tu la colles dans le terminal > tu l'exécutes

• la commande recrée un Fusion Drive apfs > avec un volume unique Macintosh HD dans le Conteneur commun > puis affiche la configuration interne

Poste le retour.

 

[Duodecim]

Et voici pour la reconstruction :

Started APFS operation on disk1s2 Untitled
Creating a new empty APFS Container
Unmounting Volumes
Switching disk1s2 to APFS
Switching disk0s2 to APFS
Creating APFS Container
FusionLC autodetect: LC Fusion
Created new APFS Container disk3
Disk from APFS operation: disk3
Finished APFS operation on disk1s2 Untitled
Started APFS operation on disk3
Preparing to add APFS Volume to APFS Container disk3
Creating APFS Volume
Created new APFS Volume disk3s1
Mounting APFS Volume
Setting volume permissions
Disk from APFS operation: disk3s1
Finished APFS operation on disk3
/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 disk3         1000.0 GB  disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *28.0 GB    disk1
   1:                        EFI EFI                     314.6 MB   disk1s1
   2:                 Apple_APFS Container disk3         27.7 GB    disk1s2

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.0 TB     disk3
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD            24.6 KB    disk3s1

 

[Membre supprimé 1060554]

Parfait : Fusion Drive recréé.

- en simple vérification > passe la commande :​

diskutil ap list

• qui affiche un tableau détaillé de l'apfs

Poste le tableau (c'est pour vérifier si les 2 partitions des 2 disques => ont bien les "performances roles" = attributs de rôles efficaces --> correctement attribués).