10.14 Mojave Erreur -69808 diskutil verifyVolume disk1

Bloc de code: 
MacBook Pro Eric:~ Eric$ diskutil ap resizeContainer disk1 450g jhfs+ Brol 0b ; diskutil list
Started APFS operation
Aligning shrink delta to 49 963 175 936 bytes and targeting a new physical store size of 449 999 998 976 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 73 886 859 264 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 Macintosh_SSD was formatted by diskmanagementd (945.250.134) and last modified by apfs_kext (945.250.134)
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.241.4) and last modified by apfs_kext (945.250.134)
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.241.4) and last modified by apfs_kext (945.250.134)
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.241.4) and last modified by apfs_kext (945.250.134)
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
 
La suite

Bloc de code: 
warning: Overallocation Detected on Main device: (870020+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870023+7) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870031+5) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870037+10) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870048+5) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870054+26) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870080+64) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870144+64) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870208+64) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870272+47) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870320+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870323+5) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870330+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870333+3) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870336+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870339+3) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870344+1) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870346+1) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870348+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870351+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870354+17) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870372+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870375+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870379+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870382+18) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870400+64) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870464+64) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870528+64) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870592+60) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870653+1) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870655+1) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870656+15) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870672+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870675+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870678+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870681+1) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870684+8) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870693+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870697+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870700+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870704+1) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870710+1) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870712+1) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870714+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870718+1) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870721+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870724+2) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870727+1) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870730+1) bitmap address (7d5d)
warning: Overallocation Detected on Main device: (870732+52) bitmap address (7d5d)
too many warnings generated; suppressing subsequent ones

MacBook Pro Eric:~ Eric$
 
et enfin

Bloc de code: 
The volume /dev/disk0s2 appears to be OK
Storage system check exit code is 0
Shrinking APFS Physical Store disk0s2 from 499 963 174 912 to 449 999 998 976 bytes
Shrinking APFS data structures
Shrinking partition
Modifying partition map
Initialized /dev/rdisk0s3 as a 46 GB case-insensitive HFS Plus volume with a 8192k journal
Mounting disk
1 new disk created or changed due to APFS operation
Disk from APFS operation: disk0s3
Finished APFS operation
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         500.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk1         450.0 GB   disk0s2
   3:                  Apple_HFS Brol                    49.8 GB    disk0s3

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +450.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh_SSD           62.5 GB    disk1s1
   2:                APFS Volume Preboot                 42.2 MB    disk1s2
   3:                APFS Volume Recovery                535.2 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4

/dev/disk2 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +2.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS Sauvegarde Time Machine 2.0 TB     disk2s2
 
Tu as bien eu la création d'un volume Brol -->
Bloc de code: 
   3:                  Apple_HFS Brol                    49.8 GB    disk0s3

  • l'apfs est donc redimensionnable. Les erreurs de sur-allocation de blocs concernant l'appareil principal (= Macintosh_SSD) --> sont imputables au spaceman (le gestionnaire d'allocation d'espace de blocs de l'apfs). Je pense que tu peux faire avec > l'apfs fonctionnant correctement par ailleurs.

Passe la commande :
Bloc de code: 
diskutil eraseVolume free null disk0s3 ; diskutil ap resizeContainer disk1 0b ; diskutil list

  • la commande supprime la partition Brol > récupère son espace au Conteneur apfs > réaffiche la configuration des disques. C'est donc le test à rebours.

Poste l'affichage retourné (comme tu as pu le voir > une vérification de l'apfs est engagée en préalable de toute opération de repartitionnement).
 
  • J’aime
Réactions: EricM
Bloc de code: 
MacBook Pro Eric:~ Eric$ diskutil eraseVolume free null disk0s3 ; diskutil ap resizeContainer disk1 0b ; diskutil list
Started erase on disk0s3 Brol
Unmounting disk
Finished erase on disk0
Started APFS operation
Aligning grow delta to 49 963 175 936 bytes and targeting a new physical store size of 499 963 174 912 bytes
Determined the maximum size for the targeted physical store of this APFS Container to be 499 962 146 816 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 Macintosh_SSD was formatted by diskmanagementd (945.250.134) and last modified by apfs_kext (945.250.134)
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.241.4) and last modified by apfs_kext (945.250.134)
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.241.4) and last modified by apfs_kext (945.250.134)
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.241.4) and last modified by apfs_kext (945.250.134)
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
 
La suite

