Samsung SM951 prevents Win7 boot.

[Zeke D]

I had had an OWC 4x PCIe adapter in slot 3, and an Apricorn Velocity X1 in slot 4. Both had ADATA SU800 drives. I had no problem booting to Sierra on the OWC, and windows 7 on the Apricorn.

I swapped out the OWC for a Samsung SM951 in a generic 4x PCIe card, and it boots fine to Sierra, but the Apricorn won't boot-- it just hangs at the card's bios screen. I pull the Apricorn, and it boots to windows just fine. I tried swapping the slots, and the issue is the same.

Specs:
2010 Mac Pro
2 x 2.93 GHz 6-Core Intel Xeon
32 GB 1066 MHz DDR3 (4x 8GB Samsung Dimms)
NVIDIA GeForce GTX 680 2048 MB

 

[tsialex]

I had had an OWC 4x PCIe adapter in slot 3, and an Apricorn Velocity X1 in slot 4. Both had ADATA SU800 drives. I had no problem booting to Sierra on the OWC, and windows 7 on the Apricorn.

I swapped out the OWC for a Samsung SM951 in a generic 4x PCIe card, and it boots fine to Sierra, but the Apricorn won't boot-- it just hangs at the card's bios screen. I pull the Apricorn, and it boots to windows just fine. I tried swapping the slots, and the issue is the same.

Specs:
2010 Mac Pro
2 x 2.93 GHz 6-Core Intel Xeon
32 GB 1066 MHz DDR3 (4x 8GB Samsung Dimms)
NVIDIA GeForce GTX 680 2048 MB

SM951-NVMe and 950Pro have lots of compatibility problems with Apple's NVMe EFI module. 950Pro can't even boot, but I didn't know that SM951-AHCI had problems before.

 

[Zeke D]

SM951-NVMe and 950Pro have lots of compatibility problems with Apple's NVMe EFI module. 950Pro can't even boot, but I didn't know that SM951-AHCI had problems before.

So I'm just out of luck if I want to use the SM951?

 

[thornslack]

Does it say no bootable device or is it literally on the bios screen?

 

[Zeke D]

Does it say no bootable device or is it literally on the bios screen?

If it is selected as the boot drive, it hangs at the bios screen. If I select it from the EFI boot menu, then it hangs at a blank screen.

Moving the SSD from the PCIe card to one of the drive bays allows it to boot to windows. It worked with a pair of sataIII SSDs in PCIe cards, just not the SM951. I don't have another AHCI SSD to test if it's just the Samsung.

 

[handheldgames]

If it is selected as the boot drive, it hangs at the bios screen. If I select it from the EFI boot menu, then it hangs at a blank screen.

Moving the SSD from the PCIe card to one of the drive bays allows it to boot to windows. It worked with a pair of sataIII SSDs in PCIe cards, just not the SM951. I don't have another AHCI SSD to test if it's just the Samsung.

I had 4 sm951 ahci ssds running in a cmp without issue using a lycom m.2 adapter, amfeltec squid and a highpoint ssd7101-a. The were used alongside an apple/samsung SSUBX & SSUAX, and a 970 pro.

It sounds like your m.2 drive or adapter may be causing the issue. It would be worth removing and re-mounting the SM951 in the m.2 slot.

Have you tested the sm951 in slot 2?

 

[Zeke D]

I had 4 sm951 ahci ssds running in a cmp without issue using a lycom m.2 adapter, amfeltec squid and a highpoint ssd7101-a. The were used alongside an apple/samsung SSUBX & SSUAX, and a 970 pro.

It sounds like your m.2 drive or adapter may be causing the issue. It would be worth removing and re-mounting the SM951 in the m.2 slot.

Have you tested the sm951 in slot 2?

I hadn't tested it in in slot 2, only 3 & 4. The booting drive I'm having issues with is not the SM951 drive itself - that boots into Sierra just fine, it's when the Apricorn Velocity X1 tries to boot into windows. Remove the SM951, and it boots fine. Swap the SM951 with a SATAIII SSD in a OWC Accelsior S, and both drives boot just fine.

Should I still reseat the AHCI SSD? Should I move the SM951 to slot 2, or should I try the Apricorn to slot 2?

 

[handheldgames]

I hadn't tested it in in slot 2, only 3 & 4. The booting drive I'm having issues with is not the SM951 drive itself - that boots into Sierra just fine, it's when the Apricorn Velocity X1 tries to boot into windows. Remove the SM951, and it boots fine. Swap the SM951 with a SATAIII SSD in a OWC Accelsior S, and both drives boot just fine.

Should I still reseat the AHCI SSD? Should I move the SM951 to slot 2, or should I try the Apricorn to slot 2?

Good points. Reseating won't help. Sounds like an interesting hardware conflict.Sorry, I don't bootcamp windows or sata III hard disks. Two posts come to mind:

https://forums.macrumors.com/thread...native-in-the-status-bar-of-your-mac.2145374/

