Mac OS 10.5.8 SNDX 4.0.5x Mac Pro
Okay still don't have exact specs for the unity but last night had a major crash and could not get the fibre manager to launch without an error. Something about medianet not installed properly. This is the same issue we had earlier in the week when we reloaded medianet to 5.1.3 and hit the atto celerity driver to _343. Then after restarting the unity and power cycling the vixel switches we were able to relaunch fibre manager and log in. Well last night this was a not go no matter what we did. Ultimately we switched to another system and pushed on.
In the process of trouble shooting I watched someone start in safe mode, zap pram and ultimately run apple jack but nothing worked. So after all that the internal raided drives for media disappeared and would not mount. After our crash earlier in the week all the unity media had been backed up to this internal raid consisting of 2 drives. In disk utility the disks appear as 1.4 TB ST31500341AS Media and underneath it says raid slice. Clicking on the slice icon show 1.4TB-Raid Slice in the info. So the internal raid is gone to us for now.
Here's the really weird part. Through trial and error, heavy on the error, I've found that if both the messed up internal raid drives are installed fibre manager won't launch with the previously mentioned error. If I take either drive out fibre manage is fine. I tried reordering them and skipping slots but any time the two are installed no fibre manager. These aren't the startup disk at all WTF? I even added and extra drive of my own to see if it could be a power supply draw issue but the extra drive mounted but any time I put the raid drive both in no fibre manager. This follows to another computer as well in the other tub same exact behavior so it's not anything but the two messed up raid drives causing the problem.
Does anyone have an explanation why a messed up raid set disrupts fibre manager? Also are there any disk utilities that work with software raid sets from a mac. Earlier in the week when we had problems the raid drives were moved to another tub and they showed up. Obviously something is wrong in raid land. I figure we can just reformat them and create a new raid set but I like to learn something here if anyone has some ideas or suggestions I'm all ears and thumbs after last night. It's not like the show has to air in a few days.. Oh wait it does Crap!!!!
--- In Avid-L2@yahoogroups.com, Bogdan Grigoresco <bogdan_grigorescu@...> wrote:
>
> Hi John,
>
> There is no 4.5.12 Unity.
> Latest version 4 is 4.2.4, so you may want to (double)check with your supplier.
> Closest match would be the editor version, but even then it's 4.0.5.12
>
> As for why you can output to tape but not render from multiple bays, it could be that your workspaces are protected, in which case the bandwidth taken by each writing client is literally double, whereas playing back is still only one stream.
>
> cheers,
> Bogdan Grigoresco
> Sr.Engineer, ACSR DS/Unity
> www.finale.tv
> --- On Fri, 9/9/11, John Moore <bigfish@...> wrote:
>
> From: John Moore <bigfish@...>
> Subject: [Avid-L2] Avid Unity 4.5.12 ish DNX 220?
> To: "Avid L2" <Avid-L2@yahoogroups.com>
> Date: Friday, September 9, 2011, 3:53 PM
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Â
>
>
>
>
>
>
>
>
>
> I've been working on an older unity version 4.5.12 ish so I'm told. We just did several projects and DNX220X and had some issues with some of the clients dropping out and losing server contact. I was able to output to HDCamSR with no stalls to speak of. I'm now on an DNX220 project and when I try to render in multiple bays they all seem to go belly up after a few safe color limit renders. The symphony keeps on chugging without issue when the mc soft stations choke. We've rebooted the unity and power cycled the vixel switches. I'm told by the AE that for DNX220X Avid says this unit can only support 1 client. Clearly we've been pushing the system but how come I can output to tape without a hitch but can't have multiple bays rendering. Am I wrong to think that with rendering the system could just delay the render process until the data comes down the pipe if there is a bottleneck caused by inadequate bandwidth on the system.  I
> remember in
>
> the past the Avid didn't like importing from a slow source and would often require moving the source to the avid's desktop to get it to import. Is rendering like this too. I know we're pushing the system but for renders I don't understand why something I would think can take its' time would cause unity client issues and stalled and incomplete renders especially when I can digital cut without a hitch. Perhaps I've just been lucky on my outputs so far.
>
>
>
> John Moore
>
>
>
> Barking Trout Productions
>
>
>
> Studio City, CA
>
>
>
> bigfish@...
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
If you want to donate to Red Cross quake relief, you can do so through your cell phone. Text redcross to 90999 to make a $10 donation. It will be on your next cell bill.
No comments:
Post a Comment