10.15 Catalina Problème de ré-attribution de espace libre APFS

[Neodyms]

Bonjour à tous

j'ai un soucis de recupération d'espace libre sur mon SSD pricipale

j'avais une partition APFS et un BOOTCAMP

j'ai créé une nouvelle partion APFS en récuperant l'espace libre pour réinstaller au propre Catalina

aujourd'hui je souhaite réatribuer l'espace libre du container disk2 qui est vide au cantainer disk3

voici le résultat de sudo diskutil list :

recmobile@MacBook-Pro-de-MacRecMobile ~ % sudo diskutil list
Password:
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk2         258.8 GB   disk0s2
   3:                 Apple_APFS Container disk3         200.2 GB   disk0s4
   4:       Microsoft Basic Data BOOTCAMP                41.0 GB    disk0s5

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +258.8 GB   disk2
                                 Physical Store disk0s2

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +200.2 GB   disk3
                                 Physical Store disk0s4
   1:                APFS Volume MacOsX - Données        151.8 GB   disk3s1
   2:                APFS Volume Preboot                 93.4 MB    disk3s2
   3:                APFS Volume Recovery                528.1 MB   disk3s3
   4:                APFS Volume VM                      3.2 GB     disk3s4
   5:                APFS Volume MacOsX                  10.9 GB    disk3s5

voici le resultat de sudo gpt show /dev/disk0:

recmobile@MacBook-Pro-de-MacRecMobile ~ % sudo gpt show /dev/disk0
Password:
      start       size  index  contents
          0          1         PMBR
          1          1         Pri GPT header
          2          4         Pri GPT table
          6      76800      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      76806        506      
      77312   63177488      2  GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC
   63254800   48882672      3  GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC
  112137472   10000640      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
  122138112         16      
  122138128          4         Sec GPT table
  122138132          1         Sec GPT header

j'ai l'impression que mon problème viens du fait que l'espace libre est avant le container disk3

Merci beaucoup d'avance

cordialement

 

[Membre supprimé 1060554]

Bonsoir Neodyms

Voici les 2 partitions impliquées -->

   2:                 Apple_APFS Container disk2         258.8 GB   disk0s2
   3:                 Apple_APFS Container disk3         200.2 GB   disk0s4

• je vais les désigner par leur numéro de rang dans la table GPT qui est indiqué en 1er : 2 & 3. Tu ne peux pas récupérer l'espace de la partition 2 que tu supprimerais => à la partition 3 (une récupération d'espace entre partitions fonctionne toujours de bas en haut > et pas l'inverse.

• par contre > tu peux très bien cloner la distribution de Catalina du Conteneur virtualisé depuis la partition 3 => dans un Conteneur qu'on recréerait virtualisé depuis la partition 2. Puis tu démarrerais sur le clone de la partition 2 > supprimerais la partition 3 > et récupérerais son espace. Ce qui réalise ton intention > mais avec plusieurs détours imposés par la logique de la récupération d'espace.

=> d'accord pour le projet ?

 

[Neodyms]

oui j'étais en train d'envisager cette hypothèse

merci pour cette réponse rapide peux tu m'aider en décrivant plus précisément la marche à suivre ?

 

[Membre supprimé 1060554]

Ton Conteneur disk2 ne contient pas de volume. Passe la commande (copier-coller) :

diskutil ap addVolume disk2 macOS ; diskutil list

• qui crée un volume intitulé macOS dans le Conteneur de la partition 2 > puis réaffiche le tableau des disques

Poste le retour.

 

[Neodyms]

Recmobile@MacBook-Pro-de-MacRecMobile ~ % diskutil ap addVolume disk2 macOS ; diskutil list
Usage:  diskutil apfs addVolume <containerRefDisk> <fs> <name>
        [-passprompt | -passphrase <passphrase> | -stdinpassphrase]
        [-passphraseHint <passHint>]
        [-reserve <reserveSize>] [-quota <quotaSize>]
        [-role <roles>]
        [-group[With] | -sibling <apfsVolumeDisk>]
        [-nomount | -mountpoint <mountPoint>]
        where <containerRefDisk> = Container Reference DiskIdentifier
              <fs> = an APFS file system personality: e.g. "APFS", "APFSX"
              <name> = a volume name
              <passphrase> = optionally create an encrypted volume (disk user)
              <passHint> = some string that can be shown even while locked
              <reserveSize> = optional minimum guaranteed file data capacity
              <quotaSize> = optional maximum file data usage limit
              <roles> = "0" or one or more of B|R|V|I|T|S|D|U|N|E|X|H|L|C|Y|G
              <apfsVolumeDisk> = another APFS Volume in the same Container
              <mountPoint> = "your" mount point (root only) (dir must exist)
