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.
Ok I'll dig out my MacBook and update my installer there.

I'm sure this has been answered, but for those of us who are currently running Beta 1 on unsupported macs do we just run the public beta installer from within the Applications folder..? Or is it necessary to make the installer USB again?

Also, as I understand it we should not use Disk Utility to format the disk beforehand, but instead should just run the installer and select the Mac drive...is this correct?
 
I'm sure this has been answered, but for those of us who are currently running Beta 1 on unsupported macs do we just run the public beta installer from within the Applications folder..? Or is it necessary to make the installer USB again?

Also, as I understand it we should not use Disk Utility to format the disk beforehand, but instead should just run the installer and select the Mac drive...is this correct?


Remake it and yes
 
Remake it and yes

Ok I will remake the USB - I am assuming using the patcher just the same as before. I am currently running a Bootcamp setup (everything is backed up). ..I would however like to keep my setup if possible. If I upgrade using the installer (without formatting the disk) and then use Gdisk to rebuild my hybrid MBR should it work?
 
Ok I will remake the USB - I am assuming using the patcher just the same as before. I am currently running a Bootcamp setup (everything is backed up). ..I would however like to keep my setup if possible. If I upgrade using the installer (without formatting the disk) and then use Gdisk to rebuild my hybrid MBR should it work?

On that I have no idea
 
Alright, just updated the tool. It now rebuilds caches whenever the post-install tool is run, so that should resolve the problems when doing an upgrade-install.
 
I'm still curious how my situation fits into all this. I pulled my drive from my MBP, updated to developer beta 2 using my supported MAC then put it back. I have done nothing else so it feels like I have missed a step but all works as far as I can tell.
 
Alright, just updated the tool. It now rebuilds caches whenever the post-install tool is run, so that should resolve the problems when doing an upgrade-install.


Ok I'll let you know. I'm gonna try to do the rebuild caches terminal command. My MacBook is stupid slow
 
Alright, just updated the tool. It now rebuilds caches whenever the post-install tool is run, so that should resolve the problems when doing an upgrade-install.

Thanks Dosdude!

Does this mean that I run the installer from the Applications folder, avoiding having to remake a new USB?

Do you have a link to the most current patcher?
 
Alright, just updated the tool. It now rebuilds caches whenever the post-install tool is run, so that should resolve the problems when doing an upgrade-install.

Can you just clarify what you meant by upgrade-install? Is there an option to install by running the beta installer directly from Applications...or is the only possible way to remake a new USB by following your old instructions from beta 1?
 
Last edited:
Can you just clarify what you meant by upgrade-install? Is there an option to install by running the beta installer directly from Applications...or is the only possible way to remake a new USB by following your old instructions from beta 1?
I meant just installing Sierra on a volume that contains an install already, without erasing it. That way, all files and settings will remain in tact. You still have to create a patched USB and boot from it, but just skip erasing the disk with Disk Utility.
 
I meant just installing Sierra on a volume that contains an install already, without erasing it. That way, all files and settings will remain in tact. You still have to create a patched USB and boot from it, but just skip erasing the disk with Disk Utility.

I did an upgrade to PB using yesterday's (2.5?) patcher. Looks like it's running fine. Seems like you made a bug fix to purge kext caches for my upgrade (from DP1) scenario. Should I remake and post install? Any reason to worry?
 
I did an upgrade to PB using yesterday's (2.5?) patcher. Looks like it's running fine. Seems like you made a bug fix to purge kext caches for my upgrade (from DP1) scenario. Should I remake and post install? Any reason to worry?
No, as long as it works, you're fine.
 
I meant just installing Sierra on a volume that contains an install already, without erasing it. That way, all files and settings will remain in tact. You still have to create a patched USB and boot from it, but just skip erasing the disk with Disk Utility.

Got it, thank you. To your knowledge should this keep the ability to rebuild my Bootcamp intact?

To explain, what I have always done on El Capitan and now with Sierra is to install the way that you are describing (no formatting in Disk Utility) in existing setups where I had Bootcamp (I always use Bootcamp).

What I found is that of course the partition stays intact, but that trying to boot into the parititon results in an operating system not found error message. This is easily fixed using a utility called Gdisk to rebuild the hybrid MBR.

In my testing I have found that Bootcamp can always be salvaged this way so long as the partition size is not altered (then it breaks).

So, do you have any insight on this? I am going to do the following, please let me know if this is correct:

1. Rebuild the USB installer with the public beta using your utility
2. My current Sierra install is on my partition named "Macintosh" - I am going to chose to install the new beta on Macintosh, without reformatting it first in Disk Utility
3. Following install it will most likely not boot up giving me a "no smoking" sign - I will reboot to the USB and run the post-installation patch
4. Hope for the best

Am I missing any steps? Thank you
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.