Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
But my rMBP is mid-2014 and the air is mid 2011. I haven't seen a kernel panic in many years. Puzzled.
[doublepost=1498140744][/doublepost]I am using a rMBP 15" 2015 model and there is no problem with it so far. Are your both models much older versions?
[doublepost=1498138776][/doublepost]

Mid 2014 rMBP and mid 2011 MBA
[doublepost=1498140825][/doublepost]

What did you do to recover from it?
Thus far I have had no success despite numerous attempts and methods in both the HFS+ filesystem and APFS. 1) Upgrading from a Sierra partition I created and fully updated to 10.12.6 Developer Beta 4. 2) Fresh installation on to a separate partition 3) From a Bootable USB installer I had created. Installer starts fine. Progress bar freezes, screen goes black then one Beep. Have found from the Developer Preview 2 installer that it is unable to verify firmware.

I believe the error lies in the osInstall.mpkg
 
Last edited:
[doublepost=1498138688][/doublepost]
It is a known issue with macOS High Sierra as of now.
[doublepost=1498138742][/doublepost]

But will it ever be enabled? If the new file system has encryption on by default, doesn't make much sense.

Other issue I found is that in iMessages macOs is not recognising numbers that have the country code added by iOS that is not saved in the contact directly, so the contacts that I do not have with the country code saved on macOS iMessages I see phone numbers instead of the name. Also if I try to start a conversation it will fail stating that the number is not registered with imessage because the country code is missing
 
First beta installed great on my 11" MacBook Air. Tried to install beta 2 this morning and the install won't finish. The progress bar is so close to the end...but nothing happens. Guess I'll let it sit for the rest of the day and see what happens.
 
Do any of you guys can turn on fileVault with APFS? I can't since day one on high Sierra. I unlock the menu but the "turn on FileVault" stays greyed out. I thought that since APFS comes with file encryption, FileVault was not needed anymore...
FileVault is enabled on my converted APFS drive on my 13" MBP 2016 TB. I had FieVault enabled before I installed MacOS High Sierra. Haven't had any problems thus far.
 
FileVault is enabled on my converted APFS drive on my 13" MBP 2016 TB. I had FieVault enabled before I installed MacOS High Sierra. Haven't had any problems thus far.

I formatted the drive, so I lost FileVault from Sierra. I tried to turn it on with no success and I thought that it was due to the fact that APFS is always encrypted
 
Thus far I have had no success despite numerous attempts and methods in both the HFS+ filesystem and APFS. 1) Upgrading from a Sierra partition I created and fully updated to 10.12.6 Developer Beta 4. 2) Fresh installation on to a separate partition 3) From a Bootable USB installer I had created. Installer starts fine. Progress bar freezes, screen goes black then one Beep. Have found from the Developer Preview 2 installer that it is unable to verify firmware.

I believe the error lies in the osInstall.mpkg

On my MBA, I downloaded the installer, created a bootable thumb drive and reinstalled. It fixed whatever was broken. It is fine now. The MBP is running but borderline flaky. Think I will try the same trick on it.
 
The fact users are willing to run alpha/beta code on their primary machine and then complain when things "break" or the experience is "poor" is interesting to me.

I see comments about people "bashing" MS for how long it took them to release Win10. They perhaps should factor in that MS has to account for a ridiculous amount of hardware configurations, which requires driver compatibility, while also incorporating new features and extended functionality. Linux also has to do the same as well.

Apple has to account for fewer hardware variables since its a controlled ecosystem, end to end. Also, let's not forget that Sierra vs High Sierra is really not all that different other than APFS. Last I checked, Apple ignored their filesystems for how long????

Let look at Linux, how many filesystem upgrades have occurred and how aggressive was their release timing?

Apple has needed a modern copy on write filesystem for a very long time. They have been using HFS since 1998..... In 2002 they introduced journaling to HFS to add more stability and recovery for failures. Most other filesystems introduced this years in advance.

In the meantime, ext3, ext4, xfs, btrfs, zfs and even ntfs all improved substantially year over year. Let's not forget that MS is now building ReFS for release soon.

I enjoy using MacOS, because of the limited hardware variables and Apple controlling the entire ecosystem end to end it makes for a very reliable platform. If they made it Open Source it probably would be even better than it is currently, but that would mean Apple letting go of full control and that is unlikely to happen anytime soon.

