Impossible d'utiliser bootcamp, problème d'espace disque

Hello, je reformule mon problème avec le retour du terminal correctement présenté
Merci d'avance


Bloc de code: 
  #:                       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                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         1000.0 GB  disk1s2

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

/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *63.3 GB    disk3
   1:               Windows_NTFS WinInstall              63.3 GB    disk3s1

/dev/disk4 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            CCCOMA_X64FRE_FR-FR... +5.3 GB     disk4

/dev/disk5 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            Boot Camp              +2.8 GB     disk5

/dev/disk6 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            Boot Camp              +2.8 GB     disk6

/dev/disk7 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            Boot Camp              +2.8 GB     disk7

/dev/disk8 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            Boot Camp              +2.8 GB     disk8

imac-de-charlotte:~ Charlotte$
 
Bonjour Lulu

Tu as un Fusion Drive de type apfs (nouveau type) > associant 1 SSD de 121 Go & 1 HDD de 1 To par leurs partitions principales. Exportation d'un Conteneur (espace-disque virtuel) hébergeant une distribution à 5 volumes de Catalina. Dans les 356,5 Go d'occupation de blocs des 1,1 To disponibles => soit 743,5 Go d'espace libre.

- passe la commande expérimentale (copier-coller) :​
Bloc de code: 
diskutil ap resizeContainer disk2 500g fat32 BOOTCAMP 0b
  • qui instruit le rétrécissement du Conteneur à 500 Go (c'est la partition du HDD seul qui supporte cette réduction) > et la création d'une partition BOOTCAMP en format FAT-32 de 600 Go (c'est en queue de HDD que la partition est créée)

Poste le retour intégral de la commande. Si elle passe => c'est qu'il n'y a pas de problème de repartitionnement ; si elle bloque => la raison de l'échec se trouvera désignée. C'est un cas où l'on peut dire qu'agir (expérimentalement) permet de savoir.
 
macomaniac a dit:
Bonjour Lulu

Tu as un Fusion Drive de type apfs (nouveau type) > associant 1 SSD de 121 Go & 1 HDD de 1 To par leurs partitions principales. Exportation d'un Conteneur (espace-disque virtuel) hébergeant une distribution à 5 volumes de Catalina. Dans les 356,5 Go d'occupation de blocs des 1,1 To disponibles => soit 743,5 Go d'espace libre.

- passe la commande expérimentale (copier-coller) :​
Bloc de code: 
diskutil ap resizeContainer disk2 500g fat32 BOOTCAMP 0b
  • qui instruit le rétrécissement du Conteneur à 500 Go (c'est la partition du HDD seul qui supporte cette réduction) > et la création d'une partition BOOTCAMP en format FAT-32 de 600 Go (c'est en queue de HDD que la partition est créée)

Poste le retour intégral de la commande. Si elle passe => c'est qu'il n'y a pas de problème de repartitionnement ; si elle bloque => la raison de l'échec se trouvera désignée. C'est un cas où l'on peut dire qu'agir (expérimentalement) permet de savoir.
Cliquez pour agrandir...


Merci beaucoup pour le retour!
Voici la réponse complète à la commande, ce n'est pas passé a priori.

Bloc de code: 
Started APFS operation
Aligning shrink delta to 621 118 201 856 bytes and targeting a new physical store size of 378 876 928 000 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 354 133 475 328 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk1s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /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 (1412.141.1) and last modified by apfs_kext (1412.141.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 77625, actual 83643134)
Checking volume
Checking the APFS volume superblock
The volume Preboot was formatted by hfs_convert (1412.141.1) and last modified by apfs_kext (1412.141.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.141.1) and last modified by apfs_kext (1412.141.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 diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.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.141.1) and last modified by apfs_kext (1412.141.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 42108, actual 2740790)
Verifying allocated space
warning: overallocation detected on Main device: (0x1+14226) bitmap address (0x2a9ad9)
warning: overallocation detected on Main device: (0x21512c+1027) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215530+4) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215535+18) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215548+43) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215574+13) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215582+9) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x21558c+47) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2155bc+20) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2155d1+27) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2155ed+10) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2155f8+1) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2155fa+1) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2155fc+2) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2155ff+4) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215604+27) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215620+6) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215627+5) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x21562e+14) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x21563d+31) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x21565d+21) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215673+3) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215677+3) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x21567e+1) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215680+1) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215682+1) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215684+11) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215690+20) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2156a5+9) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2156b0+1) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2156b2+1) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2156b4+4) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2156bb+2) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2156bf+16) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2156d0+2) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2156d3+2) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2156d6+5) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2156dc+4) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2156e1+37) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215707+32) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x21572a+1) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x21572c+1) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x21572f+94) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x21578f+5) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x215796+5) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x21579d+2) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2157a1+32) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2157c2+27) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2157de+6) bitmap address (0x2ac377)
warning: overallocation detected on Main device: (0x2157e7+1) bitmap address (0x2ac377)
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
Shrinking APFS Physical Store disk1s2 from 999 995 129 856 to 378 876 928 000 bytes
Shrinking APFS data structures
APFS Container Resize error code is 49186
Error: -69501: Unable to resize APFS Container structures due to APFS Snapshot presence (perhaps caused by Time Machine)
 
