Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Yosemite Kills my Pegasus Raids

Mark Andersen

Mark Andersen

Well-known member
Joined
Feb 12, 2008
Messages
1,483
Reaction score
4
Points
38
Age
63
Location
USA
Website
www.rubberball.com
So the moment I "upgraded" to Yosemite both my Pegasus Thunderbolt raids vanished. I mean the boxes are still here (he he) but they are dark and not responding. Has anyone else had this issue? I know there are lots of smart Mac guys on this forum. Probably too smart to Jump into Yosemite so soon.
 
Mark, I have a Pegasus R6 12TB, and I happened to update it before the Yosemite upgrade. I didn't even realize this could've been a problem, but luckily I can tell you with the updated software and firmware, it works like a charm.

Do you have another non-Yosemite system you can use to update the Pegasus?
 
didn't have any problems with Yosemite and any of my Promise Pegasus raids. Working well across the board. All the R6 's (TB-1) and the R8's (TB-2)
 
Mark Andersen said:
Unfortunately my Mac Pro was the last to get Yosemite, I don't personally have TB machine that isn't Yosemite now.
Click to expand...

Maybe just updating your Pegasus Utility software will fix it. If not, give Pegasus support a call; there are probably some Terminal options they can walk you through to get the thing to show up, and then from there you can update the firmware and should be good to go.
 
Mark Andersen said:
So the moment I "upgraded" to Yosemite both my Pegasus Thunderbolt raids vanished. I mean the boxes are still here (he he) but they are dark and not responding. Has anyone else had this issue? I know there are lots of smart Mac guys on this forum. Probably too smart to Jump into Yosemite so soon.
Click to expand...

Try hitting the Power button to turn them back on. Worked for me, and no issues at all.
 
Mark Andersen said:
So the moment I "upgraded" to Yosemite both my Pegasus Thunderbolt raids vanished. I mean the boxes are still here (he he) but they are dark and not responding. Has anyone else had this issue? I know there are lots of smart Mac guys on this forum. Probably too smart to Jump into Yosemite so soon.
Click to expand...

Promise is on it. Not sure how long it will take to fix. Also not sure why we're in this situation to begin with because this has been an issue with Yosemite since the earlier betas. But many companies don't seem to actually address or fix such issues until the final version of the OS actually ships. They did release a new version of the Promise Utility and firmware for the Pegasus2 (possibly the Pegasus1) recently. This fixes the shut-off problem, but I occasionally have the Pegasus2 un-mount for no apparent reason and then pop back up on the desktop after a few seconds. Seems to only do it after the system first powers on or wakes from sleep and then once it comes back, it's fine. I think this all has something to do with how OS X Yosemite manages power states for storage. I think a temporary work-around is to manually configure your RAID to never sleep, but I have not tried it myself. I'm spending a lot of time in Yosemite for some of my app development and testing I'm doing lately, but it's new and quirky. If I don't need Yosemite, I boot into 10.9.5.
 
Umm, that worked! (Hitting the power button) I feel a little dumb for not trying it, but in my dark office I actually couldn't see the buttons where the raids are positioned. Funny thing is the guy at Tech support at Promise was surprised that the raids booted up because he believed that they wouldn't work until new drivers were released. It seems that nobody is quite sure what is going on but mine are working again so that's good.
 
Be careful if yours is a Pegasus2, they intermittently unmount (eject) themselves on Mavericks.
 
My brain had a premature posting... Not Mavericks. I meant to say on Yosemite. OS X 10.10. Premature, uh, ejection. First I thought I had a bad TB cable, but the issue started with installing Yosemite, only does it in Yosemite, does it on two systems with two different RAIDs and all the cables I've tried. I know a few others with the same issue. Promise was able to confirm and say they saw the problem and are looking into it yesterday, after months of reporting/ asking, they wouldn't deal with it before because Yosemite was not officially released.
 
Jeff Kilgroe said:
My brain had a premature posting... Not Mavericks. I meant to say on Yosemite. OS X 10.10. Premature, uh, ejection. First I thought I had a bad TB cable, but the issue started with installing Yosemite, only does it in Yosemite, does it on two systems with two different RAIDs and all the cables I've tried. I know a few others with the same issue. Promise was able to confirm and say they saw the problem and are looking into it yesterday, after months of reporting/ asking, they wouldn't deal with it before because Yosemite was not officially released.
Click to expand...

