Red One 320 gb drive tests

[Marco Naylor]

Hello everyone,

Doing some tests on a Red Drive 320gb. We are letting the camera run for about 12 -15 minutes, and we are getting some kind of "Sata hard drive" message, and it stops recording.

Has anyone experienced this?

If so can you please shed some light on the matter.

Thanks

Cowboy Bill

 

[Brigham Edgar]

It is a hard drive or cable fault that build 20 reports and makes you stop recording. The only way around this i think is to change from build 20 to another build.
RED has said that you need to send in your drive and cable if this happens.

 

[Marco Naylor]

If I wanted to go back to Build 18 because of time restraints, where can I find a download for Build 18

 

[ericyoung]

If I wanted to go back to Build 18 because of time restraints, where can I find a download for Build 18

Direct download here:
http://www.red.com/support/release_history/7#109

Download page with all Beta builds here:
http://www.red.com/support/release_history/7

Download page with all Release builds here:
http://www.red.com/support/release_history/4

You could also try Beta build V21.0.2 as this has Build 20 functionality while disabling the stopping on Sata Fault alert.

 

[Julio Quintana]

I was having the same error on Build 20. I sent in my drive and cable to RED and they sent it back a couple of days later. No explanation whatsoever, but the camera works perfectly now.

 

[jimhare]

Yes, it's a problem that always existed. You may have got strange restarts or shutdowns in the past, which was this issue manifesting itself.

In build 20 they started reporting it, but that just stops the shot, even if the fault isn't fatal.

In build 21 they removed the message again, but if you got it in 20, you need to send your drive and cable in to correct the problem.

 

[Ivan G]

I'm having the same issue now. I'll be sending my in soon as well. Although I never had this issue with any prior build.

 

[James Press]

One of ours is with RED fixing this as we speak.

 

[Casey Schendel]

I thought the error only happened on the 640GB drives, glad to hear I'm not the only one to encounter that problem.