Le message d'échec prétend que le blocage du repartitionnement a été dû a des snapshots : instantanés Time Machine retenant de l'espace de blocs occupés > qui peuvent se balader partout dans l'espace du Conteneur et s'il verrouillent des blocs de queue de Conteneur => invalidant toute possibilité de dégager une bande continue d'espace libre préparatoire à un repartitionnement. Or la vérification n'avère nulle part la présence de snapshots associés à aucun volume du Conteneur.

- par contre le fsroot tree (segment de l'apfs générateur de volume) du volume-Données : Macintosh HD - Données => a un décompte de blocs invalide > de même que celui du volume-Système : Macintosh HD > enfin : une erreur massive de sur-allocation d'espace de blocs affecte le spaceman (space_manager) = le gestionnaire de l'allocation des blocs de l'apfs. Malgré la déclaration finale synthétique lénifiante :​
Bloc de code: 
Storage system check exit code is 0
  • le code de sortie de la vérification du système de stockage apfs = 0 (comme zéro erreur) => la vérification analytique a témoigné qu'il n'en est rien > mais qu'il y a corruption de l'apfs sur 3 points --> tous impliquant un décompte des blocs occupés invalide.

Redémarre (Menu  > Redémarrer) > et tiens aussitôt pressées les 2 touches ⌘R (cmd R) = démarrage sur l'OS de récupération local. Quand tu as un écran affichant une fenêtre de 4 Utilitaires macOS (= écran de la session de récupération) > lance l'Utilitaire de disque -->

- presse la pastille : "Présentation" (coin gauche supérieur) et sélectionne : "Afficher tous les appareils" => le Conteneur apfs global est alors affiché​

- sélectionne-le et fais un S.O.S. dessus pour tenter de réparer l'apfs​

Puis redémarre (Menu  > Redémarrer) > ta session réouverte --> repasse la commande :
Bloc de code: 
diskutil ap resizeContainer disk2 500g fat32 BOOTCAMP 0b
  • et poste encore le retour intégral => qu'on voie s'il y a eu un changement.
 
Voici la réponse
je suis obligé de me laisser guider, c'est très interessant mais je ne comprend pas tout!


Bloc de code: 
Last login: Fri Oct  9 13:29:15 on console

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
imac-de-charlotte:~ Charlotte$ diskutil ap resizeContainer disk2 500g fat32 BOOTCAMP 0b
Started APFS operation
Aligning shrink delta to 621 118 201 856 bytes and targeting a new physical store size of 378 876 928 000 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 354 469 019 648 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk1s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /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 (1412.141.1) and last modified by apfs_kext (1412.141.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 168823, actual 83734332)
Checking volume
Checking the APFS volume superblock
The volume Preboot was formatted by hfs_convert (1412.141.1) and last modified by apfs_kext (1412.141.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.141.1) and last modified by apfs_kext (1412.141.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 diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.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.141.1) and last modified by apfs_kext (1412.141.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 42697, actual 2741379)
Verifying allocated space
warning: overallocation detected on Main device: (0x1+14226) bitmap address (0x2a8217)
warning: overallocation detected on Main device: (0x21512c+1027) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215530+4) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215535+18) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215548+43) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215574+13) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215582+9) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x21558c+47) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2155bc+20) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2155d1+27) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2155ed+10) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2155f8+1) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2155fa+1) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2155fc+2) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2155ff+4) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215604+27) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215620+6) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215627+5) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x21562e+14) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x21563d+31) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x21565d+21) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215673+3) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215677+3) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x21567e+1) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215680+1) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215682+1) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215684+11) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215690+20) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2156a5+9) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2156b0+1) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2156b2+1) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2156b4+4) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2156bb+2) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2156bf+16) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2156d0+2) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2156d3+2) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2156d6+5) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2156dc+4) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2156e1+37) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215707+32) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x21572a+1) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x21572c+1) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x21572f+94) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x21578f+5) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x215796+5) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x21579d+2) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2157a1+32) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2157c2+27) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2157de+6) bitmap address (0x2a80de)
warning: overallocation detected on Main device: (0x2157e7+1) bitmap address (0x2a80de)
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
Shrinking APFS Physical Store disk1s2 from 999 995 129 856 to 378 876 928 000 bytes
Shrinking APFS data structures
APFS Container Resize error code is 49186
Error: -69501: Unable to resize APFS Container structures due to APFS Snapshot presence (perhaps caused by Time Machine)
imac-de-charlotte:~ Charlotte$
 
