Saltar al contenido principal

Repara tus cosas

Derecho a reparar

Tienda

Disponible desde Mayo del 2020, El MacBook Pro 13" incorpora un procesador quad-core Intel de 8ª generación Core i5 e i7, y una gráfica integrada Intel Iris Plus 645. (Modelo A2289/EMC3456 con dos puertos Thunderbolt 3)

Preguntas 29 Ver todo

/Volumes/macOS Base System/AppleInternal/Library/Ext/doesn't exist...

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

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

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

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?

Contesta esta pregunta Yo también tengo este problema

Es esta una buena pregunta?

Puntuación 0

Comentarios:

How did you migrate your apps and data over from your old system to this one?

- de

Hi Dan, I don't ever use migration and nothing was transferred. I have purchased & returned 7 or 8 MBA's over the last two years because of this problem, which exist on my 2011 MBA. I believe the online RAM file that contains macOS X Base System files is being shared. I just don't know how to stop it.

- de

I'm confused! You selected MacBook Pro 13" Two Thunderbolt Ports 2020 Are we working on a MacBook Air system? Which is it?

- de

The problem originated on my MBA.. I posted this under MBP although the same problem exists on both. Btw.. I have been dealing with Apple Support's Engineers since last month, and their response to all of this is,

"I got a response back from the engineers. They stated that this expected behavior. The information doesn’t show anything mounted incorrectly. The data they are viewing is showing the MacBook Pro is operating as expected."

Unbelievable...

- de

@catmama - So lets fix this! Its fixable! But I need the info to tell you how!

So let's start again.... How did you migrate your apps and data over from your old system to this one?

- de

Mostrar 1 comentario más

Agregar un comentario

1 Respuesta

Respuesta Más Útil

@catmama - I have only seen this issue when someone used cloning software.

Sadly out of the millions of systems Apple has sold over the years that can support Mojave or Catalina I would say less than a dozen have faced this issue. So its not pervasive!

But I don't know in your case where the corruption is... Is it buried in your backup so when you restored you bought it over from your old systems.

The only way to real fix this is to fully nuke your systems drive. The problem is the newer MacBook Pro’s can’t be easily wiped without making it hard to recover the OS.

So you’ll need to take your system to an Apple Store and just tell them you have some very sensitive data on it and you need to make sure its fully wiped down. Let them have the fun of doing it. As far as your OS and apps. You’ll want to stick with Mojave if you are using older applications as Catalina does not support 32bit apps of extensions. I encountered major issues with my photo editing as I have 3rd party tools which are 32bit and didn’t realize so it made one big mess on my Mac Pro. It took me a week to rebuild my system back.

I would stick with Mojave and you’ll want to go back to your application sources to get fresh copies. As far as your data I really recommend you use a second (or more) drives to host it and only carry what you are actively working on.

Fue útil esta respuesta?

Puntuación 1

Comentarios:

Dan, I know you're trying to be helpful, and I truly appreciate it, I know this probe isn't pervasive among other users, been it's been pervasive on every single one of the 8 MacBook's I've purchased and had to return, because NO ONE at Apple will even acknowledge I have an issue. I went to the Genius's last year, they were completely clueless. it's an online (http:// file) that is being shared.. if only I could identify it. Thank you...

- de

Wait, so you've actually seen this, before?? Unfortunately returning this won't stop this from happening again. If I would destroy my 2011 MBA before I fire up the next one, if I knew that would prevent the problem from occurring.. I've certainly thought about it,

- de

Thats not what I said! You don't need to destroy any hardware!!

The issue is the carry over of a file corruption!

- de

Agregar un comentario

Añadir tu respuesta

Lisa estará eternamente agradecido.
Ver Estadísticas:

Ultimas 24 horas: 0

Ultimos 7 días: 1

Ultimos 30 días: 11

Todo El Tiempo: 220