Welcome to our community

Be a part of something great, join today!

Register 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 :)

Major_problem_build_20.1.3!!!

Peter Östlund said:
Just back from a music concert shoot in Nairobi. Two cameras, both identical and upgraded. Red Drives and Red Bricks. The one closest to the speakers got repeatedly SATA-errors. My theory is that the powerful sound waves has something to do in this. We now have a major problem with the project. It cannot be re shooted...
Click to expand...

That's not a build specific issue. That would happen to any hard disk operation. When I was asked what to do with shooting arena size concert and they needed to continuously shoot for two hours so not other choice but hard disk, I told them to isolate from the camera, so the hard disk won't directly pick up the vibration from floor through tripod, then went through without any errors. But if you stand in front of the PA speaker, no hard disk based system would work.
 
Brad Webb said:
Would a solid state drive work in those conditions?
Click to expand...

The problem with hard disk is the head being really light weight.
Solid state won't any the same problem for sure.
 
Thanks for the enlightenment guys. Maybe you could wish the drive would be isolated enough to be able to handle sound waves and other minor movements. It is, after all, a camera, not a computer.
Macintosh computers has been used on music stages since long in the middle of the sound epicenter.
The camera was not just in front of the speakers approx. 10 meters away and it was not a hard rock concert, more funk.
Well I guess later versions of the drives will be more rugged.
The developing never stops at Red.
 
REDDRIVE handle short intermediate shocks pretty good before you get drops, but long symmetric sin wave, like concerts or helicopters seem to mess with drive function.
 
sata_trans_fault

sata_trans_fault

We are having problems with our Red One cameras sn.1990 and sn.4990.
The set up was 25 fps 1/50 sec 4K 16:9 RC 36. We notice those problems after we install build 20.1.3. During recording on RED raid 320GB we are getting message sata_trans_fault recording error and in down left corner where usually is 4K RC36 you can see safe to remove message, you get this message when you unmount the media. But we are in the middle of recording, recoding stop and you can't play back that take because the camera didn't make quick time proxies. You have only R3D file from beginning of recording till camera stop and you get message sata_trans_fault recording error. We are having break down in the middle of the take. During whole day of shooting we get like 20-30 times this sata_trans_fault recording error, sometimes we are getting no_media_path and rocket_id_error messages.
The next day we reinstall the build 20.1.3 and put the new from the bag sata red drive cable on each camera and still having errors on booth HDD drives and on booth cameras. We have two RED Raid 320GB for each camera. The booth cameras works fine on RED CF 8GB cards.
The camera sn.1990 is on five weeks movie shooting and camera assistant notice that the sata_trans_fault recording error appears more often when camera records highly contrast pictures (dark woods and weary bright sky), and the camera is on 45-degree angle. But not only then, they are having problems whole day.
The camera sn.4990 was on one-week short movie and last 4 days we had to work on CF 8GB cards because nobody liked the fact that the camera could stop recording any time in the middle of the take.
After we finished the short movie with sn.4990 we put back build 17.3.4.1 and went on one day shooting with two Red Raid 320 GB drives and didn’t have any problems with sata_trans_fault recording error.
Is it possible that build 20 is making recording problems? Did you have similar cases with other RED cameras users? The build 20 is my prime suspect, because we didn’t have sata_trans_fault recording error before. Only after build 20 on both cameras.
Please give as some suggestions for the right solutions.
Best regards

Mario Hobor
 
yes, the problem occurs on build 20. you can use other builds and not get the problem. However, Red recommend you send the drive in and get it fixed.
 
well last Friday we were taking a bold step and up'ing all 9 of our bodies to the latest V20 and one body just started this epidemic with two of the newer 640gb drives... So am i meant to understand that if we back down to our previous build it should indeed go away? brent ill reach out in just bit...
 
sergio arguello said:
well last Friday we were taking a bold step and up'ing all 9 of our bodies to the latest V20 and one body just started this epidemic with two of the newer 640gb drives... So am i meant to understand that if we back down to our previous build it should indeed go away? brent ill reach out in just bit...
Click to expand...

The error message in the display goes away, but the connection problem to the drive is still there. You need to send in the drives and get it fixed. File support ticket. They have also removed the error message in build 21.

I have begun to test drive before a shoot on B20, then I see if there is any problem with drive, then I flash camera to 21. In this way I have totally eliminated random camera reboots.
 
