I have not been able to mount the Pegasus R2 M4 on my new Mac Mini with the M1 SOC. I am able to run Promise Utility but it does not recognize the drive's presence at all.
In Finder, Drive Utility, Storgage tab on "About This Mac," the R2 is not visible at all
In the detailed system report, the R2 appears in the Thunderbolt portion. I have attached a screenshot of that report.
The Promise kernel extension currently only supports the x86_64 system architecture and not the new arm64 architecture. Here's to hoping Promise will update the kext to support it for these "legacy" disk arrays, or at the very least the kexts for the Pegasus3 series is backwards compatible with Pegasus2.
Additionally, since the Developer Transition Kit (DTK) Mac minis that were available last summer did not sport Thunderbolt I/O it would have made 3rd party support more difficult to test, I presume. Although, other Thunderbolt manufacturers are seeing day-one compatibility, but that's most likely due to them relying on the standard Thunderbolt interface protocols and not a custom kext like Promise.
Hi Stephen and Derek,
Promise is in the process of doing Big Sur compatibility testing with the Sanlink and Pegasus line.
The question of compatibility with the M1 line of Macs has been raised and Promise is looking into it. I don't know if the M1's x86_64 compatibility layer will support a driver, but it might be possible to manually load the kext with kextload. This is speculation as I do not yet have an M1 mac to test against, but it's worth a try.
Hi Stephen and Derek,
Promise is in the process of doing Big Sur compatibility testing with the Sanlink and Pegasus line.
The question of compatibility with the M1 line of Macs has been raised and Promise is looking into it. I don't know if the M1's x86_64 compatibility layer will support a driver, but it might be possible to manually load the kext with kextload. This is speculation as I do not yet have an M1 mac to test against, but it's worth a try.
Hi,
I've tried manually loading it with kextload and the result is:
Executing: /usr/bin/kmutil load -p /System/Library/Extensions/PromiseSTEX.kext
Incompatible architecture: Binary is for x86_64, but needed arch arm64e
Incompatible architecture: Binary is for x86_64, but needed arch arm64e
Hi,
Any updates on this?
I've come across this issue with my R4 and MacMini (M1, 2020). All of my photos and music are inaccessible now.
Thanks
A
Hi Stephen and Derek,
Promise is in the process of doing Big Sur compatibility testing with the Sanlink and Pegasus line.
The question of compatibility with the M1 line of Macs has been raised and Promise is looking into it. I don't know if the M1's x86_64 compatibility layer will support a driver, but it might be possible to manually load the kext with kextload. This is speculation as I do not yet have an M1 mac to test against, but it's worth a try.
I would be interested in the solution to this - having the exact same issue.
I have just discovered that the M1 Pegasus driver (v6.2.16) is now available for download on the Promise support page.
Or you can download it from this link...
Please read the install guide. Big Sur has security features that must be modified.
----
Enable System Extensions
M1 Mac running macOS 11 or later requires a one-time change to the Boot Policy before you install
the Promise Pegasus Driver. Follow the instruction in this section if the Boot Policy setting has not
yet been changed. First check to see if the Boot Policy needs to be changed
I have just discovered that the M1 Pegasus driver (v6.2.16) is now available for download on the Promise support page.
Or you can download it from this link...
Please read the install guide. Big Sur has security features that must be modified.
----
Enable System Extensions
M1 Mac running macOS 11 or later requires a one-time change to the Boot Policy before you install
the Promise Pegasus Driver. Follow the instruction in this section if the Boot Policy setting has not
yet been changed. First check to see if the Boot Policy needs to be changed
Ok this does work on my macbook pro M1 "sort of". its buggy, speed isn't as good as when pluged into an intel mac or windows PC with thunderbolt.
And for me my pegasus 2 R4 didnt' like being plugged directly into the macbook pros usb 4 ports what I had to do was plug it into my thunderbolt Caldigit TB3 plus dock to get the speed and stability back.
So it does work the driver no question but it's definitely a rushed job and requires some big fixes for sure.
Ok this does work on my macbook pro M1 "sort of". its buggy, speed isn't as good as when pluged into an intel mac or windows PC with thunderbolt.
And for me my pegasus 2 R4 didnt' like being plugged directly into the macbook pros usb 4 ports what I had to do was plug it into my thunderbolt Caldigit TB3 plus dock to get the speed and stability back.
So it does work the driver no question but it's definitely a rushed job and requires some big fixes for sure.
Check out this screenshot. Which shows an endless display of alerts from macOS saying (translated): "Safely remove "Promise RAID before disconnecting or turning off".
I tried your suggestion @Paul Kerry with connecting via a Thunderbolt Dock (I have a TB3 Dock from OWC). But I have the same problem there as I have when connecting directly to the iMac.
Speed it not a problem, I get about 400 MB both read and write. My only problem is the constant disconnects, it's unusable. ðŸ˜
PS: Forum admins, uploading a screenshot didn't work. So I had to link to Imgur.
