10.15 Catalina DD non reconnu au démarrage avec partition type FFFF

Bloc de code: 
-bash-3.2# gpt add -b 409640 -s 302734368 -t 7C3457EF-0000-11AA-AA11-00306543ECAC disk1 ; diskutil list internal
gpt add: disk1: Suspicious MBR at sector 0
disk1s2 added
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS HDD                     499.8 GB   disk0s2

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

/dev/disk24 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +155.0 GB   disk24
                                 Physical Store disk1s2
   1:                APFS Volume Preboot                 26.2 MB    disk24s2
   2:                APFS Volume                         523.5 MB   disk24s3
   3:                APFS Volume                         1.1 GB     disk24s4
   4:                APFS Volume                         126.1 GB   disk24s5
   5:                APFS Volume                         11.0 GB    disk24s6
 
La recréation du descripteur => a permis la régénération d'un Conteneur apfs disk24 à partir de la partition recréée.

- 4 volumes sur 5 ne paraissent pas remontés. Passe la commande :​
Bloc de code: 
diskutil mountDisk disk24 ; diskutil list internal

  • qui les remonte en lot et réaffiche la configuration interne

Poste le retour.
 
Bloc de code: 
-bash-3.2# diskutil mountDisk24 ; diskutil list internal
diskutil: did not recognize verb "mountDisk24"; type "diskutil" for a list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS HDD                     499.8 GB   disk0s2

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

/dev/disk24 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +155.0 GB   disk24
                                 Physical Store disk1s2
   1:                APFS Volume Preboot                 26.2 MB    disk24s2
   2:                APFS Volume Recovery                523.5 MB   disk24s3
   3:                APFS Volume VM                      1.1 GB     disk24s4
   4:                APFS Volume Macintosh SSD – données 126.1 GB   disk24s5
   5:                APFS Volume Macintosh SSD           11.0 GB    disk24s6
 
Victoire ! -->
Bloc de code: 
/dev/disk24 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +155.0 GB   disk24
                                 Physical Store disk1s2
   1:                APFS Volume Preboot                 26.2 MB    disk24s2
   2:                APFS Volume Recovery                523.5 MB   disk24s3
   3:                APFS Volume VM                      1.1 GB     disk24s4
   4:                APFS Volume Macintosh SSD – données 126.1 GB   disk24s5
   5:                APFS Volume Macintosh SSD           11.0 GB    disk24s6

  • le Conteneur apfs est régénéré > avec les 5 volumes de la distribution Catalina.

Redémarre (Menu  > Disque de démarrage >choisis Macintosh SSD > Redémarrer) -->

- je te souhaite une bonne réouverture de session :coucou:​

Je m'éclipse. Je reviendrai aux nouvelles demain matin.
 
Je comprends plus trop mais c'est impressionnant comme tu gères. Tu bosses chez Apple ?!!

---------------------------------------
Merci infiniment pour ton aide !! Malheureusement au démarrage, j'ai cette icône :

1584920724476.png​

Bonne nuit et merci encore
 
Dernière édition par un modérateur:
Si tu démarres avec les 2 touches ⌘R (cmd R) tenues pressées = démarrage sur l'OS de secours recelé dans le volume Recovery du Conteneur apfs reconstruit -->

- est-ce que tu vois s'afficher une  directe (au lieu d'un globe terrestre) ? - est-ce que tu obtiens bien un écran affichant une fenêtre de 4 Utilitaires macOS (= écran de la session de secours) ?​
 
Redémarre avec les 3 touches ⌘⌥R (par internet) => sur l'OS de secours Catalina.

- quand tu as l'écran aux 4 Utilitaires macOS > passe la commande :​
Bloc de code: 
diskutil list internal

  • et poste la configuration interne.
 
Voilà, c'est fait. J'obtiens ceci :
Bloc de code: 
-bash-3.2# diskutil list internal
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS HDD                     499.8 GB   disk0s2

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

/dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +155.0 GB   disk3
                                 Physical Store disk1s2
   1:                APFS Volume Preboot                 26.2 MB    disk3s2
   2:                APFS Volume Recovery                523.5 MB   disk3s3
   3:                APFS Volume VM                      1.1 GB     disk3s4
   4:                APFS Volume Macintosh SSD – données 126.0 GB   disk3s5
   5:                APFS Volume Macintosh SSD           11.0 GB    disk3s6
 
