CentOS 5 :: Unable To Recover Deleted Files From Ext3 Partition?
Feb 10, 2011
I am using CentOS 5.5.I suppose this is an oft repeated question. I accidentally deleted, using rm command, 2 wmv files. The files were in a single ext3 1Tb drive, with just 1 partition --- the ext3 one. Each file is 600 - 800mb. The 1Tb drive has only about 20Gb data.Immediately after deleting the files i unmounted the drive (/dev/sdc1). Thereafter i searched the the net and came to know of the recovery tools foremost and photorec. I have installed both of them. I am currently running both of them as root --- foremost is just showing a lot of * signs on the terminal and photorec has managed to find some txt and png files --- but no wmv.For foremost i used: /usr/sbin/foremost -t wmv -i /dev/sdc1For photorec i followed some instructions available on the web.
In the meantime, based on some post on the net i ran debugfs as root, then cd into the directory where the files were deleted. Then on typing ls -d i managed to get the inodes of the 2 deleted files and the names of the deleted files are also correct. The instructions on the net http://www.theavidcoder.com/?p=3 tell me to run fsstat and dls both of which i am unable to find in /bin, /usr/bin, /usr/sbin and /sbin. So i am unable to proceed further.
recover deleted files using "debugfs" & "extundelete" by running:Code:sudo debugfs /dev/sda3 and find inode number of deleted file using "ls -d" command and then running:Code:sudo extundelete /dev/sda3 --restore-file <inode#>but when my desired file was in a deleted folder I can't find my desired file inode number using debugfs
A HP Netserver LP2000r, with original SCSI controller and HP NetRaid-2M controller, 3x 36GB Ultra3 HDD in RAID5, Debian (sarge/etch), has crashed after 992 days without reboot. From all that I can see, a hardware failure, most likely with the memory. The HP Diagnostic tools cannot find any problem, but everytime I boot into Knoppix, I get between 2minutes and 2 hours of runtime, and then either a kernel oops or just a complete and sudden halt.
Well, the box has earned its money. However, there is some data on the drives that I need to recover (yes, I have beaten myself up properly about not backing up that data, don't even go there !). There are three partitions: sda1 is /, sda2 is swap and sda3 is a LVM volume with 3 logical volumes on it. As far as I can tell, the hardware defect must have been creeping in and has made a total mess of the inodes in all these partitions.
After booting into Knoppix, I can restore the volumes using pvscan, vgscan, lvscan, vgcfgrestore and vgchange. If I try and mount them: mayhem. So I try and check them, using fsck.ext3. All sorts of interesting nonsense, such as a completely empty inode 11 (the first inode) and then obviously from there on all else is pointless. I tried using debugfs, but the information on what to do with it is somewhat spurious.
P.S.: Tomorrow I will go and get myself a 16GB Flash Drive and then hopefully I will be able to dump the partitions one by one onto that drive and transfer the images onto a different computer for analysis and data recovery.
I used the ext3 format when I formatted my partition prior to installing Ubuntu10.10. I had accidentally deleted a file and began the process to get it back. It wasn't critical but helpful to recover the file. To make a long story short I ran into to some unexpected road blocks. I tried to use PhotoRec to get the job done but with no success.
I'm just looking down the road in the event I might have to recover something important.If it would be better going back to the Fat32 file system I would rather do it sooner than later. Just as a side note I am dual booting between linux and windows.
I wanted to upgrade from Intrepid to Jaunty. I opted for a format/reinstall as I figured upgrading usually sucks. To save my important data, I resized my partition (partition A), formatted the empty space with ext3 (now partition B), and moved the necessary files from partition A to partition B. Then I went through the install process and installed Jaunty on partition A, telling the installer to NOT format partition B. It gave a warning about the installer deleting system folders (var, usr, etc) but I figured it didn't apply. I was wrong.
So now partition B is "empty." I know it didn't format it, but I need to get those files off of there. I have created an image of partition B using ddrescue, but I don't know where to go from there. I tried using foremost, but it won't recover things like my virtual machines and completely nukes the original file structure I had. And I've tried mounting it (using sudo mount -t ext3 -o loop /home/user/recovery.img /mnt), but that doesn't seem to work. The mount command completes successfully, but nothing shows up in the folder I mounted it to.
I was installing windows vista on my computer, so I backed up everything to a external drive which was formatted with ext2. I then proceeded to install windows vista. When I got to the partition section I tried installing windows vista to my raid 0. When it didn't work I decided that I would delete all my existing partitions and create a new one. Well in my haste I accidentally deleted my ext2 partition from my backup drive that was still connected. As soon as I realized what I had done I shutdown the windows install and disconnected my external drive. This is the current state of my drive from parted:
Model: WD 15EADS External (scsi) Disk /dev/sdb: 1500GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags
I know that the drive only had one partition before and that it took up the entire disk and it was ext2 (maybe ext3).
I am facing a serious problem.I installed UBUNTU 10.04 and encrypted it during installation. I accidentally erased some of the necessary files from root folder. now the the OS is NOT booting.luckily i still have the encryption key i have some important documents in that drive (desktop folder).
PS: I have tried to run Live Ubuntu it shows the Root, but it does not enter any of the folder.
Now am terribly frustrated because i reinstalled my linux installation(Ubuntu 8.04) after falling prey to an inode error. So i reinstalled stuff under my root partition under which i had some files which i obviously lost.I have tried recovering the files (mostly mp3 files) using photorec and the max file size i managed to recover was 4.0MB. the rest fall in the tune of 300kb.My question is, is there a way to make a full recovery of the above files seeing that they indeed can be recovered?
My laptop has two os. one is windows vista. and other is Ubuntu. I am currently on ubuntu system, this is my primary OS.There are 4 partitions of my hard diskWindows OSLinux(Ubuntu OSData Now the problem part. The data partition is NTFS. I have mounted this partition on the location /media/windrive-a under ubuntu OS.A little while back i decided to delete the mounting of the data partition and i fired command rm -r /media/windrive-a/. To give me a shock; all my data on data drive is gone.Now, I know this is not the command to remove mounted partition. But I have committed the wrong. Is there any way i can get my data back. These are very important data for me.
Deleted a whole bunch of files, I have backed it up but it was from about 2 weeks ago and as I had added loads of stuff in the meantime I urgently need to recover the files.Ubuntu 9.10. Any and every file recovery program you know please.Preferably one that allows me to recover an entire directory, not just individual files, but it'll be fine if that is it.
Yesterday I accidentaly deleted all files from my desktop (with rm). Now I am looking for way how to recover them.
I tried to use scalpel to recover them which found many files (more than 800000 zip files). I stopped the process cause It would take ages. I would like to recover files only from desktop folder. Is this possible?
I moved a few files from a directory in my home directory structure to the KDE trash folder, and then deleted them from the trash folder. About a minute later I regretted this, and now I'd like to see if there's any way to recover the files. First, are there any good utilities for restoring accidentally deleted files? If so, where would I look for these files? Does the KDE trash config file actually correspond to a physical directory somewhere, or do the files just remain hidden in their original location?
I wiped out 60% of my VirtualBox .vdi files on one of my partions. The file sizes ranged from 3gb to 9gb files. (I did have some backups but 4 months ago). Needless to say I'll be backing my files up more often (especially my Virtual Image .vdi files). So here are the steps...: [ Look, I know it seems like allot of steps, but its worth it in the end!!]
(By the way, these are all ext3 filesystems, I would imagine you could recover fat32 [windows} type filesystems too, but I just did this under Linux filesystems) 1--> If you've found yourself deleted any files, try to unmount the partition. ( In my case it was an external 2 1/2 hard drive, command used to unmount is sudo umount /dev/sda3)
1b--> If you only have one partition, then I'd suggest shutting down your computer and putting a Live CD in it (preferably the Ubuntu Live CD).
2--> Whether 1 or 1b applies to you, install ext3grep from Synaptic or any package manager. (if you had to reboot via a live CD, make sure you unmount the partition that has the deleted files.(example umount /dev/sda1 or in my case it was umount /dev/sda3). If you're on the LiveCD of Ubuntu, I believe it will let you install the ext3grep package using Synaptic Package manager and it will put it in RAM under the Live Desktop Session.
3--> Now here's the important part before you proceed any further. If the partition that has the deleted files is taking up 30gb (yes 30gb used space), then you have to mount an existing partition GREATER than 30gb ***FREE*** SPACE. I happened to have another partition /media/sda7 already mounted that had 50 gb free.
So at this point, you must go to any directory under your (recovery partition, i'm referring to my 50gb partition /media/sda7). To do this, run the command cd /media/sda7, now you're in your (recovery partition). You can make a new directory if you want, or just use any existing directory on the /media/sda7 partition. (I made a directory something like mkdir ./Yikes ) So I get into the directory by cd /media/sda7/Yikes then run the following command....:
ext3grep --restore-all /dev/sda3
4--> ***Keep in mind, you just ran that command from the /media/sda7/Yikes directory on your recovery partition. ***This will create a folder called "RESTORED_FILES" under/in the Yikes Directory.*** The ext3grep command you just submitted will try to recover every single file on that partition that has the deleted files (i.e. /dev/sda3). There is a way to restore single files and their paths, but I got frustrated and just did a full restore.
5--> Depending on the partition size and number of files, it could take 30 minutes to 2 hours or more before you start to see messages in the terminal screen saying "Restored file... Abc.txt or sam.jpg". Let it finish!!! At first you will see it saying "Group 1, Group 2 and crazy characters going across the screen, that's normal." You know it's begining the actual restore process when you start to see "Restored file...".
6--> At this point you can open a DIFFERENT terminal screen and do cd /media/sda7/Yikes/RESTORED_FILES to see the files being restored under the various directories. This does work because I was able to restore at least 25gb worth of files. Again, file sizes ranged from 3gb to 9gb!!
7--> Final step when the 1st terminal screen is done restoring the files, you can either open them up from the /media/sda7/Yikes/RESTORED_FILES directory to check them out, or you can copy them back to where they were deleted before. BUT I WOULD SAY TO MAKE A BACKUP OF THE RESTORED FILES, or keep the restored files in the /media/sda7 partition.
-->Again, I did a "ext3grep --restore-all /dev/sda3" command from the partition that had plenty of free space (i.e. 50gb) to restore the 30 gb worth of deleted files (and that ext3grep --restore-all /dev/sda3 command was run in the following directory /media/sda7/Yikes ).
-->Remember to unmount the /dev/sda3 partition (i.e. the partition that has the deleted files). DO NOT MOUNT /devs/sda3 when running the ext3grep --restore-all command. The ext3grep documentation states you don't want to write anything to that partition because you run the risk of writing over files or directories that could be recovered.
-->This ext3grep utility saved me Big Time!! 4 to 5 months of work restored because of this utility. You can get it from Synaptic Package Manger searching for ext3grep.
I just downloaded, burned, and tried the ISO image. only to find out it's not a bootable, live CD, but rather a Windows program, ie. it requires booting into Windows and running it from the CD, which is not a good idea since the first thing to do in this case is to quit the OS to prevent it from using those newly available sectors to write new data. can a Linux-based live CD try and recover files recently deleted in an NTFS partition?
I cannot boot into by Ubuntu 9.1 machine.... Trying either GUI or rescue mode gives me the following error messages (which i copied by hand since they were in cli)
Code: mount : mounting /dev/disk/by-uuid/64e5cb0d-058a-4a4c-af4b-7afb6427a72e3 on root failed : invalid argument
mount : mounting /sys on /root/sys failed : no such file or directory mount : mounting /dev on /root/dev failed : no such file or directory mount : mounting /proc on /root/proc failed : no such file or directory
Target doesnt have /sbin/init The only thing i remember doing before this is deleting some bootloader files... but they were on another disk so I didn't think that it would affect my ubuntu install. Guess I was wrong how I can recover my system?
With the release of CentOS 5.5 ext4 is considered stable in this distribution so I decided to migrate to it. Luckily I started from migrating fresh server with CentOS 5.5 using some instruction I found on the internet. I think I shouldn�t say, that I screwed the whole thing up ;) After about 6 hours cursing, kicking, and crying I solved the task and figured the correct sequence of actions. The small problem with migrating root partition is that you can�t unmount it BTW.
During migration task, I found, that CentOS 5.5 rescue mode is somewhat broken a little in terms of ext4 support. It can mount ext4 partitions successfully. But its e2fsprogs package (tune2fs, e2fsck etc.) doesnt see ext4 partitions and say, that superblock is corrupted on a partition once is converted to ext4 (at least it did it for me. May be I should force filesystem type with -t ext4 switch?). Keep in mind, that if you screw your system up too badly, you will not be able to run tune2fs and e2fsck on it from rescue modeBut you will still able to mount it if it is not corrupted badly. In all below examples,Boot your system normally and login as root. Upgrade kernel if you wish (I usually use yum upgrade to upgrade all on new machines). Then upgrade/install some other packages