Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
When you said "big issue!" you scared me for a while :)
[doublepost=1558104605][/doublepost]Now 7102 looks more attractive than ever. If you ever look for support from Highpoint don't even mention MAC. Only Windows, boot, raid...
 
When you said "big issue!" you scared me for a while :)
[doublepost=1558104605][/doublepost]Now 7102 looks more attractive than ever. If you ever look for support from Highpoint don't even mention MAC. Only Windows, boot, raid...

ha ha, sorry for my bad English.

I also want to test on MacOS Mojave, but my sapphire pulse rx580 is too thick to plug SSD7102 on PCI slot 2, maybe the driver and raid mode works on Mojave.
 
Last edited:
Device (16,0) could be the ID of the PEX-8314, where 0x7102 and 0x91a4 are connected, no?
16,0 is the bus and device number of the Marvell chip. The NVMe devices have bus numbers 12,15,17. Bridges are not listed in the PCIe list and would have a different bus number. Need ioreg or "lspci -tvnn" output to be sure.
 
  • Like
Reactions: tsialex
Then I use CCC to clone my MacOS High Sierra 10.13.6 boot drive to this SamsungRaid0 drive and reboot from it, succeed!
Does this mean the 7102 is booting using an EFI option rom driver from the card on a Mac Pro? I guess this would require EFI Shell info to find out. Maybe "nvram -p" output in macOS would give a clue (after you set the raid as the boot drive in Startup Disk preferences panel).

I try to boot from other drive without install SSD7101-A driver, the SamsungRaid0 drive is not work and disappear in Disk Utility.
That makes sense. Without the driver, the OS can't understand how the NVMe drives are formatted (they are formatted differently than the way that Disk Utilities does it for its raids).

And more, I clone a boot drive with no SSD7101-A driver to the SamsungRaid0 drive, it is not bootable.
So I think maybe clean installation of MacOS on SSD7102 array drive and boot from it is not useful, because of no SSD7101-A driver on it.
That makes sense. The EFI driver can understand the RAID, so you can probably see it in the Startup Manager (when you press Option during boot) and in boot loaders like rEFInd and you can use the EFI Shell to view files from it. When the OS starts, the disk driver from the OS needs to take over, but if it doesn't exist then booting stops.
 
Big issue!
SSD7101-A's MacOS driver works on SSD7102, I use "HighPoint RAID Management" to create array, guess what?
Awesome!
View attachment 837551

In Disk Utility, you can find a external drive model name listed as HPT DISK 3_0 Media, then I erase/format it and named as SamsungRaid0, no issue.
View attachment 837552

I test R/W speed of the SamsungRaid0 drive, the performance seems great, maybe the same as SSD7101-A.
View attachment 837553
View attachment 837554


Then I use CCC to clone my MacOS High Sierra 10.13.6 boot drive to this SamsungRaid0 drive and reboot from it, succeed!
View attachment 837555

I try to boot from other drive without install SSD7101-A driver, the SamsungRaid0 drive is not work and disappear in Disk Utility.
And more, I clone a boot drive with no SSD7101-A driver to the SamsungRaid0 drive, it is not bootable.
So I think maybe clean installation of MacOS on SSD7102 array drive and boot from it is not useful, because of no SSD7101-A driver on it.

That's my test report.
That's great news! I had a feeling it would work. If it didn't, I was going to tell you to try the software for the ssd7110. The driver & NVMe Manger for the 7110 would probably work too and that card was also designed with RAID boot support unlike 7101A. I havn't checked the file size of all the 7100 series driver/NVMe Manger software to see if they are the same size or not. For all I know they could be the same or different. If they do vary between each card, I'd be curious to see if there are extra options in the 7110 NVMe Manager or if it's driver closer matched the hardware on your board. I hope someone tests the actual 7110 card soon. Be interesting to see what's under the hood since it has SAS/SATA support too. I bet it will be very similar to 7102 with extra components for the SAS ports.

Nice that you have the option for RAID 0,1,5 & 1/0 arrays using the HPT software and Mac OS sees it as one physical drive. Opens up more ways you can use your card. If anything you have assured me it would be ok for me to buy a 7102 and get the HPT software working on Mac OS one way or another, even though HPT is not officially supporting it. Perhaps even squeeze out a few extra features over a 7101A although in the end they are both stellar cards performance wise.
 