On voit bien le Conteneur affiché avec ses 5 volumes.

- passe la commande :​
Bloc de code: 
diskutil verifyVolume disk3

  • qui vérifie l'apfs du Conteneur et de ses volumes

Poste le retour.
 
Bloc de code: 
-bash-3.2# diskutil verifyVolume disk3
Started file system verification on disk3
Error: -69502: Storage system verify or repair with one or more encrypted and locked volumes (e.g. in an APFS Container) is not supported
ça n'a pas l'air bon :(
 
Il s'agit seulement de FileVault qui est activé et verrouille les 2 volumes principaux -->

- lance l'Utilitaire de disque (dans la fenêtre des 4 Utilitaires macOS) > sélectionne Macintosh HD grisé (= non monté) > ton mot-de-passe de session dans le panneau qui le requiert => Macintosh HD doit être libellé en noir, si remonté. Et il doit en être de même de manière synchone pour le volume-Données compagnon : Macintosh HD - Données​

=> est-ce que c'est bien le cas ?
 
Quitte l'Utilitaire de disque > relance le terminal > repasse la commande :
Bloc de code: 
diskutil verifyVolume disk3

  • et poste le retour.
 
Bon courage !!
Bloc de code: 
-bash-3.2# disutil verifyVolume disk3
-bash: disutil: command not found
-bash-3.2# diskutil verifyVolume disk3
Started file system verification on disk3
Verifying storage system
Performing fsck_apfs -n -x /dev/disk1s2
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 Preboot was formatted by hfs_convert (945.230.6) and last modified by apfs_kext (1412.81.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 (945.230.6) and last modified by apfs_kext (1412.81.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 (945.230.6) and last modified by apfs_kext (1412.81.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 SSD – données was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.81.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
error: Cross Check : FSroot tree references extent (0x128c7e4 + 59) which is not present in the ExtentRef tree
error: Cross Check : FSroot tree references extent (0x128c82c + 1) which is not present in the ExtentRef tree
error: Cross Check : FSroot tree references extent (0x128c840 + 57) which is not present in the ExtentRef tree
error: Cross Check : Mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (0xee0e7d + 2)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (0x128c7e4 + 59)
error: Cross Check : Mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (2) for extent (0x128c81f + 13)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (0x128c82c + 1)
error: Cross Check : Mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (2) for extent (0x128c82d + 19)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (0x128c840 + 57)
warning: apfs_fs_alloc_count is not valid (expected 30770020, actual 30770256)
Checking volume
Checking the APFS volume superblock
The volume Macintosh SSD was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.81.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
error: underallocation detected on Main device: (0x12880b2+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x12880df+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x12880e6+6) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128815e+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x12881a1+4) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128820a+13) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288218+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128821a+10) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288225+2) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288228+1) bitmap address (0x23544)
...
error: sm: sm_free_count (3958067) is not valid (3974698) (sm_dev 0)
Space Verification failed
The volume /dev/disk1s2 could not be verified completely
Storage system check exit code is 0
Finished file system verification on disk3
-bash-3.2#

J'ai dû supprimer plusieurs lignes sinon le message ne passait pas...
 
Il y a des erreurs dans la branche de l'apfs génératrice du volume-Données : Macintosh SSD - Données > et dans le spaceman (gestionnaire de l'allocation des blocs).

- passe la commande :​
Bloc de code: 
diskutil repairVolume disk3

  • qui tente de réparer l'apfs

Poste le retour.

[Je reviendrai dans ce fil cet après-midi.]
 
