MacBook (2015) update bootloop, 'too many corpses' error

Hi All!

I'm trying to update from Catalina to Big Sur or Monterey on an early 2015 macbook retina. Both installers always get stuck in a bootloop. The OS volume itself, although listed as such in disk utility, does not appear as bootable in Option boot. I have tried the usual things like clean installs, Diagnostic check, disk first aid, resetting NVRAM, and reinstalling OS from Internet Recovery. The firmware version is current(above 500).

I also tried a bootable Big Sur USB drive created with Terminal.

Catalina has so far been reinstalling from a third party drive with no issues.


Some Progress: Resetting NVRAM and in Internet Recovery selecting the bootup volume finally got Big Sur to replace the installer as the bootable volume. However, it only loads a bout half way and gets stuck in a "too many corpses" loop.

The exact Verbose repeated error line is:

"apfs_get_firmlink_target_vnode:2013:disk1S1:0 vnode lookupat(Library) failed with error 2"


Single User Mode runs for a while and stops but does not seem to give much useful info.

Some have suggested using /sbin/mount-uw and making some changes to the boot cache and rc.server.

By now, I am fairly convinced it is something with the computer and not anything I have tried so far.

Could use some advice before having to replace the computer.

Thanks--BFR


Posted on Mar 17, 2026 4:13 PM

Reply
Question marked as Top-ranking reply

Posted on Mar 22, 2026 2:14 PM

BxxxFR wrote:

The Macbook's SSD is original equipment. As a last resort, I had thought of trying to install the OS on an external drive (the one I use for Time Machine backups).

I was going to suggest trying to install macOS onto an external USB3 drive as a test. But I would not advise you to use a TM backup drive unless it is an old backup drive you no longer need, otherwise you risk damaging your backups.


However, both Big Sur and Monterey installer do still require using the internal SSD to update the system firmware.


Might this also be a fimware issue? Afterall, Big Sur install keeps looking for a firmlink.

Possibly. It could also be an issue with the internal SSD or drive layout since firmware updates are applied from the internal SSD which requires a valid partition & file system.


apfs_get_firmlink_target_vnode:2013:disk1S1:0 vnode lookupat(Library) failed with error 2

I wasn't familiar with "firmlink", but it appears it is a special type of link for APFS volumes that ties together (aka links) various separate locations in the file system to appear as a single entity to the end user. For example, it makes the two separate macOS volumes in macOS 10.15+ ("Macintosh HD" and "Macintosh HD - Data") appear as one ("Macintosh HD") to the end user so that is what users expect to see since that is how previous versions of macOS appeared.


This is not referring to firmware.


If you can boot the laptop into Catalina, then you can try checking the health of the internal SSD by running DriveDx (free trial period) and posting the complete text report here using the "Additional Text" icon which appears like a piece of paper on the forum editing toolbar.


With the updated information that a properly prepared macOS USB installer is having the same issues, then it certainly seems like this laptop most likely has a hardware issue of some sort.


You have tried using different USB sticks...especially a different brand? The quality of many USB sticks is extremely poor.

13 replies

Mar 17, 2026 6:40 PM in response to BxxxFR

I don't know the cause of that lugubrious message. The only resolution that I know of is to completely erase the affected volume. Did you try that?


Some have suggested using /sbin/mount-uw and making some changes to the boot cache and rc.server.


From that, you may have already read this reply:


crashed: too many corpses being created


Here are some other relevant Discussions, but to my knowledge nothing fixed it other than to erase the drive.


45min Boot Screen

Mac not booting, stuck on start screen despite disk repair

Too many corpses being created

Update .2Supplement crashing my MacBook & Safe Mode crashing too. Help

High Sierra: qmasterd/opendirectoryd: Too many corpses being created

Mar 18, 2026 3:48 PM in response to John Galt

Hi John--Thanks for the response

Why yes, erasing the whole drive is one of the first things I tried as meant by "clean install" in my list. Many of the posts you reference I believe are related to other OSs, not Big Sur. The same issue is probably causing the Monterey install to fail as well.