There is another post out there that changes a pcie ssd from external to internal. That may help you as well.

 

[Zeke D]

Definitely a useful post, but I don't think that that will solve my problem. I just moved the SATAIII SSD from the PCIe card to one of the bays. I'd printed some spare trays, so it was no big deal. I use Windows for a little bit of gaming, so a slower drive isn't a huge deal.

Good points. Reseating won't help. Sounds like an interesting hardware conflict.Sorry, I don't bootcamp windows or sata III hard disks. Two posts come to mind:

https://forums.macrumors.com/thread...native-in-the-status-bar-of-your-mac.2145374/

There is another post out there that changes a pcie ssd from external to internal. That may help you as well.

 

[crjackson2134]

I had the same issue with Windows / SSUBX with Windows on my Apricorn Card.

I was able to get it working by cloning the Windows drive to one in a Bay. Then booting that Windows drive so that it can re-detect the hardware (keep the Apricorn installed when doing this, but without a Windows drive mounted on the Apricorn. A blank drive instead). Once this is successful, clone it back to the Apricorn mounted drive, and remove the bay mounted drive after shutting down.

It probably will take a few reboot attempts, because Windows is sensitive and wants to boot only from the drive uuid where it was installed. Using the most recent version of WinClone can and usually does adjust the Windows boot file to reflect the new drive. Shutdown and remove the windows drive from the Mac Bay mounted position before trying to boot your new copy. Only one copy of Windows should be installed at a time.

As said earlier, it may take multiple boot attempts before it loads. I pulled the last hair out of my head before I was able to find a working solution. I’ve done this a few times now, and in the end it has always worked for me.

Not 100% sure it will work for you, but what have you got to lose by trying?

On one occasion, I had to use Paragon Drive Manager, select the Windows drive, and ran the option that repairs and corrects Athe windows boot files. This was an occasion where WinClone failed me. I no longer have the Apricorn adapter installed, and all these issues went away.

I’m not sure really why this works for me, it doesn’t really seem logical either. I just know that for some reason, it solved my problem.

 

[handheldgames]

I had the same issue with Windows / SSUBX with Windows on my Apricorn Card.

I was able to get it working by cloning the Windows drive to one in a Bay. Then booting that Windows drive so that it can re-detect the hardware (keep the Apricorn installed when doing this, but without a Windows drive mounted on the Apricorn. A blank drive instead). Once this is successful, clone it back to the Apricorn mounted drive, and remove the bay mounted drive after shutting down.

It probably will take a few reboot attempts, because Windows is sensitive and wants to boot only from the drive uuid where it was installed. Using the most recent version of WinClone can and usually does adjust the Windows boot file to reflect the new drive. Shutdown and remove the windows drive from the Mac Bay mounted position before trying to boot your new copy. Only one copy of Windows should be installed at a time.

As said earlier, it may take multiple boot attempts before it loads. I pulled the last hair out of my head before I was able to find a working solution. I’ve done this a few times now, and in the end it has always worked for me.

Not 100% sure it will work for you, but what have you got to lose by trying?

On one occasion, I had to use Paragon Drive Manager, select the Windows drive, and ran the option that repairs and corrects Athe windows boot files. This was an occasion where WinClone failed me. I no longer have the Apricorn adapter installed, and all these issues went away.

I’m not sure really why this works for me, it doesn’t really seem logical either. I just know that for some reason, it solved my problem.

Considering the SSUBX is almost identical to the SM951, thanks for sharing the added info. It should give Zeke an idea of what can be expected.

 

[Zeke D]

Nice I'll give that one a tray. I have the WD flavor of Acronis, so I can do all the cloning that way.

I had the same issue with Windows / SSUBX with Windows on my Apricorn Card.

I was able to get it working by cloning the Windows drive to one in a Bay. Then booting that Windows drive so that it can re-detect the hardware (keep the Apricorn installed when doing this, but without a Windows drive mounted on the Apricorn. A blank drive instead). Once this is successful, clone it back to the Apricorn mounted drive, and remove the bay mounted drive after shutting down.

It probably will take a few reboot attempts, because Windows is sensitive and wants to boot only from the drive uuid where it was installed. Using the most recent version of WinClone can and usually does adjust the Windows boot file to reflect the new drive. Shutdown and remove the windows drive from the Mac Bay mounted position before trying to boot your new copy. Only one copy of Windows should be installed at a time.

As said earlier, it may take multiple boot attempts before it loads. I pulled the last hair out of my head before I was able to find a working solution. I’ve done this a few times now, and in the end it has always worked for me.

Not 100% sure it will work for you, but what have you got to lose by trying?

On one occasion, I had to use Paragon Drive Manager, select the Windows drive, and ran the option that repairs and corrects Athe windows boot files. This was an occasion where WinClone failed me. I no longer have the Apricorn adapter installed, and all these issues went away.

