crwdns2934243:0crwdne2934243:0 Dan
crwdns2947189:0crwdne2947189:0:
/Volumes/macOS Base System/AppleInternal/Library/Ext/doesn't exist...
crwdns2934249:0crwdne2934249:0:
| The problem I have with my new 2020 13” MacBook Pro running Catalina 10.15.7 unfortunately, is not a new problem. 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. 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 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. The following information is from a recent install log of macOS Sierra, which I have included because “using product at distance 5” began here. 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. I believe this is caused by a shared file. | |
| Sep 14 19:28:14 MacBook-Air osinstallersetupd[547]: '''Using product <OSISInstallMediaProduct> based on media at /Volumes/OS X Install ESD at distance 5''' | |
| Sep 14 19:28:14 MacBook-Air osinstallersetupd[547]: '''Using product PKSecureNetEnabledProduct <file:///Volumes/Macintosh%20HD/macOS%20Install%20Data/> at distance 5''' | |
| 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. After a month of sending logs, pictures, etc. to the engineers at Apple Support, they continue to claim; ''“this is expected behavior. The information doesn’t show anything mounted incorrectly. The data they are viewing is showing the MacBook Pro operating as expected”, so I continue to look for a solution.'' The software update below occurred directly after initial set-up and installation of Catalina. | |
| ---- Begin System Software Update Arming ----- | |
| Ensuring /Volumes/macOS Base System's caches are up to date. | |
| Warning: /Volumes/macOS Base System/AppleInternal/Library/Extensions: No such file or directory | |
| Warning: /Volumes/macOS Base System/Library/Apple/System/Library/Extensions: No such file or directory | |
| Note: /Volumes/macOS Base System/System/Library/Kernels/kernel: No such file or directory | |
| Primary kext cache does not need update. | |
| CSFDE property cache does not need update. | |
| Localized EFI Login resources do not need update. | |
| Mounting helper partition... | |
| Looking for missing files. | |
| Copying files used by the booter. | |
| creating com.apple.Boot.plist data with UUID B392677C-67A5-4583-B8DF-DEB7B13F0E6C. | |
| copying /Volumes/macOS Base System/System/Library/Caches/com.apple.corestorage/EncryptedRoot.plist.wipekey to /System/Volumes/Data/macOS Install Data/Locked Files/Boot Files | |
| copying /Volumes/macOS Base System/usr/standalone/i386/EfiLoginUI/ to /System/Volumes/Data/macOS Install Data/Locked Files/Boot Files | |
| copying /Volumes/macOS Base System/System/Library/Caches/com.apple.corestorage/EFILoginLocalizations to /System/Volumes/Data/macOS Install Data/Locked Files/Boot Files | |
| copying /Volumes/macOS Base System/System/Library/PrelinkedKernels/prelinkedkernel to /System/Volumes/Data/macOS Install Data/Locked Files/Boot Files | |
| Copying files read before the booter runs. | |
| Moving aside old label. | |
| Copying new booter. | |
| Activating new booter. | |
| Activating files used by the booter. | |
| Activating files used before the booter runs. | |
| Successfully updated disk1s2/macOS Install Data/Locked Files/Boot Files. | |
| Rolling back any incomplete updates. | |
| Sep 13 23:22:43 MacBook-Pro OSInstaller[644]: Finding disk for productURL: /macOS Install Data | |
| Sep 13 23:22:43 MacBook-Pro OSInstaller[644]: '''Using product <OSProduct: 0x7fa16ed59900> at distance 5''' | |
| ++Sep 30 Install++ | |
| Sep 30 16:27:17 MacBook-Pro OSInstaller[665]: '''Using product <OSProduct: 0x7fa04f31f320> at distance 5''' | |
| - | [br] |
| - | |
| - | [br] |
| - | |
| === Update (10/22/2020) === | |
| - | |
| I returned the MBP to Costco yesterday and took the opportunity to look at the install log of the MBP on display. Interestingly I found the same issue of files not found in | |
| /Volumes/macOS Base System/ etc., and copied to | |
| /Systems/Volumes/Data/macOS Base System/ etc.. | |
| Additional information from Setup and installation; | |
| 2020-09-13 15:59:53-07 MacBook-Pro Language Chooser[270]: Setup: Factory cable attached:0 | |
| 2020-09-13 16:19:58-07 Lisas-MacBook-Pro suhelperd[703]: Mount point /Volumes/RecoveryHDMeta | |
| 2020-09-13 16:20:06-07 Lisas-MacBook-Pro atomicupdatetool[1465]: atomicupdatetool: Failed to prep /Volumes/macOS Base System for brtool | |
| 2020-09-13 16:20:06-07 Lisas-MacBook-Pro atomicupdatetool[1465]: atomicupdatetool:EnsureRecoveryBooter: Started operations on Target (Subject) Volume = disk1s2 | |
| - | |
| - | [br] |
| It looks like the system attempts to add the recovery volume, etc. directly into /Volumes/ and when it cannot, it copies the files into /Systems/Volumes/Data/. | |
| 2020-09-13 16:19:58-07 Lisas-MacBook-Pro suhelperd[703]: Mount point /Volumes/RecoveryHDMeta | |
| Mount point /Volumes/RecoveryHDMeta | |
| Failed to prep /Volumes/macOS Base System for brtool | |
| Assert existing-or-new subject dir name should be recoveryVolumeSubjectDir=/Volumes/Recovery/B392677C-67A5-4583-B8DF-DEB7B13F0E6C | |
| If exists, do hard test for any existing Recovery Volume subject dir being a DIR | |
| UUID recoveryVolumeSubjectDirPreExisted=0 | |
| No subject dir found in Recovery so will create | |
| Recovery vol subj dir url for creation = file:///Volumes/Recovery/B392677C-67A5-4583-B8DF-DEB7B13F0E6C | |
| Did create dir; err=(null) | |
| Determined appleBootPartitionSlurpProceed=0 | |
| Not slurping legacy Apple_Boot | |
| No caller opinion if to do boot install, and no path | |
| Determined bootSystemInstallProceed=1 | |
| - | Determined bootSystemSourcePath=/System/Volumes/Data |
| + | Determined bootSystemSourcePath=/System/Volumes/Data[br] |
| - | [br] |
| - | I am wondering if this is a problem (bug?) that occurs when Catalina is installed during the initial setup process in new MacBooks only. If so, is Apple aware of this? It might explain the response I received from Apple’s Engineers: “''the information doesn’t show anything mounted incorrectly. The data they are viewing is showing the MacBook Pro is operating as expected”''. |
| + | I am wondering if this is a problem (bug?) that occurs when Catalina is installed during the initial setup process in new MacBooks only. If so, is Apple aware of this? It might explain the response I received from Apple’s Engineers: “''the information doesn’t show anything mounted incorrectly. The data they are viewing is showing the MacBook Pro is operating as expected”''. |
| - | |
| + | Interpreted translation - ''Yes, we know''… I only found it because I was looking for something else. While I have an issue with my 2011 MBA which has caused me similar issues with new MacBooks, this problem is something else entirely. |
| - | [br] |
| - | |
| - | [br] |
| - | |
| - | [br] |
| - | |
| - | [br] |
| + | Any thoughts? |
crwdns2866306:0crwdne2866306:0:
MacBook Pro 13" Two Thunderbolt Ports 2020
crwdns2915684:0crwdne2915684:0:
open
crwdns2934245:0crwdne2934245:0 Lisa
crwdns2947189:0crwdne2947189:0:
/Volumes/macOS Base System/AppleInternal/Library/Ext/doesn't exist...
crwdns2934249:0crwdne2934249:0:
| The problem I have with my new 2020 13” MacBook Pro running Catalina 10.15.7 unfortunately, is not a new problem. 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. 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 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. The following information is from a recent install log of macOS Sierra, which I have included because “using product at distance 5” began here. 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. I believe this is caused by a shared file. | |
| Sep 14 19:28:14 MacBook-Air osinstallersetupd[547]: '''Using product <OSISInstallMediaProduct> based on media at /Volumes/OS X Install ESD at distance 5''' | |
| Sep 14 19:28:14 MacBook-Air osinstallersetupd[547]: '''Using product PKSecureNetEnabledProduct <file:///Volumes/Macintosh%20HD/macOS%20Install%20Data/> at distance 5''' | |
| 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. After a month of sending logs, pictures, etc. to the engineers at Apple Support, they continue to claim; ''“this is expected behavior. The information doesn’t show anything mounted incorrectly. The data they are viewing is showing the MacBook Pro operating as expected”, so I continue to look for a solution.'' The software update below occurred directly after initial set-up and installation of Catalina. | |
| ---- Begin System Software Update Arming ----- | |
| Ensuring /Volumes/macOS Base System's caches are up to date. | |
| Warning: /Volumes/macOS Base System/AppleInternal/Library/Extensions: No such file or directory | |
| Warning: /Volumes/macOS Base System/Library/Apple/System/Library/Extensions: No such file or directory | |
| Note: /Volumes/macOS Base System/System/Library/Kernels/kernel: No such file or directory | |
| Primary kext cache does not need update. | |
| CSFDE property cache does not need update. | |
| Localized EFI Login resources do not need update. | |
| Mounting helper partition... | |
| Looking for missing files. | |
| Copying files used by the booter. | |
| creating com.apple.Boot.plist data with UUID B392677C-67A5-4583-B8DF-DEB7B13F0E6C. | |
| copying /Volumes/macOS Base System/System/Library/Caches/com.apple.corestorage/EncryptedRoot.plist.wipekey to /System/Volumes/Data/macOS Install Data/Locked Files/Boot Files | |
| copying /Volumes/macOS Base System/usr/standalone/i386/EfiLoginUI/ to /System/Volumes/Data/macOS Install Data/Locked Files/Boot Files | |
| copying /Volumes/macOS Base System/System/Library/Caches/com.apple.corestorage/EFILoginLocalizations to /System/Volumes/Data/macOS Install Data/Locked Files/Boot Files | |
| copying /Volumes/macOS Base System/System/Library/PrelinkedKernels/prelinkedkernel to /System/Volumes/Data/macOS Install Data/Locked Files/Boot Files | |
| Copying files read before the booter runs. | |
| Moving aside old label. | |
| Copying new booter. | |
| Activating new booter. | |
| Activating files used by the booter. | |
| Activating files used before the booter runs. | |
| Successfully updated disk1s2/macOS Install Data/Locked Files/Boot Files. | |
| Rolling back any incomplete updates. | |
| Sep 13 23:22:43 MacBook-Pro OSInstaller[644]: Finding disk for productURL: /macOS Install Data | |
| Sep 13 23:22:43 MacBook-Pro OSInstaller[644]: '''Using product <OSProduct: 0x7fa16ed59900> at distance 5''' | |
| ++Sep 30 Install++ | |
| Sep 30 16:27:17 MacBook-Pro OSInstaller[665]: '''Using product <OSProduct: 0x7fa04f31f320> at distance 5''' | |
| [br] | |
| [br] | |
| + | |
| + | === Update (10/22/2020) === |
| + | |
| + | I returned the MBP to Costco yesterday and took the opportunity to look at the install log of the MBP on display. Interestingly I found the same issue of files not found in |
| + | |
| + | /Volumes/macOS Base System/ etc., and copied to |
| + | |
| + | /Systems/Volumes/Data/macOS Base System/ etc.. |
| + | |
| + | Additional information from Setup and installation; |
| + | |
| + | 2020-09-13 15:59:53-07 MacBook-Pro Language Chooser[270]: Setup: Factory cable attached:0 |
| + | |
| + | 2020-09-13 16:19:58-07 Lisas-MacBook-Pro suhelperd[703]: Mount point /Volumes/RecoveryHDMeta |
| + | |
| + | 2020-09-13 16:20:06-07 Lisas-MacBook-Pro atomicupdatetool[1465]: atomicupdatetool: Failed to prep /Volumes/macOS Base System for brtool |
| + | |
| + | 2020-09-13 16:20:06-07 Lisas-MacBook-Pro atomicupdatetool[1465]: atomicupdatetool:EnsureRecoveryBooter: Started operations on Target (Subject) Volume = disk1s2 |
| + | |
| + | [br] |
| + | |
| + | It looks like the system attempts to add the recovery volume, etc. directly into /Volumes/ and when it cannot, it copies the files into /Systems/Volumes/Data/. |
| + | |
| + | 2020-09-13 16:19:58-07 Lisas-MacBook-Pro suhelperd[703]: Mount point /Volumes/RecoveryHDMeta |
| + | |
| + | Mount point /Volumes/RecoveryHDMeta |
| + | |
| + | Failed to prep /Volumes/macOS Base System for brtool |
| + | |
| + | Assert existing-or-new subject dir name should be recoveryVolumeSubjectDir=/Volumes/Recovery/B392677C-67A5-4583-B8DF-DEB7B13F0E6C |
| + | |
| + | If exists, do hard test for any existing Recovery Volume subject dir being a DIR |
| + | |
| + | UUID recoveryVolumeSubjectDirPreExisted=0 |
| + | |
| + | No subject dir found in Recovery so will create |
| + | |
| + | Recovery vol subj dir url for creation = file:///Volumes/Recovery/B392677C-67A5-4583-B8DF-DEB7B13F0E6C |
| + | |
| + | Did create dir; err=(null) |
| + | |
| + | Determined appleBootPartitionSlurpProceed=0 |
| + | |
| + | Not slurping legacy Apple_Boot |
| + | |
| + | No caller opinion if to do boot install, and no path |
| + | |
| + | Determined bootSystemInstallProceed=1 |
| + | |
| + | Determined bootSystemSourcePath=/System/Volumes/Data |
| + | |
| + | [br] |
| + | |
| + | I am wondering if this is a problem (bug?) that occurs when Catalina is installed during the initial setup process in new MacBooks only. If so, is Apple aware of this? It might explain the response I received from Apple’s Engineers: “''the information doesn’t show anything mounted incorrectly. The data they are viewing is showing the MacBook Pro is operating as expected”''. Interpreted translation - ''Yes, we know''… I only found it because I was looking for something else. While I have an issue with my 2011 MBA which has caused me similar issues with new MacBooks, this problem is something else entirely. Any thoughts? |
| + | |
| + | [br] |
| + | |
| + | [br] |
| + | |
| + | [br] |
| + | |
| + | [br] |
| + | |
| + | [br] |
crwdns2866306:0crwdne2866306:0:
MacBook Pro 13" Two Thunderbolt Ports 2020
crwdns2915684:0crwdne2915684:0:
open
crwdns2934241:0crwdne2934241:0 Lisa
crwdns2947189:0crwdne2947189:0:
/Volumes/macOS Base System/AppleInternal/Library/Ext/doesn't exist...
crwdns2934249:0crwdne2934249:0:
The problem I have with my new 2020 13” MacBook Pro running Catalina 10.15.7 unfortunately, is not a new problem. 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. 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 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. The following information is from a recent install log of macOS Sierra, which I have included because “using product at distance 5” began here. 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. I believe this is caused by a shared file. Sep 14 19:28:14 MacBook-Air osinstallersetupd[547]: '''Using product <OSISInstallMediaProduct> based on media at /Volumes/OS X Install ESD at distance 5''' Sep 14 19:28:14 MacBook-Air osinstallersetupd[547]: '''Using product PKSecureNetEnabledProduct <file:///Volumes/Macintosh%20HD/macOS%20Install%20Data/> at distance 5''' 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. After a month of sending logs, pictures, etc. to the engineers at Apple Support, they continue to claim; ''“this is expected behavior. The information doesn’t show anything mounted incorrectly. The data they are viewing is showing the MacBook Pro operating as expected”, so I continue to look for a solution.'' The software update below occurred directly after initial set-up and installation of Catalina. ---- Begin System Software Update Arming ----- Ensuring /Volumes/macOS Base System's caches are up to date. Warning: /Volumes/macOS Base System/AppleInternal/Library/Extensions: No such file or directory Warning: /Volumes/macOS Base System/Library/Apple/System/Library/Extensions: No such file or directory Note: /Volumes/macOS Base System/System/Library/Kernels/kernel: No such file or directory Primary kext cache does not need update. CSFDE property cache does not need update. Localized EFI Login resources do not need update. Mounting helper partition... Looking for missing files. Copying files used by the booter. creating com.apple.Boot.plist data with UUID B392677C-67A5-4583-B8DF-DEB7B13F0E6C. copying /Volumes/macOS Base System/System/Library/Caches/com.apple.corestorage/EncryptedRoot.plist.wipekey to /System/Volumes/Data/macOS Install Data/Locked Files/Boot Files copying /Volumes/macOS Base System/usr/standalone/i386/EfiLoginUI/ to /System/Volumes/Data/macOS Install Data/Locked Files/Boot Files copying /Volumes/macOS Base System/System/Library/Caches/com.apple.corestorage/EFILoginLocalizations to /System/Volumes/Data/macOS Install Data/Locked Files/Boot Files copying /Volumes/macOS Base System/System/Library/PrelinkedKernels/prelinkedkernel to /System/Volumes/Data/macOS Install Data/Locked Files/Boot Files Copying files read before the booter runs. Moving aside old label. Copying new booter. Activating new booter. Activating files used by the booter. Activating files used before the booter runs. Successfully updated disk1s2/macOS Install Data/Locked Files/Boot Files. Rolling back any incomplete updates. Sep 13 23:22:43 MacBook-Pro OSInstaller[644]: Finding disk for productURL: /macOS Install Data Sep 13 23:22:43 MacBook-Pro OSInstaller[644]: '''Using product <OSProduct: 0x7fa16ed59900> at distance 5''' ++Sep 30 Install++ Sep 30 16:27:17 MacBook-Pro OSInstaller[665]: '''Using product <OSProduct: 0x7fa04f31f320> at distance 5''' [br] [br]
crwdns2866306:0crwdne2866306:0:
MacBook Pro 13" Two Thunderbolt Ports 2020
crwdns2915684:0crwdne2915684:0:
open