The key seems to be related to "apfs_get_firmlink_target_vnode:2013:disk1S1:0 vnode lookupat(Library) failed with error 2" which is where the bootup gets stuck about half way through..

"Too many corpses" may just be the result of numerous consecutive failures in a row, which will undoubtedly differ in various situations and OSs.


I might try clearing the boot cache from single user mode.


Appendages crossed.....




Mar 19, 2026 8:39 AM in response to BxxxFR

Did you erase the whole physical SSD? FYI, see the following Apple article for using Disk Utility to erase the whole physical SSD (follow the "If you cannot use Erase All Content & Settings" option at the bottom of the article):

Erase your Mac and reset it to factory settings - Apple Support


Is this laptop using the original Apple OEM SSD which shipped with it from the factory?


If you followed the advice from @D.I. Johnson in your other thread to acquire & create a bootable macOS USB installer, then there should be no issues installing macOS assuming you also erased the whole physical SSD unless your laptop has a hardware issue of some sort (could be with the USB stick used for the installer since the quality of most USB sticks is terrible).


If you are using a third party SSD, then that could be the problem since the third party SSD or the SSD adapter could be incompatible (usually the fault of the adapter).



Mar 19, 2026 12:39 PM in response to BxxxFR

BxxxFR wrote:

Hi John--Thanks for the response
Why yes, erasing the whole drive is one of the first things I tried as meant by "clean install" in my list.


Apple does not employ that terminology, leading to numerous interpretations of it, resulting in communication errors anger and misery. For example there are many people on this site complained they "clean installed" macOS then were surprised to find out everything got lost.


Erase and reinstall macOS - Apple Support

Erase your Mac - Apple Support


Erase is unambiguous.


Many of the posts you reference I believe are related to other OSs, not Big Sur.


The reason is that I have not heard of it in recent years, and the fact your Mac is over a decade old makes them relevant.

Mar 19, 2026 6:46 PM in response to BxxxFR

Was macOS Big Sur or Monterey ever previously installed on this laptop? This is another very important question in addition the questions I asked in my previous post.


Just thought of another thing you can try. Try installing macOS to an external USB3 SSD to see what happens as it would eliminate an issue with the internal SSD. However, if Big Sur or especially Monterey was never previously installed on this laptop, then it may not be possible to do so now if the internal SSD is bad, or if it is a third party internal NVMe SSD.


We need more details about your system & its history. Please answer the questions I asked earlier instead of going back to your old thread which should be considered dead now since the discussion has moved here. And use only official Apple methods for installing macOS and creating bootable USB installers. Using any other methods will just lead to confusion & problems. If you have a good Internet connection, then try using Internet Recovery Mode using Command + Option + R to see if it will boot to the online Monterey installer.


Either we are missing some important background details or your laptop has a hardware issue if official Apple methods we have described & linked do not work. I've installed macOS so many times over the years for troubleshooting purposes, I know that it will work unless there is a hardware issue preventing the installation.

Mar 20, 2026 6:52 PM in response to BxxxFR

BxxxFR wrote:

Hi All!
I'm trying to update from Catalina to Big Sur or Monterey on an early 2015 macbook retina.


Which "early 2015 MacBook retina" is this?

  • If it is a 12" Retina MacBook, you cannot upgrade it to Monterey. Big Sur is the end of the line.
  • If it is a 13" Retina MacBook Pro, you can upgrade it to Monterey, but no further.
  • It presumably isn't a 11" or 13" MacBook Air, as MacBook Airs did not yet have Retina displays.

Mar 21, 2026 2:19 PM in response to BxxxFR

Hi HWT and thanks for your responses.


Yes, all original Apple equipment.


In my last attempt, I used Teminal Mode to make a brand new Big Sur usb drive installer downloaded directly from Apple, completely erased the hard drive (display all objects and erase the top line SSDxxx), and got the same results as with all my other previous attempts with both Monterey and Big Sur. Did I miss a step?


The installer exits every time - 8 minutes to go for Monterey and 11 minutes to go for Big Sur - into a 10 second boot loop. The only bootable volume is the installer. In my last attempt with Big Sur, however, I was able to make the OS the bootable volume by resetting NVRAM, selecting Big Sur OS in Internet Recovery as the bootable volume, and restarting.


