I can confirm that my 970 pro with X5690 and DT-120 had no issues with CCC. Copying and booting Mojave without any issues.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Can a Mac Pro boot up to Mojave with a non metal card?
- Thread starter HyperX13
- Start date
- Sort by reaction score
Interesting. Well, I have an Aquacomputer Kryo in the mail somewhere along with a 970EVO Plus. I'll definitely pull the Velocity X2 for a few weeks (if the PLUS boots) and see if I have any troubles.
If I boot from a bay mounted SSD, problem abates, If I boot with HD7970 installed instead of the RX580, the problem abates (but I’m going to test it again to make sure I’m not wrong).
I can cause the boot-problem on demand when booted from the 970 Pro w/RX580, by using CCC to make a compressed/read-only drive image of the 970, and storing the image on a SATA mounted spinner. Upon either reboot, or shutdown and cold boot, it will hang everytime.
Prior to yesterday, it seemed random, but I seem have to have found a way to induce the problem. Hopefully this will help figuring this out. I’ve ordered a passthrough PCIe adapter to test with, and I’m going to pull the RX580 again for retesting..
At least more people are seeing this problem now, so maybe someone will stumble across the cause/cure.
I can cause the boot-problem on demand when booted from the 970 Pro w/RX580, by using CCC to make a compressed/read-only drive image of the 970, and storing the image on a SATA mounted spinner. Upon either reboot, or shutdown and cold boot, it will hang everytime.
Prior to yesterday, it seemed random, but I seem have to have found a way to induce the problem. Hopefully this will help figuring this out. I’ve ordered a passthrough PCIe adapter to test with, and I’m going to pull the RX580 again for retesting..
At least more people are seeing this problem now, so maybe someone will stumble across the cause/cure.
Well out of curiosity I ran Drive Dx on my system and it came back with this:
Since the "interface cable/power supply" in my case is actually the Velocity Solo card, I wonder if there's a problem with the card. I suppose a clean install on my forthcoming NVMe drive would be a good idea.
Since the "interface cable/power supply" in my case is actually the Velocity Solo card, I wonder if there's a problem with the card. I suppose a clean install on my forthcoming NVMe drive would be a good idea.
Would suggest you clone to another drive. Also worth seeing how that SATA SSD reports when connected directly via SATA sled (or optical bay) vs using the Apricorn adapter. That would troubleshoot the adapter issue vs potential drive issue.
I'm curious; I presume the RX580 is in slot 1 and the Velocity Solo card is in slot 2. Is the card in slot 2 perfectly seated and vertical, with slot cover also correctly aligned (no contact, strain, or displacement caused by the GPU)?
I've seen DrDx report CRC errors when an adapter is just barely mis-seated (looked perfect, but wasn't) and reseating the card in the slot cured it. Some cards are more finicky than others. Testing the drive in a SATA bay, as @bsbeamer suggests, can help determine whether the drive itself is producing CRC errors, however there is some chance that when re-installing the drive into the Velocity Solo and re-installing that into the PCIe slot the CRC errors will go away.
CRC errors are permanent and will be kept into the SMART, it can stop growing when installed into a south bridge SATA port, but that value will be forever with the drive.
Yes, you are correct and also precise!
Instead of telling "the errors may go away" I should have told "the errors may stop accumulating".