OS X says R6 not properly ejected after waking from sleep

  • Last Post 18 March 2019
John Rhee posted this 06 March 2019

Just picked up the new Pegasus3 R6 and have it connected to my 2018 Macbook Pro 15". One thing that I noticed is that when I wake my computer up from sleep, it keeps giving me this error message saying that the r6 wasn't ejected properly. However when I close out that error message, the R6 icon is still there on my desktop. Is this a bug or is this something that I shuld be oncerned about?



Order By: Standard | Latest | Votes
arunkumar b posted this 07 March 2019

Hi John,

Please switch the Thunderbolt ports at Pegasus and computer.Also try with another Thunderbolt cable to see if it helps.

If the problem persist,please open support case at https://support.promise.com and attach the service report for further Investigation

Steps to save the subsystem report :

1) Open Promise Utility.

2) Click subsystem information icon on the top of the window.

3) Click the lock symbol on the left bottom corner of the screen to unlock the utility.

4) Click on save service report button to save the subsystem report and attach it to this case.





John Rhee posted this 18 March 2019

Thanks Arun. It seems to be an intermittent problem. For awhile it was fine, although I don't think my computer was really sleeping during those moments. ANyway I'm actually using an active thunderbolt 3 cable (Caldigit) to connect the unit to my 2018 Macbook pro. I'm wondering if that could be it? Anyway the disconnect and reconnect happened to me again today. This time my only observation was that after the screensaver, my monitor went black for a moment (sleep mode). I immediately reawoke it and saw that the OS X warning poped up but I don't think it really effected the unit since it was still present on the desktop after clearing. The only warning that I see from the Promise Utility is this:

0      Ctrl 1         Warning     Mar 18, 2019 11:30:18         0x0004004A          000000000000000000 0000000000000000 0000000000000000 00000000000000   Last shutdown is abnormal      

Anyway I'll keep an eye on it some more.