Voila les résultats. J'attends cet aprem alors. En tout cas, encore une fois merci pour tout ce temps!!
Bloc de code: 
-bash-3.2# diskutil repairVolume disk3
Started file system repair on disk3
Repairing storage system
Performing fsck_apfs -y -x /dev/disk1s2
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 Preboot was formatted by hfs_convert (945.230.6) and last modified by apfs_kext (1412.81.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 (945.230.6) and last modified by apfs_kext (1412.81.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 (945.230.6) and last modified by apfs_kext (1412.81.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 SSD – données was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.81.1)
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the extent ref tree
Checking the fsroot tree
error: Cross Check : FSroot tree references extent (0x128c7e4 + 59) which is not present in the ExtentRef tree
error: Cross Check : FSroot tree references extent (0x128c82c + 1) which is not present in the ExtentRef tree
error: Cross Check : FSroot tree references extent (0x128c840 + 57) which is not present in the ExtentRef tree
error: Cross Check : Mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (0xee0e7d + 2)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (0x128c7e4 + 59)
error: Cross Check : Mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (2) for extent (0x128c81f + 13)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (0x128c82c + 1)
error: Cross Check : Mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (2) for extent (0x128c82d + 19)
error: Cross Check : Mismatch between extentref entry reference count (0) and calculated fsroot entry reference count (1) for extent (0x128c840 + 57)
warning: apfs_fs_alloc_count is not valid (expected 30770022, actual 30770258)
Checking volume
Checking the APFS volume superblock
The volume Macintosh SSD was formatted by diskmanagementd (1412.11.7) and last modified by apfs_kext (1412.81.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
error: underallocation detected on Main device: (0x12880b2+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x12880df+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x12880e6+6) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128815e+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x12881a1+4) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128820a+13) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288218+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128821a+10) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288225+2) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288228+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128822b+10) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288236+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288238+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128823b+11) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288247+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288249+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128824b+9) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288255+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288257+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288259+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128825b+14) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128826a+10) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288275+4) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128827a+12) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288287+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x12882fa+7) bitmap address (0x23544)
error: underallocation detected on Main device: (0x1288376+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x12883f8+1) bitmap address (0x23544)
warning: overallocation detected on Main device: (0x1288000+4) bitmap address (0x23544)
warning: overallocation detected on Main device: (0x1288005+3) bitmap address (0x23544)
warning: overallocation detected on Main device: (0x1288009+5) bitmap address (0x23544)
warning: overallocation detected on Main device: (0x128800f+2) bitmap address (0x23544)
warning: overallocation detected on Main device: (0x1288012+2) bitmap address (0x23544)
warning: overallocation detected on Main device: (0x1288015+1) bitmap address (0x23544)
warning: overallocation detected on Main device: (0x1288017+1) bitmap address (0x23544)
...
error: underallocation detected on Main device: (0x128ffad+19) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128ffc4+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128ffc8+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128ffce+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128ffd1+1) bitmap address (0x23544)
error: underallocation detected on Main device: (0x128fffd+1) bitmap address (0x23544)
The volume /dev/disk1s2 appears to be OK
Storage system check exit code is 0
Finished file system repair on disk3
-bash-3.2#
 
Les erreurs de l'apfs n'ont pas été corrigées.

- passe encore la commande :​
Bloc de code: 
bless --info /Vol*/Macin*

  • qui affiche le chemin de démarrage de Macintosh SSD

Poste le retour.
 
Aie... Voici :
Bloc de code: 
-bash-3.2# bless --info /Vol*/Macin*
 12884905113 => Blessed System File is {Preboot}/2B1CF1C0-A008-48DC-A4F8-DC7F3B9B16D2/System/Library/CoreServices/boot.efi
 12884904112 => Blessed System Folder is {Preboot}/2B1CF1C0-A008-48DC-A4F8-DC7F3B9B16D2/System/Library/CoreServices
The blessed volume in this APFS container is "/Volumes/Macintosh SSD".
No blessed APFS snapshot for this volume.
 
Le chemin de démarrage est valide.

- retente une fois de plus ta chance : Menu  > Disque de démarrage > Macintosh SSD > Redémarrer​

=> décris ce qui se passe...
 

Sujets similaires

J
10.12 Sierra Réinstallation mac Sierra
Réponses
2
Affichages
458
macOS
JulieReap
J
F
Problème osx base system
Réponses
3
Affichages
493
macOS
Locke
Locke
J
10.13 High Sierra Permission denied en essayant d'installer High Sierra depuis une clef USB
Réponses
12
Affichages
2K
macOS
jackoup
J
D
10.13 High Sierra Panneau interdit au démarrage du Imac
Réponses
12
Affichages
2K
macOS
Locke
Locke
V
disque dur hs
Réponses
5
Affichages
805
macOS
Locke
Locke
Haut Bas