RedUndead

[Johnny Sousa]

I'm trying to install red undead and it doesn't work. It's not installing.

Its on a macbook pro, and I've installed several times. Anyone else having this problem?

Thanks.

 

[Deanan]

It's not showing up in the terminal?

 

[Johnny Sousa]

I guess I'm not understanding how to use it.

I have terminal on, but don't see anything about redundead.

 

[Dexter Gregoire]

with the terminal window open type;

diskutil list

then hit return or 'enter'.

Well that's as far as I got, now what?

 

[Michael Neborak]

seriously? its not that hard, just type in diskutil list to get the name of the red drive that you have connected to the computer and once you know the name (something like /dev/disk2 which you put an r in front of) you will type redundead /dev/rdisk2/ /Users/*/Desktop/Recover with the * being your username. This address is specific to me because I have a folder named recover on the desktop. Its not that hard, comon if you're using the Red you should have some knowledge of computers, I mean, com'on...

 

[Jeff Kilgroe]

in the terminal type redundead and see what it says.

If you are not savvy with the unix command line or your terminal window, here's a quick and dirty tutorial on redundead, I'll have you list the disks twice so you know for sure which one you're looking for...

Don't connect your RED media just yet. You first need to figure out where you're going to put the recovered files. Make sure you have enough space to hold all the potentially recovered files. Create a folder in a place you can easily navigate to. For this example, I'm going to assume you will connect an external disk to your system named "SATAdisk" and you will presumably connect your RED media by firewire or USB or whatever.

Go ahead and connect that SATAdisk and create a folder called REDfiles.

Open terminal and type: diskutil list

This will list all the storage devices attached to your system and their size.

Connect your RED media to be recovered (CF, RED DRIVE, RED RAM). And type again: diskutil list

You should be able to identifiy the RED media. It will probably be named 'disk1' or 'disk2', etc.. We'll assume the RED media comes up as 'disk2'.

OK, now you're ready to run REDUNDEAD. You need to execute the program and give it the source, followed by the destination for the recovered files. So we type:

redundead /dev/rdisk2 /volumes/SATAdisk/REDfiles/

It will start working away... and will tell you when it's done.

Notice that even though the RED media will be named 'disk1' or similar, you will specify it with an "r" in front of the name in the source line. Notice above it's 'rdisk2'.

 

[Tim Bradley]

in the terminal type redundead and see what it says.

If you are not savvy with the unix command line or your terminal window, here's a quick and dirty tutorial on redundead, I'll have you list the disks twice so you know for sure which one you're looking for...

Don't connect your RED media just yet. You first need to figure out where you're going to put the recovered files. Make sure you have enough space to hold all the potentially recovered files. Create a folder in a place you can easily navigate to. For this example, I'm going to assume you will connect an external disk to your system named "SATAdisk" and you will presumably connect your RED media by firewire or USB or whatever.

Go ahead and connect that SATAdisk and create a folder called REDfiles.

Open terminal and type: diskutil list

This will list all the storage devices attached to your system and their size.

Connect your RED media to be recovered (CF, RED DRIVE, RED RAM). And type again: diskutil list

You should be able to identifiy the RED media. It will probably be named 'disk1' or 'disk2', etc.. We'll assume the RED media comes up as 'disk2'.

OK, now you're ready to run REDUNDEAD. You need to execute the program and give it the source, followed by the destination for the recovered files. So we type:

redundead /dev/rdisk2 /volumes/SATAdisk/REDfiles/

It will start working away... and will tell you when it's done.

Notice that even though the RED media will be named 'disk1' or similar, you will specify it with an "r" in front of the name in the source line. Notice above it's 'rdisk2'.

Thanks Jeff for explaining Redundead for all of us that had no idea terminal !!

Cheers, Tim.

 

[Ryan Dean]

**You can also open up disk utility (with your RED drive attached) click on the appropriate drive and get info>> that will tell you what your disk drive # is.

I just had an issue where the AC accidentally reformatted the RED drive. Thanks to Jon and Dan @ RED they walked me through REDundead. I didn't only retrieve all the footage, but ended up looking like a hero! Thank you guys for your continued support!

-r

 

[Nelson Goforth]

Jeff, Thank you for the informative response... it saved an hour's work on a shoot today.

Michael, arcane Unix commands are hardly 'some knowledge of computers'. You are clearly superior to most (if not all of us) since Unix is evidently something with which you sprang full grown from the forehead of Zeus, but some of us had to learn it, and most of us have never had the need. I can awk and perl and sed but I've never had to diskutil... I'm embarrassed at the poverty of my skills. You can only imagine the awe in which I hold your disdainful unwillingness to share even the simple fact that "Terminal" is an application that is tucked away in the Applications/Utilities directory, and of which the vast majority of Mac users are totally unaware. You've never had to ask for help yourself, of course, or expected a thoughtful reply, so why should you bow so low as to provide such for others who don't just know.

And what does 'comon' mean? I mean, seriously?

 

[Ariana]

seriously? its not that hard, just type in diskutil list to get the name of the red drive that you have connected to the computer and once you know the name (something like /dev/disk2 which you put an r in front of) you will type redundead /dev/rdisk2/ /Users/*/Desktop/Recover with the * being your username. This address is specific to me because I have a folder named recover on the desktop. Its not that hard, comon if you're using the Red you should have some knowledge of computers, I mean, com'on...