Mario and sergio, Build 20.1.3 has the SATA warnings built into the code. So, it would makes sense you get those warnings in that build. If you roll back, no warnings - but you could get a reboot with no warning. Best practice is to use 20.1.3 and if you get those warnings, send in your drives and drive cables. If you rather risk a potential reboot, sure, roll back to pre-20 or even try the beta Build 21 as we suppressed those warnings. If you have further questions, please direct them to tech support on www.red.com/support so we can help in the most efficient manner.

BC
 
Brent@RED said:
Mario and sergio, Build 20.1.3 has the SATA warnings built into the code. So, it would makes sense you get those warnings in that build. If you roll back, no warnings - but you could get a reboot with no warning. Best practice is to use 20.1.3 and if you get those warnings, send in your drives and drive cables. If you rather risk a potential reboot, sure, roll back to pre-20 or even try the beta Build 21 as we suppressed those warnings. If you have further questions, please direct them to tech support on www.red.com/support so we can help in the most efficient manner.

BC
Click to expand...

Brent, I guess the only way to check if cables or drives are bad is to go through the camera using 20.1.3. Any better ways than hoping we do not get the reboot with other built. Lim
 
Got my drive back yesterday and No data trans error!!!!! Thanks very much red for the quick turnaround :)
 
Hi I have the same pb
i talk to someone from RED team, they told me to downgrade ti build 17
Is there someone can help me to downgrade the Build
Thank you very much
 
High-speed related??

High-speed related??

I recently experienced the "SATA TRANS ERROR" issue with a Red 320Gb RAID drive again. This time it was occurring specifically at high-speed in 2k.

The problem occurred on a job shooting with Build 20.1.3 (release not BETA), recording in 2K 16:9 29.97 at RC36, when shooting at 100fps.

While recording at high-speed, the LCD would darken after 5-10 seconds, and soon after, the recording would stop without notice and camera would display the "SATA TRANS ERROR" message.

The drive was tested on multiple camera bodies and with several different drive cables, so I feel like it was definitely drive specific (although the common denominator was Build 20).

Issue was then recreated further through in house testing at different framerates and in 2:1 format.

I assume that this issue is in some way related to B20's more stringent error system, as none of these record faults caused camera shut-down -- just loss of recording.

Now however, the issue seems to have disappeared. Performed several high speed tests on the same drive yesterday, and it had no issues.

Just wanted to see how many of these error occurrences have been related to normal 4k 16:9 versus 2k high speed recording, and if there is any update on what is being done to diagnose it (perhaps it is caused by temperature, although my in house tests were under normal conditions).

Build 21 isn't a viable option for rental houses until it is a release build, and if this issue is being caused by a large percentage of the drives out there, Red needs to address these deeper drive issues on a specific level (which I realize is why they are asking us to send them in).

Unfortunately, it's tough to send the drives in when these errors are occurring frequently and the drives are always needed for jobs.

The drive issues are especially pesky because they can't always be recreated easily every time (we have sent drives in for service that definitely had problems, only to be subsequently told that when they got to Red there was no issue).

It would be great if Red can address the specific hardware issue that is causing this. If B21 eliminates the warning system then that is helpful, but it is also concerning if there is still going to be a deeper issue that will then go unnoticed. Keeping my fingers crossed...
 
I only started getting the message after installing Build 20, but only with Arri Zeiss super speed lenses. And only with hot exposures. I was shooting a woman at sunrise in a field of tall grass with morning light spilling round her. Also when I shot a child with a balloon against a huge water fountain. On both I was even F-16 but with super speeds. It seems when there is a lot of light and information to be captured by either the drive or the sensor through fast lenses, the error happens. I never get the error with slower lenses (Cooke 2.8 or Angenieux zooms or the RED lenses. To clear the error message and reshoot just use the exit button and go with less light. Definitely an issue the RED folks need to address. Hope this helps.
 
SATA_TRANS error

SATA_TRANS error

As this is the third identical post on this same subject this morning, I'll simply repeat what I said on the others:

If you are seeing SATA_TRANS error you need to schedule an inspection of your RED-DRIVE with RED tech support.

Meanwhile you can mitigate this by requesting Build 20 v20.1.6 from RED tech support or you can use BETA Build 21.
 
I upgraded to Build 20 in November and, in the month and a half since, I have shot hundreds of hours of footage.

I received a "SATA_TRANS_ERROR" using Build 20.1.6. once during that time, only when I first hit "Record". About to upgrade to Build 21.

As an FYI, before Build 20, never once had a reboot issue.

Sean@RED - I just sent you an e-mail regarding the Error. Thanks!
 
You must log in or register to reply here.
Back
Top