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.
@dosdude1 Happy to report that upgrading to Developer Beta 9 via MAS was successful and went smooth. Had to of course apply the post install patches again.

dDYvy0g.png

@nekton1 Maybe the problem is that you tried to update with the disk inside the Tempo? I did the upgrade with SSD in one of the standard Mac Pro bays.
 
Last edited:
  • Like
Reactions: dosdude1
I finally installed HS with DP8 on my iMac last night on APFS, and got the update to 9 today no problem. Could be your multi-disk issue at play again?

Can you check if NightShift is gone on your machine too now? System Preferences > Displays.
[doublepost=1504305337][/doublepost]
Could be I guess. I will pull the second disk and see if that fixes the issue!

Or try putting in one of the standard bays, if you had it inside the Tempo when you attempted to upgrade.
 
@dosdude1 Happy to report that upgrading to Developer Beta 9 via MAS was successful and went smooth. Had to of course apply the post install patches again.

dDYvy0g.png


One caveat, though: it disabled NightShift mode.

@nekton1 Maybe the problem is that you tried to update with the disk inside the Tempo? I did the upgrade with SSD in one of the standard Mac Pro bays.

I ran the upgrade on an SSD in the standard SATA bay but the PCIe card with other boot disks was in place too.

I'll pull it and see what happens.
 
I had to reapply the Night Shift patch. CoreBrightness framework gets updated (thus patch gets overwritten) pretty much on every update of HS.

How? Patch Updater doesn't give me the NightShift patch now, and I don't have CoreBrightness.framework patched handy :).
[doublepost=1504305505][/doublepost]
I ran the upgrade on an SSD in the standard SATA bay but the PCIe card with other boot disks was in place too.

I'll pull it and see what happens.

Ah, ok, then try that :). Could you answer my question regarding powering the Tempo card?
 
Additional question: do you have to connect power to the card, or does it take it straight from the PCI port?
Powered from PCIe bus
[doublepost=1504307903][/doublepost]Even just with one SSD in SATA drive, it sees the beta 9 update, downloads it, does the 2 minute stub install, restarts to complete the install and runs though RefiND to boot straight back into beta 8.
Weird.
I am just rebuilding a beta 9 USB booter/patcher and starting over fresh on one SSD in one SATA slot .
 
I finally installed HS with DP8 on my iMac last night on APFS, and got the update to 9 today no problem. Could be your multi-disk issue at play again?

@Stratus Fear Hi, I also have the 2007 iMac, with the Penryn processor upgrade, what Core 2 Duo model did you get because mine shows 400 MHz and yours shows 700 MHz.

Thanks!
 
In Beta 9, Apple has taken control over the APFS conversion process...

$ sudo diskutil apfs convert disk0s2
Started APFS operation on disk0s2 High Sierra
Converting HFS Volume to an APFS Container which will export one APFS Volume
The target is the Journaled HFS+ volume "High Sierra" backed by the GPT partition disk0s2
Exiting conversion operations with error code -69546
Error: -69546: Conversion to APFS of a macOS system volume is only allowed in the OS Installer Environment

So likely the only way now to get APFS onto a HDD is to format a drive as APFS and clone over an existing High Sierra installation.
 
In Beta 9, Apple has taken control over the APFS conversion process...

$ sudo diskutil apfs convert disk0s2
Started APFS operation on disk0s2 High Sierra
Converting HFS Volume to an APFS Container which will export one APFS Volume
The target is the Journaled HFS+ volume "High Sierra" backed by the GPT partition disk0s2
Exiting conversion operations with error code -69546
Error: -69546: Conversion to APFS of a macOS system volume is only allowed in the OS Installer Environment

So likely the only way now to get APFS onto a HDD is to format a drive as APFS and clone over an existing High Sierra installation.

It’s not working booting in recovery or booted off a USB stick?
 
This is from another drive also installed with Beta 9. I am pretty sure that I converted with that approach before without being booted of the USB installer.

Ahhh I see. I bet the intent is to prevent people from attempting to convert a mounted OS file system. They probably aren’t bothering to check whether it’s the running system or not.
 
So why is the MBP 3.1 not able to run HS but 4.1 can? They are virtually identical except the CPU which looks like just a minor revision C2D.
 
So why is the MBP 3.1 not able to run HS but 4.1 can? They are virtually identical except the CPU which looks like just a minor revision C2D.

The 3,1 uses a Merom generation Core 2 that doesn’t support SSE4.1 instructions that macOS has been compiled with since Sierra. Since the CPU on those models is soldered rather than socketed, it’s impossible to upgrade them to a CPU that supports those instructions. The 4,1 uses a Penryn generation Core 2 that supports SSE4.1 instructions.
 
  • Like
Reactions: dosdude1
The 3,1 uses a Merom generation Core 2 that doesn’t support SSE4.1 instructions that macOS has been compiled with since Sierra. Since the CPU on those models is soldered rather than socketed, it’s impossible to upgrade them to a CPU that supports those instructions. The 4,1 uses a Penryn generation Core 2 that supports SSE4.1 instructions.
Ah thanks. Brings back memories of Tiger(?) where people were patching the kernel to support older intel CPUs on PC laptops.
 
Now that Beta 9 is out, is there any point in waiting for the GM release? I’m assuming having the beta should not affect the update process to 10.13.1 as long as the appropriate patches are in place.

Machine is a 2009 13” MacBookPro5,5 still on El Capitan.

Actually, I could just clone over my existing High Sierra test install (for my iMac) from my external drive and then run the post installer patches, but that one isn’t APFS and it would be nice to have a clean install too.
 
Last edited:
I have just installed HS Beta 9, everything works amazing, iCloud services (iMessage, FaceTime), NightShift, etc. But the only thing is that when I was installing the Post-Install patches, the APFS Patch was grayed out and I was unable to install the APFS file system. Any suggestions?

Thanks.
 
I have just installed HS Beta 9, everything works amazing, iCloud services (iMessage, FaceTime), NightShift, etc. But the only thing is that when I was installing the Post-Install patches, the APFS Patch was grayed out and I was unable to install the APFS file system. Any suggestions?

Thanks.
Did you install macOS on an APFS volume? That option is only available if you're patching an install on an APFS volume.
 
Here you go, just checked, Developer Beta 9 shows up:

Code:
https://swscan.apple.com/content/catalogs/others/index-10.13seed-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog.gz

Make sure your /Users/Shared/.SeedEnrollment.plist is set to DeveloperSeed.

Wonderful, thank you.
 
And how do I do that (without a fresh install)?
Boot into your High Sierra installer and convert the disk to APFS using Disk Utility. Not sure how reliable that is though, so make sure you back up important data. And I believe it only works if you're using an SSD.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.