No subject dir found in Recovery so will create UUID recoveryVolumeSubjectDirPreExisted=0 If exists, do hard test for any existing Recovery Volume subject dir being a DIR directly into /Volumes/ and when it cannot, it copies the files into /Systems/Volumes/Data/.įailed to prep /Volumes/macOS Base System for brtoolĪssert existing-or-new subject dir name should be recoveryVolumeSubjectDir=/Volumes/Recovery/B392677C-67A5-4583-B8DF-DEB7B13F0E6C It looks like the system attempts to add the recovery volume, etc. 16:20:06-07 Lisas-MacBook-Pro atomicupdatetool: atomicupdatetool:EnsureRecoveryBooter: Started operations on Target (Subject) Volume = disk1s2 16:20:06-07 Lisas-MacBook-Pro atomicupdatetool: atomicupdatetool: Failed to prep /Volumes/macOS Base System for brtool 16:19:58-07 Lisas-MacBook-Pro suhelperd: Mount point /Volumes/RecoveryHDMeta 15:59:53-07 MacBook-Pro Language Chooser: Setup: Factory cable attached:0 Systems/Volumes/Data/macOS Base System/ etc.Īdditional information from Setup and installation Volumes/macOS Base System/ etc., and copied to Interestingly I found the same issue of files not found in
#MAC OS BASE SYSTEM INSTALL#
I returned the MBP to Costco yesterday and took the opportunity to look at the install log of the MBP on display. Sep 30 16:27:17 MacBook-Pro OSInstaller: Using product at distance 5 Sep 13 23:22:43 MacBook-Pro OSInstaller: Using product at distance 5 Sep 13 23:22:43 MacBook-Pro OSInstaller: Finding disk for productURL: /macOS Install Data Successfully updated disk1s2/macOS Install Data/Locked Files/Boot Files. Localized EFI Login resources do not need update.Ĭreating data with UUID B392677C-67A5-4583-B8DF-DEB7B13F0E6C.Ĭopying /Volumes/macOS Base System/System/Library/Caches// to /System/Volumes/Data/macOS Install Data/Locked Files/Boot FilesĬopying /Volumes/macOS Base System/usr/standalone/i386/EfiLoginUI/ to /System/Volumes/Data/macOS Install Data/Locked Files/Boot FilesĬopying /Volumes/macOS Base System/System/Library/Caches//EFILoginLocalizations to /System/Volumes/Data/macOS Install Data/Locked Files/Boot FilesĬopying /Volumes/macOS Base System/System/Library/PrelinkedKernels/prelinkedkernel to /System/Volumes/Data/macOS Install Data/Locked Files/Boot FilesĬopying files read before the booter runs.Īctivating files used before the booter runs. Note: /Volumes/macOS Base System/System/Library/Kernels/kernel: No such file or directoryĬSFDE property cache does not need update.
Warning: /Volumes/macOS Base System/Library/Apple/System/Library/Extensions: No such file or directory Warning: /Volumes/macOS Base System/AppleInternal/Library/Extensions: No such file or directory
#MAC OS BASE SYSTEM UPDATE#
Begin System Software Update Arming -Įnsuring /Volumes/macOS Base System's caches are up to date. The software update below occurred directly after initial set-up and installation of Catalina.
#MAC OS BASE SYSTEM PRO#
The data they are viewing is showing the MacBook Pro operating as expected”, so I continue to look for a solution. The information doesn’t show anything mounted incorrectly. to the engineers at Apple Support, they continue to claim “this is expected behavior. After a month of sending logs, pictures, etc. I recently discovered the following information which demonstrates that this problem exists /Volumes/macOS Base System being copied/moved to /Volumes/System/Volumes/macOS Base System/ because Volumes/macOS Base System/(and associated files) do not exist. Sep 14 19:28:14 MacBook-Air osinstallersetupd: Using product PKSecureNetEnabledProduct at distance 5 Sep 14 19:28:14 MacBook-Air osinstallersetupd: Using product based on media at /Volumes/OS X Install ESD at distance 5 I believe this is caused by a shared file. Please note, reinstallation of macOS from recovery, internet recovery or a USB installer does not copy or move macOS Base System from /System/Volumes/Data back to /Volumes. The following information is from a recent install log of macOS Sierra, which I have included because “using product at distance 5” began here. This problem has occurred on the previous eight MBA’s I purchased and returned during the past two years because I have been unable to resolve this problem.
As a result, the install is always based on “using product at distance 5” with the startup volume in /Volumes/System/ or /Volumes/System/Volumes/ instead of /Volumes/, where it belongs. This problem started in December 2018 when the recovery partition on my 2011 MBA got messed up during one of my attempts at performing a clean, USB installations of macOS High Sierra. The problem I have with my new 2020 13” MacBook Pro running Catalina 10.15.7 unfortunately, is not a new problem.
0 kommentar(er)
