Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Good afternoon.
MacAir 2012 13" (5,2) with a problem upgrading from 15.6.1 to 15.7.
I always use the OCLP procedures with a USB installer.
This time, well into the install process, it stopped with this dialog box:View attachment 2554787
After clinking the 'OK', I had this dialog box underneath:
View attachment 2554792
Haven't seen this before, so I waited about 45 minutes to see if anything would happen. Nothing.
So, as many of you would have told me, I powered down, wait about 15 seconds, and powered her back up.
It went back to the MACOS installer and started again. But with about 15 minutes left, it again stopped with the same two dialog boxes.
Has anyone see this before and possibly a fix.
Thank you in advance,
Jim
I’ve seen that back in the beta versions in big sur.

I’d connect to ethernet. And try again. if that doesn’t work, boot from a good known-system and perform an OTA update. Can you boot into 15.6.1 using safe mode?

The latest version of OCLP should offer you to patch the system automatically as soon as the ota installation process is launched
 
  • Like
Reactions: Kevo
It is set to "hibernatemode 0".
Disabling the hibernate mode didn't work unfortunately.

I think I should check a compatible MacOS version, though it's really time consuming to switch over to an older OS.
I really hope to find a solution for this.
I eventually tried Big Sur and… no issues at all. Did Apple change power management in Sequoia?
 
Screenshot 2025-09-21 at 12.38.33.png


This could be helpful to some of you, in regards to the discussion about Tahoe popping up in SoftwareUpdate. Once Beta updates are selected as shown, the Tahoe upgrade does not pop up on my machine.
 
Last edited:
OCLP and Migration Assistant do NOT play nicely. Macbook 9,1 with fresh Sequoia 15.6 install.
Time Machine disk from M1 MBA running 15.6.
Used Mgration Assistant to migrate ONLY User folder from TM disk, but NOT system files, applications or anythinge else.
Result: Boot loop after migration completed - sigh
Check out this Mr. Macintosh video on migration?
 
OCLP and Migration Assistant do NOT play nicely. Macbook 9,1 with fresh Sequoia 15.6 install.
Time Machine disk from M1 MBA running 15.6.
Used Mgration Assistant to migrate ONLY User folder from TM disk, but NOT system files, applications or anythinge else.
Result: Boot loop after migration completed - sigh
Right... I found that out quite some time ago... It's never been fixed really..Yeah Mr Macintosh has a vid on it. I did try that once but if I recall, it still wasn't right.. That was on the 2012MBP. I went back to Catalina and up to Sonoma and stayed there.. I just tried Sequoia on my MBA and didn't really like it much. Too quirky. I reloaded Monterey and restored from TM then went up to OCLP/Sonoma 14.8. Works fine. I'll stay on Sonoma most likely till machine dies, or go back to Monterey if something weird comes up.. But it works fine on my 2012MBP and this 2015MBA. My 2015MBP is my daily so I don't think I'll stay on Monterey on it. Just wish Sequoia wasn't so quirky. It messed up my Movies library and just didn't seem to run as well as Sonoma.
 
Last edited:
Right... I found that out quite some time ago... It's never been fixed really..Yeah Mr Macintosh has a vid on it. I did try that once but if I recall, it still wasn't right.. That was on the 2012MBP. I went back to Catalina and up to Sonoma and stayed there.. I just tried Sequoia on my MBA and didn't really like it much. Too quirky. I reloaded Monterey and restored from TM then went up to OCLP/Sonoma 14.8. Works fine. I'll stay on Sonoma most likely till machine dies, or go back to Monterey if something weird comes up.. But it works fine on my 2012MBP and this 2015MBA. My 2015MBP is my daily so I don't think I'll stay on Monterey on it. Just wish Sequoia wasn't so quirky. It messed up my Movies library and just didn't seem to run as well as Sonoma.
I was originally going to stay on Sonoma as well, but after upgrading to Sequoia from Sonoma, I've been running it about almost a month now, and the little quirks I had before (outside the known issues) has been fine. I guess it really depends on the hardware being used. With that said, I created a second APFS Volume on the fusion drive, and stuck Monterey on it as a backup.
 
