10.15 Catalina probleme de redemarrage macbook pro

macomaniac

Ouroboros
Club MacG
20 Septembre 2012
71 793
21 532
Forêt de Fontainebleau
Passe la commande informative :
Bloc de code:
ls /Volumes/"Macintosh HD 750 Go - Données"/private/var/db/caches/opendirectory
  • qui liste les contenus du dossier opendirectory

=> poste le retour.
 

macomaniac

Ouroboros
Club MacG
20 Septembre 2012
71 793
21 532
Forêt de Fontainebleau
Donc le dossier est vide et le cache a bien été supprimé.

- tente ta chance : redémarre avec "alt" pour obtenir l'écran de choix du volume de démarrage > choisis : Macintosh HD 750 Go > démarre dessus​

=> tu n'auras qu'à décrire ce qui s'est passé.
 

macomaniac

Ouroboros
Club MacG
20 Septembre 2012
71 793
21 532
Forêt de Fontainebleau
Alors le plan B consiste à cloner les 356 Go de Macintosh HD 750 Go - Données => dans le volume (format apfs requis) d'un DDE USB. Puis supprimer le Conteneur de Catalina (disque de 750 Go). Réinstaller Catalina. Récupérer à la fin les données du clone via l'Assistant de migration. Un peu longuet mais gagnant.

- as-tu un DDE USB disponible avec dans les 400 Go d'espace libre (le clonage délayant toujours sur la destination) ?​
 

Myster dee

Membre confirmé
16 Juillet 2019
151
0
48
j'avais deja cloner la derniere fois lors de mon probleme d'espace purgeable
puis je reprendre le meme ??
 

macomaniac

Ouroboros
Club MacG
20 Septembre 2012
71 793
21 532
Forêt de Fontainebleau
Hé ! on peut récupérer le clone mais d'abord le mettre à jour. À condition que le volume soit de format apfs (requis pour l'Assistant de migration de Catalina). Sinon > il va falloir recréer le clone de neuf.

- avais-tu utilisé la démo de Carbon Copy Cloner ?​
 

macomaniac

Ouroboros
Club MacG
20 Septembre 2012
71 793
21 532
Forêt de Fontainebleau
Branche le DDE qui supporte le clone au Mac. Puis passe les commandes :
Bloc de code:
diskutil list
df -H
  • qui affichent : la configuration des disques & l'occupation des volumes montés

Poste les retours => que je voie le volume du clone.
 

Myster dee

Membre confirmé
16 Juillet 2019
151
0
48
ok voila
Bloc de code:
 diskutil list
/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         1000.0 GB  disk0s2

/dev/disk1 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *750.2 GB   disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:                 Apple_APFS Container disk3         694.8 GB   disk1s2
   3:       Microsoft Basic Data BOOTCAMP                55.0 GB    disk1s3

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1000.0 GB  disk2
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD 1 To       950.8 GB   disk2s1
   2:                APFS Volume Preboot                 24.1 MB    disk2s2
   3:                APFS Volume Recovery                507.3 MB   disk2s3
   4:                APFS Volume VM                      4.3 GB     disk2s4

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +694.8 GB   disk3
                                 Physical Store disk1s2
   1:                APFS Volume Macintosh HD 750 Go ... 357.9 GB   disk3s1
   2:                APFS Volume Preboot                 25.1 MB    disk3s2
   3:                APFS Volume Recovery                523.5 MB   disk3s3
   4:                APFS Volume VM                      4.3 GB     disk3s4
   5:                APFS Volume Macintosh HD 750 Go     11.0 GB    disk3s5

/dev/disk4 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk4
   1:                        EFI EFI                     209.7 MB   disk4s1
   2:          Apple_CoreStorage DeeMaxtor               1.5 TB     disk4s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk4s3
   4:                 Apple_APFS Container disk6         1.0 TB     disk4s4
   5:                  Apple_HFS DeeMax2                 750.0 GB   disk4s5
   6:                 Apple_APFS Container disk5         747.6 GB   disk4s6

/dev/disk5 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +747.6 GB   disk5
                                 Physical Store disk4s6
   1:                APFS Volume Clone 750 Go            177.6 GB   disk5s1
   2:                APFS Volume Preboot                 22.0 MB    disk5s2
   3:                APFS Volume Recovery                514.5 MB   disk5s3

/dev/disk6 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.0 TB     disk6
                                 Physical Store disk4s4
   1:                APFS Volume Clone 1 To              940.5 GB   disk6s1
   2:                APFS Volume Preboot                 22.0 MB    disk6s2
   3:                APFS Volume Recovery                514.5 MB   disk6s3

/dev/disk7 (external, virtual):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS DeeMaxtor              +1.5 TB     disk7
                                 Logical Volume on disk4s2
                                 A33476A1-5538-4F98-A9D8-8A25E0C30FC1
                                 Unlocked Encrypted