Micheal, your post sounds very abrasive and immature like it's coming from a punk ass kid. How old are you?

 

[Mohamed Kamel]

Hey guys,

Attached is my attempt on the above instructions, after i tried to recover my reddrive...it didnt do anything for about 3 minutes and then said "Done!"

and my recovery folder was empty.

so what am i missing?? need help please.

Thank you.

 

[Conrad Hunziker]

You can use the latest version of R3D Data Manager, which provides a GUI for recovering R3D files, in addition to other features.

 

[Mohamed Kamel]

Conrad im using at the moment the trial version u sent me the other day, and when i clicked on the "R3D File Recovery" tab, it opened a new window and was scanning for attached drives....but it took a really long time so i thought maybe because the redrive is very damaged its freezing the scan or something, so i unplugged it and i was right...it scanned for the normal drives in like 2 seconds.

So what now? does this mean the data will never be recovered?

 

[Conrad Hunziker]

No - it means there is more wrong with it than can be fixed in the field. Judging from this and your other posts, its time to contact Red support and send the drive to them.

 

[Conrad Hunziker]

on a new mac pro, how can i get this working? i click the r3d recovery button and nothing happens

Are you using the latest version? It is currently 5.1.

In addition, it helps to remove unnecessary mount points from your system, including mobileme or other network share you arent using. When you first start the r3d recovery window, R3D Data Manager will search your system for all attached hard drives. This will take some time if you have a lot of drives attached.

 

[Drew Suppa]

It's too early in the morning to be failing this epically.

I'm DIT on a feature and the AC handed me some 16GB CF cards to download that were shot as plates before principal began.

Due to the economy, my new laptop ended up being a 13" MacBook Pro; I have a USB powered CF reader that I've not had problems with in the past with my old setup, but today for some reason, the CFs aren't mounting. I can't even see what's wrong in DiskUtility.

I've also downloaded and run REDUndead in the Terminal and can't seem to get it recovering files.

Help me walk through... call me stupid; it's my first time working in the Terminal.

I want to recover the files to my desktop, so I created a file called Recover there. In Terminal, I do the following:

Last login: Sun Aug 2 06:26:44 on ttys000
drew-suppas-macbook-pro:~ drewsuppa$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *149.1 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Endeavour 99.9 Gi disk0s2
3: Apple_HFS Media 48.7 Gi disk0s3
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *465.8 Gi disk3
1: EFI 200.0 Mi disk3s1
2: Apple_HFS G-RAID_1 465.4 Gi disk3s2
/dev/disk7
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *14.4 Gi disk7
1: Windows_FAT_32 14.4 Gi disk7s1
drew-suppas-macbook-pro:~ drewsuppa$ redundead/dev/rdisk7/volumes/users/drewsuppa/desktop/Recover
-bash: redundead/dev/rdisk7/volumes/users/drewsuppa/desktop/Recover: No such file or directory
drew-suppas-macbook-pro:~ drewsuppa$

I see the file sitting on my desktop... is my file path horribly off? Why isn't this working?

Help!

 

[Drew Suppa]

I've also downloaded R3D Manager, and the little wheel just spins when trying to scan for drives...

 

[Drew Suppa]

Okay, scratch that.

It seems the issue is with my CF Card reader, which is funny because I've never had this issue before. For some reason, it was unable to mount on my desktop, and thus also not in DiskUtility nor with REDUndead in the Terminal.

Sorry to sound like an idiot; Murphy's Law in full effect this morning.

 

[Felipe Abreu]

Post Faliure Recover

Post Faliure Recover

Do you guys know, if red undead can recover files that doest show cause the camera failed to finish the post function? (this happens in concerts when we record one shot with almost an hour duration)
One more question, is the same command for recovering corrupt files and recovering formmated/deleted files? Thanks!!!!!


Felipe Abreu

 

[Conrad Hunziker]

REDUndead recovers R3D files only. So if you are missing R3D files because of a post hang (and you shutdown the camera), then it would be able to recover those.

R3D Data Manager provides a GUI to REDUndead and goes a step beyond - sorting R3D files based on shot date, recreating RDM/RDC folders and recreating the MOV reference files. Most often it is just those MOV reference movies that are missing from a hung post on camera - so you would be able to re-create them automatically with R3D Data Manager file recovery process. Please note you should really only use this tool if you are missing R3D files, not just to solely re-create the reference MOV, as it is quite a slow process to recover R3D files.

As for recovering corrupt files - it depends on why the corruption was caused. It will search for R3D files on a drive and write them to another drive. But if the R3D file was partially overwritten (for example) it wont be able to restore the original missing data. In essence REDUndead is a file recovery tool, not a R3D fix tool.