Tech support walked me through a firmware update, which is supposed to help. In the process I was told to uncheck the "put HDs to sleep whenever possible" box in energy saver preferences. The new firmware is supposed to only shut down the raids when the Mac is shut down.
 
Mark Andersen said:
Tech support walked me through a firmware update, which is supposed to help. In the process I was told to uncheck the "put HDs to sleep whenever possible" box in energy saver preferences. The new firmware is supposed to only shut down the raids when the Mac is shut down.
Click to expand...

You have to uncheck that box whenever you're running any external RAID. Period. Does not solve the current issue of the un-mounting, though. It doesn't shut down the RAID or anything like that, the drive will just suddenly disappear from finder and you'll get a message about it not being properly ejected. It usually will re-mount and come back online on its own after 20 to 60 seconds. Seems to happen to me only once, maybe twice in a day. It is an issue with Yosemite and the Pegasus2. Operation under 10.9.x is fine.

And while whatever the issue is only occurs under Yosemite, I don't think it's specifically an Apple problem. The Areca RAID and my CalDigit TB units all seem to be operating just fine. :/

Antony Newman said:
Glad I went Areca.

Dont think I'd ever switch unless they Promise to test OS' in public beta.

AJ
Click to expand...


I'll bet you a pint that Areca doesn't test, nor specifically address such issues, for OS's in beta status. It's not uncommon for new OS releases to be incompatible with various Areca RAID cards when they first release, even after lengthy betas. In this situation of Thunderbolt storage though, there are no specific drivers. This situation is a bit odd. But the latest firmware does fix all but the occasional unexplained eject. Previous firmware would not properly power-on with the system, nor consistently wake when it should. Also only in regards to Yosemite, worked fine with 10.9.x
 
Jeff, I had to notify ARECA about MRAID not installing under 10.10. They've since patched the installer to work.

However I've noticed on my mac (powernap is disabled) that the mac will sometimes wake up the RAID, which will spin up, then power back down a minute later, maybe every 45 minutes. Any thoughts on what's causing this? Have you seen this under 10.10?
 
I think I'm starting to see some other glitches on 10.10 and everything seems to come back to power management and states with the storage subsystem layer in OSX. I've pretty well ironed out the disconnect issue and it seems to be eliminated by just not allowing the system to sleep. Most of the disconnects seem to happen when the system wakes up and even though I'm using the system, the RAID isn't used and then it will eject itself after a few minutes, but not sleep or power down. It usually comes back online on its own after a few moments. I'm seeing a few other things like when I have more than one RAID in a sleep or low power state and I go to access one thing, it wakes up everything. If you have Time Machine doing backups or something, even if it isn't accessing your RAID, it will wake it up with the call to wake whatever storage it might need. Like an all or nothing approach in this release. That could be causing it.

10.10 is nice and I like a lot of what they have done, but like many initial releases there are a few glitches. I wouldn't jump into using this on a critical system just yet. With the exception of 10.9.3, it seems that the .3 point releases are where most OS X versions tend to get good. Apple had to move swiftly to 10.9.4 because 10.9.3 was a big oops. Hopefully we'll see 10.10.1 soon and it's only been a week since 10.10 went gold anyway.
 
I've got a MacProCyliner that's been running 10.10 for a week now. With the Pegasus R8 boxes (Thunderbolt-2) - no problems (other than the wait for everything to spin up) when accessing that particular raid or if the systems been asleep -->> BUT the older Pegasus R6 boxes (which are all Thunderbolt-1) have disconnected and reconnected a few times. Also the Promise Pegasus SSD J4 - will also cycle occasionally...
 
Isaac Marchionna said:
So you think it's time machine that's causing the issue with the random drive spin ups while asleep? I may just want to do hard shut downs overnight.
Click to expand...

Oh, so the RAID wakes up while the system and everything else is asleep? Then after a minute or so it goes back to sleep? If that's the case, I've seen that too, but not since 10.9 thru 10.9.2 as pretty much all the TB RAIDs, regardless of manufacturer, were doing that. Now I'd be curious to know if everyone is running on upgrades to 10.10 or running clean installs? I have mine clean-installed on a fresh partition.
 
You must log in or register to reply here.
Back
Top