Then again, Microsoft is now the leader in Open Source projects, who would have thought, so I guess miracles do happen?
 
I had converted the HDD of my MacBook Pro 2010 to APF with the first version of High Sierra, and it totally hosed down the whole system. Did a clean install without formatting to APFS, and it still lagged. With the version 2 of High Sierra, it seems to be running like it had with Sierra previously.

Anyone else with a 2010 MacBook Pro who upgraded or converted to APFS with version 2 of High Sierra had any problems?


Yep lots of experience with same MB (I assume it's the same). I am writing this on a MBP 2010 i7 15" running second developer High Sierra update. My main Mac is a new Mac Pro 6 core and I run the same beta on an external boot SSD as that's my real work machine. It seems fine on the MP. On this old MBP I have a 250 GB SSD internally now, took the HDD out years ago (and the optical) and it is working well... sort of.

If you haven't already, I might suggest you replace an internal HDD if still using one, they were dogs in the first place so an SSD is going to give you a 10x speed up (that's what I got).

My MacPro with the external 10.13 boot was the Mac's original 10.12.5 (at the time) cloned with CCC and updated to 10.3 with all apps and a lot of symlinks of apps' required System level in many cases data folders on an external e.g. iTunes, Photos, FCPro X, Logic Pro X etc. so as to keep the drive boot size down. I also cloned the external so all symlinks could be tested. Both the booting SSD and the external data drive (this is a 6TB TAID 0 over Thunderbolt) are APFS, no issues in my tests. The update to beta 2 has not exhibited any differences but I didn't have any issues in beta 1 anyway. I was thrilled all the symlinks worked perfectly on the new 10.13 APFS boot and its mate, the external RAID 0 also APFS. I half expected a catastrophic failure there!

The MBP on the other hand was a virgin install and I tested both HFS+ and APFS and also converting HFS+ to APFS after the fact ... all worked no problem (remember I have an SSD).

It had two glitches though in all scenarios: Firstly (and I could repeat this) Maps showed garbled images after initial install and boot. Secondly if I shut the lid it would not wake up. Manual sleep was fine but not the lid induced version. Maps was only fixed with a reinstall of the OS via the Recover Partition. Disk Utilities from there had no luck. Now with beta 2 updated Maps was garbled again! Same thing to fix, reinstall over top via RP. The lid still kills the wake up so nothing has changed there. So, like Mac Pro, I have not seen a single difference between beta 1 and 2. Not better not worse.

Got to say I like 10.13 a lot. Especially the no auto play on CNN web site and similar. Great job there Apple! :)
 
  • Like
Reactions: LinkinJunior
Dropping support for 32 bit apps is going to be a deal breaker for many small businesses.
Yesterday I was doing my job at my non profit which includes a lot of creative materials and media. While waiting for iDVD to finish our current project I opened Activitiy Monitor and added the column to see which apps were 32 bit.
Shockingly the iLife products were 32 bit as well as Adobe Suites and Office and others.
I looked to see if Apple released an update to iLife that is 64 bit but see nothing is available. Also it looks like we have to purchase an Adobe subscription to move to 64 bit and Office had a solution.
Looks like our organization will stay on a 32 bit support desktop for some time until a solution is provided without breaking the budgets.
Personally I will remain on iOS 10 as well because of too many 32 bit apps on my 7+ Apple needs a switch to turn off the 32 bit message on iOS 10.

"Lack of support" for 32 bit apps is still 27 months away (assuming upgrading operating systems on release date and not later.....

Microsoft Office 2011 is no longer supported for High Sierra... I believe the later one is 64 bit is it not? Microsoft has a habit of using stuff that is not suppose to be used as a public interface -- so often new releases of the OS -- Microsoft has had to patch the suite for use. This has happened with Microsoft Office 2011 and as it is no longer supported -- it will not be patched.

"iLife"... I thought that was gone a long time ago replaced by individual apps on the app store (which you get for free on a new Mac).... Pages, Numbers, etc. are all 64 bit.

iDVD was discontinued a while ago.

If you are still using discontinued programs, you can still use an older version of macOS/OS X since they tend to be updated with security patches for about 3+ years after release date.

Any discontinued product or version may stop at anytime -- and since they are no longer supported -- they would not be patched ... irregardless of discontinuing support for 32 bit apps.
 
  • Like
Reactions: JosephAW
Other issue I found is that in iMessages macOs is not recognising numbers that have the country code added by iOS that is not saved in the contact directly, so the contacts that I do not have with the country code saved on macOS iMessages I see phone numbers instead of the name. Also if I try to start a conversation it will fail stating that the number is not registered with imessage because the country code is missing

anyone? :)
 
