Pegasus2 R4 - DISK NOT EJECTED PROPERLY Issue with macOS 11.3

  • 3.4K Views
  • Last Post 19 May 2022
Robert Bousfield posted this 29 April 2021

Mac Pro 2013 / macOS Big Sur 11.3 / Promise Pegasus2 R4

 

After upgrading to macOS Big Sur 11.3 I am notified that the two volumes on my Promise RAID are disconnected when my Mac wakes from sleep.

 

 

Console log shows the Mac thinks the cable has been disconnected - it hasn't and same cable was working fine with macOS 11.2.3

 

default    19:51:20.253087+0100    kernel    STEX : Thunderbolt cable disconnected while wake up

 

I also tried a new Thunderbolt 2 cable - same issue.

 

Anyone else seeing this behaviour?

 

Thanks.

 

 

 

Update - 29th Oct 2021

I  raised a support ticket when I became aware of this issue (Case #20210511022143S,  in case anyone wants to reference it in any communication with Promise) but sadly seem to be getting nowhere with Promise Support about this.

The last response gave the impression that they had not read and understood the original reason for the ticket and many updates added with each macOS system update that did not fix the issue from Apple's side.

They even suggested that I remove the Promise Driver - something that is not possible as the driver is supplied by Apple and resides on a sealed (read only) System Volume on Big Sur and Monterey.

I think I am getting to the point of retiring this unit which is a real shame as it has performed flawlessly till this issue came about as a result of some change Apple made with the 11.3 update.

 

 

  • Liked by
  • Ricardo Mejia
  • Jay Dude
Order By: Standard | Latest | Votes
Jan Vercammen posted this 01 May 2021

Dear Robert,

I too see this kind of behaviour on my Mac Pro late 2013 with Pegasus2 R4 after Big Sur 11.3. 

  • Put Mac to sleep
  • After a while the R4 turns off
  • Shortly later R4 turns back on - does something ??? - then turns back off  (did not happen before 11.3)
  • Wake up with spacebar

Resulting in 2 of those messages.

Kind regards,
Jan

 

Felix Sorger posted this 01 May 2021

Hi Robert and Jan,

I am having the exact same problem and same behaviour as described by Robert. It actually really disconnets because FCPX exits because it cannot (could not) read/access the open Library anymore.

Kind regards,

Felix

 

 

Latest Software Promise Utility and Firmware

Pegasus2 R4

Big Sur 11.3, Mac Mini 2018, 3.2 i7, 32GB RAM with EGPU BM Radeon Pro 580

Robert Bousfield posted this 04 May 2021

Hi Jan/Felix,

Many thanks for taking the time to also report you are also seeing the same behaviour.

I have raised a support ticket with Apple about this.

The problem is still present in the macOS 11.3.1 update released last night  - which I understand was a primarily a security patch so I did not expect any change in this behaviour but one always hopes 😉

Best,

Rob

William Wood posted this 06 May 2021

Same problem here...

Mac Pro late 2013 with Pegasus2 R4 after Big Sur 11.3 and with 11.3.1.

Rick WS posted this 10 May 2021

Yep... Same here.. anyone has a fix yet?
iMac 5k late 2014 with Big Sur 11.3.1 and Pegasus2 R4 (Which I absolutely both love to this day..great purchases)



Keith Diefendorff posted this 11 May 2021

Mac Pro 2013 / macOS Big Sur 11.3 / Promise Pegasus2 R4

 

After upgrading to macOS Big Sur 11.3 I am notified that the two volumes on my Promise RAID are disconnected when my Mac wakes from sleep.

 

 

Console log shows the Mac thinks the cable has been disconnected - it hasn't and same cable was working fine with macOS 11.2.3

 

default    19:51:20.253087+0100    kernel    STEX : Thunderbolt cable disconnected while wake up

 

I also tried a new Thunderbolt 2 cable - same issue.

 

Anyone else seeing this behaviour?

 

Thanks.

 

 

 

 

 

Keith Diefendorff posted this 11 May 2021

Same problem for me on 11.3.1.

Rick WS posted this 12 May 2021

Yeah.. tried thunderbolt cable too..that's what Promise told me to try with earlier issues with Pegasus not sleeping very quietly.. it can wake up sometimes and run for a while.. or a long while sometimes.. and goes back to sleep while my iMac is sleeping. 

New issue that I've noticed yesterday is that now my Promise won't show in the 'favourites' list of my Finder anymore. 
I assume this is a consequence of it being noticed as 'unsafely removed'...

Still on 11.3.1 and iMac 5k. 


Felix Sorger posted this 12 May 2021

For the moment, as workaround, I use a little App called Amphetamine which prevents the disk to go to sleep. No issues with that, no disconnects.

And when I am not actively using the disk for a day or so I unmount it and turn it off so it is not running for nothing.

Sean Merriam posted this 15 May 2021

Came here looking for solutions to the same problem - Mac Pro late 2013 running 11.3.1 with Final Cut. I didn't pay attention that it does only happen when the machine goes to sleep.  Never happens while using it.  Relief to feel that the array is not on it's last legs. It's been a beast for many years.

Nick Vincent posted this 16 May 2021

Same issue here with Mac Pro 2013 / macOS Big Sur 11.3.1 / Promise Pegasus2 R6 

Since the last upgrade to 11.3.1, my Pegasus is thought as disconnected from the Mac when it goes to sleep.

I didn't have this issue with the previous versions of Big Sur.

Let's hope it's sorted out soon.

Nick Vincent posted this 26 May 2021

Same issue here with Mac Pro 2013 / macOS Big Sur 11.3.1 / Promise Pegasus2 R6 

Since the last upgrade to 11.3.1, my Pegasus is thought as disconnected from the Mac when it goes to sleep.

I didn't have this issue with the previous versions of Big Sur.

Let's hope it's sorted out soon.

And for the ones wondering, the same applies to macOS 11.4 of course...

Ricardo Mejia posted this 31 May 2021

I have the same issue:

Mac Pro (Late 2013)

macOS Big Sur V 11.4

Pegasus 2 R4

 

When I awake my computer in the morning, I am finding a long list of notifications that were sent every 5 minutes since the computer went to sleep with the message "Disk not ejected properly".

 

I have to re-start the computer because the storage is not recognized.

 

I did the same  as others: change the cable, changed the thunderbolt port in both, the computer and drive. No effect. 

 

For now, the only thing that works for me is to turn the computer off every night to avoid the messages (not ideal since that is when updates happen).

 

Hopefully we'll see a solution soon.

Ricardo Mejia posted this 01 June 2021

Problem Solved!

I updated the firmware of my Pegasus 2 R4

That took care of the problem.

I hope this helps you all.

Install Promise Utility. In the top menu: Promise Utility --> Check for Updates

Nick Vincent posted this 02 June 2021

Problem Solved!

I updated the firmware of my Pegasus 2 R4

That took care of the problem.

I hope this helps you all.

Install Promise Utility. In the top menu: Promise Utility --> Check for Updates

Very happy for you! Can I ask you what version you're on? 

I have been checking for updates for my R6 and Version 4.04.0000.42 (C05) seems to be the latest for my R6.

Robert Bousfield posted this 02 June 2021


Install Promise Utility. In the top menu: Promise Utility --> Check for Updates

 

Hi Ricardo.

 

This does not work for me - no updates reported from the Utility.

 

I am current on firmware version : 5.04.0000.64 (Utility version 4.04.0000.42 (C05) )

 

What version did your update take you to?

 

Rob

Ricardo Mejia posted this 02 June 2021

Rob and Nick:

I updated to Firmware Version: 5.04.0000.64

Utility version 4.04.0000.42 (C05)    (Nick, maybe it was just a typo in your message, but just in case, this is the version of the Promise Utility, not the firmware)

 

I had to re-start the system and the Pegasus unit before any change took effect.

Also, this is how I configured the Energy Saver

 

 

  • Liked by
  • Jean Marc BARA
  • Margaux Yiu
Jean Marc BARA posted this 02 June 2021

Same issue here. Glad to see I am not alone.  Have two Pegasus2 R4 connected to Mac Pro "trash can".  Problem started with MacOS upgrade to Big Sur.  For the moment I will be using Ricardo Mejia's Energy Saver settings suggestions in the previous post.  If anyone at Apple or Promise is reading this, I hope that this "Disk not ejected properly" issue will be fixed so as to be able to give hard drives a rest when computer is not in use, without having to Shut Down.

Jean-Marc

Robert Bousfield posted this 03 June 2021

Rob and Nick:

I updated to Firmware Version: 5.04.0000.64

Utility version 4.04.0000.42 (C05)    (Nick, maybe it was just a typo in your message, but just in case, this is the version of the Promise Utility, not the firmware)

I had to re-start the system and the Pegasus unit before any change took effect.

Also, this is how I configured the Energy Saver

 

Thanks for confirming those versions Ricardo.

 

I had had already disabled the Mac from sleeping as a workaround for the issue.

 

Since my machine is not a server this is not ideal, and as Jean commented it would be good to have a real fix to restore the ability to sleep as expected.

 

Rob

 

 

 

 

Nick Vincent posted this 03 June 2021

Thanks Ricardo,

Yes, I'm on 4.04.0000.42 (C05) for the utility software and Firmware Version: 5.04.0000.64 for the R6.

Unfortunately, this doesn't solve anything on my side.

Best,

 

 

Ricardo Mejia posted this 03 June 2021

Ok then, back on square one :(

 

Jon Haile posted this 08 June 2021

I'm having this same problem with the Pegasus2 R6 on macOS 11.4. Also up to date with utility/firmware at 4.04.0000.42 (C05) for the utility and 5.04.0000.64 for firmware. I've tried a few combinations of settings in the Energy Saver, but no matter what if I leave the drive pugged in overnight, I come back to a sea of disconnection notcies in the morning.

Nick Vincent posted this 23 July 2021

Hi,

Has anyone tried macOS Big Sur 11.5 update? I'd like to know if this fixes our issue with our Pegasus R4/R6 drives.

Thanks,

N.

Nick Vincent posted this 26 July 2021

Hi, Anyone knows if v15 of Big Sur has our problem resolved?

Thanks!

N.

Jan Vercammen posted this 26 July 2021

Unfortunately it is not solved in 11.5 - very disappointing. 

Jan. 

Keith Diefendorff posted this 29 August 2021

When is someone going to fix this?

It is really a terribly annoying problem. Every time I get on my machine I have to spend 5 minutes individually deleting a long list of "DISK NOT EJECTED PROPERLY messages, which float on top of all other windows and cannot be ignored or bulk deleted.

I've updated to the latest Pegasus2R6 firmware, no help. The message has persisted through seveal major and minor MacOS updates, including the latest 11.5. I have no idea if it is Apple or Promise's problem, but if it's Apple's then someone at Promise should get with someone at Apple to fix it, since these are the one of the main RAID systems recommended by Apple and sold in their online-store.

--

Keith

Nick Vincent posted this 11 September 2021

I agree with you, Keith – it's a very odd bug that slipped in through 11.4 and it should get fixed by now. It's also not very promising (pun not intended) for macOS Monterey...

John Baughman posted this 20 October 2021

Mac Pro 2013 / macOS Big Sur 11.3 / Promise Pegasus2 R4

 

After upgrading to macOS Big Sur 11.3 I am notified that the two volumes on my Promise RAID are disconnected when my Mac wakes from sleep.

 

 

Console log shows the Mac thinks the cable has been disconnected - it hasn't and same cable was working fine with macOS 11.2.3

 

default    19:51:20.253087+0100    kernel    STEX : Thunderbolt cable disconnected while wake up

 

I also tried a new Thunderbolt 2 cable - same issue.

 

Anyone else seeing this behaviour?

 

Thanks.

 

 

 

 

 

John Baughman posted this 20 October 2021

Very frustrating behavior.  I can't believe this is a known problem for so long without a solution.

John

Nick Vincent posted this 24 October 2021

Has anyone tried Big Sur 11.6, just to know?...

Robert Bousfield posted this 25 October 2021

Has anyone tried Big Sur 11.6, just to know?...

 

Hi Nick - the problem is present in every macOS from version 11.3 onwards, including the one that will ship later today.

 

Arvid Eriksson posted this 28 October 2021

Hello all.

I have had this problem since April 2020 and macOS 10.13. I posted about my troubles in this thread: https://forum.promise.com/thread/pegasus2-r4-no-standby-sleep-mode-on-macos-catalina-10-15-3/

I'm now on 11.6 and the problem persists. A Promise Admin responded to my post in the other thread clarifying "this is a macOS issue".

Has anyone had any response from Apple in their support forums?

Kind regards,
Arvid

Robert Bousfield posted this 29 October 2021

Hi Arvid.

 

Sorry to hear you are also having issues but the problem you reported does not appear to be the same issue as my original post.

 

My Promise R2 has no problems going to sleep or waking with the Mac - the issue is that the volumes hosted on the unit are ejected when the Mac sleeps/wakes.



Rob

Robert Bousfield posted this 29 October 2021

Update -

I  raised a support ticket when I became aware of this issue (Case #20210511022143S,  in case anyone wants to reference it in any communication with Promise) but sadly seem to be getting nowhere with Promise Support about this.

The last response gave the impression that they had not read and understood the original reason for the ticket and many updates added with each macOS system update that did not fix the issue from Apple's side.

They even suggested that I remove the Promise Driver - something that is not possible as the driver is supplied by Apple and resides on a sealed (read only) System Volume on Big Sur and Monterey.

I think I am getting to the point of retiring this unit which is a real shame as it has performed flawlessly till this issue came about as a result of some change Apple made with the 11.3 update.


Peter P. posted this 30 October 2021

My workaround for this issue (it's really disappointing that Promise does nothing to fix it!): I've disabled energy saving mode for hard disks in the Energy panel and installed Jettison to unmount exteranl disks before going to sleep and to remount on wakeup. Originally I used this software years ago with USB disks, but with Thunderbolt drives it should not be needed. Well, it is again with Promise drives :(

Eric F posted this 08 December 2021

I have this same problem.  I was on a 2019 16" Macbook Pro, Big Sur, now I'm on a 16" M1 Max Macbook pro, Monterey.  New computer, same issue.  

Pegasus 2 R4

Promise support simply says it's an Apple issue and offers no help, other than "set to never sleep".

Margaux Yiu posted this 05 January 2022

I’ve had this issue for years with older iMac (2018?) and now same with:

MacBook Pro M1 (2020) | OS 11.6.2 (Big Sur)

Pegasus2 R4 | Firmware 5.04.0000.64

I just updated the Promise Uttility, Firmware, and OS. Still getting the error when laptop goes to sleep. Every single time.

Doesn’t look like anyone from Promise cares at all about this issue. For the past several years, the sleep error happened about once a week. With new MBP, it’s happening every sleep.

Will try not sleeping computer, but I hate that option. 

  • Liked by
  • Edward K
Edward K posted this 12 January 2022

I have the same issue and have tried new Thunderbolt cables. I have also checked the firware and ensure it's the most recent version.

I've even tried TWO different MacBook (M1 Pro and also the M1 Pro MAx)

 

Every time I get the disk eject failure.

On the latest machine, I  even did a clean install of all software in case some extension or other vestigial piece was causing an issue.

I've followed all advice to update the utilities and firmware.....Come on! Promise......??

 

John Baughman posted this 14 January 2022

Someone here recommended the Amphetamine app. it works great on my iMac. no more disconnect messages. 

  • Liked by
  • Rick WS
Rick WS posted this 31 January 2022

Thanks John, 

I will try this. Now have bought the newest M1 Max MBP and (logically) have the same issue. 
Am quite annoyed by Promise not coming up with a solution in all this time. 

I'll try the Amphetamine app, does that mean the discs will keep spinning all the time? In that case it's not a solution as I don't want them to be spinning all night long. Might as well turn the MBP off completely every time in that case. 

Thanks!

Edward K posted this 31 January 2022

I sent a (frustrated) email to tech support and got this email in response (copied below)

Although I appreciate they're trying to help, I would be more appreciative of a timeline for resolution of this situation. I don't understand given how widespead (and acknowledged this issue is) they still SELL this system without a disclaimer that it doesn't work on Apple silicon.

I'm now taking this up with Apple too...

Love product......but....

 

 

 

...............................

 

Hi Edward,

 

This is an issue that has plagued macOS users with firewire external drives, USB external drives and thunderbolt external drives from every manufacturer.

 

Google shows that there are a lot of macOS users looking for a solution to this issue…

 

·         https://www.google.com/search?q=%22drive+not+ejected+properly%22+on+wake&

 

Sometimes updating macOS fixes this and the next macOS update brings it back. In the link you posted below one forum poster says it has worked fine for 8 years till he updated to Monterey.

 

Ø  This same thing is happening to me. I was previously using a late 2013 MacPro (trashcan) with a Pegasus2 R4 8TB unit. Worked flawlessly for almost 8 years. My Trashcan is running Catalina (10.15.7). I just received my new M1 Max macbook (Monterey 12.0.1) and experienced these same ejections.

 

Unfortunately, this is a macOS issue. It is not a Pegasus issue or a Promise issue.

 

This is one solution that was said to work a few years back…

 

·         https://discussions.apple.com/thread/8218757

·         After working with several Apple Senior Advisors for more than six weeks, I am pleased to say that this issue has been solved. It was solved by removing a file (Pegasus2R2ICON.kext) from the systems library and placing it in the trash.

 

I do not know if this still works, and I’ve not been able to test it.

 

Another solution is to not let your MAC sleep. With the M1 MAC this is a very viable option. When the MAC sleeps, it powers down all external devices, including ThunderBolt drives, and apparently it wakes before external drives have time to power up, resulting in the disk not ejected properly issue.

 

There are also some utilities that may help.

 

Regards,

--R

 

John Baughman posted this 31 January 2022

Thanks John, 

I will try this. Now have bought the newest M1 Max MBP and (logically) have the same issue. 
Am quite annoyed by Promise not coming up with a solution in all this time. 

I'll try the Amphetamine app, does that mean the discs will keep spinning all the time? In that case it's not a solution as I don't want them to be spinning all night long. Might as well turn the MBP off completely every time in that case. 

Rick,

Amphetamine is a very comprehensive app with many options for customization of the timing.  You can set it to run indefinitely, for a set number of hours, or according to the clock. For example, you could set it to block disk sleep "until 10:00PM" if you don't want it running all night.  It is free and costs nothing to try it out. Very responsive developer.

I've tried to research the issue of whether or not putting spinning hard drives to sleep is useful or perhaps even harmful.  The online opinions vary. Sure you can cut down on energy use, with a rough estimate of 10- 15 dollars per year savings from each hard drive you sleep or shut down.  But a plurality of informed commenters seem to say that sleeping your drives may actually shorten their life spans.

Robert Bousfield posted this 31 January 2022

Hi Edward,

 

What a terrible response on so many levels.

 

Yes, Apple has changed something (in my case between macOS 11.2 and 11.3.x) but that does not absolve Promise from investigating this. As a prominent supplier they should have a much better contact/develop relationship with Apple about what changes were made to cause these issues and hopefully come up with a fix.


To link back to a support article that mentions removing a very old Promise component from the System Library is not at all helpful given since Catalina this area is not modifiable (which '-R' is aware of as I have seen their response in another post that points this out).


Not allowing your Mac to sleep (using Energy Saver, the Amphetamine utility) is a workaround, not a solution.


I have a Thunderbolt 3 M.2 storage device connected to my Mac and it does not give the same error on sleep/wake so it is not all Thunderbolt devices. Nor do the two USB 3 hard drives I  use for backup.


This attitude is so disappointing but I suspect that given the high price of Promise devices there are relatively few of us users out there for us to make a difference. I suspect if the same issues were happening to the more recent models it would be a different matter.


I did enquire if it was possible to purchase a Pegasus3 device with no hard drives but apparently this is not an option as Promise only sell units fully populated. I had hoped they would make an exception but sadly not :(

  • Liked by
  • Rick WS
Edward K posted this 01 February 2022

Robert Bousfield 

I spent an hour or so with Apple Tech Suport on chat and finally was given a call by a more senior agent.

They walked me through the process of troubleshooting (nothing I had not tried)

They also suggested attempting to use another Thunderbolt drive to see if the same error appeared. I had a second 4Tb SSD drive and attempted to use that - no issue when left to 'sleep' overnight.

 

So, this does indeed seem to be a Pegasus 2 issue. 

 

 

Jay Dude posted this 03 February 2022

I encountered this scary behaviour today - on a MacPro 2019 running Monterey 12.2.

Jay Dude posted this 03 February 2022

Tried this, with an error as a result:

https://kb.promise.com/search/?term=10399

 

cliib> ctrl -a mod -s "powersavinglevel=0"

 

Error (0x8030): there is not any change to the settings

Rick WS posted this 14 February 2022

Hi everyone, 

Very disappointing to read the official Promise response that Edward posted. I purchased the Pegasus2vR4 via the Apple website. It's meant to work with Apple. The fact that Promise is not interested in fixing this problem is simply a let down. 
Blaming it on Apple is cheap and doesn't do justice to the customers they sold this to. IMO.

Is this purely an Pegaus2 issue? Do we know for certain that Pegasus32-series does not have this issue? 
If so.. did anyone purchase a Pegasus32 R4 or R6 or R8 and daisy chained the Pegasus 2 R4 to it?

I'd be open to that potentially. 

I looked at the amphetamine app.. the at this time, I set the screen to always on and all the settings to never sleep. 
And just turn off the mbp alltogether after the night. 

It's now way less.. even without using the Amphetamine app. I'll keep that as a backup. As someone said.. it's a workaround. 

Basically it's just poor aftersales service of Pegasus. I understand that stuff gets old and at one point a company decides to not upgrade to new software etc..
But with this being the case..  How can we invest in new equipment from them when we don't know when and if they'll launch new products and stop upgrading the ones we just purchased..

Yeah.. not walking that line again. 

Good luck all!

Rick WS posted this 14 February 2022

I looked at the LaCie as you would be able to daisy chain that.. 
Their website reports users with the same issues as we all are having.. 
They also seem to have no proper solution, they recommend ejecting the disc before putting the device to sleep. 

https://www.lacie.com/as/en/support/kb/disk-not-ejected-properly-on-mac/

With this.. I'm absolutely not convinced that the R32 does not have these issues also.. I can't seem to find it now online..but if LaCie also experiences this..


Eric F posted this 14 February 2022

I looked at the LaCie as you would be able to daisy chain that.. 
Their website reports users with the same issues as we all are having.. 
They also seem to have no proper solution, they recommend ejecting the disc before putting the device to sleep. 

https://www.lacie.com/as/en/support/kb/disk-not-ejected-properly-on-mac/

With this.. I'm absolutely not convinced that the R32 does not have these issues also.. I can't seem to find it now online..but if LaCie also experiences this..


Just keep in mind that if you put the R2 on the end of your chain, it can slow down TB3 products in the middle.

I  suspect this sleep issue is just a firmware problem that Promise doesn't think is worth the effort to update.

I am not buying Promise products again, after this experience.  I have an OWC Thunderbay 4 RAID and don't experience ay sleep problems.  Could be because it's a softwaare raid instead of a hardware raid?  My single Lacie Rugged TB2 SSD doesn't have the sleep priblem either.

Robert Bousfield posted this 15 February 2022

I  suspect this sleep issue is just a firmware problem that Promise doesn't think is worth the effort to update.



 

I have been thinking the same thing for a while now.

 

The Promise3 unit got a firmware update last month, nothing for the Promise2 :(

Jay Dude posted this 15 February 2022

I'm suffering from this unmounting too in Monterey 12.2.

Found a kind of a workaround: 

I added a cron job that accesses the raid every hour, to keep it alive.

In my case the cron starts a shell script that puts the current time in a file on the raid.

Seems to work, although not a real solution.

Peter P. posted this 16 February 2022

I looked at the LaCie as you would be able to daisy chain that.. 
Their website reports users with the same issues as we all are having.. 
They also seem to have no proper solution, they recommend ejecting the disc before putting the device to sleep. 

https://www.lacie.com/as/en/support/kb/disk-not-ejected-properly-on-mac/

With this.. I'm absolutely not convinced that the R32 does not have these issues also.. I can't seem to find it now online..but if LaCie also experiences this..

Actually, I think that's just a boilerplate FAQ and not at all specific to our situation here. Thunderbolt drives can disconnect e.g. if one device in the daisy chain does so during sleep. Once I had repeatable issues of a LaCie drive disconnecting "randomly", until I found out that the power connector of a device further up the chain was almost-but-not-quite pulled by me re-arranging the cables several times.

However, this is abnormal behavior that (usually) indicates some other problem that needs to be fixed.

Edward K posted this 17 March 2022

To those of you looking for an answer. I can't give a solution to the problem howeber the suggestion to use "Jettison" works.

It ejects the drives whenever the mac goes to sleep (and they connect back up when you wake the Mac)

It doesn't leave me feeling super confident, but it works!

I've been using it for a few weeks now without an issue (and it's inexpensive)

Edward

  • Liked by
  • Peter P.
Rick WS posted this 21 April 2022

"I am not buying Promise products again, after this experience.  I have an OWC Thunderbay 4 RAID and don't experience ay sleep problems.  Could be because it's a softwaare raid instead of a hardware raid?  My single Lacie Rugged TB2 SSD doesn't have the sleep priblem either." 

 

Do you run the Thunderbay on an M1 Mac? I had it all installed with the pegasus, still the sleep issues..but it worked up to 2 hours ago and can't find the issue. I'm heavily dependent on the storage and this doesn't seem reliable after 3 months of being fine(ish). 
Thinking to go to the Thunderbay too..

 

Eric F posted this 21 April 2022

"I am not buying Promise products again, after this experience.  I have an OWC Thunderbay 4 RAID and don't experience ay sleep problems.  Could be because it's a softwaare raid instead of a hardware raid?  My single Lacie Rugged TB2 SSD doesn't have the sleep priblem either." 

Do you run the Thunderbay on an M1 Mac? I had it all installed with the pegasus, still the sleep issues..but it worked up to 2 hours ago and can't find the issue. I'm heavily dependent on the storage and this doesn't seem reliable after 3 months of being fine(ish). 
Thinking to go to the Thunderbay too..

Yes, the thundberbay is TB3 and works great on the M1. Just don't buy Ironwolf drives.  They have a powersaving function that puts them to sleep too often.

Rick WS posted this 19 May 2022

This issue won't be solved at all... I'm ready to purchase a newer version of the raid system. Does anyone know from experience if the Pegasus 32 series DON'T have this issue?

Promise helpdesk have been kind..but not able to provide solutions. And no reason given. Since that damages the brand..I've been looking at the Thunderbay 4 now.. Does anyone have experience with that? I'd like to daisy chain at least one monitor, but with the P2R4 that would lose me access to my monitor all the time too. 
Cannot have that!


Anyone with experience or great ideas..I'd be obliged!

Cheers, 



Mac Pro 2013 / macOS Big Sur 11.3 / Promise Pegasus2 R4

 

After upgrading to macOS Big Sur 11.3 I am notified that the two volumes on my Promise RAID are disconnected when my Mac wakes from sleep.

 

 

Console log shows the Mac thinks the cable has been disconnected - it hasn't and same cable was working fine with macOS 11.2.3

 

default    19:51:20.253087+0100    kernel    STEX : Thunderbolt cable disconnected while wake up

 

I also tried a new Thunderbolt 2 cable - same issue.

 

Anyone else seeing this behaviour?

 

Thanks.

 

 

 

Update - 29th Oct 2021

I  raised a support ticket when I became aware of this issue (Case #20210511022143S,  in case anyone wants to reference it in any communication with Promise) but sadly seem to be getting nowhere with Promise Support about this.

The last response gave the impression that they had not read and understood the original reason for the ticket and many updates added with each macOS system update that did not fix the issue from Apple's side.

They even suggested that I remove the Promise Driver - something that is not possible as the driver is supplied by Apple and resides on a sealed (read only) System Volume on Big Sur and Monterey.

I think I am getting to the point of retiring this unit which is a real shame as it has performed flawlessly till this issue came about as a result of some change Apple made with the 11.3 update.

 

 

Close