MacBook-Pro-de-Didier:~ MysterDee$ df -H
Filesystem      Size   Used  Avail Capacity iused               ifree %iused  Mounted on
/dev/disk2s1    1.0T   951G    44G    96% 1097667 9223372036853678140    0%   /
devfs           220k   220k     0B   100%     744                   0  100%   /dev
/dev/disk2s4    1.0T   4.3G    44G     9%       1 9223372036854775806    0%   /private/var/vm
map -hosts        0B     0B     0B   100%       0                   0  100%   /net
map auto_home     0B     0B     0B   100%       0                   0  100%   /home
/dev/disk1s3     55G    17G    38G    31%   60857            37445939    0%   /Volumes/BOOTCAMP
/dev/disk3s1    695G   358G   321G    53%  825279 9223372036853950528    0%   /Volumes/Macintosh HD 750 Go - Données
/dev/disk3s5    695G    11G   321G     4%  484198 9223372036854291609    0%   /Volumes/Macintosh HD 750 Go
/dev/disk4s5    750G   175G   575G    24%    1263          4294966016    0%   /Volumes/DeeMax2
/dev/disk5s1    748G   178G   569G    24% 1006871 9223372036853768936    0%   /Volumes/Clone 750 Go
/dev/disk7      1.5T   965G   535G    65% 2470215          4292497064    0%   /Volumes/DeeMaxtor
/dev/disk6s1    1.0T   941G    61G    94% 1103077 9223372036853672730    0%   /Volumes/Clone 1 To
 

macomaniac

Ouroboros
Club MacG
20 Septembre 2012
71 793
21 532
Forêt de Fontainebleau
Clone 750 Go (format apfs) a 178 Go d'occupation. Macintosh HD 750 Go a 359 Go d'occupation.

- et surtout l'arborescence des volumes doit différer. Car Clone 750 Go devait être un clone de volume Mojave > alors que Macintosh HD 750 Go est un volume-Données de Catalina.​

Afin de vérifier ce point > passe les 2 commmandes abrégées (copier-coller) :
Bloc de code:
ls /Vol*/Mac*\ -*
ls /Vol*/Cl*\ 7*
  • qui listent les objets de 1er rang de Macintosh HD 750 Go > puis de Clone 750 Go

Poste les 2 retours.
 

Myster dee

Membre confirmé
16 Juillet 2019
151
0
48
ok
Bloc de code:
Applications    Users        home        private
Library        Volumes        mnt        sw
System        cores        opt        usr
MacBook-Pro-de-Didier:~ MysterDee$ ls /Vol*/Cl*\ 7*
Applications            home
Library                installer.failurerequests
System                private
Users                sbin
Volumes                tmp
bin                usr
dev                var
etc
 

macomaniac

Ouroboros
Club MacG
20 Septembre 2012
71 793
21 532
Forêt de Fontainebleau
Rien à voir. Il faudrait repartitionner le Conteneur de Clone 750 Go > pour créer un nouveau Conteneur > et y cloner le volume-Données de Catalina.

- avais-tu utilisé la démo de Carbon Copy Cloner ou avais-tu une licence ? - car si c'est le 1er cas > la démo doit être périmée.​
 

macomaniac

Ouroboros
Club MacG
20 Septembre 2012
71 793
21 532
Forêt de Fontainebleau
Passe la commande (copier-coller) :
Bloc de code:
diskutil ap resizeContainer disk5 250g jhfs+ "Clone MH750 Données" 0b
  • la commande rétrécit le Conteneur de Clone 750 Go à 250 Go > et crée un volume Clone MH750 Données d'environ 500 Go en format classique

Poste le retour quand tu auras récupéré l'invite de commande : MacBook-Pro-de-Didier:~ MysterDee$ en signal de fin.

Note : un repartionnement non destructeur peut prendre un temps notable. Par ailleurs > on ne peut pas repartitionner un Conteneur apfs => en créant directement un nouveau Conteneur apfs. Il faut créer d'abord un volume de format jhfs+ > qu'on convertira ensuite à l'apfs.
 

Myster dee

Membre confirmé
16 Juillet 2019
151
0
48
voila
Bloc de code:
Started APFS operation
Aligning shrink delta to 497 620 516 864 bytes and targeting a new physical store size of 249 999 998 976 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 186 629 750 784 bytes
Resizing APFS Container designated by APFS Container Reference disk5
The specific APFS Physical Store being resized is disk4s6
Verifying storage system
Performing fsck_apfs -n -x -S /dev/disk4s6
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 Clone 750 Go was formatted by hfs_convert (945.275.7) and last modified by apfs_kext (945.275.7)
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.7)
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.7)
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: (1106206+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106208+2) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106211+5) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106217+7) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106229+3) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106239+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106240+11) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106254+13) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106268+2) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106275+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106279+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106296+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106298+5) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106309+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106317+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106376+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106390+2) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106411+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106433+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106436+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106457+3) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106461+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106463+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106466+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106471+5) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106477+4) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106485+2) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106490+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106500+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106502+5) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106508+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106510+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106513+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106516+3) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106529+2) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106532+2) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106535+4) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106541+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106543+2) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106546+14) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106560+5) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106566+12) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106587+2) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106590+5) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106596+2) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106604+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106662+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106692+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106752+1) bitmap address (1c727)
warning: Overallocation Detected on Main device: (1106810+1) bitmap address (1c727)
too many warnings generated; suppressing subsequent ones
The volume /dev/disk4s6 appears to be OK
Storage system check exit code is 0
Shrinking APFS Physical Store disk4s6 from 747 620 515 840 to 249 999 998 976 bytes
Shrinking APFS data structures
Shrinking partition
Modifying partition map
Initialized /dev/rdisk4s7 as a 463 GB case-insensitive HFS Plus volume with a 40960k journal
Mounting disk
1 new disk created or changed due to APFS operation
Disk from APFS operation: disk4s7
Finished APFS operation