"Lack of support" for 32 bit apps is still 27 months away (assuming upgrading operating systems on release date and not later.....

Microsoft Office 2011 is no longer supported for High Sierra... I believe the later one is 64 bit is it not? Microsoft has a habit of using stuff that is not suppose to be used as a public interface -- so often new releases of the OS -- Microsoft has had to patch the suite for use. This has happened with Microsoft Office 2011 and as it is no longer supported -- it will not be patched.

"iLife"... I thought that was gone a long time ago replaced by individual apps on the app store (which you get for free on a new Mac).... Pages, Numbers, etc. are all 64 bit.

iDVD was discontinued a while ago.

If you are still using discontinued programs, you can still use an older version of macOS/OS X since they tend to be updated with security patches for about 3+ years after release date.

Any discontinued product or version may stop at anytime -- and since they are no longer supported -- they would not be patched ... irregardless of discontinuing support for 32 bit apps.

It's funny. For some reason iDVD would not burn a project on my Mac mini 2014 10.12.x so I turned on my PowerBook G4 17" 2GB ram 10.5.x and accessed the project over the network, created the disk image without any problem. So the code must be more stable on the PPC anyway. Good that these old computers still have a use.
 
I installed on an external USB3 SSD on top of Sierra 10.12.6 beta 4 (I think), and DP1 went smooth as butter. But, then I noticed it didn't update the SSD to APFS. It *did* put it in an APFS container, but the volume was still HFS+. So, I tried to use Disk Utility in Restore 10.13 restore mode, and selected "Update to APFS" and viola... it refused to boot. In fact, if I have the USB drive connected, my Mac refuses to boot no matter what. The only recourse was to blow away the volume, destroy the APFS container, blah blah blah. I then used command line to create APFS container and volume, but can't install directly to the APFS volume. Weird. Will see if DP2 exhibits the same results.

Same result with DP2. Sad face.
 
On my MBA, I downloaded the installer, created a bootable thumb drive and reinstalled. It fixed whatever was broken. It is fine now. The MBP is running but borderline flaky. Think I will try the same trick on it.
Same error with the Public Beta 1 so its not looking promising. Thinking of getting a second Mac a 2015 21.5" 4k Retina iMac things should be ok then.
 
The fact users are willing to run alpha/beta code on their primary machine and then complain when things "break" or the experience is "poor" is interesting to me.

I see comments about people "bashing" MS for how long it took them to release Win10. They perhaps should factor in that MS has to account for a ridiculous amount of hardware configurations, which requires driver compatibility, while also incorporating new features and extended functionality. Linux also has to do the same as well.

Apple has to account for fewer hardware variables since its a controlled ecosystem, end to end. Also, let's not forget that Sierra vs High Sierra is really not all that different other than APFS. Last I checked, Apple ignored their filesystems for how long????

Let look at Linux, how many filesystem upgrades have occurred and how aggressive was their release timing?

Apple has needed a modern copy on write filesystem for a very long time. They have been using HFS since 1998..... In 2002 they introduced journaling to HFS to add more stability and recovery for failures. Most other filesystems introduced this years in advance.

In the meantime, ext3, ext4, xfs, btrfs, zfs and even ntfs all improved substantially year over year. Let's not forget that MS is now building ReFS for release soon.

I enjoy using MacOS, because of the limited hardware variables and Apple controlling the entire ecosystem end to end it makes for a very reliable platform. If they made it Open Source it probably would be even better than it is currently, but that would mean Apple letting go of full control and that is unlikely to happen anytime soon.

Then again, Microsoft is now the leader in Open Source projects, who would have thought, so I guess miracles do happen?

I "let look at Linux"

Lol. This is the year of the Linux desktop :)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.