OCLP and Migration Assistant do NOT play nicely. Macbook 9,1 with fresh Sequoia 15.6 install.
Time Machine disk from M1 MBA running 15.6.
Not that surprised that from M1 to OCLP legacy will be troublesome for obvious reasons and the fact that it will be less used than the other way around, and from OCLP to Legacy Intel to M1 has worked fine here so far.
 
Last edited:
OCLP and Migration Assistant do NOT play nicely. Macbook 9,1 with fresh Sequoia 15.6 install.
Time Machine disk from M1 MBA running 15.6.
Used Mgration Assistant to migrate ONLY User folder from TM disk, but NOT system files, applications or anythinge else.
Result: Boot loop after migration completed - sigh

The same thing happened to me. I tried using Migration Assistant to bring everything over from macOS Monterey 12.7.6 to Sequoia 15.6 and it caused the system to become unbootable. I wiped the Sequoia system and reinstalled it afterwards.

Better to copy the folders manually.

I am curious whether Carbon Copy Cloner, Superduper, or ChronoSync would be able to restore the files to an OCLP system without messing it up.
 
iMac 18,2 mid-spec, stock, previously running Sonoma via OCLP, seamless over-the-top upgrade to 15.7 using an external installer.
If/when (no, make that when) this machine's drive fails, I will fully gut it and upgrade drive, RAM, and CPU. At that point, if OCLP allows, I'll go for Tahoe. However, if it becomes evident that Tahoe is a poor upgrade on such a machine, then it will become a Linux box. And a very good one it will make, too.
 
  • Like
Reactions: MacMorrison
I’ve seen that back in the beta versions in big sur.

I’d connect to ethernet. And try again. if that doesn’t work, boot from a good known-system and perform an OTA update. Can you boot into 15.6.1 using safe mode?

The latest version of OCLP should offer you to patch the system automatically as soon as the ota installation process is launched
It finally work after three try. but now when I boot using the option key, it says: "Sequoia-data-data-data"
Same in Disk Uitility. I was able to rename the volume in disk utility to: "Sequoia", but don't know how to change the name when I reboot.
 
It finally work after three try. but now when I boot using the option key, it says: "Sequoia-data-data-data"
Same in Disk Uitility. I was able to rename the volume in disk utility to: "Sequoia", but don't know how to change the name when I reboot.
That is what I meant when I wrote that the installer gets confused.
The boot name will change next time you update your OS.
 
Last edited:
It finally work after three try. but now when I boot using the option key, it says: "Sequoia-data-data-data"
Same in Disk Uitility. I was able to rename the volume in disk utility to: "Sequoia", but don't know how to change the name when I reboot.
look here how to re-name the HD
 
Not that surprised that from M1 to OCLP legacy will be troublesome for obvious reasons and the fact that it will be less used than the other way around, and from OCLP to Legacy Intel to M1 has worked fine here so far.
I wouldn't have been surprised too if I had migrated system files, applications, etc., but I just moved the User folder; does User folder contain something that affects system files?
 
I wouldn't have been surprised too if I had migrated system files, applications, etc., but I just moved the User folder; does User folder contain something that affects system files?
I have never had a reason to check exactly what Mgration Assistant does, but it certainly does not only copy files.
 
Last edited:
I have never had a reason to check exactly what MI does, but it certainly does not only copy files.
I was curious about this myself. I don't use "Migration Assistant" myself, and I always manually copy stuff from the Time Machine backup. However, when looking at the backups, it seems like it's only the user data backed up now, and not the system portion of the drive. Time Machine used to back up the whole drive, now it seems like it's just the data, so that make sense why it would cause issues, unless it's due to volume no longer being sealed. The other thing I'm curious about is, is the issue on all unsupported macs, or just really old ones without AVX2, or something else common to newer models.

