Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
OK so about APFS, I have installed the latest DP6, ran Disk Sensei to get trim kext in place, then ran Trimforce. Right now i have the latest build, the latest firmware, and trim on my samsung SSD.

However, it will not let me convert my SSD to apfs. I have tried via an install usb, via recovery, and via disk utility in the actual os. None of them give me the option to convert.

Any ideas that can help me?

No idea on this matter yet. If that's Apple's artificial limitation, better not to do a "force conversion" at this moment. It's just a beta, not worth to find any complicated work around may become useless on next update. Also, may be the APFS can work on cMP, but only on a newly formatted partition. May be it can't boot after a manual conversion, who knows? Especially we have the 2nd firmware upgrade, IMO, that's a indication that Apple is trying to fix something.
 
OK so about APFS, I have installed the latest DP6, ran Disk Sensei to get trim kext in place, then ran Trimforce. Right now i have the latest build, the latest firmware, and trim on my samsung SSD.

However, it will not let me convert my SSD to apfs. I have tried via an install usb, via recovery, and via disk utility in the actual os. None of them give me the option to convert.

Any ideas that can help me?
Did you run the High Sierra installer to update the firmware on the Mac Pro? What firmware version is installed on the computer?
 
Last edited:
Did the High Sierra installer update the firmware on the Mac Pro? What firmware version is installed on the computer?

It contain the firmware updated, when you run the installer, it will tell you firmware upgrade required, and then run the updated if you accept the upgrade.

But you can stop the installer once the firmware update is completed. So, you can effectively only do the firmware update but not to install the beta OS.

The most up to date firmware version is MP51.0084.B00
 
It contain the firmware updated, when you run the installer, it will tell you firmware upgrade required, and then run the updated if you accept the upgrade.

But you can stop the installer once the firmware update is completed. So, you can effectively only do the firmware update but not to install the beta OS.

The most up to date firmware version is MP51.0084.B00
Yes, I was trying to ask if the poster had run the update on that Mac Pro but had typos that made my question not make sense.
 
Ok so I had DP5 installed, then i updated to DP6 via the AppStore.

But then i read about you guys seeing a new firmware, so i downloaded the full installer, then did only the portion of the firmware, Since the dp6 was already installed. I dont think the install order would affect the apfs conversion.
[doublepost=1502900852][/doublepost]
Erase SSD and it will give you the option of APFS. Otherwise wait for Apple to fix this.

I have a full bootable clone so erasing and then cloning over isn’t a huge deal and would only take up an hours or so time, but the point of the beta is to try these things out and see what’s works and what doesn’t. I’m ok keeping it HFS for now. Just wondering if anyone else is seeing this, and bringing it to attention
 
Reformatting is no big deal to be. I always do this for major OS updates.

For those who have used APFS, does it improve spotlight search times? If they could eliminate that 1-2 second delay after typing in the search field it would be really nice.
 
im curious where did you find that dump, do you have a path to where i might find it on my own system? also what does "show report" show? do you have a screen shot? :)

I also noticed that the picture, shows firmware of a MBP9,1 (2012 non retina MacBook Pro 15 inch), not a Mac Pro 5,1...


Sorry for the late reply, was busy today.
First, I got a new warning today, even with the new firmware, so the bug is not solved.
My Mac restarted so I can't find it anymore but I am positive it was in /private/tmp
Show report showed nothing, when I clicked on show report I got the same notification with the same dump, sending to Apple worked, nothing else did.
I opened the dump file, it's hex so can't read anything, opened in TextEdit too but there does not seem to be any readable text.

Edit: I tried to find it in my backup, sadly it doesn't backup /private/temp *

* It shouldn't backup tmp, no reason, same for other folders/files like sleepimage or VM
 
Last edited:
Sorry for the late reply, was busy today.
First, I got a new warning today, even with the new firmware, so the bug is not solved.
My Mac restarted so I can't find it anymore but I am positive it was in /private/tmp
Show report showed nothing, when I clicked on show report I got the same notification with the same dump, sending to Apple worked, nothing else did.
I opened the dump file, it's hex so can't read anything, opened in TextEdit too but there does not seem to be any readable text.

Edit: I tried to find it in my backup, sadly it doesn't backup /private/temp *

* It shouldn't backup tmp, no reason, same for other folders/files like sleepimage or VM
Is this on a cMP 5,1 or a MacBook Pro though?
 
I told you, someone asked me, should I ignore the poster then!.
But hey, I am gone so no more interfering with your thread.
C'mon, don't be like that.
There's no harm in mentioning that you're talking about other Macs when you do (even when replying), it would save me some time searching for same dumps on my cMP, lol
 
#134 is the post I told "you" here it's on a Mac Mini, I later on said again it's on a Mini and a MBP, so if you follow this thread you should be aware of what I said.

Read #134
 
  • Like
Reactions: owbp
I know, it's just easy to go over such a thing when everyone is writing about Mac Pro in its own subforum.
That's the only reason I told what I did in previous post.
 
they are probably too power-hungry to run off 2x 6pin connectors.

The RX Vega 64 is. But you shouldn't have any trouble running the RX Vega 56.
[doublepost=1502994631][/doublepost]
Back on-off topic - ahem - my cMP 4,1>5,1 (dual tray) that I updated the firmware to B00 to - still running 10.12.6 - is showing TRIM enabled for both of my Samsung 850 EVO SSDs plus my Samsung 960 EVO NVMe as well. So TRIM sticks when upgrading the firmware whilst still remaining with Sierra 10.12.6, even for NVMe.

What I really, really want now more than anything else is for native NVMe support. But what would be really, really, really nice is for NVMe boot support. C'mon Apple - puh-leeez!

I updated the firmware and my non-Apple drives are not showing as TRIM enabled. Isn't a bad idea to force enable TRIM on a non-Apple Samsung SSD? I read it doesn't implement it correctly and you could end up with corrupted data. So I think it's best to leave it off.
[doublepost=1502994869][/doublepost]With the firmware update my cMP feels a lot snappier. :) Still running Sierra.
 
Last edited:
Isn't a bad idea to force enable TRIM on a non-Apple Samsung SSD? I read it doesn't implement it correctly and you could end up with corrupted data.
There was a problem specific to some older Linux kernels that could lead to data corruption when using Trim on those Linux systems. The problem has been fixed for quite a while and has never affected Macs.
 
Feels the same to me!
For me it's a tinny bit worse o_O
Screenshot 2017-08-17 20.44.58.png
Screenshot 2017-08-17 20.45.12.png
Screenshot 2017-08-18 02.29.45.png

:D
But I'm sure it has nothing to do with firmware u update.
 
One thing I wonder about that new firmware is if it allow other CPUs that were not supported to work? It'd be great, especially since CPUs that old can be bought for very cheap nowadays!
 
One thing I wonder about that new firmware is if it allow other CPUs that were not supported to work? It'd be great, especially since CPUs that old can be bought for very cheap nowadays!

No one test it yet, if you can buy a fully refundable CPU, you may try any report. However, it's very unlikely Apple will do that. Apple never expect anyone upgrade the CPU by themselves. There is no need to support any CPU that's not an Apple standard option.
 
the only cpu that could have been added is the high clock dual core xeon around 4Ghz, but I don't see why they would add that. It would be nice if they could remove the 2.5GT/sec limitation with the rom.
 
  • Like
Reactions: dabotsonline
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.