Well I was told this morning they optimized the Unity last night. When I booted up there was a 20 minute scan and index of one of my media workspaces and then things worked fine but I haven't done any captures today. Then I had to quit out of Avid to mount a graphics server and reimport some stuff from it. After restarting with the graphics server mounted I reimported about 6 graphics to a different workspace and after importing Avid hung rebuilding the database for the original workspace it rebuilt first thing this morning. I've come to find from the AE the unity is still optimizing and he tried to stop it but couldn't. My limited understanding of optimizing is all users should be off the system. I'm thinking this is explaining the rebuilding of the workspace a second time. I'm thinking it's not a good idea to be working with Unity optimizing. Am I correct?
--- In Avid-L2@yahoogroups.com, "johnrobmoore" wrote:
>
> I didn't realize that unity was qualified for any V6 Avid. I've had issues on a medianet running fibre to a mac os 10.6.8 where I had to back rev from V6 to V5.5 in order to access media. I could get to projects but the media was just erroring out. Changing nothing but a back Rev to 5.5.3 and the media was accessable on the Unity. How come that one acted weird. Hmmmmmmm?
>
> --- In Avid-L2@yahoogroups.com, "jeffsengpiehl" wrote:
> >
> > V6 is qualified and supported for that version of Unity.
> >
> > Sounds like you have an odd amount of drives in an allocation group containing mirrored workspaces. Mirrored workspaces MUST be in groups containing an even amount of drives.
> > If that's the case, then your Unity is full, and you need to even the allocation group out.
> >
> > JDS
> >
> > --- In Avid-L2@yahoogroups.com, John Moore wrote:
> > >
> > > Today I found I couldn't capture anything longer than 8:15 at DNX 220 or approx 12:15 at DNX 145 on our fibre attached Unity. SNDX 6.0.3.2 Mac OS 10.7.4 and fibre manager V 5.5.1. The error I get is File 'Volumes/i80//Avid MediaFiles/MXF/zNITRIS02.1/Creating/Creating18' not found. Earlier in the day I got a similar prompt when importing to a different workspace on a different project and it turned out the workspace was almost full. In the current case there is over 100 gigs of free space in the two different workspaces I've tried. Even trying to capy a 9 gig mxf file at the finder level with a workspace with 150 gigs free errors out at about 3 plus gigs into the transfer. I'm told by the AE something happened and an allocation group renamed itself as a name identical or maybe similar to another allocation group and perhaps this is the culprit. They want to optimize the system but we are slammed right now. Just curious what the Unity
> > > gurus think and can suggest. I do realize V6 isn't qualified/supported for this older Unity but it has been working for them for quite a while without significant issues. Is this the kind of whacky behavior that might be expected when a Unity hasn't been optimized in a while. Needless to say there is no onsite maintenance crew. TIA
> > >
> > > John Moore
> > >
> > > Barking Trout Productions
> > >
> > > Studio City, CA
> > >
> > > bigfish@
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (4) |
No comments:
Post a Comment