Add a new APFS Volume to an existing APFS Container. If you specify a
passphrase, it will be encrypted with the "disk" user and that passphrase.
Ownership of the affected disks is required.
Example:  diskutil apfs addVolume disk5 APFS Foo1
          diskutil apfs addVolume disk5 APFS FooSecure2 -passphrase hello
          diskutil apfs addVolume disk5 APFS Foo3 -quota 10g -reserve 5g
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk2         258.8 GB   disk0s2
   3:                 Apple_APFS Container disk3         200.2 GB   disk0s4
   4:       Microsoft Basic Data BOOTCAMP                41.0 GB    disk0s5

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +258.8 GB   disk2
                                 Physical Store disk0s2

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +200.2 GB   disk3
                                 Physical Store disk0s4
   1:                APFS Volume MacOsX - Données        151.8 GB   disk3s1
   2:                APFS Volume Preboot                 93.4 MB    disk3s2
   3:                APFS Volume Recovery                528.1 MB   disk3s3
   4:                APFS Volume VM                      4.3 GB     disk3s4
   5:                APFS Volume MacOsX                  10.9 GB    disk3s5

 

[Membre supprimé 1060554]

J'ai oublié la mention du système de fichiers dans la commande de création du volume.

- voici la commande éditée :​

diskutil ap addVolume disk2 apfs macOS ; diskutil list

• poste le retour.

 

[Neodyms]

recmobile@MacBook-Pro-de-MacRecMobile ~ % diskutil ap addVolume disk2 apfs macOS ; diskutil list
Will export new APFS Volume "macOS" from APFS Container Reference disk2
Started APFS operation on disk2
Preparing to add APFS Volume to APFS Container disk2
Creating APFS Volume
Created new APFS Volume disk2s1
Mounting APFS Volume
Setting volume permissions
Disk from APFS operation: disk2s1
Finished APFS operation on disk2
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk2         258.8 GB   disk0s2
   3:                 Apple_APFS Container disk3         200.2 GB   disk0s4
   4:       Microsoft Basic Data BOOTCAMP                41.0 GB    disk0s5

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +258.8 GB   disk2
                                 Physical Store disk0s2
   1:                APFS Volume macOS                   1.0 MB     disk2s1

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +200.2 GB   disk3
                                 Physical Store disk0s4
   1:                APFS Volume MacOsX - Données        151.8 GB   disk3s1
   2:                APFS Volume Preboot                 93.4 MB    disk3s2
   3:                APFS Volume Recovery                528.1 MB   disk3s3
   4:                APFS Volume VM                      4.3 GB     disk3s4
   5:                APFS Volume MacOsX                  10.9 GB    disk3s5

 

[Membre supprimé 1060554]

Ça a marché cette fois-ci : volume macOS disponible.

----------

Maintenant va à cette page internet : ☞Carbon Copy Cloner☜ (clique le lien rouge). Télécharge le logiciel et déplace-le dans les Applications. C'est un logiciel de clonage éprouvé. Tu as droit à une démo gratuite de 1 mois (sans restrictions logicielles) dont tu vas profiter.

----------

À présent lance CCC > et dans son panneau définis une tâche telle que :

• SOURCE = MacOsX

• DESTINATION = macOS

• SafetyNet = Désactivé

• Presse le bouton "Cloner"

Le logiciel va cloner MacOsX dans macOS > créer un volume macOS - Données pour y cloner le volume MacOsX - Données > enfin créer les volumes auxiliaires requis dans le conteneur de destination. Préviens quand c'est fini.

 

[Neodyms]

des que c'est fait je redémare sur macOS ?

 

[Membre supprimé 1060554]

Oui : tu redémarres > en pressant la touche "alt" pour avoir l'écran de choix du volume de démarrage. Tu choisis macOS et tu démarres dessus.

- si tu récupères bien une session conforme à l'antérieure en y retrouvant tes données > passe une commande :​

diskutil list

• et reposte le tableau des disques.