Does this mean the 7102 is booting using an EFI option rom driver from the card on a Mac Pro? I guess this would require EFI Shell info to find out. Maybe "nvram -p" output in macOS would give a clue (after you set the raid as the boot drive in Startup Disk preferences panel).

Actually I'm not sure how 7102 boot.
I post "nvram -p" output here, can you find some clue?

----------------------------------------------------------------
LocationServicesEnabled %01

efi-backup-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>6D1E747C-DC7F-418B-8BB2-B730F377971A</string></dict></dict><key>BLLastBSDName</key><string>disk3s2</string></dict></array>%00

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>83B132E0-B23E-4857-A02F-83C2B9AF053A</string></dict></dict><key>BLLastBSDName</key><string>disk10s2</string></dict></array>

BootCampHD %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%7f%ff%04%00

bluetoothInternalControllerInfo %15%82%ac%05%00%00%11Z4Q%c9%ee%9c%ff

NVMeCommandErrorQueue %01%00%00%00

nvda_drv 1

NVMeCommandErrorOpcode %02%00%00%00

SystemAudioVolumeDB %f2

prev-lang:kbd en:0

fmm-computer-name %e2%80%9cwjesse%e2%80%9d%e7%9a%84 Mac Pro

bluetoothActiveControllerInfo %15%82%ac%05%00%00%00%00%11Z4Q%c9%ee%9c%ff

efi-boot-device-data %03%01%08%00%00%01%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00%d8%df%96;%00%00%00%00%e02%b1%83>%b2WH%a0/%83%c2%b9%af%05:%02%02%7f%ff%04%00

SystemAudioVolume 2

EFIBluetoothDelay %b8%0b

efi-backup-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%01%01%01%06%00%00%00%01%01%06%00%00%04%01%01%06%00%00%00%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00@%ceRt%00%00%00%00|t%1em%7f%dc%8bA%8b%b2%b70%f3w%97%1a%02%02%7f%ff%04%00
 
Actually I'm not sure how 7102 boot.
I post "nvram -p" output here, can you find some clue?

----------------------------------------------------------------
LocationServicesEnabled %01

efi-backup-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>6D1E747C-DC7F-418B-8BB2-B730F377971A</string></dict></dict><key>BLLastBSDName</key><string>disk3s2</string></dict></array>%00

efi-boot-device <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>83B132E0-B23E-4857-A02F-83C2B9AF053A</string></dict></dict><key>BLLastBSDName</key><string>disk10s2</string></dict></array>

BootCampHD %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%02%1f%03%12%0a%00%00%00%00%00%00%00%7f%ff%04%00

bluetoothInternalControllerInfo %15%82%ac%05%00%00%11Z4Q%c9%ee%9c%ff

NVMeCommandErrorQueue %01%00%00%00

nvda_drv 1

NVMeCommandErrorOpcode %02%00%00%00

SystemAudioVolumeDB %f2

prev-lang:kbd en:0

fmm-computer-name %e2%80%9cwjesse%e2%80%9d%e7%9a%84 Mac Pro

bluetoothActiveControllerInfo %15%82%ac%05%00%00%00%00%11Z4Q%c9%ee%9c%ff

efi-boot-device-data %03%01%08%00%00%01%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00%d8%df%96;%00%00%00%00%e02%b1%83>%b2WH%a0/%83%c2%b9%af%05:%02%02%7f%ff%04%00

SystemAudioVolume 2

EFIBluetoothDelay %b8%0b

efi-backup-boot-device-data %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%01%01%01%06%00%00%00%01%01%06%00%00%04%01%01%06%00%00%00%03%12%0a%00%01%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00@%ceRt%00%00%00%00|t%1em%7f%dc%8bA%8b%b2%b70%f3w%97%1a%02%02%7f%ff%04%00
Every Apple_RAID array has a partition (Apple_Boot) that is used to boot, please post a diskutil list to show if the AppleBoot is disk10s2
 
Hello everyone,
so does the 7102 work with both AHCI and NVME?