Aucune réparation n'a été possible => même échec au repartitionnement.

- par acquit de conscience > passe la commande :​
Bloc de code: 
tmutil listlocalsnapshotdates
  • la commande liste les dates de prises de snapshots pour tout volume apfs actuellement monté

Poste le retour.
 
macomaniac a dit:
Aucune réparation n'a été possible => même échec au repartitionnement.

- par acquit de conscience > passe la commande :​
Bloc de code: 
tmutil listlocalsnapshotdates
  • la commande liste les dates de prises de snapshots pour tout volume apfs actuellement monté

Poste le retour.
Cliquez pour agrandir...
le retour :

Bloc de code: 
imac-de-charlotte:~ Charlotte$ tmutil listlocalsnapshotdates
Snapshot dates for all disks:
2020-10-09-083506
2020-10-09-093610
2020-10-09-103621
2020-10-09-113628
2020-10-09-123648
2020-10-09-133510
 
Hé ben ! en voilà une surprise... aucun snapshot n'est attesté par la vérification de l'apfs (comme cela devrait se passer canoniquement parlant) > mais ne voilà-t-il pas que 6 snapshots sortent tels des lapins blancs du chapeau d'Alice ...... ! :hilarious:

- le listage par dates ne fait pas connaître quel est le volume de référence des snapshots. Passe la commande :​
Bloc de code: 
diskutil ap listSnaps disk2s1
  • qui liste les snapshots associés au volume-Données

Poste le retour.
 
macomaniac a dit:
Hé ben ! en voilà une surprise... aucun snapshot n'est attesté par la vérification de l'apfs (comme cela devrait se passer canoniquement parlant) > mais ne voilà-t-il pas que 6 snapshots sortent tels des lapins blancs du chapeau d'Alice ...... ! :hilarious:

- le listage par dates ne fait pas connaître quel est le volume de référence des snapshots. Passe la commande :​
Bloc de code: 
diskutil ap listSnaps disk2s1
  • qui liste les snapshots associés au volume-Données

Poste le retour.
Cliquez pour agrandir...

La réponse!


