I'm using [k]Ubuntu 8.04.1. KDE

I did google it, but without any luck.

Adept offers only gddrescue.

I did 'shift+delete' one folder this morning and now I want to get it back >.<

Here is a article at InformationWeek.com that discusses several tools for file recovery. I hope one of them works for you.
http://www.informationweek.com/news/...yText=&isPrev=

I thank both of you. Cookies for all

Now I have this dumb situation. I've downloaded 'pmagic-3.0.iso.zip' from http://exo.enarel.eu/mirror/partedmagic/. I did extract the zip file and I got *.iso file. I did mount *.iso file in /mnt/iso and I have no clue what to do next??

http://img165.imageshack.us/img165/5...reen001bd6.jpg

Depends..
Let us assume that you want to create a usable partition magic CD.

I haven't a clue what OS you are using (Oh, yes I do-- Kubuntu ).. OK, You can either use something like k3b to burn the ISO to a CD, or you can do what I would do (because I have never tried out k3b) and burn the image to a CD using the following command in a terminal (konsole) window:

root# cdrecord dev=/dev/hdc speed=4 padsize=63s -pad -dao -v -eject ./path/to/file.iso

And just substitute in your own /dev/h?? for your burning device, and fill in the right path to the ISO image file. That should do it. Then you can reboot and boot up the pmagic CD.

Sasha

I did speed it up. Gone for reboot.

Not to dampen your enthusiasm but in general with filesystems, especially journalling ones, the decrease in recovery success can be counted in seconds. Especially if they continue to see read/writes after the incident. Once a file is gone the system should be "frozen" immediately (ALT+PRN+U or forced power-off) and not used anymore. Short and simple: if the directory you deleted was in /home/raimonds, then by using it to surf the 'net, posting your question and downloading the ISO and burning it chances of recovery, let alone full recovery are near nill. What should have been done was power off the system right after the deletion, make an image of the partition and *then* investigate options for recovery.

Unfortunately you didn't know that and nobody told you.

[EDIT]Lets hope that's Parted Magic you burned and not Partition Magic. (I suggest a Live CD like HELIX). Mount the "victim" drive read-only, then mount another partition in read-write mode (preferably a clean external drive) and use photorec in "test" mode to see what it thinks it can find. If it doesn't find enough for your taste you can tweak options before letting it recover data which may (or may not) be a lenghty process.

@ UnSpawn-- Oops, I should have been more concise in my above post. Yes, I suspect it is Parted Magic, rather than Partition Magic, that the OP has downloaded. I downloaded the same one a few weeks back.

Also, to the OP (and others) -- Something I never clued into until several months ago, was the fact that Midnight Commander (our favorite console file manager) is quite capable of easily UNdeleting recently deleted stuff.
It never occurred to me before, that the red colored filenames prepended with exclamation points were deleted files, and that they could be theoretically restored right there on the spot.

NOTE: In my case, this is an Ext2 file system. I cannot speak to other file systems and UNdeleting stuff, with or without MC.
NOTE 2: Also, I am not sure how exactly the OP lost his/her files, but FWIW, I have also had more success than failure (albeit tedious at times) restoring files that have wound up in "Lost & Found" during power outage induced shutdowns or FSCK-ups or whatever; there's a thread around here with "Lost and Found" in the title, in which someone explains to me a method of restoring stuff from there, if you feel like searching for it. But in the case of non-binary files in Lost&Found, it's a matter of simply opening & reading the #123456 files in there and figuring out what they used to be called and where they were lost from. For binaries, you kinda need to have an idea what they were, or else you need to play "Let's execute it and see what it does/says"

SVA

Indeed, but MC, "recover" or "debugfs" won't show the same results with Ext3 compared to Ext2 (BTW the thread you mean is http://www.linuxquestions.org/questi...ntents-550845/) and binary remains in L+F have a different cause. But let's see what the OP comes up with next...