It is probably not a USB issue. I have a third party multiple OS usb drive which has successfully installed Mojave and Catalina-(repeatedly) and I overwrote my other third party Monterey usb drive with Big Sur directly from Apple. Big Sur on the multi-OS drive also gives the same result.


Thinking out loud--Could a firmlink error indicate a firmware problem? If so, there may not be a way to repair it with Intel silicon.

"apfs_get_firmlink_target_vnode:2013:disk1S1:0 vnode lookupat(Library) failed with error 2",


Best regards



Mar 21, 2026 2:31 PM in response to John Galt

Hi John--

Sorry about starting multiple threads. I took your advice by erasing the third party Monterey installer and creating a Big Sur (downloaded directly from Apple in Terminal mode) on it instead. Got the exact same results...


Since there is an apparent firmlink issue, I am beginning to suspect a firmware issue:

"apfs_get_firmlink_target_vnode:2013:disk1S1:0 vnode lookupat(Library) failed with error 2"


Best regards

Mar 21, 2026 3:19 PM in response to HWTech

High HW--Thanks for hangin in with me and sorry about the multiple threads.


No- Big Sur or Monterey were never installed. Big Sur via software update had failed, but at that time I had an old router and could not access Internet Recovery so got a third party multiple OS installer.

With that, Big Sur failed again, but Mojave and Catalina worked fine.


The Macbook's SSD is original equipment. As a last resort, I had thought of trying to install the OS on an external drive (the one I use for Time Machine backups). I could be wrong, but because Catalina repeatedly installs, I don't suspect the internal SSD. I have done a complete HD erase (display all objects and erase the SSDxxx) to no avail.


I now do have a good internet connection, so maybe booting directly to an Apple installer might work.

In Terminal Mode,however, I erased my third party Monterey installer and made it a bootable Big Sur installer.

I *** u me that would be an official Apple method.


Might this also be a fimware issue? Afterall, Big Sur install keeps looking for a firmlink.

apfs_get_firmlink_target_vnode:2013:disk1S1:0 vnode lookupat(Library) failed with error 2


What other info would you need? Early 2015 Retina Macbook Pro with, however, only 8GB RAM.


Best regards


Question marked as Top-ranking reply

Mar 22, 2026 2:14 PM in response to BxxxFR

BxxxFR wrote:

The Macbook's SSD is original equipment. As a last resort, I had thought of trying to install the OS on an external drive (the one I use for Time Machine backups).

I was going to suggest trying to install macOS onto an external USB3 drive as a test. But I would not advise you to use a TM backup drive unless it is an old backup drive you no longer need, otherwise you risk damaging your backups.


However, both Big Sur and Monterey installer do still require using the internal SSD to update the system firmware.


Might this also be a fimware issue? Afterall, Big Sur install keeps looking for a firmlink.

Possibly. It could also be an issue with the internal SSD or drive layout since firmware updates are applied from the internal SSD which requires a valid partition & file system.


apfs_get_firmlink_target_vnode:2013:disk1S1:0 vnode lookupat(Library) failed with error 2

I wasn't familiar with "firmlink", but it appears it is a special type of link for APFS volumes that ties together (aka links) various separate locations in the file system to appear as a single entity to the end user. For example, it makes the two separate macOS volumes in macOS 10.15+ ("Macintosh HD" and "Macintosh HD - Data") appear as one ("Macintosh HD") to the end user so that is what users expect to see since that is how previous versions of macOS appeared.


This is not referring to firmware.


If you can boot the laptop into Catalina, then you can try checking the health of the internal SSD by running DriveDx (free trial period) and posting the complete text report here using the "Additional Text" icon which appears like a piece of paper on the forum editing toolbar.


With the updated information that a properly prepared macOS USB installer is having the same issues, then it certainly seems like this laptop most likely has a hardware issue of some sort.


You have tried using different USB sticks...especially a different brand? The quality of many USB sticks is extremely poor.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

MacBook (2015) update bootloop, 'too many corpses' error

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.