How to recover deleted files?
Are there any tools, methods, incantations to recover recently deleted files on Ubuntu?
If it makes any difference, I want to recover a Keepass 2.x database file. But would be better to have a method/tool that works on any kind of file.
data-recovery
add a comment |
Are there any tools, methods, incantations to recover recently deleted files on Ubuntu?
If it makes any difference, I want to recover a Keepass 2.x database file. But would be better to have a method/tool that works on any kind of file.
data-recovery
Related, but not really a duplicate: Can files/directories deleted from terminal be restored?
– Seth♦
Nov 6 '14 at 3:59
add a comment |
Are there any tools, methods, incantations to recover recently deleted files on Ubuntu?
If it makes any difference, I want to recover a Keepass 2.x database file. But would be better to have a method/tool that works on any kind of file.
data-recovery
Are there any tools, methods, incantations to recover recently deleted files on Ubuntu?
If it makes any difference, I want to recover a Keepass 2.x database file. But would be better to have a method/tool that works on any kind of file.
data-recovery
data-recovery
edited Dec 2 '13 at 15:22
Braiam
51.6k20136220
51.6k20136220
asked Sep 9 '10 at 1:40
Decio LiraDecio Lira
4,666103241
4,666103241
Related, but not really a duplicate: Can files/directories deleted from terminal be restored?
– Seth♦
Nov 6 '14 at 3:59
add a comment |
Related, but not really a duplicate: Can files/directories deleted from terminal be restored?
– Seth♦
Nov 6 '14 at 3:59
Related, but not really a duplicate: Can files/directories deleted from terminal be restored?
– Seth♦
Nov 6 '14 at 3:59
Related, but not really a duplicate: Can files/directories deleted from terminal be restored?
– Seth♦
Nov 6 '14 at 3:59
add a comment |
11 Answers
11
active
oldest
votes
TestDisk can sometimes recover recently deleted files.
4
May be important to someone to know that specific for camera's cards, on TestDisk exists PhotoRec
– Luis Siquot
Oct 7 '15 at 19:34
1
At this moment, TestDisk does not have a graphical user interface and the help (man) pages are not enough informative for me.
– silviubogan
Dec 4 '15 at 14:52
3
PhotoRec (cgsecurity.org/wiki/PhotoRec) worked great for me to recover accidentally deleted files (on Ubuntu 14.04 with ext4). I first tried with TestDisk but it wasn't able to recover them. Anyway, I found both tools crafted in the same folder.
– Andrea
Jan 14 '16 at 14:00
1
@silviubogan actually TestDisk has a pretty good Textual User Interface with menus and explanations along the way. All actions have an associated key to perform them and they are clearly written on every screen for easier access.
– Andrea Lazzarotto
Jun 24 '16 at 12:30
add a comment |
I have used foremost to recover damaged hard disk both under NTFS (windows), FAT32 (Flash card from a Nokia phone) and ext3 with great results. Command line only, but quite it's easy, something like this:
sudo foremost -i /dev/sda -o <dir where recovered files will be stored>
It will order the recovered files on folders by file-type. Openoffice docs are recovered as zip files. As you need to execute it as root (in order to direct access the hardware), output files are also owned by root, so you will likely need to change their ownership afterwards.
This is probably too old question but, how does GIMP files look like after recovery?
– wakeup
Oct 3 '13 at 21:04
I don't know, I have never tried to recover them.
– Javier Rivera
Oct 4 '13 at 6:28
@JavierRivera - I do not believe thatforemost
can recover.xcf
files. See the man page it can only deal with these file types: (jpg, gif, png, bmp, avi, exe, mpg, mp4, wav, riff, wmv, mov, pdf, ole, doc, zip, rar, htm, and cpp).
– slm
Mar 31 '14 at 0:48
already running...let me wait for results. Will share.
– Patrick Mutwiri
Apr 15 '16 at 5:09
how much time does it take to finish?? for a 32GB usb memory
– Mina Michael
Mar 23 '17 at 23:17
add a comment |
extundelete is really great if your file system is ext3 or ext4.
Note: extundelete requires you to unmount your drive to work properly (this is a good idea to do ASAP anyway, to avoid potentially overwriting the hopefully-recoverable bytes in the deleted files).
Unmounting the drive on a live system can be tricky... you'll often get the 'device is busy
' message. To clear this 'properly' requires shutting down all processes accessing the file system. But... you were likely working in your home directory, and a zillion processes are hooked into your home directory, so good luck with that.
The trick to getting around this is to do a 'lazy' unmount:
$ mount
/dev/sda7 on /home type ext4 (rw)
$ sudo umount -l /home
where:
- that example is for me prepping my
/home
mount for use with extundelete. You obviously need to replace/home
with your mount of interest - I did the
mount
command first to figure out what device (/dev/sda7
) I need to pass to extundelete (output is truncated for brevity) - that is a lower case L in the
-l
option
4
A lazy unmount doesn't really help since the fs remains mounted until all files on it are closed. You just need to shut down the system as soon as you delete the files, and run extundelete from a livecd.
– psusi
Jul 7 '11 at 1:52
@psusi - It is absolutely untrue to say that it doesn't help!!umount -l
prevents any new files from being opened/created and written (web caches and such). However, it does not prevent existing opened files from still being written to (ie: it does not close existing files). You suggest shutting down, but I think a lazy unmount will (most of the time) result in less written files, depending on the partition in question. On that note, it is best is to have extundelete installed already, and if not, make sure to install it to some partition other than the one you are trying to recover!
– Russ
Jul 11 '11 at 15:30
As long as the fs is still mounted, attempting to access it will result in corruption. That is the reason that extundelete requires you unmount the fs in the first place. The lazy unmount simply fools it into thinking it is not mounted, and therefore, that it is safe to proceed with manipulating the disk, when that is not true. Proceeding with extundelete before the fs is actually dismounted can hose the whole disk.
– psusi
Jul 11 '11 at 18:15
1
@psusi - "can hose the whole disk"??! With a read-only operation? I don't get your argument, or what has you so paranoid. extundelete does not "manipulate the disk". The worst possible thing I can imagine happening is that extundelete expects an unmounted/static partitition and if, while reading the journal info, the lazily unmounted disk changes due to processes that had files open, extundelete may get confused and the recovery may fail. "possibly failed recovery" != "hosed disk". If it does fail, shut down, pray shutdown doesn't trash your lost data, and use a livecd as you suggest.
– Russ
Jul 12 '11 at 16:55
1
God bless this program! And you @Russ. Recovered all my files!
– Vladimir Kovalchuk
May 1 '17 at 4:10
|
show 1 more comment
If you deleted some file by accident but still know some strings which were written in that file you can use:
grep -a -B 25 -A 100 'containing string' /dev/sda1 > result.txt
1
what if the file is binary and not text?
– Decio Lira
Sep 9 '10 at 12:11
Assuming it was text, how can he recover the file with result.txt? I'm not getting it..
– sergio91pt
Jul 2 '11 at 11:40
I tried several other prior answers. None of them worked. This simple trick did! Thanks!
– JamesThomasMoon1979
Jul 15 '15 at 17:41
Its really worked, awesome stuff. Thanks a lot.
– Snehal Parmar
Nov 24 '15 at 9:13
2
It should be noted that25
and100
are just some magic numbers that probably need to be tweaked for the specific case.
– Andrea Lazzarotto
Jun 24 '16 at 12:32
|
show 3 more comments
To recover the directory you can use extundelete
Install extundelete
sudo apt-get install extundelete
Command to recover
sudo extundelete --restore-directory /home/Documents/ /dev/sda1
Note: In place of dev/sda1
put your hardisk partition name.
/home/Documents/
is your path to deleted directiory.
1
I usedautopsy
to find the inodes I needed and thenextundelete
to restore them. Worked well!
– Raphael
Dec 7 '14 at 13:05
My results looks.....~/Books$ sudo extundelete --restore-directory /home/newubuntu/Books/LaTeX /dev/sda2 WARNING: Extended attributes are not restored. Loading filesystem metadata ... 522 groups loaded. Loading journal descriptors ... 32242 descriptors loaded. Writing output to directory RECOVERED_FILES/ Failed to restore file /home/newubuntu/Books/LaTeX Could not find correct inode number past inode 2621441.
– alhelal
May 3 '17 at 2:51
I want to send confirmation in the command. How?
– alhelal
May 8 '18 at 14:01
sudo extundelete -y --restore-directory /home/Documents/ /dev/sda1
like this.
– alhelal
May 8 '18 at 14:02
add a comment |
R-Linux(Recovery studio) is one of the best. I have used this tool many times before. I worked at a company where they used the commercial version, 9/10 times it recovers everything you want. Truly superb application. Saved mine, and friends behinds many times before.
R-Linux is a free file recovery utility for the Ext2/Ext3/Ext4 FS
file system used in the Linux OS and several Unixes. R-Linux uses the
same InteligentScan technology as R-Studio, and flexible parameter
settings to provide the fastest and most reliable file recovery for
the Linux platform. However, unlike R-Studio, R-Linux cannot recover
data over network or reconstruct RAIDs, or provide object copy.
Features (from their website):
R-Linux recover files:
- Removed by virus attack, power failure or system crash;
- After the partition with the files was re-formatted, damaged, or deleted;
- When the partition structure on a disk was changed or damaged. In this case, R-Linux can scan the disk trying to find previously existing partitions and restore files from found partitions.
- From disks with bad sectors. In this case, R-Linux can first copy the entire disk or its part into an image file and then process the image file. This is especially useful when new bad sectors are constantly appearing on the disk, and remaining information must be immediately saved.
R-Linux Advanced features:
- Standard "Windows Explorer" - style interface.
- Host OS:
- Linux variant: Linux, kernel 2.6 and above
- Windows variant: Win2000, XP, 2003, Vista, Windows 7, Windows 8
- Supported file systems: Ext2/Ext3/Ext4 FS (Linux) only.
Recognition and parsing Dynamic (Windows 2000/XP/Vista/Win7), Basic, GPT and BSD (UNIX) partitions layout schema and Apple partition map. Dynamic partitions over GPT are supported as well as dynamic partitions over MBR.
Creates image files for an entire hard drive, logical disk, or its part. Such image files can be processed like regular disks. Images can be either simple exact object copies (Plain images) compatible with the old versions of R-Linux, or compressed images that can be compressed, split into several parts, and password-protected. Such images are fully compatible with the images created by R-Drive Image, but incompatible with the old versions of R-Linux.
Recognizes localized names.
- Recovered files can be saved on any (including network) disks accessible by the host operating system.
I didn't expect this to be free for Linux. I already know R-Studio and it is a fabulous software. Great that it's free for Linux filesystems.
– 0x01
Jun 12 '18 at 15:37
1
This tool is only free for recovering files less than 256kb
– Tik0
Aug 16 '18 at 8:38
add a comment |
If using secondary internal HD (suspect the same for external HD) for recovered file import (from main HD, where the files originally were), it’s necessary to make a directory, into which the files will be put in on secondary HD.
To do it, you need to have BIOS setting for booting from CD first!
1. Start Live Ubuntu Rescue-Remix CD, give command to boot, then when it boots into terminal, check your HDs by command – Code: sudo fdisk -l
Realize what HD is main, and which is secondary, and what partition to check for files and into which to recover them – linux ext3 or Windows NTFS! Mine was Linux. Have enough room on it!
(Then you can try to run Photorec (“sudo photorec”) and hopefully you’ll be able to see all your HDs. I was not that lucky, so I had to make directory and mount sec. HD.)
- Make directory for recovered files first, e.g. – media/disk. Give command – Code:
sudo mkdir /media/disk
If alright, terminal prompt simply returns.
- Must mount secondary HD, or it’ll be invisible, even if “sudo fdisk -l” does show it. Give command for your secondary HD –
Code:sudo mount -t ext3 /dev/sdb2 /media/disk
If alright, terminal prompt simply returns.
Run Photorec by command – Code:
sudo photorec
Go thru settings, and only choose file types that you want, otherwise you’ll have thousands of files to sift thru!
For more details you may please visit: http:/www..ubuntumanual.org/posts/357/recover-your-deleted-files-in-ubuntu
add a comment |
Try Scalpel
sudo apt-get install scalpel
for more info
man scalpel
trying it now. I don't quite understand how to add new files to the conf file. Do you have nay source with details?
– Decio Lira
Sep 9 '10 at 2:30
2
I found howtoforge.com/recover-deleted-files-with-scalpel which is better than nothing. Good luck, this ain't no MS-DOS.
– msw
Sep 9 '10 at 2:58
see also ubuntu.stackexchange.com/questions/2596/… I use a relatively heavy system backup, but have "Back in Time" set up to dup selected directories from /home/msw (including .config which also catches.config/keepassx/*
(your locations may vary)) to a spare partition nightly. I've also been using Unix since forever and you usually become pretty careful after the second time you blow awaythe-really-critical.file
;)
– msw
Sep 9 '10 at 3:06
Scalpel seems to be doing the same as foremost but while scalpel is no longer developed since 10 years, foremost got many updates in recent years.
– sebix
Aug 1 '15 at 18:41
add a comment |
Autopsy and the Sleuthkit tools are great for recovering deleted files, with a user-friendly UI, as well as being available in the repos.
good to know. will take a look at them. ;)
– Decio Lira
Oct 12 '10 at 19:03
1
I'd upvote it if you would have added some links.
– MadMike
Nov 14 '13 at 10:48
I usedautopsy
to find the inodes I needed and thenextundelete
to restore them. Worked well!
– Raphael
Dec 7 '14 at 13:03
add a comment |
Install scalpel
sudo apt-get install scalpel
Edit the scalpel.conf file and uncomment the file types you want to recover.
Create an empty folder (eg:recovered_data)
Find the partition your data was. You can use lsblk to get the partition map.
sudo lsblk
Run scalpel (assume the data was in sda1)
sudo scalpel -o recovered_data/ /dev/sda1
add a comment |
Recently I used ext3grep to recover a large SQLite 3 file that was deleted from an ext3 file system.
I had tried many other undelete tools, all which couldn't recover the file (from a dd image of the disk).
In order to use ext3grep, I needed to download and compile the source. Carefully reading http://www.xs4all.nl/~carlo17/howto/undelete_ext3.html from top to bottom in order to understand how the ext3 file system works and how to use the journal to find where deleted files use to be on the disk was also required.
This is not a simple solution, but very, very powerful. If you're prepared to invest a few hours to study the document and compile the program, it's well worth it.
Thanks, I maybe try that. will this only work with ext3 file systems? What about ext4?
– Decio Lira
Sep 23 '10 at 17:28
I'm not sure about ext4 but I think ext4 is backward compatible to ext3. I would assume it would work but have never tried.
– Stacey Richards
Oct 21 '10 at 10:55
add a comment |
protected by Community♦ Oct 9 '14 at 7:36
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
11 Answers
11
active
oldest
votes
11 Answers
11
active
oldest
votes
active
oldest
votes
active
oldest
votes
TestDisk can sometimes recover recently deleted files.
4
May be important to someone to know that specific for camera's cards, on TestDisk exists PhotoRec
– Luis Siquot
Oct 7 '15 at 19:34
1
At this moment, TestDisk does not have a graphical user interface and the help (man) pages are not enough informative for me.
– silviubogan
Dec 4 '15 at 14:52
3
PhotoRec (cgsecurity.org/wiki/PhotoRec) worked great for me to recover accidentally deleted files (on Ubuntu 14.04 with ext4). I first tried with TestDisk but it wasn't able to recover them. Anyway, I found both tools crafted in the same folder.
– Andrea
Jan 14 '16 at 14:00
1
@silviubogan actually TestDisk has a pretty good Textual User Interface with menus and explanations along the way. All actions have an associated key to perform them and they are clearly written on every screen for easier access.
– Andrea Lazzarotto
Jun 24 '16 at 12:30
add a comment |
TestDisk can sometimes recover recently deleted files.
4
May be important to someone to know that specific for camera's cards, on TestDisk exists PhotoRec
– Luis Siquot
Oct 7 '15 at 19:34
1
At this moment, TestDisk does not have a graphical user interface and the help (man) pages are not enough informative for me.
– silviubogan
Dec 4 '15 at 14:52
3
PhotoRec (cgsecurity.org/wiki/PhotoRec) worked great for me to recover accidentally deleted files (on Ubuntu 14.04 with ext4). I first tried with TestDisk but it wasn't able to recover them. Anyway, I found both tools crafted in the same folder.
– Andrea
Jan 14 '16 at 14:00
1
@silviubogan actually TestDisk has a pretty good Textual User Interface with menus and explanations along the way. All actions have an associated key to perform them and they are clearly written on every screen for easier access.
– Andrea Lazzarotto
Jun 24 '16 at 12:30
add a comment |
TestDisk can sometimes recover recently deleted files.
TestDisk can sometimes recover recently deleted files.
answered Sep 9 '10 at 6:05
vh1vh1
1,07376
1,07376
4
May be important to someone to know that specific for camera's cards, on TestDisk exists PhotoRec
– Luis Siquot
Oct 7 '15 at 19:34
1
At this moment, TestDisk does not have a graphical user interface and the help (man) pages are not enough informative for me.
– silviubogan
Dec 4 '15 at 14:52
3
PhotoRec (cgsecurity.org/wiki/PhotoRec) worked great for me to recover accidentally deleted files (on Ubuntu 14.04 with ext4). I first tried with TestDisk but it wasn't able to recover them. Anyway, I found both tools crafted in the same folder.
– Andrea
Jan 14 '16 at 14:00
1
@silviubogan actually TestDisk has a pretty good Textual User Interface with menus and explanations along the way. All actions have an associated key to perform them and they are clearly written on every screen for easier access.
– Andrea Lazzarotto
Jun 24 '16 at 12:30
add a comment |
4
May be important to someone to know that specific for camera's cards, on TestDisk exists PhotoRec
– Luis Siquot
Oct 7 '15 at 19:34
1
At this moment, TestDisk does not have a graphical user interface and the help (man) pages are not enough informative for me.
– silviubogan
Dec 4 '15 at 14:52
3
PhotoRec (cgsecurity.org/wiki/PhotoRec) worked great for me to recover accidentally deleted files (on Ubuntu 14.04 with ext4). I first tried with TestDisk but it wasn't able to recover them. Anyway, I found both tools crafted in the same folder.
– Andrea
Jan 14 '16 at 14:00
1
@silviubogan actually TestDisk has a pretty good Textual User Interface with menus and explanations along the way. All actions have an associated key to perform them and they are clearly written on every screen for easier access.
– Andrea Lazzarotto
Jun 24 '16 at 12:30
4
4
May be important to someone to know that specific for camera's cards, on TestDisk exists PhotoRec
– Luis Siquot
Oct 7 '15 at 19:34
May be important to someone to know that specific for camera's cards, on TestDisk exists PhotoRec
– Luis Siquot
Oct 7 '15 at 19:34
1
1
At this moment, TestDisk does not have a graphical user interface and the help (man) pages are not enough informative for me.
– silviubogan
Dec 4 '15 at 14:52
At this moment, TestDisk does not have a graphical user interface and the help (man) pages are not enough informative for me.
– silviubogan
Dec 4 '15 at 14:52
3
3
PhotoRec (cgsecurity.org/wiki/PhotoRec) worked great for me to recover accidentally deleted files (on Ubuntu 14.04 with ext4). I first tried with TestDisk but it wasn't able to recover them. Anyway, I found both tools crafted in the same folder.
– Andrea
Jan 14 '16 at 14:00
PhotoRec (cgsecurity.org/wiki/PhotoRec) worked great for me to recover accidentally deleted files (on Ubuntu 14.04 with ext4). I first tried with TestDisk but it wasn't able to recover them. Anyway, I found both tools crafted in the same folder.
– Andrea
Jan 14 '16 at 14:00
1
1
@silviubogan actually TestDisk has a pretty good Textual User Interface with menus and explanations along the way. All actions have an associated key to perform them and they are clearly written on every screen for easier access.
– Andrea Lazzarotto
Jun 24 '16 at 12:30
@silviubogan actually TestDisk has a pretty good Textual User Interface with menus and explanations along the way. All actions have an associated key to perform them and they are clearly written on every screen for easier access.
– Andrea Lazzarotto
Jun 24 '16 at 12:30
add a comment |
I have used foremost to recover damaged hard disk both under NTFS (windows), FAT32 (Flash card from a Nokia phone) and ext3 with great results. Command line only, but quite it's easy, something like this:
sudo foremost -i /dev/sda -o <dir where recovered files will be stored>
It will order the recovered files on folders by file-type. Openoffice docs are recovered as zip files. As you need to execute it as root (in order to direct access the hardware), output files are also owned by root, so you will likely need to change their ownership afterwards.
This is probably too old question but, how does GIMP files look like after recovery?
– wakeup
Oct 3 '13 at 21:04
I don't know, I have never tried to recover them.
– Javier Rivera
Oct 4 '13 at 6:28
@JavierRivera - I do not believe thatforemost
can recover.xcf
files. See the man page it can only deal with these file types: (jpg, gif, png, bmp, avi, exe, mpg, mp4, wav, riff, wmv, mov, pdf, ole, doc, zip, rar, htm, and cpp).
– slm
Mar 31 '14 at 0:48
already running...let me wait for results. Will share.
– Patrick Mutwiri
Apr 15 '16 at 5:09
how much time does it take to finish?? for a 32GB usb memory
– Mina Michael
Mar 23 '17 at 23:17
add a comment |
I have used foremost to recover damaged hard disk both under NTFS (windows), FAT32 (Flash card from a Nokia phone) and ext3 with great results. Command line only, but quite it's easy, something like this:
sudo foremost -i /dev/sda -o <dir where recovered files will be stored>
It will order the recovered files on folders by file-type. Openoffice docs are recovered as zip files. As you need to execute it as root (in order to direct access the hardware), output files are also owned by root, so you will likely need to change their ownership afterwards.
This is probably too old question but, how does GIMP files look like after recovery?
– wakeup
Oct 3 '13 at 21:04
I don't know, I have never tried to recover them.
– Javier Rivera
Oct 4 '13 at 6:28
@JavierRivera - I do not believe thatforemost
can recover.xcf
files. See the man page it can only deal with these file types: (jpg, gif, png, bmp, avi, exe, mpg, mp4, wav, riff, wmv, mov, pdf, ole, doc, zip, rar, htm, and cpp).
– slm
Mar 31 '14 at 0:48
already running...let me wait for results. Will share.
– Patrick Mutwiri
Apr 15 '16 at 5:09
how much time does it take to finish?? for a 32GB usb memory
– Mina Michael
Mar 23 '17 at 23:17
add a comment |
I have used foremost to recover damaged hard disk both under NTFS (windows), FAT32 (Flash card from a Nokia phone) and ext3 with great results. Command line only, but quite it's easy, something like this:
sudo foremost -i /dev/sda -o <dir where recovered files will be stored>
It will order the recovered files on folders by file-type. Openoffice docs are recovered as zip files. As you need to execute it as root (in order to direct access the hardware), output files are also owned by root, so you will likely need to change their ownership afterwards.
I have used foremost to recover damaged hard disk both under NTFS (windows), FAT32 (Flash card from a Nokia phone) and ext3 with great results. Command line only, but quite it's easy, something like this:
sudo foremost -i /dev/sda -o <dir where recovered files will be stored>
It will order the recovered files on folders by file-type. Openoffice docs are recovered as zip files. As you need to execute it as root (in order to direct access the hardware), output files are also owned by root, so you will likely need to change their ownership afterwards.
answered Sep 9 '10 at 7:15
Javier RiveraJavier Rivera
29.8k977101
29.8k977101
This is probably too old question but, how does GIMP files look like after recovery?
– wakeup
Oct 3 '13 at 21:04
I don't know, I have never tried to recover them.
– Javier Rivera
Oct 4 '13 at 6:28
@JavierRivera - I do not believe thatforemost
can recover.xcf
files. See the man page it can only deal with these file types: (jpg, gif, png, bmp, avi, exe, mpg, mp4, wav, riff, wmv, mov, pdf, ole, doc, zip, rar, htm, and cpp).
– slm
Mar 31 '14 at 0:48
already running...let me wait for results. Will share.
– Patrick Mutwiri
Apr 15 '16 at 5:09
how much time does it take to finish?? for a 32GB usb memory
– Mina Michael
Mar 23 '17 at 23:17
add a comment |
This is probably too old question but, how does GIMP files look like after recovery?
– wakeup
Oct 3 '13 at 21:04
I don't know, I have never tried to recover them.
– Javier Rivera
Oct 4 '13 at 6:28
@JavierRivera - I do not believe thatforemost
can recover.xcf
files. See the man page it can only deal with these file types: (jpg, gif, png, bmp, avi, exe, mpg, mp4, wav, riff, wmv, mov, pdf, ole, doc, zip, rar, htm, and cpp).
– slm
Mar 31 '14 at 0:48
already running...let me wait for results. Will share.
– Patrick Mutwiri
Apr 15 '16 at 5:09
how much time does it take to finish?? for a 32GB usb memory
– Mina Michael
Mar 23 '17 at 23:17
This is probably too old question but, how does GIMP files look like after recovery?
– wakeup
Oct 3 '13 at 21:04
This is probably too old question but, how does GIMP files look like after recovery?
– wakeup
Oct 3 '13 at 21:04
I don't know, I have never tried to recover them.
– Javier Rivera
Oct 4 '13 at 6:28
I don't know, I have never tried to recover them.
– Javier Rivera
Oct 4 '13 at 6:28
@JavierRivera - I do not believe that
foremost
can recover .xcf
files. See the man page it can only deal with these file types: (jpg, gif, png, bmp, avi, exe, mpg, mp4, wav, riff, wmv, mov, pdf, ole, doc, zip, rar, htm, and cpp).– slm
Mar 31 '14 at 0:48
@JavierRivera - I do not believe that
foremost
can recover .xcf
files. See the man page it can only deal with these file types: (jpg, gif, png, bmp, avi, exe, mpg, mp4, wav, riff, wmv, mov, pdf, ole, doc, zip, rar, htm, and cpp).– slm
Mar 31 '14 at 0:48
already running...let me wait for results. Will share.
– Patrick Mutwiri
Apr 15 '16 at 5:09
already running...let me wait for results. Will share.
– Patrick Mutwiri
Apr 15 '16 at 5:09
how much time does it take to finish?? for a 32GB usb memory
– Mina Michael
Mar 23 '17 at 23:17
how much time does it take to finish?? for a 32GB usb memory
– Mina Michael
Mar 23 '17 at 23:17
add a comment |
extundelete is really great if your file system is ext3 or ext4.
Note: extundelete requires you to unmount your drive to work properly (this is a good idea to do ASAP anyway, to avoid potentially overwriting the hopefully-recoverable bytes in the deleted files).
Unmounting the drive on a live system can be tricky... you'll often get the 'device is busy
' message. To clear this 'properly' requires shutting down all processes accessing the file system. But... you were likely working in your home directory, and a zillion processes are hooked into your home directory, so good luck with that.
The trick to getting around this is to do a 'lazy' unmount:
$ mount
/dev/sda7 on /home type ext4 (rw)
$ sudo umount -l /home
where:
- that example is for me prepping my
/home
mount for use with extundelete. You obviously need to replace/home
with your mount of interest - I did the
mount
command first to figure out what device (/dev/sda7
) I need to pass to extundelete (output is truncated for brevity) - that is a lower case L in the
-l
option
4
A lazy unmount doesn't really help since the fs remains mounted until all files on it are closed. You just need to shut down the system as soon as you delete the files, and run extundelete from a livecd.
– psusi
Jul 7 '11 at 1:52
@psusi - It is absolutely untrue to say that it doesn't help!!umount -l
prevents any new files from being opened/created and written (web caches and such). However, it does not prevent existing opened files from still being written to (ie: it does not close existing files). You suggest shutting down, but I think a lazy unmount will (most of the time) result in less written files, depending on the partition in question. On that note, it is best is to have extundelete installed already, and if not, make sure to install it to some partition other than the one you are trying to recover!
– Russ
Jul 11 '11 at 15:30
As long as the fs is still mounted, attempting to access it will result in corruption. That is the reason that extundelete requires you unmount the fs in the first place. The lazy unmount simply fools it into thinking it is not mounted, and therefore, that it is safe to proceed with manipulating the disk, when that is not true. Proceeding with extundelete before the fs is actually dismounted can hose the whole disk.
– psusi
Jul 11 '11 at 18:15
1
@psusi - "can hose the whole disk"??! With a read-only operation? I don't get your argument, or what has you so paranoid. extundelete does not "manipulate the disk". The worst possible thing I can imagine happening is that extundelete expects an unmounted/static partitition and if, while reading the journal info, the lazily unmounted disk changes due to processes that had files open, extundelete may get confused and the recovery may fail. "possibly failed recovery" != "hosed disk". If it does fail, shut down, pray shutdown doesn't trash your lost data, and use a livecd as you suggest.
– Russ
Jul 12 '11 at 16:55
1
God bless this program! And you @Russ. Recovered all my files!
– Vladimir Kovalchuk
May 1 '17 at 4:10
|
show 1 more comment
extundelete is really great if your file system is ext3 or ext4.
Note: extundelete requires you to unmount your drive to work properly (this is a good idea to do ASAP anyway, to avoid potentially overwriting the hopefully-recoverable bytes in the deleted files).
Unmounting the drive on a live system can be tricky... you'll often get the 'device is busy
' message. To clear this 'properly' requires shutting down all processes accessing the file system. But... you were likely working in your home directory, and a zillion processes are hooked into your home directory, so good luck with that.
The trick to getting around this is to do a 'lazy' unmount:
$ mount
/dev/sda7 on /home type ext4 (rw)
$ sudo umount -l /home
where:
- that example is for me prepping my
/home
mount for use with extundelete. You obviously need to replace/home
with your mount of interest - I did the
mount
command first to figure out what device (/dev/sda7
) I need to pass to extundelete (output is truncated for brevity) - that is a lower case L in the
-l
option
4
A lazy unmount doesn't really help since the fs remains mounted until all files on it are closed. You just need to shut down the system as soon as you delete the files, and run extundelete from a livecd.
– psusi
Jul 7 '11 at 1:52
@psusi - It is absolutely untrue to say that it doesn't help!!umount -l
prevents any new files from being opened/created and written (web caches and such). However, it does not prevent existing opened files from still being written to (ie: it does not close existing files). You suggest shutting down, but I think a lazy unmount will (most of the time) result in less written files, depending on the partition in question. On that note, it is best is to have extundelete installed already, and if not, make sure to install it to some partition other than the one you are trying to recover!
– Russ
Jul 11 '11 at 15:30
As long as the fs is still mounted, attempting to access it will result in corruption. That is the reason that extundelete requires you unmount the fs in the first place. The lazy unmount simply fools it into thinking it is not mounted, and therefore, that it is safe to proceed with manipulating the disk, when that is not true. Proceeding with extundelete before the fs is actually dismounted can hose the whole disk.
– psusi
Jul 11 '11 at 18:15
1
@psusi - "can hose the whole disk"??! With a read-only operation? I don't get your argument, or what has you so paranoid. extundelete does not "manipulate the disk". The worst possible thing I can imagine happening is that extundelete expects an unmounted/static partitition and if, while reading the journal info, the lazily unmounted disk changes due to processes that had files open, extundelete may get confused and the recovery may fail. "possibly failed recovery" != "hosed disk". If it does fail, shut down, pray shutdown doesn't trash your lost data, and use a livecd as you suggest.
– Russ
Jul 12 '11 at 16:55
1
God bless this program! And you @Russ. Recovered all my files!
– Vladimir Kovalchuk
May 1 '17 at 4:10
|
show 1 more comment
extundelete is really great if your file system is ext3 or ext4.
Note: extundelete requires you to unmount your drive to work properly (this is a good idea to do ASAP anyway, to avoid potentially overwriting the hopefully-recoverable bytes in the deleted files).
Unmounting the drive on a live system can be tricky... you'll often get the 'device is busy
' message. To clear this 'properly' requires shutting down all processes accessing the file system. But... you were likely working in your home directory, and a zillion processes are hooked into your home directory, so good luck with that.
The trick to getting around this is to do a 'lazy' unmount:
$ mount
/dev/sda7 on /home type ext4 (rw)
$ sudo umount -l /home
where:
- that example is for me prepping my
/home
mount for use with extundelete. You obviously need to replace/home
with your mount of interest - I did the
mount
command first to figure out what device (/dev/sda7
) I need to pass to extundelete (output is truncated for brevity) - that is a lower case L in the
-l
option
extundelete is really great if your file system is ext3 or ext4.
Note: extundelete requires you to unmount your drive to work properly (this is a good idea to do ASAP anyway, to avoid potentially overwriting the hopefully-recoverable bytes in the deleted files).
Unmounting the drive on a live system can be tricky... you'll often get the 'device is busy
' message. To clear this 'properly' requires shutting down all processes accessing the file system. But... you were likely working in your home directory, and a zillion processes are hooked into your home directory, so good luck with that.
The trick to getting around this is to do a 'lazy' unmount:
$ mount
/dev/sda7 on /home type ext4 (rw)
$ sudo umount -l /home
where:
- that example is for me prepping my
/home
mount for use with extundelete. You obviously need to replace/home
with your mount of interest - I did the
mount
command first to figure out what device (/dev/sda7
) I need to pass to extundelete (output is truncated for brevity) - that is a lower case L in the
-l
option
answered Jul 6 '11 at 22:18
RussRuss
464511
464511
4
A lazy unmount doesn't really help since the fs remains mounted until all files on it are closed. You just need to shut down the system as soon as you delete the files, and run extundelete from a livecd.
– psusi
Jul 7 '11 at 1:52
@psusi - It is absolutely untrue to say that it doesn't help!!umount -l
prevents any new files from being opened/created and written (web caches and such). However, it does not prevent existing opened files from still being written to (ie: it does not close existing files). You suggest shutting down, but I think a lazy unmount will (most of the time) result in less written files, depending on the partition in question. On that note, it is best is to have extundelete installed already, and if not, make sure to install it to some partition other than the one you are trying to recover!
– Russ
Jul 11 '11 at 15:30
As long as the fs is still mounted, attempting to access it will result in corruption. That is the reason that extundelete requires you unmount the fs in the first place. The lazy unmount simply fools it into thinking it is not mounted, and therefore, that it is safe to proceed with manipulating the disk, when that is not true. Proceeding with extundelete before the fs is actually dismounted can hose the whole disk.
– psusi
Jul 11 '11 at 18:15
1
@psusi - "can hose the whole disk"??! With a read-only operation? I don't get your argument, or what has you so paranoid. extundelete does not "manipulate the disk". The worst possible thing I can imagine happening is that extundelete expects an unmounted/static partitition and if, while reading the journal info, the lazily unmounted disk changes due to processes that had files open, extundelete may get confused and the recovery may fail. "possibly failed recovery" != "hosed disk". If it does fail, shut down, pray shutdown doesn't trash your lost data, and use a livecd as you suggest.
– Russ
Jul 12 '11 at 16:55
1
God bless this program! And you @Russ. Recovered all my files!
– Vladimir Kovalchuk
May 1 '17 at 4:10
|
show 1 more comment
4
A lazy unmount doesn't really help since the fs remains mounted until all files on it are closed. You just need to shut down the system as soon as you delete the files, and run extundelete from a livecd.
– psusi
Jul 7 '11 at 1:52
@psusi - It is absolutely untrue to say that it doesn't help!!umount -l
prevents any new files from being opened/created and written (web caches and such). However, it does not prevent existing opened files from still being written to (ie: it does not close existing files). You suggest shutting down, but I think a lazy unmount will (most of the time) result in less written files, depending on the partition in question. On that note, it is best is to have extundelete installed already, and if not, make sure to install it to some partition other than the one you are trying to recover!
– Russ
Jul 11 '11 at 15:30
As long as the fs is still mounted, attempting to access it will result in corruption. That is the reason that extundelete requires you unmount the fs in the first place. The lazy unmount simply fools it into thinking it is not mounted, and therefore, that it is safe to proceed with manipulating the disk, when that is not true. Proceeding with extundelete before the fs is actually dismounted can hose the whole disk.
– psusi
Jul 11 '11 at 18:15
1
@psusi - "can hose the whole disk"??! With a read-only operation? I don't get your argument, or what has you so paranoid. extundelete does not "manipulate the disk". The worst possible thing I can imagine happening is that extundelete expects an unmounted/static partitition and if, while reading the journal info, the lazily unmounted disk changes due to processes that had files open, extundelete may get confused and the recovery may fail. "possibly failed recovery" != "hosed disk". If it does fail, shut down, pray shutdown doesn't trash your lost data, and use a livecd as you suggest.
– Russ
Jul 12 '11 at 16:55
1
God bless this program! And you @Russ. Recovered all my files!
– Vladimir Kovalchuk
May 1 '17 at 4:10
4
4
A lazy unmount doesn't really help since the fs remains mounted until all files on it are closed. You just need to shut down the system as soon as you delete the files, and run extundelete from a livecd.
– psusi
Jul 7 '11 at 1:52
A lazy unmount doesn't really help since the fs remains mounted until all files on it are closed. You just need to shut down the system as soon as you delete the files, and run extundelete from a livecd.
– psusi
Jul 7 '11 at 1:52
@psusi - It is absolutely untrue to say that it doesn't help!!
umount -l
prevents any new files from being opened/created and written (web caches and such). However, it does not prevent existing opened files from still being written to (ie: it does not close existing files). You suggest shutting down, but I think a lazy unmount will (most of the time) result in less written files, depending on the partition in question. On that note, it is best is to have extundelete installed already, and if not, make sure to install it to some partition other than the one you are trying to recover!– Russ
Jul 11 '11 at 15:30
@psusi - It is absolutely untrue to say that it doesn't help!!
umount -l
prevents any new files from being opened/created and written (web caches and such). However, it does not prevent existing opened files from still being written to (ie: it does not close existing files). You suggest shutting down, but I think a lazy unmount will (most of the time) result in less written files, depending on the partition in question. On that note, it is best is to have extundelete installed already, and if not, make sure to install it to some partition other than the one you are trying to recover!– Russ
Jul 11 '11 at 15:30
As long as the fs is still mounted, attempting to access it will result in corruption. That is the reason that extundelete requires you unmount the fs in the first place. The lazy unmount simply fools it into thinking it is not mounted, and therefore, that it is safe to proceed with manipulating the disk, when that is not true. Proceeding with extundelete before the fs is actually dismounted can hose the whole disk.
– psusi
Jul 11 '11 at 18:15
As long as the fs is still mounted, attempting to access it will result in corruption. That is the reason that extundelete requires you unmount the fs in the first place. The lazy unmount simply fools it into thinking it is not mounted, and therefore, that it is safe to proceed with manipulating the disk, when that is not true. Proceeding with extundelete before the fs is actually dismounted can hose the whole disk.
– psusi
Jul 11 '11 at 18:15
1
1
@psusi - "can hose the whole disk"??! With a read-only operation? I don't get your argument, or what has you so paranoid. extundelete does not "manipulate the disk". The worst possible thing I can imagine happening is that extundelete expects an unmounted/static partitition and if, while reading the journal info, the lazily unmounted disk changes due to processes that had files open, extundelete may get confused and the recovery may fail. "possibly failed recovery" != "hosed disk". If it does fail, shut down, pray shutdown doesn't trash your lost data, and use a livecd as you suggest.
– Russ
Jul 12 '11 at 16:55
@psusi - "can hose the whole disk"??! With a read-only operation? I don't get your argument, or what has you so paranoid. extundelete does not "manipulate the disk". The worst possible thing I can imagine happening is that extundelete expects an unmounted/static partitition and if, while reading the journal info, the lazily unmounted disk changes due to processes that had files open, extundelete may get confused and the recovery may fail. "possibly failed recovery" != "hosed disk". If it does fail, shut down, pray shutdown doesn't trash your lost data, and use a livecd as you suggest.
– Russ
Jul 12 '11 at 16:55
1
1
God bless this program! And you @Russ. Recovered all my files!
– Vladimir Kovalchuk
May 1 '17 at 4:10
God bless this program! And you @Russ. Recovered all my files!
– Vladimir Kovalchuk
May 1 '17 at 4:10
|
show 1 more comment
If you deleted some file by accident but still know some strings which were written in that file you can use:
grep -a -B 25 -A 100 'containing string' /dev/sda1 > result.txt
1
what if the file is binary and not text?
– Decio Lira
Sep 9 '10 at 12:11
Assuming it was text, how can he recover the file with result.txt? I'm not getting it..
– sergio91pt
Jul 2 '11 at 11:40
I tried several other prior answers. None of them worked. This simple trick did! Thanks!
– JamesThomasMoon1979
Jul 15 '15 at 17:41
Its really worked, awesome stuff. Thanks a lot.
– Snehal Parmar
Nov 24 '15 at 9:13
2
It should be noted that25
and100
are just some magic numbers that probably need to be tweaked for the specific case.
– Andrea Lazzarotto
Jun 24 '16 at 12:32
|
show 3 more comments
If you deleted some file by accident but still know some strings which were written in that file you can use:
grep -a -B 25 -A 100 'containing string' /dev/sda1 > result.txt
1
what if the file is binary and not text?
– Decio Lira
Sep 9 '10 at 12:11
Assuming it was text, how can he recover the file with result.txt? I'm not getting it..
– sergio91pt
Jul 2 '11 at 11:40
I tried several other prior answers. None of them worked. This simple trick did! Thanks!
– JamesThomasMoon1979
Jul 15 '15 at 17:41
Its really worked, awesome stuff. Thanks a lot.
– Snehal Parmar
Nov 24 '15 at 9:13
2
It should be noted that25
and100
are just some magic numbers that probably need to be tweaked for the specific case.
– Andrea Lazzarotto
Jun 24 '16 at 12:32
|
show 3 more comments
If you deleted some file by accident but still know some strings which were written in that file you can use:
grep -a -B 25 -A 100 'containing string' /dev/sda1 > result.txt
If you deleted some file by accident but still know some strings which were written in that file you can use:
grep -a -B 25 -A 100 'containing string' /dev/sda1 > result.txt
answered Sep 9 '10 at 11:39
NewProggie
1
what if the file is binary and not text?
– Decio Lira
Sep 9 '10 at 12:11
Assuming it was text, how can he recover the file with result.txt? I'm not getting it..
– sergio91pt
Jul 2 '11 at 11:40
I tried several other prior answers. None of them worked. This simple trick did! Thanks!
– JamesThomasMoon1979
Jul 15 '15 at 17:41
Its really worked, awesome stuff. Thanks a lot.
– Snehal Parmar
Nov 24 '15 at 9:13
2
It should be noted that25
and100
are just some magic numbers that probably need to be tweaked for the specific case.
– Andrea Lazzarotto
Jun 24 '16 at 12:32
|
show 3 more comments
1
what if the file is binary and not text?
– Decio Lira
Sep 9 '10 at 12:11
Assuming it was text, how can he recover the file with result.txt? I'm not getting it..
– sergio91pt
Jul 2 '11 at 11:40
I tried several other prior answers. None of them worked. This simple trick did! Thanks!
– JamesThomasMoon1979
Jul 15 '15 at 17:41
Its really worked, awesome stuff. Thanks a lot.
– Snehal Parmar
Nov 24 '15 at 9:13
2
It should be noted that25
and100
are just some magic numbers that probably need to be tweaked for the specific case.
– Andrea Lazzarotto
Jun 24 '16 at 12:32
1
1
what if the file is binary and not text?
– Decio Lira
Sep 9 '10 at 12:11
what if the file is binary and not text?
– Decio Lira
Sep 9 '10 at 12:11
Assuming it was text, how can he recover the file with result.txt? I'm not getting it..
– sergio91pt
Jul 2 '11 at 11:40
Assuming it was text, how can he recover the file with result.txt? I'm not getting it..
– sergio91pt
Jul 2 '11 at 11:40
I tried several other prior answers. None of them worked. This simple trick did! Thanks!
– JamesThomasMoon1979
Jul 15 '15 at 17:41
I tried several other prior answers. None of them worked. This simple trick did! Thanks!
– JamesThomasMoon1979
Jul 15 '15 at 17:41
Its really worked, awesome stuff. Thanks a lot.
– Snehal Parmar
Nov 24 '15 at 9:13
Its really worked, awesome stuff. Thanks a lot.
– Snehal Parmar
Nov 24 '15 at 9:13
2
2
It should be noted that
25
and 100
are just some magic numbers that probably need to be tweaked for the specific case.– Andrea Lazzarotto
Jun 24 '16 at 12:32
It should be noted that
25
and 100
are just some magic numbers that probably need to be tweaked for the specific case.– Andrea Lazzarotto
Jun 24 '16 at 12:32
|
show 3 more comments
To recover the directory you can use extundelete
Install extundelete
sudo apt-get install extundelete
Command to recover
sudo extundelete --restore-directory /home/Documents/ /dev/sda1
Note: In place of dev/sda1
put your hardisk partition name.
/home/Documents/
is your path to deleted directiory.
1
I usedautopsy
to find the inodes I needed and thenextundelete
to restore them. Worked well!
– Raphael
Dec 7 '14 at 13:05
My results looks.....~/Books$ sudo extundelete --restore-directory /home/newubuntu/Books/LaTeX /dev/sda2 WARNING: Extended attributes are not restored. Loading filesystem metadata ... 522 groups loaded. Loading journal descriptors ... 32242 descriptors loaded. Writing output to directory RECOVERED_FILES/ Failed to restore file /home/newubuntu/Books/LaTeX Could not find correct inode number past inode 2621441.
– alhelal
May 3 '17 at 2:51
I want to send confirmation in the command. How?
– alhelal
May 8 '18 at 14:01
sudo extundelete -y --restore-directory /home/Documents/ /dev/sda1
like this.
– alhelal
May 8 '18 at 14:02
add a comment |
To recover the directory you can use extundelete
Install extundelete
sudo apt-get install extundelete
Command to recover
sudo extundelete --restore-directory /home/Documents/ /dev/sda1
Note: In place of dev/sda1
put your hardisk partition name.
/home/Documents/
is your path to deleted directiory.
1
I usedautopsy
to find the inodes I needed and thenextundelete
to restore them. Worked well!
– Raphael
Dec 7 '14 at 13:05
My results looks.....~/Books$ sudo extundelete --restore-directory /home/newubuntu/Books/LaTeX /dev/sda2 WARNING: Extended attributes are not restored. Loading filesystem metadata ... 522 groups loaded. Loading journal descriptors ... 32242 descriptors loaded. Writing output to directory RECOVERED_FILES/ Failed to restore file /home/newubuntu/Books/LaTeX Could not find correct inode number past inode 2621441.
– alhelal
May 3 '17 at 2:51
I want to send confirmation in the command. How?
– alhelal
May 8 '18 at 14:01
sudo extundelete -y --restore-directory /home/Documents/ /dev/sda1
like this.
– alhelal
May 8 '18 at 14:02
add a comment |
To recover the directory you can use extundelete
Install extundelete
sudo apt-get install extundelete
Command to recover
sudo extundelete --restore-directory /home/Documents/ /dev/sda1
Note: In place of dev/sda1
put your hardisk partition name.
/home/Documents/
is your path to deleted directiory.
To recover the directory you can use extundelete
Install extundelete
sudo apt-get install extundelete
Command to recover
sudo extundelete --restore-directory /home/Documents/ /dev/sda1
Note: In place of dev/sda1
put your hardisk partition name.
/home/Documents/
is your path to deleted directiory.
edited Mar 8 '14 at 8:45
answered Feb 23 '14 at 15:01
Aatish SaiAatish Sai
767616
767616
1
I usedautopsy
to find the inodes I needed and thenextundelete
to restore them. Worked well!
– Raphael
Dec 7 '14 at 13:05
My results looks.....~/Books$ sudo extundelete --restore-directory /home/newubuntu/Books/LaTeX /dev/sda2 WARNING: Extended attributes are not restored. Loading filesystem metadata ... 522 groups loaded. Loading journal descriptors ... 32242 descriptors loaded. Writing output to directory RECOVERED_FILES/ Failed to restore file /home/newubuntu/Books/LaTeX Could not find correct inode number past inode 2621441.
– alhelal
May 3 '17 at 2:51
I want to send confirmation in the command. How?
– alhelal
May 8 '18 at 14:01
sudo extundelete -y --restore-directory /home/Documents/ /dev/sda1
like this.
– alhelal
May 8 '18 at 14:02
add a comment |
1
I usedautopsy
to find the inodes I needed and thenextundelete
to restore them. Worked well!
– Raphael
Dec 7 '14 at 13:05
My results looks.....~/Books$ sudo extundelete --restore-directory /home/newubuntu/Books/LaTeX /dev/sda2 WARNING: Extended attributes are not restored. Loading filesystem metadata ... 522 groups loaded. Loading journal descriptors ... 32242 descriptors loaded. Writing output to directory RECOVERED_FILES/ Failed to restore file /home/newubuntu/Books/LaTeX Could not find correct inode number past inode 2621441.
– alhelal
May 3 '17 at 2:51
I want to send confirmation in the command. How?
– alhelal
May 8 '18 at 14:01
sudo extundelete -y --restore-directory /home/Documents/ /dev/sda1
like this.
– alhelal
May 8 '18 at 14:02
1
1
I used
autopsy
to find the inodes I needed and then extundelete
to restore them. Worked well!– Raphael
Dec 7 '14 at 13:05
I used
autopsy
to find the inodes I needed and then extundelete
to restore them. Worked well!– Raphael
Dec 7 '14 at 13:05
My results looks
.....~/Books$ sudo extundelete --restore-directory /home/newubuntu/Books/LaTeX /dev/sda2 WARNING: Extended attributes are not restored. Loading filesystem metadata ... 522 groups loaded. Loading journal descriptors ... 32242 descriptors loaded. Writing output to directory RECOVERED_FILES/ Failed to restore file /home/newubuntu/Books/LaTeX Could not find correct inode number past inode 2621441.
– alhelal
May 3 '17 at 2:51
My results looks
.....~/Books$ sudo extundelete --restore-directory /home/newubuntu/Books/LaTeX /dev/sda2 WARNING: Extended attributes are not restored. Loading filesystem metadata ... 522 groups loaded. Loading journal descriptors ... 32242 descriptors loaded. Writing output to directory RECOVERED_FILES/ Failed to restore file /home/newubuntu/Books/LaTeX Could not find correct inode number past inode 2621441.
– alhelal
May 3 '17 at 2:51
I want to send confirmation in the command. How?
– alhelal
May 8 '18 at 14:01
I want to send confirmation in the command. How?
– alhelal
May 8 '18 at 14:01
sudo extundelete -y --restore-directory /home/Documents/ /dev/sda1
like this.– alhelal
May 8 '18 at 14:02
sudo extundelete -y --restore-directory /home/Documents/ /dev/sda1
like this.– alhelal
May 8 '18 at 14:02
add a comment |
R-Linux(Recovery studio) is one of the best. I have used this tool many times before. I worked at a company where they used the commercial version, 9/10 times it recovers everything you want. Truly superb application. Saved mine, and friends behinds many times before.
R-Linux is a free file recovery utility for the Ext2/Ext3/Ext4 FS
file system used in the Linux OS and several Unixes. R-Linux uses the
same InteligentScan technology as R-Studio, and flexible parameter
settings to provide the fastest and most reliable file recovery for
the Linux platform. However, unlike R-Studio, R-Linux cannot recover
data over network or reconstruct RAIDs, or provide object copy.
Features (from their website):
R-Linux recover files:
- Removed by virus attack, power failure or system crash;
- After the partition with the files was re-formatted, damaged, or deleted;
- When the partition structure on a disk was changed or damaged. In this case, R-Linux can scan the disk trying to find previously existing partitions and restore files from found partitions.
- From disks with bad sectors. In this case, R-Linux can first copy the entire disk or its part into an image file and then process the image file. This is especially useful when new bad sectors are constantly appearing on the disk, and remaining information must be immediately saved.
R-Linux Advanced features:
- Standard "Windows Explorer" - style interface.
- Host OS:
- Linux variant: Linux, kernel 2.6 and above
- Windows variant: Win2000, XP, 2003, Vista, Windows 7, Windows 8
- Supported file systems: Ext2/Ext3/Ext4 FS (Linux) only.
Recognition and parsing Dynamic (Windows 2000/XP/Vista/Win7), Basic, GPT and BSD (UNIX) partitions layout schema and Apple partition map. Dynamic partitions over GPT are supported as well as dynamic partitions over MBR.
Creates image files for an entire hard drive, logical disk, or its part. Such image files can be processed like regular disks. Images can be either simple exact object copies (Plain images) compatible with the old versions of R-Linux, or compressed images that can be compressed, split into several parts, and password-protected. Such images are fully compatible with the images created by R-Drive Image, but incompatible with the old versions of R-Linux.
Recognizes localized names.
- Recovered files can be saved on any (including network) disks accessible by the host operating system.
I didn't expect this to be free for Linux. I already know R-Studio and it is a fabulous software. Great that it's free for Linux filesystems.
– 0x01
Jun 12 '18 at 15:37
1
This tool is only free for recovering files less than 256kb
– Tik0
Aug 16 '18 at 8:38
add a comment |
R-Linux(Recovery studio) is one of the best. I have used this tool many times before. I worked at a company where they used the commercial version, 9/10 times it recovers everything you want. Truly superb application. Saved mine, and friends behinds many times before.
R-Linux is a free file recovery utility for the Ext2/Ext3/Ext4 FS
file system used in the Linux OS and several Unixes. R-Linux uses the
same InteligentScan technology as R-Studio, and flexible parameter
settings to provide the fastest and most reliable file recovery for
the Linux platform. However, unlike R-Studio, R-Linux cannot recover
data over network or reconstruct RAIDs, or provide object copy.
Features (from their website):
R-Linux recover files:
- Removed by virus attack, power failure or system crash;
- After the partition with the files was re-formatted, damaged, or deleted;
- When the partition structure on a disk was changed or damaged. In this case, R-Linux can scan the disk trying to find previously existing partitions and restore files from found partitions.
- From disks with bad sectors. In this case, R-Linux can first copy the entire disk or its part into an image file and then process the image file. This is especially useful when new bad sectors are constantly appearing on the disk, and remaining information must be immediately saved.
R-Linux Advanced features:
- Standard "Windows Explorer" - style interface.
- Host OS:
- Linux variant: Linux, kernel 2.6 and above
- Windows variant: Win2000, XP, 2003, Vista, Windows 7, Windows 8
- Supported file systems: Ext2/Ext3/Ext4 FS (Linux) only.
Recognition and parsing Dynamic (Windows 2000/XP/Vista/Win7), Basic, GPT and BSD (UNIX) partitions layout schema and Apple partition map. Dynamic partitions over GPT are supported as well as dynamic partitions over MBR.
Creates image files for an entire hard drive, logical disk, or its part. Such image files can be processed like regular disks. Images can be either simple exact object copies (Plain images) compatible with the old versions of R-Linux, or compressed images that can be compressed, split into several parts, and password-protected. Such images are fully compatible with the images created by R-Drive Image, but incompatible with the old versions of R-Linux.
Recognizes localized names.
- Recovered files can be saved on any (including network) disks accessible by the host operating system.
I didn't expect this to be free for Linux. I already know R-Studio and it is a fabulous software. Great that it's free for Linux filesystems.
– 0x01
Jun 12 '18 at 15:37
1
This tool is only free for recovering files less than 256kb
– Tik0
Aug 16 '18 at 8:38
add a comment |
R-Linux(Recovery studio) is one of the best. I have used this tool many times before. I worked at a company where they used the commercial version, 9/10 times it recovers everything you want. Truly superb application. Saved mine, and friends behinds many times before.
R-Linux is a free file recovery utility for the Ext2/Ext3/Ext4 FS
file system used in the Linux OS and several Unixes. R-Linux uses the
same InteligentScan technology as R-Studio, and flexible parameter
settings to provide the fastest and most reliable file recovery for
the Linux platform. However, unlike R-Studio, R-Linux cannot recover
data over network or reconstruct RAIDs, or provide object copy.
Features (from their website):
R-Linux recover files:
- Removed by virus attack, power failure or system crash;
- After the partition with the files was re-formatted, damaged, or deleted;
- When the partition structure on a disk was changed or damaged. In this case, R-Linux can scan the disk trying to find previously existing partitions and restore files from found partitions.
- From disks with bad sectors. In this case, R-Linux can first copy the entire disk or its part into an image file and then process the image file. This is especially useful when new bad sectors are constantly appearing on the disk, and remaining information must be immediately saved.
R-Linux Advanced features:
- Standard "Windows Explorer" - style interface.
- Host OS:
- Linux variant: Linux, kernel 2.6 and above
- Windows variant: Win2000, XP, 2003, Vista, Windows 7, Windows 8
- Supported file systems: Ext2/Ext3/Ext4 FS (Linux) only.
Recognition and parsing Dynamic (Windows 2000/XP/Vista/Win7), Basic, GPT and BSD (UNIX) partitions layout schema and Apple partition map. Dynamic partitions over GPT are supported as well as dynamic partitions over MBR.
Creates image files for an entire hard drive, logical disk, or its part. Such image files can be processed like regular disks. Images can be either simple exact object copies (Plain images) compatible with the old versions of R-Linux, or compressed images that can be compressed, split into several parts, and password-protected. Such images are fully compatible with the images created by R-Drive Image, but incompatible with the old versions of R-Linux.
Recognizes localized names.
- Recovered files can be saved on any (including network) disks accessible by the host operating system.
R-Linux(Recovery studio) is one of the best. I have used this tool many times before. I worked at a company where they used the commercial version, 9/10 times it recovers everything you want. Truly superb application. Saved mine, and friends behinds many times before.
R-Linux is a free file recovery utility for the Ext2/Ext3/Ext4 FS
file system used in the Linux OS and several Unixes. R-Linux uses the
same InteligentScan technology as R-Studio, and flexible parameter
settings to provide the fastest and most reliable file recovery for
the Linux platform. However, unlike R-Studio, R-Linux cannot recover
data over network or reconstruct RAIDs, or provide object copy.
Features (from their website):
R-Linux recover files:
- Removed by virus attack, power failure or system crash;
- After the partition with the files was re-formatted, damaged, or deleted;
- When the partition structure on a disk was changed or damaged. In this case, R-Linux can scan the disk trying to find previously existing partitions and restore files from found partitions.
- From disks with bad sectors. In this case, R-Linux can first copy the entire disk or its part into an image file and then process the image file. This is especially useful when new bad sectors are constantly appearing on the disk, and remaining information must be immediately saved.
R-Linux Advanced features:
- Standard "Windows Explorer" - style interface.
- Host OS:
- Linux variant: Linux, kernel 2.6 and above
- Windows variant: Win2000, XP, 2003, Vista, Windows 7, Windows 8
- Supported file systems: Ext2/Ext3/Ext4 FS (Linux) only.
Recognition and parsing Dynamic (Windows 2000/XP/Vista/Win7), Basic, GPT and BSD (UNIX) partitions layout schema and Apple partition map. Dynamic partitions over GPT are supported as well as dynamic partitions over MBR.
Creates image files for an entire hard drive, logical disk, or its part. Such image files can be processed like regular disks. Images can be either simple exact object copies (Plain images) compatible with the old versions of R-Linux, or compressed images that can be compressed, split into several parts, and password-protected. Such images are fully compatible with the images created by R-Drive Image, but incompatible with the old versions of R-Linux.
Recognizes localized names.
- Recovered files can be saved on any (including network) disks accessible by the host operating system.
edited Oct 9 '14 at 15:27
Seth♦
34.2k26110162
34.2k26110162
answered Oct 9 '14 at 8:10
blade19899blade19899
17.5k18100160
17.5k18100160
I didn't expect this to be free for Linux. I already know R-Studio and it is a fabulous software. Great that it's free for Linux filesystems.
– 0x01
Jun 12 '18 at 15:37
1
This tool is only free for recovering files less than 256kb
– Tik0
Aug 16 '18 at 8:38
add a comment |
I didn't expect this to be free for Linux. I already know R-Studio and it is a fabulous software. Great that it's free for Linux filesystems.
– 0x01
Jun 12 '18 at 15:37
1
This tool is only free for recovering files less than 256kb
– Tik0
Aug 16 '18 at 8:38
I didn't expect this to be free for Linux. I already know R-Studio and it is a fabulous software. Great that it's free for Linux filesystems.
– 0x01
Jun 12 '18 at 15:37
I didn't expect this to be free for Linux. I already know R-Studio and it is a fabulous software. Great that it's free for Linux filesystems.
– 0x01
Jun 12 '18 at 15:37
1
1
This tool is only free for recovering files less than 256kb
– Tik0
Aug 16 '18 at 8:38
This tool is only free for recovering files less than 256kb
– Tik0
Aug 16 '18 at 8:38
add a comment |
If using secondary internal HD (suspect the same for external HD) for recovered file import (from main HD, where the files originally were), it’s necessary to make a directory, into which the files will be put in on secondary HD.
To do it, you need to have BIOS setting for booting from CD first!
1. Start Live Ubuntu Rescue-Remix CD, give command to boot, then when it boots into terminal, check your HDs by command – Code: sudo fdisk -l
Realize what HD is main, and which is secondary, and what partition to check for files and into which to recover them – linux ext3 or Windows NTFS! Mine was Linux. Have enough room on it!
(Then you can try to run Photorec (“sudo photorec”) and hopefully you’ll be able to see all your HDs. I was not that lucky, so I had to make directory and mount sec. HD.)
- Make directory for recovered files first, e.g. – media/disk. Give command – Code:
sudo mkdir /media/disk
If alright, terminal prompt simply returns.
- Must mount secondary HD, or it’ll be invisible, even if “sudo fdisk -l” does show it. Give command for your secondary HD –
Code:sudo mount -t ext3 /dev/sdb2 /media/disk
If alright, terminal prompt simply returns.
Run Photorec by command – Code:
sudo photorec
Go thru settings, and only choose file types that you want, otherwise you’ll have thousands of files to sift thru!
For more details you may please visit: http:/www..ubuntumanual.org/posts/357/recover-your-deleted-files-in-ubuntu
add a comment |
If using secondary internal HD (suspect the same for external HD) for recovered file import (from main HD, where the files originally were), it’s necessary to make a directory, into which the files will be put in on secondary HD.
To do it, you need to have BIOS setting for booting from CD first!
1. Start Live Ubuntu Rescue-Remix CD, give command to boot, then when it boots into terminal, check your HDs by command – Code: sudo fdisk -l
Realize what HD is main, and which is secondary, and what partition to check for files and into which to recover them – linux ext3 or Windows NTFS! Mine was Linux. Have enough room on it!
(Then you can try to run Photorec (“sudo photorec”) and hopefully you’ll be able to see all your HDs. I was not that lucky, so I had to make directory and mount sec. HD.)
- Make directory for recovered files first, e.g. – media/disk. Give command – Code:
sudo mkdir /media/disk
If alright, terminal prompt simply returns.
- Must mount secondary HD, or it’ll be invisible, even if “sudo fdisk -l” does show it. Give command for your secondary HD –
Code:sudo mount -t ext3 /dev/sdb2 /media/disk
If alright, terminal prompt simply returns.
Run Photorec by command – Code:
sudo photorec
Go thru settings, and only choose file types that you want, otherwise you’ll have thousands of files to sift thru!
For more details you may please visit: http:/www..ubuntumanual.org/posts/357/recover-your-deleted-files-in-ubuntu
add a comment |
If using secondary internal HD (suspect the same for external HD) for recovered file import (from main HD, where the files originally were), it’s necessary to make a directory, into which the files will be put in on secondary HD.
To do it, you need to have BIOS setting for booting from CD first!
1. Start Live Ubuntu Rescue-Remix CD, give command to boot, then when it boots into terminal, check your HDs by command – Code: sudo fdisk -l
Realize what HD is main, and which is secondary, and what partition to check for files and into which to recover them – linux ext3 or Windows NTFS! Mine was Linux. Have enough room on it!
(Then you can try to run Photorec (“sudo photorec”) and hopefully you’ll be able to see all your HDs. I was not that lucky, so I had to make directory and mount sec. HD.)
- Make directory for recovered files first, e.g. – media/disk. Give command – Code:
sudo mkdir /media/disk
If alright, terminal prompt simply returns.
- Must mount secondary HD, or it’ll be invisible, even if “sudo fdisk -l” does show it. Give command for your secondary HD –
Code:sudo mount -t ext3 /dev/sdb2 /media/disk
If alright, terminal prompt simply returns.
Run Photorec by command – Code:
sudo photorec
Go thru settings, and only choose file types that you want, otherwise you’ll have thousands of files to sift thru!
For more details you may please visit: http:/www..ubuntumanual.org/posts/357/recover-your-deleted-files-in-ubuntu
If using secondary internal HD (suspect the same for external HD) for recovered file import (from main HD, where the files originally were), it’s necessary to make a directory, into which the files will be put in on secondary HD.
To do it, you need to have BIOS setting for booting from CD first!
1. Start Live Ubuntu Rescue-Remix CD, give command to boot, then when it boots into terminal, check your HDs by command – Code: sudo fdisk -l
Realize what HD is main, and which is secondary, and what partition to check for files and into which to recover them – linux ext3 or Windows NTFS! Mine was Linux. Have enough room on it!
(Then you can try to run Photorec (“sudo photorec”) and hopefully you’ll be able to see all your HDs. I was not that lucky, so I had to make directory and mount sec. HD.)
- Make directory for recovered files first, e.g. – media/disk. Give command – Code:
sudo mkdir /media/disk
If alright, terminal prompt simply returns.
- Must mount secondary HD, or it’ll be invisible, even if “sudo fdisk -l” does show it. Give command for your secondary HD –
Code:sudo mount -t ext3 /dev/sdb2 /media/disk
If alright, terminal prompt simply returns.
Run Photorec by command – Code:
sudo photorec
Go thru settings, and only choose file types that you want, otherwise you’ll have thousands of files to sift thru!
For more details you may please visit: http:/www..ubuntumanual.org/posts/357/recover-your-deleted-files-in-ubuntu
edited Oct 9 '14 at 8:14
blade19899
17.5k18100160
17.5k18100160
answered Jul 2 '11 at 11:23
AbhilashAbhilash
6911
6911
add a comment |
add a comment |
Try Scalpel
sudo apt-get install scalpel
for more info
man scalpel
trying it now. I don't quite understand how to add new files to the conf file. Do you have nay source with details?
– Decio Lira
Sep 9 '10 at 2:30
2
I found howtoforge.com/recover-deleted-files-with-scalpel which is better than nothing. Good luck, this ain't no MS-DOS.
– msw
Sep 9 '10 at 2:58
see also ubuntu.stackexchange.com/questions/2596/… I use a relatively heavy system backup, but have "Back in Time" set up to dup selected directories from /home/msw (including .config which also catches.config/keepassx/*
(your locations may vary)) to a spare partition nightly. I've also been using Unix since forever and you usually become pretty careful after the second time you blow awaythe-really-critical.file
;)
– msw
Sep 9 '10 at 3:06
Scalpel seems to be doing the same as foremost but while scalpel is no longer developed since 10 years, foremost got many updates in recent years.
– sebix
Aug 1 '15 at 18:41
add a comment |
Try Scalpel
sudo apt-get install scalpel
for more info
man scalpel
trying it now. I don't quite understand how to add new files to the conf file. Do you have nay source with details?
– Decio Lira
Sep 9 '10 at 2:30
2
I found howtoforge.com/recover-deleted-files-with-scalpel which is better than nothing. Good luck, this ain't no MS-DOS.
– msw
Sep 9 '10 at 2:58
see also ubuntu.stackexchange.com/questions/2596/… I use a relatively heavy system backup, but have "Back in Time" set up to dup selected directories from /home/msw (including .config which also catches.config/keepassx/*
(your locations may vary)) to a spare partition nightly. I've also been using Unix since forever and you usually become pretty careful after the second time you blow awaythe-really-critical.file
;)
– msw
Sep 9 '10 at 3:06
Scalpel seems to be doing the same as foremost but while scalpel is no longer developed since 10 years, foremost got many updates in recent years.
– sebix
Aug 1 '15 at 18:41
add a comment |
Try Scalpel
sudo apt-get install scalpel
for more info
man scalpel
Try Scalpel
sudo apt-get install scalpel
for more info
man scalpel
edited Apr 28 '12 at 19:08
Jorge Castro
36.1k105422617
36.1k105422617
answered Sep 9 '10 at 2:13
RojanRojan
3,48421214
3,48421214
trying it now. I don't quite understand how to add new files to the conf file. Do you have nay source with details?
– Decio Lira
Sep 9 '10 at 2:30
2
I found howtoforge.com/recover-deleted-files-with-scalpel which is better than nothing. Good luck, this ain't no MS-DOS.
– msw
Sep 9 '10 at 2:58
see also ubuntu.stackexchange.com/questions/2596/… I use a relatively heavy system backup, but have "Back in Time" set up to dup selected directories from /home/msw (including .config which also catches.config/keepassx/*
(your locations may vary)) to a spare partition nightly. I've also been using Unix since forever and you usually become pretty careful after the second time you blow awaythe-really-critical.file
;)
– msw
Sep 9 '10 at 3:06
Scalpel seems to be doing the same as foremost but while scalpel is no longer developed since 10 years, foremost got many updates in recent years.
– sebix
Aug 1 '15 at 18:41
add a comment |
trying it now. I don't quite understand how to add new files to the conf file. Do you have nay source with details?
– Decio Lira
Sep 9 '10 at 2:30
2
I found howtoforge.com/recover-deleted-files-with-scalpel which is better than nothing. Good luck, this ain't no MS-DOS.
– msw
Sep 9 '10 at 2:58
see also ubuntu.stackexchange.com/questions/2596/… I use a relatively heavy system backup, but have "Back in Time" set up to dup selected directories from /home/msw (including .config which also catches.config/keepassx/*
(your locations may vary)) to a spare partition nightly. I've also been using Unix since forever and you usually become pretty careful after the second time you blow awaythe-really-critical.file
;)
– msw
Sep 9 '10 at 3:06
Scalpel seems to be doing the same as foremost but while scalpel is no longer developed since 10 years, foremost got many updates in recent years.
– sebix
Aug 1 '15 at 18:41
trying it now. I don't quite understand how to add new files to the conf file. Do you have nay source with details?
– Decio Lira
Sep 9 '10 at 2:30
trying it now. I don't quite understand how to add new files to the conf file. Do you have nay source with details?
– Decio Lira
Sep 9 '10 at 2:30
2
2
I found howtoforge.com/recover-deleted-files-with-scalpel which is better than nothing. Good luck, this ain't no MS-DOS.
– msw
Sep 9 '10 at 2:58
I found howtoforge.com/recover-deleted-files-with-scalpel which is better than nothing. Good luck, this ain't no MS-DOS.
– msw
Sep 9 '10 at 2:58
see also ubuntu.stackexchange.com/questions/2596/… I use a relatively heavy system backup, but have "Back in Time" set up to dup selected directories from /home/msw (including .config which also catches
.config/keepassx/*
(your locations may vary)) to a spare partition nightly. I've also been using Unix since forever and you usually become pretty careful after the second time you blow away the-really-critical.file
;)– msw
Sep 9 '10 at 3:06
see also ubuntu.stackexchange.com/questions/2596/… I use a relatively heavy system backup, but have "Back in Time" set up to dup selected directories from /home/msw (including .config which also catches
.config/keepassx/*
(your locations may vary)) to a spare partition nightly. I've also been using Unix since forever and you usually become pretty careful after the second time you blow away the-really-critical.file
;)– msw
Sep 9 '10 at 3:06
Scalpel seems to be doing the same as foremost but while scalpel is no longer developed since 10 years, foremost got many updates in recent years.
– sebix
Aug 1 '15 at 18:41
Scalpel seems to be doing the same as foremost but while scalpel is no longer developed since 10 years, foremost got many updates in recent years.
– sebix
Aug 1 '15 at 18:41
add a comment |
Autopsy and the Sleuthkit tools are great for recovering deleted files, with a user-friendly UI, as well as being available in the repos.
good to know. will take a look at them. ;)
– Decio Lira
Oct 12 '10 at 19:03
1
I'd upvote it if you would have added some links.
– MadMike
Nov 14 '13 at 10:48
I usedautopsy
to find the inodes I needed and thenextundelete
to restore them. Worked well!
– Raphael
Dec 7 '14 at 13:03
add a comment |
Autopsy and the Sleuthkit tools are great for recovering deleted files, with a user-friendly UI, as well as being available in the repos.
good to know. will take a look at them. ;)
– Decio Lira
Oct 12 '10 at 19:03
1
I'd upvote it if you would have added some links.
– MadMike
Nov 14 '13 at 10:48
I usedautopsy
to find the inodes I needed and thenextundelete
to restore them. Worked well!
– Raphael
Dec 7 '14 at 13:03
add a comment |
Autopsy and the Sleuthkit tools are great for recovering deleted files, with a user-friendly UI, as well as being available in the repos.
Autopsy and the Sleuthkit tools are great for recovering deleted files, with a user-friendly UI, as well as being available in the repos.
answered Oct 12 '10 at 3:24
nathwillnathwill
2,2151017
2,2151017
good to know. will take a look at them. ;)
– Decio Lira
Oct 12 '10 at 19:03
1
I'd upvote it if you would have added some links.
– MadMike
Nov 14 '13 at 10:48
I usedautopsy
to find the inodes I needed and thenextundelete
to restore them. Worked well!
– Raphael
Dec 7 '14 at 13:03
add a comment |
good to know. will take a look at them. ;)
– Decio Lira
Oct 12 '10 at 19:03
1
I'd upvote it if you would have added some links.
– MadMike
Nov 14 '13 at 10:48
I usedautopsy
to find the inodes I needed and thenextundelete
to restore them. Worked well!
– Raphael
Dec 7 '14 at 13:03
good to know. will take a look at them. ;)
– Decio Lira
Oct 12 '10 at 19:03
good to know. will take a look at them. ;)
– Decio Lira
Oct 12 '10 at 19:03
1
1
I'd upvote it if you would have added some links.
– MadMike
Nov 14 '13 at 10:48
I'd upvote it if you would have added some links.
– MadMike
Nov 14 '13 at 10:48
I used
autopsy
to find the inodes I needed and then extundelete
to restore them. Worked well!– Raphael
Dec 7 '14 at 13:03
I used
autopsy
to find the inodes I needed and then extundelete
to restore them. Worked well!– Raphael
Dec 7 '14 at 13:03
add a comment |
Install scalpel
sudo apt-get install scalpel
Edit the scalpel.conf file and uncomment the file types you want to recover.
Create an empty folder (eg:recovered_data)
Find the partition your data was. You can use lsblk to get the partition map.
sudo lsblk
Run scalpel (assume the data was in sda1)
sudo scalpel -o recovered_data/ /dev/sda1
add a comment |
Install scalpel
sudo apt-get install scalpel
Edit the scalpel.conf file and uncomment the file types you want to recover.
Create an empty folder (eg:recovered_data)
Find the partition your data was. You can use lsblk to get the partition map.
sudo lsblk
Run scalpel (assume the data was in sda1)
sudo scalpel -o recovered_data/ /dev/sda1
add a comment |
Install scalpel
sudo apt-get install scalpel
Edit the scalpel.conf file and uncomment the file types you want to recover.
Create an empty folder (eg:recovered_data)
Find the partition your data was. You can use lsblk to get the partition map.
sudo lsblk
Run scalpel (assume the data was in sda1)
sudo scalpel -o recovered_data/ /dev/sda1
Install scalpel
sudo apt-get install scalpel
Edit the scalpel.conf file and uncomment the file types you want to recover.
Create an empty folder (eg:recovered_data)
Find the partition your data was. You can use lsblk to get the partition map.
sudo lsblk
Run scalpel (assume the data was in sda1)
sudo scalpel -o recovered_data/ /dev/sda1
answered Apr 10 '18 at 9:21
KasunKasun
313
313
add a comment |
add a comment |
Recently I used ext3grep to recover a large SQLite 3 file that was deleted from an ext3 file system.
I had tried many other undelete tools, all which couldn't recover the file (from a dd image of the disk).
In order to use ext3grep, I needed to download and compile the source. Carefully reading http://www.xs4all.nl/~carlo17/howto/undelete_ext3.html from top to bottom in order to understand how the ext3 file system works and how to use the journal to find where deleted files use to be on the disk was also required.
This is not a simple solution, but very, very powerful. If you're prepared to invest a few hours to study the document and compile the program, it's well worth it.
Thanks, I maybe try that. will this only work with ext3 file systems? What about ext4?
– Decio Lira
Sep 23 '10 at 17:28
I'm not sure about ext4 but I think ext4 is backward compatible to ext3. I would assume it would work but have never tried.
– Stacey Richards
Oct 21 '10 at 10:55
add a comment |
Recently I used ext3grep to recover a large SQLite 3 file that was deleted from an ext3 file system.
I had tried many other undelete tools, all which couldn't recover the file (from a dd image of the disk).
In order to use ext3grep, I needed to download and compile the source. Carefully reading http://www.xs4all.nl/~carlo17/howto/undelete_ext3.html from top to bottom in order to understand how the ext3 file system works and how to use the journal to find where deleted files use to be on the disk was also required.
This is not a simple solution, but very, very powerful. If you're prepared to invest a few hours to study the document and compile the program, it's well worth it.
Thanks, I maybe try that. will this only work with ext3 file systems? What about ext4?
– Decio Lira
Sep 23 '10 at 17:28
I'm not sure about ext4 but I think ext4 is backward compatible to ext3. I would assume it would work but have never tried.
– Stacey Richards
Oct 21 '10 at 10:55
add a comment |
Recently I used ext3grep to recover a large SQLite 3 file that was deleted from an ext3 file system.
I had tried many other undelete tools, all which couldn't recover the file (from a dd image of the disk).
In order to use ext3grep, I needed to download and compile the source. Carefully reading http://www.xs4all.nl/~carlo17/howto/undelete_ext3.html from top to bottom in order to understand how the ext3 file system works and how to use the journal to find where deleted files use to be on the disk was also required.
This is not a simple solution, but very, very powerful. If you're prepared to invest a few hours to study the document and compile the program, it's well worth it.
Recently I used ext3grep to recover a large SQLite 3 file that was deleted from an ext3 file system.
I had tried many other undelete tools, all which couldn't recover the file (from a dd image of the disk).
In order to use ext3grep, I needed to download and compile the source. Carefully reading http://www.xs4all.nl/~carlo17/howto/undelete_ext3.html from top to bottom in order to understand how the ext3 file system works and how to use the journal to find where deleted files use to be on the disk was also required.
This is not a simple solution, but very, very powerful. If you're prepared to invest a few hours to study the document and compile the program, it's well worth it.
answered Sep 23 '10 at 8:00
Stacey RichardsStacey Richards
385127
385127
Thanks, I maybe try that. will this only work with ext3 file systems? What about ext4?
– Decio Lira
Sep 23 '10 at 17:28
I'm not sure about ext4 but I think ext4 is backward compatible to ext3. I would assume it would work but have never tried.
– Stacey Richards
Oct 21 '10 at 10:55
add a comment |
Thanks, I maybe try that. will this only work with ext3 file systems? What about ext4?
– Decio Lira
Sep 23 '10 at 17:28
I'm not sure about ext4 but I think ext4 is backward compatible to ext3. I would assume it would work but have never tried.
– Stacey Richards
Oct 21 '10 at 10:55
Thanks, I maybe try that. will this only work with ext3 file systems? What about ext4?
– Decio Lira
Sep 23 '10 at 17:28
Thanks, I maybe try that. will this only work with ext3 file systems? What about ext4?
– Decio Lira
Sep 23 '10 at 17:28
I'm not sure about ext4 but I think ext4 is backward compatible to ext3. I would assume it would work but have never tried.
– Stacey Richards
Oct 21 '10 at 10:55
I'm not sure about ext4 but I think ext4 is backward compatible to ext3. I would assume it would work but have never tried.
– Stacey Richards
Oct 21 '10 at 10:55
add a comment |
protected by Community♦ Oct 9 '14 at 7:36
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
Related, but not really a duplicate: Can files/directories deleted from terminal be restored?
– Seth♦
Nov 6 '14 at 3:59