P.S. I never used "Migration Assistant" even under a supported install. I've only used that function in iOS upon getting a new iPhone.
 
The same thing happened to me. I tried using Migration Assistant to bring everything over from macOS Monterey 12.7.6 to Sequoia 15.6 and it caused the system to become unbootable. I wiped the Sequoia system and reinstalled it afterwards.

Better to copy the folders manually.

I am curious whether Carbon Copy Cloner, Superduper, or ChronoSync would be able to restore the files to an OCLP system without messing it up.
I'm using CCC when making a fresh installation to an erased disk: making a data clone with CCC to the fresh disk (say xx), then install macOS on it (which makes the two APFS volumes xx and xx - Data out of xx). I use this method after migration assistant had failed several times to end correctly, even before OCLP and dosdude times.
The data part can be updated with CCC when macOS is already installed, at least that worked safely in my case.
 
Last edited:
  • Like
Reactions: MacMorrison
It finally work after three try. but now when I boot using the option key, it says: "Sequoia-data-data-data"
Same in Disk Uitility. I was able to rename the volume in disk utility to: "Sequoia", but don't know how to change the name when I reboot.
The -data-data... happened to me several times on my MBP5,2, when updating OTA or from VME installer. Most of the times it was that harmless, but I also had cased where the system was unbootable afterwards, could not even be re-installed from VME installer and required a clean install.
 
look here how to re-name the HD
Thank you kindly for your reply and I read the article closely. Actually, several times.
Not being a true geek, I'm concerned I could possible screw up my whole system. Thinking about just living with it. It doesn't seem to affect booting.
 
  • Like
Reactions: MacRumors3590
Thinking about just living with it. It doesn't seem to affect booting.
If you can live with it, it will 100% update the volume names by itself when you update to 15.7.1. or beyond, to what you have set in Disk Utility.

Edit: Had a reason/chance to test this with 15.7.1 and it still works and fixed the name on a MBA 3,2 that had the naming issue after faulty naming during install. FWIW.
 
Last edited:
  • Like
Reactions: macpro_mid2014
Thank you kindly for your reply and I read the article closely. Actually, several times.
Not being a true geek, I'm concerned I could possible screw up my whole system. Thinking about just living with it. It doesn't seem to affect booting.
I had the - Data drive name thing happen to me with this last update to 15.7 because I forgot to plug into ethernet before running the update. I had unplugged my Thunderbolt display and usb devices and forgot to plug the ethernet directly to my MBP before walking away to let it do it's thing.

In any case, after plugging in and rebooting after it got stuck, it added the extra "- Data" to my drive name.

I simply renamed the drive in the Finder. I have the disk set to show on my desktop. After doing that I checked get info and disk utility to see what it did and it seems like it did the right thing. After reading the posts here, I checked startup disk in system settings and it's correct there too.

One thing that may be different is that I do use FileVault on my drive. I'm not sure how that affects things overall, but it might. YMMV.
 
I had the - Data drive name thing happen to me with this last update to 15.7 because I forgot to plug into ethernet before running the update. I had unplugged my Thunderbolt display and usb devices and forgot to plug the ethernet directly to my MBP before walking away to let it do it's thing.

In any case, after plugging in and rebooting after it got stuck, it added the extra "- Data" to my drive name.

I simply renamed the drive in the Finder. I have the disk set to show on my desktop. After doing that I checked get info and disk utility to see what it did and it seems like it did the right thing. After reading the posts here, I checked startup disk in system settings and it's correct there too.

One thing that may be different is that I do use FileVault on my drive. I'm not sure how that affects things overall, but it might. YMMV.
Kevo, thanks.
Could you please check this: restart your computer holding the option key together to the startup manager, thus going to EFI boot and then your individual volumes ( if you have more than one MACOS). See if that says "Sequoia" or "Sequoia-data"
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.