Bloc de code: 
imac-de-charlotte:~ Charlotte$ diskutil ap listSnaps disk2s1
Snapshots for disk2s1 (6 found)
|
+-- 94B09FD9-2B6A-45D5-9ECF-97DE16B85F4C
|   Name:        com.apple.TimeMachine.2020-10-09-083506.local
|   XID:         151882
|   Purgeable:   Yes
|   NOTE:        This snapshot limits the minimum size of APFS Container disk2
|
+-- 4EDE1460-6188-4174-ABD8-030B6E014C06
|   Name:        com.apple.TimeMachine.2020-10-09-093610.local
|   XID:         152492
|   Purgeable:   Yes
|
+-- 85CA0F9E-6631-4B66-B978-BF7631621D2A
|   Name:        com.apple.TimeMachine.2020-10-09-103621.local
|   XID:         153198
|   Purgeable:   Yes
|
+-- 5FC67A18-34FA-45F0-B2DA-1101FD574AA3
|   Name:        com.apple.TimeMachine.2020-10-09-113628.local
|   XID:         153941
|   Purgeable:   Yes
|
+-- 79E8174C-EA9D-47B0-894A-BFBE024580B5
|   Name:        com.apple.TimeMachine.2020-10-09-123648.local
|   XID:         154627
|   Purgeable:   Yes
|
+-- A4985A76-BDC9-4613-A508-C3107B8A8391
    Name:        com.apple.TimeMachine.2020-10-09-133510.local
    XID:         155475
    Purgeable:   Yes
 
D'accord : le mystère est éventé (ce qui n'empêche que des corruptions locales n'affectent l'apfs).

- passe la commande (copier-coller) :​
Bloc de code: 
sudo tmutil thinlocalsnapshots /System/Volumes/Data 99000000000 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 associés au volume-Données > lequel est monté dans le volume-Système démarré à la localisation spécifique : /System/Volumes/Data. Attends d'entendre une voix rogue déclarer : "Enfin ! terminé la purge..." en guise de signal de fin.

Poste le retour.
 
macomaniac a dit:
D'accord : le mystère est éventé (ce qui n'empêche que des corruptions locales n'affectent l'apfs).

- passe la commande (copier-coller) :​
Bloc de code: 
sudo tmutil thinlocalsnapshots /System/Volumes/Data 99000000000 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 associés au volume-Données > lequel est monté dans le volume-Système démarré à la localisation spécifique : /System/Volumes/Data. Attends d'entendre une voix rogue déclarer : "Enfin ! terminé la purge..." en guise de signal de fin.

Poste le retour.
Cliquez pour agrandir...
Voila le retour


Bloc de code: 
imac-de-charlotte:~ Charlotte$ sudo tmutil thinlocalsnapshots /System/Volumes/Data 99000000000 4 ; say 'ENFIN TERMINÉ LA PURGE'
Password:
Thinned local snapshots:
com.apple.TimeMachine.2020-10-09-083506.local
com.apple.TimeMachine.2020-10-09-083506.local
com.apple.TimeMachine.2020-10-09-093610.local
com.apple.TimeMachine.2020-10-09-093610.local
com.apple.TimeMachine.2020-10-09-103621.local
com.apple.TimeMachine.2020-10-09-103621.local
com.apple.TimeMachine.2020-10-09-113628.local
com.apple.TimeMachine.2020-10-09-113628.local
com.apple.TimeMachine.2020-10-09-123648.local
com.apple.TimeMachine.2020-10-09-123648.local
com.apple.TimeMachine.2020-10-09-133510.local
com.apple.TimeMachine.2020-10-09-133510.local
imac-de-charlotte:~ Charlotte$
 
Snaphots supprimés. Ne t'étonne pas d'en voir listés 12 au lieu des 6 attendus : les volumes Système & Données étant appairés dans le fonctionnement de Catalina > les snapshots impliquent en paires cette paire de volumes. Donc on ne peut supprimer les snapshots d'un volume sans supprimer les snapshots appariés de l'autre.

- test ! repasse la commande de repartitionnement :​
Bloc de code: 
diskutil ap resizeContainer disk2 500g fat32 BOOTCAMP 0b
  • et poste le retour.
 
