RED UNDEAD not working

[José L. Martínez]

Trying RED undead with 3 different ssd 128gb modules and got nothing. Running both as norm user and via sudo, when putting the sad dev path (root, no partition) red undead keep working for hours, then a Done! message and nothing is extracted. When using the partition root the done message is automatic and nothing appears. This is the command I'm using. Anything wrong or ideas?.

sudo redundead /dev/disk2 /Users/user/Desktop/recover

got a long read and nothing output

sudo redundead /dev/disk2s1 /Users/user/Desktop/recover

got immediate Done! and nothing output.

Cheers,

Jose

[alexjentz]

Hi Jose,

try using "rdisk2" instead of "disk2" ;)

[José L. Martínez]

Hi,

Now I get the red led blinking and a much quicker Done! at the end, but still no recover files.

Are EPIC M files compatible with red undead?

J

[alexjentz]

i honestly did not have to try with epic files yet. did you go with or without the s1 ?

mayb you could try without for a different result.

also: sometimes the disk numbers change or get mixed up. restarting, freshly connecting the reader and ssd after that and then diskutil list to find out which rdisk it is will maybe help

[Thomas Wright]

i get done on a 128gb red ram, MX footage mind. anyone got a help?

[Andrew Wilsak]

Someone may correct me if I'm wrong, but I was trying to do the same thing not too far back with some test footage on the epic I decided I wanted back after formatting and after encountering the same problem and doing some research it doesn't seem like you are able to recover data from an SSD through redundead or really any other cheap widely available means.

[Jeff Kilgroe]

REDUNDEAD doesn't work with EPIC footage, yet...

And depending on how the SSD's operate internally, it may be difficult for any form of conventional data recovery methods to work. Actually that holds true for a lot of SSD storage on the market these days. Many use internal data compression on the actual transports or data pathways to attempt to move data faster, they tend to jump around when placing data in attempt to level out the wear on the FLASH memory. So if you have a freshly erased or formatted drive, the wear-leveling table may (most likely) be different than what it was previously when data was written. So no guaranty you will be able to recover anything meaningful... Let alone even be able to read sequential bytes from the SSD in the same way sequential bytes were written to it under a previous formatting.

[Deanan]

We have an internal version of redundead with Epic support getting ready to be released.

If you need it sooner, email me.

[alexjentz]

Deanan, i have an Epic Shoot next Saturday in New York, i guess i'll drop you an mail in any case it isn't released till then ;)

[Jeff Kilgroe]

Deanan, i have an Epic Shoot next Saturday in New York, i guess i'll drop you an mail in any case it isn't released till then ;)

Haha... That reads like you're planning on failure. ;)

Been shooting RED here since December '07... Never actually needed to use REDUNDEAD. Or at least not for myself. I did test and play with it a bunch when it was released. Learned that I needed to zero-out all my media before sending out to rental customers if there could potentially be stuff on the media that I didn't want prying eyes to see. Ran it once for a client who was hoping to recover something...