the 7102 work with AHCI ssd, but you can not create raid array by HighPoint RAID Management .
I think the same as 7101-A.
[doublepost=1558186971][/doublepost]
Every Apple_RAID array has a partition (Apple_Boot) that is used to boot, please post a diskutil list to show if the AppleBoot is disk10s2

I'm not sure how to show diskutil list, like this?
or please tell me how to do it, thanks.
Storage.jpg
 
the 7102 work with AHCI ssd, but you can not create raid array by HighPoint RAID Management .
I think the same as 7101-A.
[doublepost=1558186971][/doublepost]

I'm not sure how to show diskutil list, like this?
or please tell me how to do it, thanks.
View attachment 837728
Open Terminal and run diskutil list, like this:
 

Attachments

  • Screen Shot 2019-05-18 at 10.49.39.png
    Screen Shot 2019-05-18 at 10.49.39.png
    67.9 KB · Views: 190
Interesting, I don't understand how the drives are merged as macOS sees just only drive. I'll test this with my SSD7101-A to see if I can do the same.

Today I replace my GPU to GT-120 and boot from MacOS Mojave boot drive, then installed SSD7101-A driver and reboot, my "HPT DISK 3_0 Media" raid0 disk becomes available.

I partition "HPT DISK 3_0 Media" raid0 disk into two drives, format the new partition named as "Raid0 Mojave" and clone MacOS Mojave boot drive to it, then it is bootable.

So I'm sure we can use SSD7102 Raid0 drive to boot MacOS Mojave.
Screen Shot 2019-05-18 at 8.53.43 AM.jpg
 
  • Like
Reactions: Mac_User 0101
Today I replace my GPU to GT-120 and boot from MacOS Mojave boot drive, then installed SSD7101-A driver and reboot, my "HPT DISK 3_0 Media" raid0 disk becomes available.

I partition "HPT DISK 3_0 Media" raid0 disk into two drives, format the new partition named as "Raid0 Mojave" and clone MacOS Mojave boot drive to it, then it is bootable.

So I'm sure we can use SSD7102 Raid0 drive to boot MacOS Mojave.
View attachment 837742

Using HFS+ correct?

Haven’t tried this with the SSD7101-A personally, but can’t you do the same with either card.
 
Last edited:
Today I replace my GPU to GT-120 and boot from MacOS Mojave boot drive, then installed SSD7101-A driver and reboot, my "HPT DISK 3_0 Media" raid0 disk becomes available.

I partition "HPT DISK 3_0 Media" raid0 disk into two drives, format the new partition named as "Raid0 Mojave" and clone MacOS Mojave boot drive to it, then it is bootable.

So I'm sure we can use SSD7102 Raid0 drive to boot MacOS Mojave.
View attachment 837742
What video card are you using? I'm wondering because I was thinking of getting a Sapphire RX 580 but someone mentioned I'd have trouble fitting a HPT m.2 carrier above it in slot 2. Any space issue with your 7102 and video card?
 
What video card are you using? I'm wondering because I was thinking of getting a Sapphire RX 580 but someone mentioned I'd have trouble fitting a HPT m.2 carrier above it in slot 2. Any space issue with your 7102 and video card?
Sapphire Pulse RX-580 and SSD7101-A is not a good fit, you have to wedge it for the fans don't hit the SSD7101-A back.
 
  • Like
Reactions: zachek
Interesting, I don't understand how the drives are merged as macOS sees just only drive. I'll test this with my SSD7101-A to see if I can do the same.
I think you can. If the ssd7100 series RAID works anything like my HPT RS6124v then the HPT GUI programs the hardware RAID controller rather than physical switches. All my enclosures that have hardware RAID appear to the OS as one physical drive so essentially the OS don't know it's RAID. Have we tried booting an APFS volume via hardware RAID?
[doublepost=1558197137][/doublepost]
Sapphire Pulse RX-580 and SSD7101-A is not a good fit, you have to wedge it for the fans don't hit the SSD7101-A back.
Thanks, I'll avoid that video card.
 
I think you can. If the ssd7100 series RAID works anything like my HPT RS6124v then the HPT GUI programs the hardware RAID controller rather than physical switches. All my enclosures that have hardware RAID appear to the OS as one physical drive so essentially the OS don't know it's RAID. Have we tried booting an APFS volume via hardware RAID?
[doublepost=1558197137][/doublepost]
Thanks, I'll avoid that video card.
What I want to understand is how it’s being done without an option ROM. ;)