Note : si ça fonctionne > le processus de repartitionnement peut être lent lorsque des données sont impliquées. Car tous les blocs mal placés en bas de Conteneur qui porteraient des fichiers => doivent être clonés sur des blocs placés en haut d'espace --> afin de dégager une bande continue d'espace de blocs libres en queue de Conteneur permettant la création d'une partition sur le HDD.

- je m'absente. Je reviendrai aux nouvelles en après-midi.​
 
Tu n'as qu'à poster le retour intégral de la commande => une fois l'opération accomplie.
 
Il faut dire aussi que j'ai outré le test à faire > en demandant la création d'une partition expérimentale BOOTCAMP de 600 Go.
 
Voici la réponse

Bloc de code: 
imac-de-charlotte:~ Charlotte$ diskutil ap resizeContainer disk2 500g fat32 BOOTCAMP 0b
Started APFS operation
Aligning shrink delta to 621 118 201 856 bytes and targeting a new physical store size of 378 876 928 000 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 345 543 540 736 bytes
Resizing APFS Container designated by APFS Container Reference disk2
The specific APFS Physical Store being resized is disk1s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l -S /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 (1412.141.1) and last modified by apfs_kext (1412.141.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 (1412.141.1) and last modified by apfs_kext (1412.141.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.141.1) and last modified by apfs_kext (1412.141.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 diskmanagementd (1412.141.1) and last modified by apfs_kext (1412.141.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.141.1) and last modified by apfs_kext (1412.141.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/disk0s2 appears to be OK
Storage system check exit code is 0
Shrinking APFS Physical Store disk1s2 from 999 995 129 856 to 378 876 928 000 bytes
Shrinking APFS data structures
Shrinking partition
Modifying partition map
4096 bytes per physical sector
/dev/rdisk1s3: 1212822272 sectors in 18950348 FAT32 clusters (32768 bytes/cluster)
bps=512 spc=64 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=740405248 drv=0x80 bsec=1213118464 bspf=148056 rdcl=2 infs=1 bkbs=6
Mounting disk
1 new disk created or changed due to APFS operation
Disk from APFS operation: disk1s3
Finished APFS operation
imac-de-charlotte:~ Charlotte$
 
Bon : ça a marché. Passe la commande :
Bloc de code: 
diskutil list internal
  • qui affiche l'actuelle configuration du disque interne

Poste le retour.
 
Good news


Bloc de code: 
imac-de-charlotte:~ Charlotte$ diskutil list internal
/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                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk2         378.9 GB   disk1s2
   3:       Microsoft Basic Data BOOTCAMP                621.1 GB   disk1s3

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.0 GB   disk2
                                 Physical Stores disk0s2, disk1s2
   1:                APFS Volume Macintosh HD - Données  334.3 GB   disk2s1
   2:                APFS Volume Preboot                 81.7 MB    disk2s2
   3:                APFS Volume Recovery                529.0 MB   disk2s3
   4:                APFS Volume VM                      1.1 MB     disk2s4
   5:                APFS Volume Macintosh HD            11.2 GB    disk2s5

imac-de-charlotte:~ Charlotte$
 

Sujets similaires

B
"espace disponible insuffisant" sur Bootcamp (disque avec 1To disponible)
Réponses
4
Affichages
3K
Windows sur Mac
Borisou
B
Kipix
Ce disque de démarrage ne peut pas être partitionné car l’espace y est insuffisant.
Réponses
11
Affichages
2K
Windows sur Mac
Kipix
Kipix
Kiddo387
Installation WINDOWS 10 via Bootcamp : espace insuffisant
Réponses
32
Affichages
4K
Windows sur Mac
staind06
S
W
Redimensionnement partition BootCamp, disque non visible par l'assistant
Réponses
3
Affichages
2K
Windows sur Mac
Locke
Locke
C
Problème avec BootCamp : disque de démarrage non partitionnable
Réponses
29
Affichages
2K
Windows sur Mac
ccc.97
C
Haut Bas
Back