![]() |
Bienvenue invité ( Connexion | Inscription )
![]() |
![]()
Message
#1
|
|
Adepte de Macbidouille ![]() Groupe : Membres Messages : 71 Inscrit : 4 Dec 2020 Membre no 213 020 ![]() |
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)
![]() ![]() |
|
|
![]() |
![]()
Message
#2
|
|
Adepte de Macbidouille ![]() Groupe : Membres Messages : 71 Inscrit : 4 Dec 2020 Membre no 213 020 ![]() |
Merci !
Je pense que l’opération s’est bien passée, malgré les mêmes erreurs en sortie : 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 disk2 2.0 TB disk0s2 3: Apple_APFS Container disk1 2.0 TB disk0s3 /dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +2.0 TB disk1 Physical Store disk0s3 1: APFS Volume Big Sur - Données 11.9 GB disk1s1 2: APFS Volume Preboot 136.1 MB disk1s2 3: APFS Volume Recovery 652.2 MB disk1s3 4: APFS Volume VM 20.5 KB disk1s4 5: APFS Volume Big Sur 32.8 KB disk1s5 6: APFS Volume Update 86.0 KB disk1s6 /dev/disk2 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +2.0 TB disk2 Physical Store disk0s2 1: APFS Volume Macintosh HD - Données 799.9 GB disk2s1 2: APFS Volume Preboot 79.9 MB disk2s2 3: APFS Volume Recovery 529.0 MB disk2s3 4: APFS Volume VM 1.1 GB disk2s4 5: APFS Volume Macintosh HD 11.0 GB disk2s5 mayaahh2:~ jeremy$ diskutil ap deletecontainer disk0s3 Started APFS operation on disk1 Deleting APFS Container with all of its APFS Volumes Unmounting Volumes Unmounting Volume "Big Sur - Données" on disk1s1 Unmounting Volume "Preboot" on disk1s2 Unmounting Volume "Recovery" on disk1s3 Unmounting Volume "VM" on disk1s4 Unmounting Volume "Big Sur" on disk1s5 Unmounting Volume "Update" on disk1s6 Deleting Volumes Deleting Container Wiping former APFS disks Switching content types Reformatting former APFS disks Initialized /dev/rdisk0s3 as a 2 TB case-insensitive HFS Plus volume with a 155648k journal Mounting disk 1 new disk created or changed due to APFS operation Disk from APFS operation: disk0s3 Finished APFS operation on disk1 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 disk2 2.0 TB disk0s2 3: Apple_HFS Untitled 2.0 TB disk0s3 /dev/disk2 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +2.0 TB disk2 Physical Store disk0s2 1: APFS Volume Macintosh HD - Données 799.9 GB disk2s1 2: APFS Volume Preboot 79.9 MB disk2s2 3: APFS Volume Recovery 529.0 MB disk2s3 4: APFS Volume VM 1.1 GB disk2s4 5: APFS Volume Macintosh HD 11.0 GB disk2s5 mayaahh2:~ jeremy$ diskutil eraseVolume free space disk0s3 Started erase on disk0s3 Untitled Unmounting disk Finished erase on disk0 mayaahh2:~ jeremy$ diskutil ap resizeContainer disk0s2 0b Started APFS operation Aligning grow delta to 2 001 907 707 904 bytes and targeting a new physical store size of 4 001 907 707 904 bytes Determined the maximum size for the targeted physical store of this APFS Container to be 4 001 906 679 808 bytes Resizing APFS Container designated by APFS Container Reference disk2 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 warning: container has been mounted by APFS version 1677.50.1, which is newer than 1412.141.1 warning: disabling overallocation repairs by default; use -o to override 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 HD - Données 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 749796, actual 195297993) Checking volume Checking the APFS volume superblock The volume Preboot 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 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 41017, actual 2697534) Verifying allocated space warning: overallocation detected on Main device: (0x231a96+3) bitmap address (0xa6871) [là, on a mille fois le même message, d’ailleurs, même le terminal en a marre, cf. au dessous] warning: overallocation detected on Main device: (0x231c48+10) bitmap address (0xa6871) 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 Growing APFS Physical Store disk0s2 from 2 000 000 000 000 to 4 001 907 707 904 bytes Modifying partition map Growing APFS data structures Finished APFS operation 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 disk2 4.0 TB disk0s2 /dev/disk2 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +4.0 TB disk2 Physical Store disk0s2 1: APFS Volume Macintosh HD - Données 800.3 GB disk2s1 2: APFS Volume Preboot 79.9 MB disk2s2 3: APFS Volume Recovery 529.0 MB disk2s3 4: APFS Volume VM 1.1 GB disk2s4 5: APFS Volume Macintosh HD 11.0 GB disk2s5 |
|
|
![]() ![]() |
Nous sommes le : 4th August 2025 - 10:16 |