APFS boots from hardware RAID arrays that show to the macOS just one disk.
 
  • Like
Reactions: Mac_User 0101
Just one side question:

Does MacsFanControl have access to the fan of 7101 or 7102? Is it adjustable?
 
Just one side question:

Does MacsFanControl have access to the fan of 7101 or 7102? Is it adjustable?
SSD7101-A have a fixed rotation fan.

SSD7102 have a variable one, but AFAIK, no software reads SSD7102 fan rotation. This is a question for HighPoint support answer.
 
<guess>
What does this card look like using "lspci", or Windows Device Manager, or ioreg?

This is not useful, you have to show the full lspci, since the controllers will have different PCIe IDs and you are doing grep for just the PEX-8747, SSD7102 has another PCIe switch, PEX-8714.
Use something like this, change the 5:* and 6:* to the correct PCIe device domains:
Code:
sudo lspci -vvx -s 5:* >SSD7102.vvx.txt; sudo lspci -vvx -s 6:* >>SSD7102.vvx.txt

I think the following command should give all the information about Slot-2 devices (PXS2 is the name for slot 2 on my MacPro3,1):
Code:
ioreg -fiw0 -n PXS2 -rl > ioregslot2.txt

I am not familiar with the terminal command, how to show the full lspci? and how to make sure my correct PCIe device domains to change the 5:* and 6:*?

I use terminal and type code you provide here, it shows command not found.
 
I am not familiar with the terminal command, how to show the full lspci? and how to make sure my correct PCIe device domains to change the 5:* and 6:*?

I use terminal and type code you provide here, it shows command not found.
You have to install pciutils: https://github.com/warexify/pciutils

I usually install from here: https://github.com/gmerlino/homebrew-pciutils

Code:
brew install --HEAD https://raw.githubusercontent.com/gmerlino/homebrew-pciutils/master/pciutils.rb

Install homebrew first: http://brew.sh
 
Last edited:
What video card are you using? I'm wondering because I was thinking of getting a Sapphire RX 580 but someone mentioned I'd have trouble fitting a HPT m.2 carrier above it in slot 2. Any space issue with your 7102 and video card?

Sapphire Pulse RX-580 and SSD7101-A is not a good fit, you have to wedge it for the fans don't hit the SSD7101-A back.

I'm using Nvidia GTX-1080 in High Sierra, but Sapphire Pulse RX-580 in Mojave.
GTX-1080 and SSD7102 fits fine.
Just like tsialex said, Sapphire Pulse RX-580 and SSD7102 is neither a good fit, there is no space for the GPU fans.
GTX-1080 do not support Mojave, so I replace RX-580 to GT-120 when test SSD7102 and Mojave.

GTX-1080 and SSD7102
P5350384.jpg
P5350385.jpg


Sapphire Pulse RX-580 and SSD7102
P5350386.jpg
 
Do you want to see something funny :
[doublepost=1558285346][/doublepost]
 

Attachments

  • Screen Shot 2019-05-19 at 12.56.34 PM.png
    Screen Shot 2019-05-19 at 12.56.34 PM.png
    249.1 KB · Views: 334
Last edited:
I'm using Nvidia GTX-1080 in High Sierra, but Sapphire Pulse RX-580 in Mojave.
GTX-1080 and SSD7102 fits fine.
Just like tsialex said, Sapphire Pulse RX-580 and SSD7102 is neither a good fit, there is no space for the GPU fans.
GTX-1080 do not support Mojave, so I replace RX-580 to GT-120 when test SSD7102 and Mojave.

GTX-1080 and SSD7102
View attachment 837866 View attachment 837867

Sapphire Pulse RX-580 and SSD7102View attachment 837869

You could place the SSD7102 in slot 1 and the Rx580 in Slot#2.

Although you would loose one PCIe 2,0 x4 slot, you are gaining 4 PCIe 3.0 x4 m.2 slots with a properly cooled SSD7102. :cool:. If you really need the SATA 3 controller, there are m.2 options.. http://www.lycom.com.tw/DT-152BM.htm
 
  • Like
Reactions: crjackson2134
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.