Thursday, January 16, 2020

Re: [Avid-L2] 4TB Glyph AtomRaid SSD Issue?

John,

      I have a few reactions to your post:

1)  I have no problem editing camera original files on the field-copied drives AS LONG AS THERE ARE PLENTY OF BACKUPS.  When I'm lucky enough to get camera originals recorded as DNxHD MXF OP-Atom files (so I can edit them as native Avid files, not AMA-linked), I will first make several backups (at least 2 copies of the originals).  At that point I have 3 copies, no one of which is any better or worse than any other.  So sure, I'll edit using any of those copies including the "original"; what's the difference?  And if I destroy one of the 3 copies, who cares which one is lost?  They are all identical; none is more useful than another!

2)  I have never had a problem using either SSDs or "Spinning Rust" drives in the field to copy from camera-original memory cards for transport to the editing room.  It's basically a choice between higher speed at higher cost (for SSDs) versus lower speed at lower cost (for spinning drives).  My choice is generally based on the logistics of copying on location.  If our shoot is fairly stationary (e.g. shooting interviews sitting in one room all day) then I can have cards copied continuously so slower speed copying doesn't hurt much.  If we're running & gunning so we don't get to copy our cards until after we wrap, having high-speed SSDs can save Overtime charges for whatever crew member is babysitting the copies.  

3)  I don't see how the use of TRIM for SSDs applies to this use case.  For copying camera original memory cards in the field, I always format my drives fresh before use, and then write once in the field, starting with an empty drive and continuing until it's (mostly) full.  Then after the drive gets back home to the editing room, I read many times to copy it but I don't write any more.  Given this WRITE ONCE, READ MANY pattern, TRIM never gets used.  What makes you think TRIM is your problem here?

In solidarity,
Wilson Chao

p.s. Ok, ok, I lied in 1) above.  In some cases the camera original drive is actually BETTER FOR EDITING than the copied drives if it was actually the original recording medium for a multi-stream recorder for use in multicam editing.  But that's a story for another post...


On Wed, Jan 15, 2020 at 7:15 PM John Moore <bigfish@pacbell.net> wrote:
Production was asked not to use SSD drives to deliver our master but they did on Glyph AtomRaid SSD 4TB drives.  Now with two  nights of shooting the second nite both the master and backup drive are not working or show only part of the data on them.  Needless to say this is a huge issue.

The drives only have 5 percent of free space on them from the field and then they used them to offline with so now about a week after editing the one night set of drives have issues.  I'm speculating it's the whole SSD Trim issue and given there was only 5 percent free space to  start with the rendering to the drive etc... has lead to corruption.  One drive that still works says the OS can't repair the drive but the files can be copied.  I haven't seen the drives from the second night as they are at Melrose Mac for analysis.

I don't quite understand how the raid aspect of this SSD drive works.  I assume it's easier to get 4 1 TB SSD chips than a single 4TB chip.  Maybe it's even more.  Bottom line is there is real trouble in River City. 

Certainly step one is to never use the drives from the field to  edit from whether they are spinning or SSD.  That was not my call but we've been lucky for a long time until the field drives are SSD. 

Hopefully the drive gurus can pull them back on line. 



John Moore Barking Trout Productions Studio City, CA bigfish@pacbell.net

_._,_._,_

Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#133876) | Reply To Group | Reply To Sender | Mute This Topic | New Topic

Your Subscription | Contact Group Owner | Unsubscribe [administrator242.death@blogger.com]

_._,_._,_

No comments:

Post a Comment