Pegasus3 R4 on Big Sur

  • 280 Views
  • Last Post 3 weeks ago
Marcus Adriansson posted this 4 weeks ago

Hello!

First: I am aware that I have installed beta software and I will have to blame myself for getting a beta experience from that :)

But with that said... I installed the latest macOS Big Sur developer beta version (20A5364e) yesterday (since I am a developer of apps) and my Promise R4 wont mount anymore. Its present in system information (see screenshot) but not in disc utilities. Anyone else have this problem and is there a solution? I re-installed drivers and the "Promise utility-app" but no luck.

Thank you! :)

Best,
Marcus

Attached Files

Order By: Standard | Latest | Votes
Robert Bousfield posted this 4 weeks ago

Same behaviour here with a Pegasus2 R4 unit. It was working in previous beta versions so something has changed in the last release.

 

I downloaded the last R_MacDrv_V6.2.9 driver from the support page and after the installer finished the drive mounted. At this point I force Quit the installer as restarting reverts to the missing volume behaviour.

 

While it is mounted the Promise Utility also works as expected.

 

 

Rob

  • Liked by
  • Marcus Adriansson
Marcus Adriansson posted this 4 weeks ago

Well look at that, it worked :) Thank you Rob!

Excited to see if it will get fixed in future versions of macOS or if Promise will release a driver update.

Robert Bousfield posted this 4 weeks ago

Well look at that, it worked :) Thank you Rob!

 

Glad it helped :) Yes, hope this is fixed by Apple in the next release. I did file a Feedback Ticket to make them aware.

Eduardo Araquel posted this 3 weeks ago

I downloaded the last R_MacDrv_V6.2.9 driver from the support page and after the installer finished the drive mounted. At this point I force Quit the installer as restarting reverts to the missing volume behaviour.

While it is mounted the Promise Utility also works as expected.

 

I attempted this but after the install completes and I force quit the installer, the drives do not mount. Is there some other trick I'm missing here?

 

Ed

Pieter Pretorius posted this 3 weeks ago

Hi,

I cannot find this driver on the support page. Is a link possible?

 

Edit: I found the driver, did what you said, and it worked!!!!!!!!!!

 

Pieter.

Marcus Adriansson posted this 3 weeks ago

I downloaded the last R_MacDrv_V6.2.9 driver from the support page and after the installer finished the drive mounted. At this point I force Quit the installer as restarting reverts to the missing volume behaviour.

While it is mounted the Promise Utility also works as expected.

I attempted this but after the install completes and I force quit the installer, the drives do not mount. Is there some other trick I'm missing here?

Ed

Hey Ed! No other "tricks" required, I ran the installer and when it was done I just force quit it instead of restarting my mac. Seems to be working for most ppl.

Best,
Marcus

Katsu Takenaka posted this 3 weeks ago

Download and install the latest driver (PromiseSTEX) which wil be gone after you reboot Mac. So, in Terminal, execute this;

sudo kextload /System/Library/Extensions/PromiseSTEX.kext

Everytime you reboot Mac, you shoud do this. So, I have made small application by Automator and put it in login items. This is the same situation as that NAS fails to mount up through SMB.

Marcus Adriansson posted this 3 weeks ago

Download and install the latest driver (PromiseSTEX) which wil be gone after you reboot Mac. So, in Terminal, execute this;

sudo kextload /System/Library/Extensions/PromiseSTEX.kext

Everytime you reboot Mac, you shoud do this. So, I have made small application by Automator and put it in login items. This is the same situation as that NAS fails to mount up through SMB.

 

Smart man! Worked nicely :) Thank you!

Best,
Marcus

Eduardo Araquel posted this 3 weeks ago

Unfortunately I get the following error when I run this line in Terminal...

Executing: /usr/bin/kmutil load -p /System/Library/Extensions/PromiseSTEX.kext

Error: Error Domain=KMErrorDomain Code=1 "Error occurred while building cache: 

1: One or more binaries has an error which prevented linking.  See other errors.

2: Could not use 'com.promise.r2p.icon' because: Cannot find symbol for metaclass pointed to by '__ZN13Pegasus2R2USB10superClassE'.  Expected symbol '__ZN28IOSCSIPeripheralDeviceType0010gMetaClassE' to be defined in another kext

com.promise.r2p.icon specific: 

1: Cannot find symbol for metaclass pointed to by '__ZN13Pegasus2R2USB10superClassE'.  Expected symbol '__ZN28IOSCSIPeripheralDeviceType0010gMetaClassE' to be defined in another kext

" UserInfo={NSLocalizedDescription=Error occurred while building cache: 

1: One or more binaries has an error which prevented linking.  See other errors.

2: Could not use 'com.promise.r2p.icon' because: Cannot find symbol for metaclass pointed to by '__ZN13Pegasus2R2USB10superClassE'.  Expected symbol '__ZN28IOSCSIPeripheralDeviceType0010gMetaClassE' to be defined in another kext

com.promise.r2p.icon specific: 

1: Cannot find symbol for metaclass pointed to by '__ZN13Pegasus2R2USB10superClassE'.  Expected symbol '__ZN28IOSCSIPeripheralDeviceType0010gMetaClassE' to be defined in another kext

}

Looks like it doesn't like the com.promise.r2p.icon extension that is installed on my system.

 

Close