[Je reviendrai demain dans ce fil pour la finalisation des opérations.

 

[Neodyms]

voila je suis bien sur MacOS

recmobile@MacBook-Pro-de-MacRecMobile ~ % diskutil list     
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk1         258.8 GB   disk0s2
   3:                 Apple_APFS Container disk2         200.2 GB   disk0s3
   4:       Microsoft Basic Data BOOTCAMP                41.0 GB    disk0s4

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +258.8 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume macOS - Données         177.1 GB   disk1s1
   2:                APFS Volume macOS                   10.9 GB    disk1s2
   3:                APFS Volume Preboot                 93.4 MB    disk1s3
   4:                APFS Volume Recovery                540.8 MB   disk1s4
   5:                APFS Volume VM                      1.1 GB     disk1s5

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +200.2 GB   disk2
                                 Physical Store disk0s3
   1:                APFS Volume MacOsX - Données        168.1 GB   disk2s1
   2:                APFS Volume Preboot                 93.4 MB    disk2s2
   3:                APFS Volume Recovery                528.1 MB   disk2s3
   4:                APFS Volume VM                      3.2 GB     disk2s4
   5:                APFS Volume MacOsX                  10.9 GB    disk2s5

maintenant je suprime MacOsX et je redimensionne macOS ?

as tu les command exact?

 

[Membre supprimé 1060554]

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

diskutil ap deleteContainer disk2 ; diskutil eraseVolume free null disk0s3 ; diskutil ap resizeContainer disk1 0b ; diskutil list

• la commande supprime l'apfs du bas (ce qui reformate un volume Untitled standard sur la partition du bas) > supprime la partition du bas reformatée > récupère son espace au Conteneur du haut > ré-affiche le tableau des disques

Poste le retour complet de la commande (s'il y avait un blocage à un point donné de l'enchaînement => que je voie où).

 

[Neodyms]

recmobile@MacBook-Pro-de-MacRecMobile ~ %
diskutil ap deleteContainer disk2 ; diskutil eraseVolume free null disk0s3 ; diskutil ap resizeContainer disk1 0b ; diskutil list
Started APFS operation on disk2
Deleting APFS Container with all of its APFS Volumes
Unmounting Volumes
Unmounting Volume "MacOsX-bak - Données" on disk2s1
Unmounting Volume "Preboot" on disk2s2
Unmounting Volume "Recovery" on disk2s3
Unmounting Volume "VM" on disk2s4
Unmounting Volume "MacOsX-bak" on disk2s5
Deleting Volumes
Deleting Container
Wiping former APFS disks
Switching content types
Reformatting former APFS disks
Initialized /dev/rdisk0s3 as a 186 GB case-insensitive HFS Plus volume with a 16384k journal
Mounting disk
1 new disk created or changed due to APFS operation
Disk from APFS operation: disk0s3
Finished APFS operation on disk2
Started erase on disk0s3 Untitled
Unmounting disk
Finished erase on disk0
Started APFS operation
Aligning grow delta to 200 223 424 512 bytes and targeting a new physical store size of 458 998 415 360 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 458 998 415 360 bytes
Resizing APFS Container designated by APFS Container Reference disk1
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Using live mode
Performing 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 MacOS-HD - Données was formatted by diskmanagementd (1412.101.1) and last modified by apfs_kext (1412.101.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
warning: apfs_fs_alloc_count is not valid (expected 3203180, actual 46340060)
Checking volume
Checking the APFS volume superblock
The volume MacOS-HD was formatted by diskmanagementd (1412.101.1) and last modified by apfs_kext (1412.101.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
warning: apfs_fs_alloc_count is not valid (expected 42086, actual 2667672)
Checking volume
Checking the APFS volume superblock
The volume Preboot was formatted by diskmanagementd (1412.101.1) and last modified by apfs_kext (1412.101.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 (1412.101.1) and last modified by apfs_kext (1412.101.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 (1412.101.1) and last modified by
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: (0x9c403+9) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c40d+156) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c4aa+2) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c4ad+49) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c4e0+24) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c4f9+34) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c51e+1) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c521+8) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c52a+8) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c537+356) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c69c+3) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c6a1+3) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c6a6+4) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c6ab+2) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c6af+1) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c6b1+9) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c6bb+4) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c6c2+1) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c6d9+2) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c6dc+7) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c6f3+90) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c74e+6) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c757+69) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c79d+1) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c79f+2) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c7a5+1) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c7a8+8) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c7b1+4) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c7b6+18) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c7c9+10) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c7d4+4) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c7d9+36) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c7ff+2) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c803+1) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c808+1) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c80a+1) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c80d+9) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c81b+1) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c81d+89) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c877+1) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c879+7) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c881+8) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c88a+1) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c88c+2) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c88f+2) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c892+2) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c895+155) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c931+140) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c9be+1) bitmap address (0x7dec)
warning: overallocation detected on Main device: (0x9c9c0+7) bitmap address (0x7dec)
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
Growing APFS Physical Store disk0s2 from 258 774 990 848 to 458 998 415 360 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk1         459.0 GB   disk0s2
   3:       Microsoft Basic Data BOOTCAMP                41.0 GB    disk0s4

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +459.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume MacOS-HD - Données      189.8 GB   disk1s1
   2:                APFS Volume MacOS-HD                10.9 GB    disk1s2
   3:                APFS Volume Preboot                 93.4 MB    disk1s3
   4:                APFS Volume Recovery                540.8 MB   disk1s4
   5:                APFS Volume VM                      1.1 GB     disk1s5

ca à l'air good ...

 

[Membre supprimé 1060554]

Problème résolu en effet !

 

[Neodyms]

Merci Beaucoup MR !

 

[Neodyms]

juste un petit retour
tout fonctionne parfaitement depuis cette copy
encore merci!

 

[Membre supprimé 1060554]

Content pour toi !