Bloc de code: 
warning: Overallocation Detected on Main device: (870020+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870023+7) bitmap address (20256)
warning: Overallocation Detected on Main device: (870031+5) bitmap address (20256)
warning: Overallocation Detected on Main device: (870037+10) bitmap address (20256)
warning: Overallocation Detected on Main device: (870048+5) bitmap address (20256)
warning: Overallocation Detected on Main device: (870054+26) bitmap address (20256)
warning: Overallocation Detected on Main device: (870080+64) bitmap address (20256)
warning: Overallocation Detected on Main device: (870144+64) bitmap address (20256)
warning: Overallocation Detected on Main device: (870208+64) bitmap address (20256)
warning: Overallocation Detected on Main device: (870272+47) bitmap address (20256)
warning: Overallocation Detected on Main device: (870320+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870323+5) bitmap address (20256)
warning: Overallocation Detected on Main device: (870330+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870333+3) bitmap address (20256)
warning: Overallocation Detected on Main device: (870336+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870339+3) bitmap address (20256)
warning: Overallocation Detected on Main device: (870344+1) bitmap address (20256)
warning: Overallocation Detected on Main device: (870346+1) bitmap address (20256)
warning: Overallocation Detected on Main device: (870348+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870351+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870354+17) bitmap address (20256)
warning: Overallocation Detected on Main device: (870372+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870375+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870379+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870382+18) bitmap address (20256)
warning: Overallocation Detected on Main device: (870400+64) bitmap address (20256)
warning: Overallocation Detected on Main device: (870464+64) bitmap address (20256)
warning: Overallocation Detected on Main device: (870528+64) bitmap address (20256)
warning: Overallocation Detected on Main device: (870592+60) bitmap address (20256)
warning: Overallocation Detected on Main device: (870653+1) bitmap address (20256)
warning: Overallocation Detected on Main device: (870655+1) bitmap address (20256)
warning: Overallocation Detected on Main device: (870656+15) bitmap address (20256)
warning: Overallocation Detected on Main device: (870672+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870675+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870678+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870681+1) bitmap address (20256)
warning: Overallocation Detected on Main device: (870684+8) bitmap address (20256)
warning: Overallocation Detected on Main device: (870693+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870697+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870700+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870704+1) bitmap address (20256)
warning: Overallocation Detected on Main device: (870710+1) bitmap address (20256)
warning: Overallocation Detected on Main device: (870712+1) bitmap address (20256)
warning: Overallocation Detected on Main device: (870714+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870718+1) bitmap address (20256)
warning: Overallocation Detected on Main device: (870721+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870724+2) bitmap address (20256)
warning: Overallocation Detected on Main device: (870727+1) bitmap address (20256)
warning: Overallocation Detected on Main device: (870730+1) bitmap address (20256)
warning: Overallocation Detected on Main device: (870732+52) bitmap address (20256)
too many warnings generated; suppressing subsequent ones
The volume /dev/disk0s2 appears to be OK
 
La fin

Bloc de code: 
Storage system check exit code is 0
Growing APFS Physical Store disk0s2 from 449 999 998 976 to 499 963 174 912 bytes
Modifying partition map
Growing APFS data structures
Finished APFS operation
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         500.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk1         500.0 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh_SSD           62.6 GB    disk1s1
   2:                APFS Volume Preboot                 42.2 MB    disk1s2
   3:                APFS Volume Recovery                535.2 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4

/dev/disk2 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +2.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS Sauvegarde Time Machine 2.0 TB     disk2s2

MacBook Pro Eric:~ Eric$
 
Opération à rebours réussie.

Je ne vois pas ton DDE (avec le volume Clone) : il n'est pas branché ?
 
  • J’aime
Réactions: EricM
Désolé, il était débranché

Bloc de code: 
MacBook Pro Eric:~ Eric$ diskutil list
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         500.3 GB   disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk1         500.0 GB   disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +500.0 GB   disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh_SSD           62.6 GB    disk1s1
   2:                APFS Volume Preboot                 42.2 MB    disk1s2
   3:                APFS Volume Recovery                535.2 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4

/dev/disk2 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +2.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS Sauvegarde Time Machine 2.0 TB     disk2s2

/dev/disk3 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 TB     disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS Sauvegarde WD           1.9 TB     disk3s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk3s3
   4:                  Apple_HFS Clone                   99.2 GB    disk3s4
   5:                 Apple_Boot Recovery HD             650.0 MB   disk3s5

MacBook Pro Eric:~ Eric$
 
Passe la commande :
Bloc de code: 
bless --info /Volumes/Clone

  • la commande affiche le chemin de démarrage de Clone > s'il en existe un

Poste le tableau retourné.
 
  • J’aime
