Partage
  • Partager sur Facebook
  • Partager sur Twitter

Impossible de partioner son disque sur Mac ?

Sujet résolu
    4 juillet 2022 à 23:35:00

    Salut tout le monde !

    J'essaie de créer une partition de 64Go sur un Mac Intel avec l'Utilitaire de disque mais l'opération échoue souvent notamment lorsque la partition est trop grosse. J'arrive à partitioner une partition de 32Go mais lorsque j'essaie 64Go j'ai un message d'erreur : "l'opération a échoué".

    Quelqu'un aurait la solution svp ?

    Voici les logs :

    Partitionnement du disque (disk0)
    
    Exécution de l’opération 1 sur 2 : Ajout de « Ubuntu » (64 Go) en scindant « SSD 1To » (disk0s2) de 1 To à 936 Go…
    
    Alignement du delta de diminution sur 64 000 000 000 octets et ciblage d’une nouvelle taille de stockage physique de 935 995 129 856 octets
    
    A déterminé que la taille minimale du stockage physique ciblé de ce conteneur APFS était de 913 552 965 632 octets
    
    Redimensionnement du conteneur APFS désigné par la référence de conteneur disk1
    
    Le stockage physique APFS en cours de redimensionnement est disk0s2
    
    Vérification du système de stockage
    
    Mode en direct actif.
    
    Exécution de fsck_apfs -n -x -l -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 SSD 1To was formatted by diskmanagementd (945.275.7) and last modified by apfs_kext (945.275.10).
    
    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 diskmanagementd (945.275.7) and last modified by apfs_kext (945.275.10).
    
    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.275.7) and last modified by apfs_kext (945.275.10).
    
    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.275.8) and last modified by apfs_kext (945.275.10).
    
    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: (1264243+2) bitmap address (184b0)
    
    warning: Overallocation Detected on Main device: (1264250+1) bitmap address (184b0)
    
    warning: Overallocation Detected on Main device: (1264253+1) bitmap address (184b0)
    
    warning: Overallocation Detected on Main device: (1264681+3) bitmap address (184b0)
    
    warning: Overallocation Detected on Main device: (1264690+1) bitmap address (184b0)
    
    warning: Overallocation Detected on Main device: (1264692+1) bitmap address (184b0)
    
    warning: Overallocation Detected on Main device: (1264694+7) bitmap address (184b0)
    
    warning: Overallocation Detected on Main device: (1264702+1) bitmap address (184b0)
    
    warning: Overallocation Detected on Main device: (1264979+1) bitmap address (184b0)
    
    warning: Overallocation Detected on Main device: (1264981+1) bitmap address (184b0)
    
    warning: Overallocation Detected on Main device: (1319015+1) bitmap address (19f3c)
    
    warning: Overallocation Detected on Main device: (1319023+1) bitmap address (19f3c)
    
    warning: Overallocation Detected on Main device: (1319056+2) bitmap address (19f3c)
    
    warning: Overallocation Detected on Main device: (1319355+1) bitmap address (19f3c)
    
    warning: Overallocation Detected on Main device: (1319382+1) bitmap address (19f3c)
    
    warning: Overallocation Detected on Main device: (1346895+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346905+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346910+2) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346926+2) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346935+4) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346940+2) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346944+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346949+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346955+2) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346959+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346968+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346976+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346978+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346981+2) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346987+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346993+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1346995+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347001+3) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347007+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347012+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347021+2) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347024+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347027+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347031+2) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347034+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347038+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347040+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347048+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347051+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347054+2) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347058+2) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347062+2) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347066+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347068+1) bitmap address (19f3f)
    
    warning: Overallocation Detected on Main device: (1347075+1) bitmap address (19f3f)
    
    too many warnings generated; suppressing subsequent ones.
    
    The volume /dev/disk0s2 appears to be OK.
    
    Le code de sortie de la vérification du système de stockage est 0.
    
    Réduction du stockage physique APFS disk0s2 de 999 995 129 856 à 935 995 129 856 octets
    
    Réduction des structures de données APFS
    
    Réduction de la partition
    
    Modification de la carte de partition
    
    Initialized /dev/rdisk0s3 as a 59 GB case-insensitive HFS Plus volume with a 8192k journal
    
    Montage du disque
    
    Création d’un nouveau conteneur APFS vide
    
    Démontage des volumes
    
    Passage de disk0s3 sur APFS
    
    Création du conteneur APFS
    
    Nouveau conteneur APFS disk2 créé
    
    Préparation de l’ajout du volume APFS au conteneur APFS disk2
    
    Création du volume APFS
    
    Nouveau volume APFS disk2s1 créé
    
    Montage du volume APFS
    
    Définition des autorisations d’accès au volume
    
    Une erreur interne s’est produite et le disque concerné par l’une des opérations indiquées est introuvable. Ce problème est peut-être temporaire ; réessayez.


    EDIT : Le partitionnement a fini par fonctionner au bout d'un certain nombre de tentatives. Néanmoins  je n'ai pas d'explication pour expliquer comment le problème a été résolu.

    -
    Edité par Autechre 9 juillet 2022 à 19:37:20

    • Partager sur Facebook
    • Partager sur Twitter

    Impossible de partioner son disque sur Mac ?

    × Après avoir cliqué sur "Répondre" vous serez invité à vous connecter pour que votre message soit publié.
    × Attention, ce sujet est très ancien. Le déterrer n'est pas forcément approprié. Nous te conseillons de créer un nouveau sujet pour poser ta question.
    • Editeur
    • Markdown