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

Jeff Kilgroe said:
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.
Click to expand...

Correct, it wakes up, LEDS show it's spinning up and checking each drive, then it powers off. This didn't happen on 10.9.x.

It's a clean install on my Mac Pros. It's odd behavior for sure.
 
Jeff Kilgroe said:
Also only in regards to Yosemite, worked fine with 10.9.x
Click to expand...

Not in my experience, at least regarding a Pegasus J4, that worked adorably for 1 year, right before installing Maverick. Then, the drive started hanging pretty frequently, requiring force quit of FCPX and J4.

BTW, Jeff, I offer (seriously) you a night with family in my house in S.Vito di Cadore or in Camogli, if/when you plan holidays in Europe, if you tell me what you would do:

I run multiple single enclosures and start to hating them when busy with different jobs.
I'm kind of between beeing single cameraman and small studio, today on a MBP, tomorrow probably on the retina imac. I'm mostly a shooter, but sometimes I have multiple edits where I can't really wait or have unreliable hardware to begin with. At the same time I can't really justify multiple big arrays, LTOs, etc..
So, here's the question:

-Better an Areca with 8 4TB WD SE (They are in the ARECA compatible list) in RAID 6 and actual older drive enclosures for backing up here and there at least most of the original media
OR
-Mirroring a couple of 4 bays in RAID 0 (a faster one like OWC thunderbolt IV with WD RE and a cheaper one like OWC or Inxtron e-sata/usb3 with WD SE or WD Black), mirroring right after an edit session with time machine not to bottleneck the faster RAID of the 2 when working and having the same actual single drive enclosures for backing up most of original media)?

Thanks!

Alvise
 
Waking an old thread up cause I am facing similar issues as Jeff mentioned. Problem is I am facing this issue across 10.10.1 through 10.10.3 as well.

Any feedback Jeff or anyone else have any ideas on how to make these issues go away? Promise support is also not sure.

My box randomly hangs/suspends itself when being copied to including random ejects. I've also noticed that it doesn't like other drives connected to the Mac Pro - 12 core cylinder and will almost always crash when copying to or from it to a USB DRIVE. All cable swaps, different workstations everything tested. Problem still persists and is erratic.
 
Mithun DSouza said:
Waking an old thread up cause I am facing similar issues as Jeff mentioned. Problem is I am facing this issue across 10.10.1 through 10.10.3 as well.

Any feedback Jeff or anyone else have any ideas on how to make these issues go away? Promise support is also not sure.

My box randomly hangs/suspends itself when being copied to including random ejects. I've also noticed that it doesn't like other drives connected to the Mac Pro - 12 core cylinder and will almost always crash when copying to or from it to a USB DRIVE. All cable swaps, different workstations everything tested. Problem still persists and is erratic.
Click to expand...
I run 24 Terabytes of promise t2 on a trashcan 8 core 10.10.3. I had some problems when connecting some other thunderbolt and usb things(even removed things like protools dongles), so basically disconnected everything then it started to work after a couple of reboots. I did so many things it's hard for me to know which thing fixed it. My bigger 12 core server is still 10.9.5 mainly since nuke 9 hasn't supported 10.10 yet, so thanks for the warning ... i won't upgrade to 10.10.3 till i get a all clear .


[edit ... also one weird thing i noticed, is if i was using a red thunderbolt cinema display, it was creating some weird problem if i used the display as a usb hub, so another thing i did is directly connect my "gamer" keyboard & mouse into the mac pro directly. I also disconnected the red r3d docking station when ever it's not in use and don't boot with it in a off state. ]
 
Last edited:
PatrickFaith said:
I run 24 Terabytes of promise t2 on a trashcan 8 core 10.10.3. I had some problems when connecting some other thunderbolt and usb things(even removed things like protools dongles), so basically disconnected everything then it started to work after a couple of reboots. I did so many things it's hard for me to know which thing fixed it. My bigger 12 core server is still 10.9.5 mainly since nuke 9 hasn't supported 10.10 yet, so thanks for the warning ... i won't upgrade to 10.10.3 till i get a all clear .
Click to expand...

Are you still facing problems with the 6-core? Or is everything sorted now?
I have a friend here locally who's running a similar R8 on his rig with a 12-core cylinder and isnt facing any issues at all.
Seems to be way too random to figure it out.

Problem is, if its a bad thunderbolt plug or something, then every single time I connect to a new plug on any box, the failed plug can make those new thunderbolt plugs fail as well and replicate the problem.
I am totally lost about this one cause never before have i faced such erratic issues.
Any and all feedback welcome.
 
Mithun DSouza said:
Are you still facing problems with the 6-core? Or is everything sorted now?
I have a friend here locally who's running a similar R8 on his rig with a 12-core cylinder and isnt facing any issues at all.
Seems to be way too random to figure it out.

Problem is, if its a bad thunderbolt plug or something, then every single time I connect to a new plug on any box, the failed plug can make those new thunderbolt plugs fail as well and replicate the problem.
I am totally lost about this one cause never before have i faced such erratic issues.
Any and all feedback welcome.
Click to expand...
No major issues now on one mac pro that is 10.10, aside from a Protools issue where the promise drive is unusable due to how how promise drive is default formatted. Maya and houdini are running fine to 10.10 promise drives though. But I still can't move my 2nd nMP to 10.10 due to the foundry not supporting that yet(my 2nd nMP has 100 Terabytes of T2 promise drives and is my primary file server, ). I view 10.10 as major operating system version change from 10.9 (like moving from windows 7 to windows 8), apple's versioning method isn't obvious when they do massive things that can effect vendors under the OS hood.
 
You must log in or register to reply here.
Back
Top