Réactions: EricM
Bloc de code: 
MacBook Pro Eric:~ Eric$ bless --info /Volumes/Clone
finderinfo[0]: 165745 => Blessed System Folder is /Volumes/Clone/System/Library/CoreServices
finderinfo[1]: 286171 => Blessed System File is /Volumes/Clone/System/Library/CoreServices/boot.efi
finderinfo[2]:      0 => Open-folder linked list empty
finderinfo[3]:      0 => No alternate OS blessed file/folder
finderinfo[4]:      0 => Unused field unset
finderinfo[5]: 165745 => OS X blessed folder is /Volumes/Clone/System/Library/CoreServices
64-bit VSDB volume id:  0x3016C8A19947A88E
MacBook Pro Eric:~ Eric$
 
Chemin de démarrage valide. Carbon Copy Cloner a "béni" (= inscrit un chemin de démarrage sur son en-tête) le volume Clone. En considérant donc qu'il recèle un Système démarrable. Cette précision devrait suffire ici à assurer la validité de Clone.

----------

Je t'engage enfin par prudence à créer un 2è utilisateur admin - un auxiliaire. Va à : Menu  > Préférences Système > Utilisateurs & groupes > déverrouille le cadenas. Presse le bouton + pour créer un utilisateur. Dans le panneau de configuration choisis : Nom complet = toto > Nom du compte = toto > Mot de passe = toto => presse le bouton : "Créer l'utilisateur" -->

- est-ce que c'est fait ?​
 
Dans le nouveau volume Macintosh_SSD > est-ce que le 1er utilisateur admin que tu as créé --> possède les mêmes identifiants de compte (mêmes noms notammment) que celui de l'ancien Macintosh_SSD dont le compte est sauvegardé dans le volume Clone ?
 
Oui, il porte exactement les mêmes identifiants.
 
Alors tu devrais pouvoir lancer la migration -->

- va à : Applications > Utilitaires > lance l'Assistant de migration > choisis l'option de récupération de données à partir d'un Mac... > et désigne-lui le volume Clone comme source.​

- si l'Assistant de migration accepte le volume Clone comme une source valide > il va te proposer de récupérer les compte d'utilisateurs > les applications tierces > des réglages généraux. S'apercevant qu'il existe dans le volume source Clone un utilisateur ayant les mêmes identifiants que celui du volume Macintosh_SSD de destination --> il devrait te demander si tu veux remplacer l'utilisateur de Macintosh_SSD par celui de Clone : tu acceptes alors. Le second utilisateur toto est là en couverture au cas où ça tournerait mal.​

=> tu n'as qu'à dire si la migration se lance...
 
Tôt ce matin, j'avais lancé la migration de Clone vers Macintosh_SSD. Il aura fallut toute la nuit pour télécharger 10.14.4 car CCC ne voulait pas faire la migration.
Tout fonctionne à nouveau donc. Je garde toto au chaud :D
 
En fait : tu es hyperactif :hilarious:. À peine on tourne la tête > tu as déjà fait 3 sauts périlleux et un saut carpé...

- moi-même > à voir les 62 Go de données de Macintosh_SSD --> j'aurai bien dû me douter que la migration avait déjà été accomplie. Mais je n'ai fait attention qu'aux lignes de vérification et de de partitionnement.​

Alors content pour toi puisque tout est redevenu normal ! Veux-tu purger ton volume Sauvegarde WD des dossiers du clone ?
 
J'ai pris cette initiative, "heureuse", j'ai eu de la chance. Le but étant de gagner du temps. Sans doute une déformation professionnelle de ma part :D

Si cela est possible et n'est pas destructeur, c'est avec curiosité que j'aimerais connaître la suite.
 
Passe la commande :
Bloc de code: 
ls -A /Volumes/"Sauvegarde WD"

  • qui liste les objets de 1er rang du volume Sauvegarde WD

Poste le tableau.
 

Sujets similaires

Aski
macOS Ventura No CoreStorage logical volume groups found
Réponses
6
Affichages
454
macOS
Locke
Locke
N
10.14 Mojave "Disque incompatible" en message d'ouverture
Réponses
8
Affichages
2K
macOS
Ahiqar
A
B
macOS Monterey souci suite à restauration Time Machine
Réponses
18
Affichages
1K
macOS
bil36
B
U
macOS Ventura Modifier taille partition
Réponses
2
Affichages
609
macOS
ubuubu
U
GTV6
10.15 Catalina Problème de boot
Réponses
7
Affichages
902
macOS
sinbad21
sinbad21
Haut Bas
Back