Memory Allocation Failure

[stefan-niedermann]

I get the following error:

Image file pass 1/2.
** MEMORY ALLOCATION FAILURE **
ERROR: Memory exhausted at line 638 in file dig.c. Scalpel was
allocating memory for carvelists when this condition occurred.
Scalpel will abort.

What can be the problem?

[kkepinski]

same here, any solutions?

[kspham]

Same here!

[shadoxxhd]

same here

[Malachiel87]

Memory exhausted at line 638 in file dig.c. Scalpel was
allocating memory for carvelists when this condition occurred.
Scalpel will abort.

[WPDuality]

Also have this issue

[crigaud]

Same here!
Ubuntu 16.04 LTS 64-bits

[RK224]

Same Problem here! Please help

[Qwertylex]

same.

[muyaedward]

Same issue here

[rborch]

same.

[alucasr]

I have the same problem... but maybe not in the same situation, ...
In my case, I was using a LV instead of a partition
scalpel /mnt/SSD -o /pathDest <--- error
scalpel /dev/sda2 -o /pathDest <--that one works
/mnt/SDD is the logical volume and its on sda2
It also works with the lv's definition path (/dev/VG_HD500GB_SSD/MVs)
I hope this could help someone else...

[neutro27joel]

I had the same issue then I realize that I was using a folder as the first parameter instead of the partition name. The second parameter is just the holder where the data goes to.
// sudo scalpel "/dev/sdd3 ( first parameter)" -o "/home/emmanuel/Desktop/recover (second parameter)"

original: sudo scalpel "/dev/sdd3" -o "/home/emmanuel/Desktop/recover"

[avarne]

I am also getting the same issue.

[mmahmoudian]

I have the same issue, but i by-passed the error by changing the command from:

sudo scalpel /the/mount/point/and/the/folder -o /the/path/to/store/recovered/files

to

sudo scalpel /dev/sdb -o /the/path/to/store/recovered/files

(For those who don't know what sd? are: you you can list all the attached devices to your computer by using the lsblk command in the terminal.)

The modification would change the place you want to recover from, to the device that you want to recover files from.

This is not exactly what I was after since I wanted to recover content of a folder rather than content of a whole partition/disk. But nevertheless, this will bypass the problem and you can later go through the recovered files, extract what you wanted and remove the rest.

[thewoz]

same here..
I try to change the command order but the issue it is still there

[srivabhinav]

Don't run the command as root.