Erreurs répétitives installation Big Sur

[maya.ahh]

Hello,

On repart ici après les aventures racontées là : https://forum.macbidouille.com/index.php?sh...419020&st=0.

On est sur un MacBook Pro récent (16 pouces, 2019) et puissant (2,4 GHz Intel Core i9 8 cœurs ; 64 Go 2667 MHz DDR4). Le système est de nouveau stable, et pour installer Big Sur, j’ai créé via Utilitaire de Disque un volume dédié, nommé BigSur (disk1s6) :

Code

mayaahh2:~ jeremy$ diskutil list
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *4.0 TB     disk0
   1:                        EFI EFI                     314.6 MB   disk0s1
   2:                 Apple_APFS Container disk1         4.0 TB     disk0s2

/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +4.0 TB     disk1
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh HD - Données  789.8 GB   disk1s1
   2:                APFS Volume Preboot                 83.2 MB    disk1s2
   3:                APFS Volume Recovery                529.0 MB   disk1s3
   4:                APFS Volume VM                      1.1 GB     disk1s4
   5:                APFS Volume Macintosh HD            11.1 GB    disk1s5
   6:                APFS Volume BigSur                  7.3 MB     disk1s6

/dev/disk2 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +1.9 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS Copies de sauvegarde... 1.9 TB     disk2s2

/dev/disk3 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        +12.9 GB    disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS Shared Support          12.6 GB    disk3s2

J’ai lancé plusieurs tentative d’installation de Big Sur (Mac Os 11.0.1), ça bloque au bout de peu de temps, avant le reboot, avec un message d'erreur : « Une erreur s’est produite lors du chargement de la mise à jour », comme sur ma photo "blanche".

Après un énième essai, cette étape a été passée, l’ordinateur redémarre, mais je retrouve l’erreur qui avait tout cassé mon ordi avant-hier soir : « Une erreur s’est produite lors de l’application de la mise à jour logicielle », comme sur photo "noire". Une fois cliqué sur Ok, il faut choisir un disque pour redémarrer, ce qui implique dans mon cas de déverrouiller Macintosh HD car il est chiffré. Double Dong de démarrage, puis c’est ok. Heureusement que j’avais fait la manip de créer un nouveau volume, merci pour ce précieux conseil !

Pour info, deux nouveaux volumes aont été créés durant l’installation foireuse :

Code

mayaahh2:~ jeremy$ diskutil list
…
   6:                APFS Volume BigSur - Données        12.0 GB    disk1s6
   7:                APFS Volume BigSur                  24.6 KB    disk1s7
   8:                APFS Volume Update                  65.5 KB    disk1s8

…

Un reboot avec alt montre un seul disque bootable, Macintosh HD. Dans le volume Update, j’ai pas mal de choses dont des logs sans doute intéressants. Voilà la fin de l’install-log :

Code

Dec  6 16:55:00 MacBook-Pro OSInstaller[203]: Operation: Install Mobile Software Update failed, Failure Reason: Error Domain=com.apple.osinstall Code=-83 "Une erreur s’est produite lors de l’application de la mise à jour logicielle." UserInfo={NSLocalizedDescription=Une erreur s’est produite lors de l’application de la mise à jour logicielle., NSUnderlyingError=0x7fdc38d33860 {Error Domain=MobileSoftwareUpdateErrorDomain Code=29 "Failed to verify package contents." UserInfo={NSLocalizedDescription=Failed to verify package contents., NSUnderlyingError=0x7fdc38d2dce0 {Error Domain=MobileSoftwareUpdateErrorDomain Code=7 "SHA-1 mismatch for /System/Volumes/Data/private/tmp/tmp-mount-gtmeiH/softwareupdate.241.RFDPIU/source/payloadv2/payload.002: 248f077478443827d5ecacbd1b990649ddb7c68a should be 5c513b5c5a6a0b0bcda9b2e53dcbb2975519663f" UserInfo={NSLocalizedDescription=SHA-1 mismatch for /System/Volumes/Data/private/tmp/tmp-mount-gtmeiH/softwareupdate.241.RFDPIU/source/payloadv2/payload.002: 248f077478443827d5ecacbd1b990649ddb7c68a should be 5c513b5c5a6a0b0bcda9b2e53dcbb2975519663f, target_update=20B50}}}}}

Pour l’instant j’arrête les essais, mais je n’ai toujours pas Big Sur ! Si quelqu’un peut m’aider, merci d’avance !

Ce message a été modifié par maya.ahh - 6 Dec 2020, 18:24.

Fichier(s) joint(s)

 IMG_7379.jpg ( 95.66 Ko ) Nombre de téléchargements : 11
 IMG_7378.jpg ( 297.69 Ko ) Nombre de téléchargements : 10

 

[maya.ahh]

Alors, en mode Recovery, le SOS Disque est ok pour Macintosh HD, et pas tout à fait pour Macintosh HD - Datas, mais je crois que le problème détecté ne concerne que le snapshot TM. Voir photo jointe.

Ensuite, néanmoins, la commande suivant fonctionne bien qu’avec des erreur :

Code

mayaahh2:~ jeremy$ diskutil ap resizecontainer disk1 2t apfs "Big Sur" 0b
Started APFS operation
Checking the extent ref tree
Checking the fsroot tree
warning: apfs_fs_alloc_count is not valid (expected 41582, actual 2709924)
Verifying allocated space
warning: overallocation detected on Main device: (0x403c44+4) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403c49+5) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403c4f+12) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403c5c+24) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403c75+16) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403c87+2) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403c8a+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403c8e+308) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403dc3+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403dc7+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403dca+3) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403dce+2) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403dd1+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403dd3+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403dd5+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403dd7+92) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403e34+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403e36+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403e38+8) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403e41+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403e43+87) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403e9c+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403e9e+26) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403eb9+16) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403eca+13) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403ed8+5) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403ede+6) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403ee5+6) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403eec+7) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403ef8+3) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403efd+3) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403f02+7) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x403f0f+254) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x404010+2) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x404014+3) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x40401b+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x40401d+2) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x404021+3) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x404027+2) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x40402a+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x404030+3) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x404034+2) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x40403a+102) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x4040a2+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x4040a4+5) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x4040aa+7) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x4040b2+5) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x4040b8+2) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x4040bd+1) bitmap address (0xb1c7)
warning: overallocation detected on Main device: (0x4040c0+61) bitmap address (0xb1c7)
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 disk0s2 from 4 001 907 707 904 to 2 000 000 000 000 bytes
Shrinking APFS data structures
Shrinking partition
Modifying partition map
Mounting disk
1 new disk created or changed due to APFS operation
Disk from APFS operation: disk0s3
Finished APFS operation
mayaahh2:~ jeremy$

Je lance, pour voir, une réparation avec la fameuse option -o…

Ce message a été modifié par maya.ahh - 7 Dec 2020, 21:17.

Fichier(s) joint(s)

 IMG_7380.jpeg ( 219.27 Ko ) Nombre de téléchargements : 7