Welcome to our community

Be a part of something great, join today!

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

My first post here is a nightmare.

Scot Yount

Well-known member
Joined
Dec 28, 2014
Messages
1,713
Reaction score
7
Points
38
Location
Marblehead, Massachusetts
Hi all,
I have never posted here and hate for this to be my first. I have Scarlet #02349 that I bought used from a church group in Florida. All looked to be in order and when I got it from the original owner I transferred ownership via RED. The camera was running firmware 5.1.35. It worked fine, except for when trying to use my new 240 gig REDMAG. I updated the firmware yesterday as per RED instructions to the latest, 5.2.41. The camera worked Perfectly. Until now. This morning I get the horrible message
Startup Error
A serious error was detected during startup.
Please send saved log file to RED support.

Needless to say I have sent the ticket, but it is Sunday. Anyone have any thoughts on what the trouble might be? Very disappointed.


scot
 
Hey Scot. Perhaps you can post your location and some here might be in your area to help you out. You need to find out if it's your Redmag or your camera that has the issue. So I understand, the 240GB card never worked with either firmware?
 
Hey Scot. Perhaps you can post your location and some here might be in your area to help you out. You need to find out if it's your Redmag or your camera that has the issue. So I understand, the 240GB card never worked with either firmware?

I am in Boston. Yes the camera worked with the 240 gig mag after the firmware update. It gave error messages before and said the 240 "wasn't a REDMAG, recording disabled" but would however record anyway. Again, all of that went away with the latest firmware and of course my menus changed from the slate blue to the groovy red. In any case, it doesn't work now with the any REDMAG ( i have an old 64 gig) and starting it up with no mag in the slot produces the same shutdown message. I did a hard restore and it came up with the same error message.
 
You did the "hold down the power button for ten seconds thing"?

what accessories do you have?

Did you upgrade with the redmote and side handle attached?

How are you powering the camera?

have you reseated all the connections?



battistella
 
You did the "hold down the power button for ten seconds thing"?

what accessories do you have?

Did you upgrade with the redmote and side handle attached?

How are you powering the camera?

have you reseated all the connections?



battistella
I have the side handle and a Canon Al mount. I was using hard power to upgrade the firmware and the aforementioned accessories were attached. I did the "Hold down the power button thing" for 20 seconds actually as it says in the manual. I don't have a REDmote. I reseated all connections. Same result. I should emphasize, that after the update, it worked flawlessly for the entire day. Then, when I started it up this morning, I get the dreaded error message.
 
I should probably also say that as it boots up, just before the color bars take over the screen and the error message pops up, the picture has a light blue haze over the left side of the image, (perhaps 30 percent) but the right side appears to be fine. I had had some issues before where the screen would go to a kind of hash (not the menu items, but the image from the lens) but a restart always cleared it. Ugh...
 
Try without the side handle.

The blue haze could just be there because the sensor is not warmed up.

Try a restore without the side handle.

The upgrade instructions almost always implicitly say to remove the side handle before upgrading.

Battistella
 
Try without the side handle.

The blue haze could just be there because the sensor is not warmed up.

Try a restore without the side handle.

The upgrade instructions almost always implicitly say to remove the side handle before upgrading.

Battistella

Thanks. I will do that. However, it all worked fine all day yesterday. I will let you know what happens.
 
Next thing I would do is roll back one to one version before the version you tried to installed.

Unplug everything. Go have a coffee. Leave the side handle unattached

when you return.

DL the version of the correct Firmware from RED.com
Place that on the SSD
Print and follow the instructions, exactly as they appear in the version upgrade readme text.
run the upgrade

Battistella
 
Thanks David,
I will do whatever it takes to fix this problem of course!!! However, I believe I followed the directions to the t. It says nothing anywhere about removing the side handle or any other module. From the text file, "The camera may take 30 seconds or longer to upgrade all the attached modules. During this time the PWR and REC LEDs flash green and nothing displays on the external monitors." It worked great for an entire day. And now is for all intents and purposes, a brick.
 
And do not attach/remove the side handle while the camera is on. DSMC modules are not hot swap.
 
Here is the page for the MX scarlet

https://www.red.com/downloads/4f8c3e5f2f74a94ac2000419

make sure you remove the SSD after the FW upgrade and wait for the ten seconds or longer before trying to power up again.

Try another SSD if you have one.

Battistella
Hi David,
Thanks for your help. I removed the side handle, and installed firmware one before the current firmware. No change. I then installed the firmware the camera had when I got it. 5.1.35. Curiously, no change. I say that because that firmware didn't have any red menus, they were all slate blue. The serious error message came up as red menu. I then reinstalled the most current firmware. No change. *sigh*....
 
Scot-

Your issue is the mag. RED swapped my first 512GB card, same symptoms as yours. Contact your Bomb squad rep and open a ticket and get them to ship you a new card asap.
 
Scot-

Your issue is the mag. RED swapped my first 512GB card, same symptoms as yours. Contact your Bomb squad rep and open a ticket and get them to ship you a new card asap.
I hope that is it....but I don't think so. I have two mags. A 64 that worked fine, and this new 240. The camera gives the same error message even with no card in the side SSD thingy. Do you think the 240 did the damage?
 
Wait.

It worked all day two days ago.

Then you did an upgrade and it bricked.

Were you on power or battery when you upgraded? Was the upgrade interrupted?

Battistella
 
Wait.

It worked all day two days ago.

Then you did an upgrade and it bricked.

Were you on power or battery when you upgraded? Was the upgrade interrupted?

Battistella

No...I did the update and it worked all day. Then, the next day it bricked. I was on hard power when I upgraded. It was not interrupted. It worked fine.
 
Cool.

Just wanted to get a handle on it. So how many cards did you roll and offload over the course of that day? Maybe the Side SSD isn't seated so well.

Battistella
 
Cool.

Just wanted to get a handle on it. So how many cards did you roll and offload over the course of that day? Maybe the Side SSD isn't seated so well.

Battistella
I was just testing the camera, so only two or three of each of the two cards. I by no means filled them. I just got the camera and was trying to establish my workflow. On the previous firmware, it didn't recognize the 240, but recorded anyway. Once I upgraded the firmware to the current version, that card was then recognized and the number of minutes that could still be recorded showed in the menus, a nice addition. I have had a couple of instances before I upgraded the firmware, where the picture would go to hash, and I would lose all control of the camera. I would have to shut it down, at least once, or maybe three times before it "repaired" itself. Curiously, now when the camera boots up, that same hash very briefly appears on the left side of the screen before the color bars appear. Also curiously, sometimes the color bars are all the wrong colors, and other times they are not. Make sense?
 
Last edited:
Back
Top