970 evo mac pro

Thanks,

The installer should be alright, since I have used it to flesh install High Sierra into several old MacBook Pros (Retina 2012 & N-R 2011) & iMac (pre 2011).

And the OSX version is 10.13.4.

Or is it my 760p is faulty (cannot white in some logic area)?

Regards,

Thanks, all,

Your guy always helpful.

I made another USB installer (this time with Mojave!), and got the same outcome. Intel 760p SSD is detected and can be formatted, but cannot write on it.

I suspect the nMP may be not being updated its firmware to High Sierra. I may need to fetch a apple SSD to verify and update.....

Anyways, thanks a lot.

Regards,

Ben (again, from Hong Kong SAR - NOT MAINLAND CHINA)

First, I want to thank all you guys for documenting this. We have 7 Late 2013 Mac Pro's in our studios and HDD space was getting tight to say the least. I have been looking for options and I like this one best. I have done all the updates and verifications and all are at boot ROM 127.0.0.0.0. I was getting read to start one but wanted to ask this question first. I bought 7 1TB Samsung M.2 970 EVO Plus NVMe SSDs and their corresponding Sintech adapter. I also bought an external NVMe enclosure to test all the SSD's before sticking them in permanently. Once I got one installed in the small enclosure and attached to the Mac Pro, of course it shows up, can be formatted with any of the available formats from APFS to Journaled, etc. I thought, why not clone my current default SSD to the new NVMe drive, ensure its bootable (by selecting it in System Preferences > Startup Disk), THEN do the hardware upgrade. Is this an option at all? I didn't see any one mention it as an option. I ask because we do have a tremendous amount of software on these systems; some software is HD authorized and others require USB dongles and such. If installing from scratch is the only option, I have to get some weekend downtime for these systems.

Let me know your thoughts on this.

Thanks

Dray @ New Ocean

Thanks for your help. I will be restorinh from Time Machine. Appears as though there is more than one way of doing this. Read a few comments about not being able to install OS over the internet due to the limitations of the adapter and others stating it is possible. Majority of users recommend booting from USB and then formatting the drive, I am just not sure how relevant it is if I am restoring from TM anyway...

After a week , I retried the late 2013 rMBPro and it is now successful. The first time I failed to disconnect the battery and it caused problems. The default SSD speed of the Apple original SSD was write 686 and read 699.

This would be the Samsung 970 NVMe using AJA:

also TRIM=YES and link width is 4. That 4 is impressive because pulling the late 2013 Mac Pro Apple default SSD which is a 4 only shows a 2 in the late 2013 rMBPro.

Hopefully this information assists others. I had to be a guinea pig. I don't mind.

It's hard for me to explain John, so I've drawn it instead. I'm presuming the person who fitted the heatsink hasn't got to slide it into an adaptor as well.

Are they just regurgitating something they read or did they actually test it in real life. I did and I was not impressed.

Both of those heatsinks/cards include a thermal pads to go between the face of the blade and the aluminium heatsink. The pad is a soft rubber sheet,

What macOS version was on the MP when the SSD failed?

How did you create the High Sierra USB installer?

should work but I gave up cloning years ago so can't give my experiences.

Thanks for the information. I am about to perform this procedure on mine.

One question, do you have to enable TRIM afterwards?

I thought enabling TRIM was only if you were moving from HDD to SSD? Am I wrong?

Probably easier to just check in sys info. I think if you enable it for one ssd and then clone across , it will be enabled for the second but not for a clean install but i could be wrong ...

I have this happening also!

Currently reinstalling Mojave to see if it resolves the issue. I had a similar problem with my iMac and restoring the OS fixed it.