I’m not sure really why this works for me, it doesn’t really seem logical either. I just know that for some reason, it solved my problem.

 

[Zeke D]

I had the same issue with Windows / SSUBX with Windows on my Apricorn Card.

So, with the Apricorn and the SM951 in the machine, and an unformatted SSD in the Apricorn, I can't even boot to the Windows installation in bay1 - it hangs at the Apricorn bios screen.

 

[crjackson2134]

So, with the Apricorn and the SM951 in the machine, and an unformatted SSD in the Apricorn, I can't even boot to the Windows installation in bay1 - it hangs at the Apricorn bios screen.

Did you clone to Bay1 or just move the drive?

If you can pull out the SM951 or the Apricorn, does it start working again? If not, I would hazard a guess you need to repair the mbr at this stage. Then install each device (1 at a time) and try a boot. Sometimes I have to attempt a reboot several times before it works. Also, power off, don’t just restart. When you get it to boot, run Windows update and check the device manager for unrecognized devices. Rinse and repeat with each drive controller until you get it booting from the bay drive. It’s a frustrating process, but that’s how I got it working again here.

 

[Zeke D]

I couldn't clone, because I couldn't boot to ANY windows drive with the Apricorn and the SM951 installed. it's like the Apricorn hijacks the boot loader at the bios screen, but it's like trying to control the SM951, and that's causing the issues.

If I pull either the Apricorn or the SM951, then everything works as expected. Plus, when the Apricorn and the Accelsior S were both installed, they both work as expected.

I suspect that it could be that the 4x PCIe adapter for the SM951 is just a pass-through, and that perhaps a card with a controller in it will stop whatever incompatibility with the Apricorn. It's a shame that the Accelsor S isn't windows bootable.

I got the PCIe adapter used, and the card has no markings, but it looks like this one: https://www.amazon.com/dp/B07GSVXFGQ/

Did you clone to Bay1 or just move the drive?

If you can pull out the SM951 or the Apricorn, does it start working again? If not, I would hazard a guess you need to repair the mbr at this stage. Then install each device (1 at a time) and try a boot. Sometimes I have to attempt a reboot several times before it works. Also, power off, don’t just restart. When you get it to boot, run Windows update and check the device manager for unrecognized devices. Rinse and repeat with each drive controller until you get it booting from the bay drive. It’s a frustrating process, but that’s how I got it working again here.

 

[crjackson2134]

I couldn't clone, because I couldn't boot to ANY windows drive with the Apricorn and the SM951 installed. it's like the Apricorn hijacks the boot loader at the bios screen, but it's like trying to control the SM951, and that's causing the issues.

If I pull either the Apricorn or the SM951, then everything works as expected. Plus, when the Apricorn and the Accelsior S were both installed, they both work as expected.

I suspect that it could be that the 4x PCIe adapter for the SM951 is just a pass-through, and that perhaps a card with a controller in it will stop whatever incompatibility with the Apricorn. It's a shame that the Accelsor S isn't windows bootable.

I see...The whole reason for WinClone (I own Acronis also) is so that you can boot macOS and clone the Win drive from there. WinClone can actually manipulate the boot files automatically and adjust for the uuid of the Windows drive as it clones. Acronis doesn’t do this. That MAY or May NOT be key in your case. It was for me.

Put only 1 of those devices in and boot Win. Then do an update. When done, pull the device and put in the other and do the update. Next try both again... If that doesn’t work, then move them to alternate slots. This also should initiate rescan of hardware. I know it goes without saying, but you should also be doing PRAM/SMC reset when moving things around.

I’m not kidding, I kept at this for a week... I was ready to burn down the house, just to melt the aluminum case of my Mac. Then it suddenly worked like I wanted. Being the stubborn PITA that I am, I didn’t stop until I was able to get this thing working every time. Of course your system and mine have differences, but I suspect if you are stubborn enough, you will make it all work.

2 things we didn’t explore or talk about... I’m working with Win10 Legacy mode and a Samsung 860 EVO for my Win drive, and I have a SOLO x2 vs your SOLO x1. The Solo x1 has an Asmedia 1061 controller, and the Solo x2 has the Marvel 9182 controller. This may in fact be the problem. Contact ApricornTechSupport and see if they know this to be a compatibility issue.

 

[Zeke D]

Time for some thread necromancy. Got the Velocity X2 in with the SM951-AHCI, And they're Co-existing... you weren’t kidding. I’ve been working on this for two weeks, and finally am ready to button the cMP back up once I figure out what windows update is bricking my win7 installation.

 

[MIKX]

What about installing Windows directly onto the SM951 - assuming that the Windows install CD can see and format it ?

 

[Zeke D]

What about installing Windows directly onto the SM951 - assuming that the Windows install CD can see and format it ?

Windows 7 doesn't support installation in EFI mode on a mac pro for some reason, which is required for installation on a PCIe drive. I've gotten Win10 installed in EFI mode, and on the SM951, but Win10 is garbage.