10 More Discussions You Might Find Interesting
1. Solaris
I have a Sun sparc classic that I am trying to recover data off. The main CPU part just clicks or beeps when powered up, but does not come on (nothing on screen, and LED in front not lighting up).
There is also an external SCSI drive, and I have verified there is a drive inside the CPU.
... (8 Replies)
Discussion started by: mackconsult
8 Replies
2. Linux
Hi all. Not sure where to post this, so figured I'd start here. I have a LVM2 partition that has become unreadable. I've scoured dozens of threads about the topic and have hit a wall, so any advice is appreciated. Below is what I think shows what my major problem is:
First, a simple mount... (3 Replies)
Discussion started by: dargason
3 Replies
3. UNIX for Advanced & Expert Users
I accidentally deleted a very important directory today with this rm -r. What would be the recommended way to recover my directory? After a lot of googleing I have seen these choices. Could I get some recommendations please?
Testdisk
Photorec- Doesn't recover file name like I would like. ... (10 Replies)
Discussion started by: cokedude
10 Replies
4. UNIX for Dummies Questions & Answers
I have a flash drive which contained very important docs. But somebidy accidently dleted those files. I want to recover these files anyhow.
I have listened the Linux have best possible chances of recovering it.
Can anybody tell me how to recover that? (1 Reply)
Discussion started by: nixhead
1 Replies
5. High Performance Computing
Hi all,
I'm writing an MPI application, in which I handle failures and recover them. In order to do that, in case of one node failure, I would like to remove that node from the MPI_COMM_WORLD group and continue with the remaining nodes.
Does anybody know how I can do that?
I'm using... (5 Replies)
Discussion started by: SaTYR
5 Replies
6. SCO
I've been working with SCO Unix for several years now but have never had to restore a system from a bare drive.
I have a bootable CD that contains what appears to be the correct files necessary to recover the boot and root filesystems.
I've got the BIOS setup such that the CD is the first... (12 Replies)
Discussion started by: teamhog
12 Replies
7. UNIX for Dummies Questions & Answers
Hello,
By accident I erased a file at work and I need to restore it from a backup tape. My manager says I will have to use the mt command with the fsf option to look through the tape but I am confuzed. I did a restore -t to get a listing of the tape. This is taking a long time.
If I sound... (1 Reply)
Discussion started by: mojoman
1 Replies
8. UNIX for Dummies Questions & Answers
Hello,
Is there a way to recover data from a SCO UNIXWARE 7.4 operating system without using a tape backup device?
We believe there is some data in some directories that was there once; but not anymore, we don't have a backup on tape.
So, is there any other solution to recover?
Hope... (0 Replies)
Discussion started by: Yorgy
0 Replies
9. UNIX for Dummies Questions & Answers
Hello,
I was reading the manual on rm and it states that when you use 'rm' the files are usual recoverable, how is this done?
Does it assume that a backup system is in place?
Cheers
Jack (4 Replies)
Discussion started by: jack1981
4 Replies
10. SCO
I am helping a company recover a system that is SCO OS 5.0.5 - they have their backup media, cd copies of SCO, but they do not have their license keys to install and SCO is being difficult in validating their license.
Does anyone have an install license key for 5.0.5 that they would be willing... (1 Reply)
Discussion started by: ggraham
1 Replies
E2IMAGE(8) System Manager's Manual E2IMAGE(8)
NAME
e2image - Save critical ext2/ext3/ext4 filesystem metadata to a file
SYNOPSIS
e2image [ -rsI ] device image-file
DESCRIPTION
The e2image program will save critical ext2, ext3, or ext4 filesystem metadata located on device to a file specified by image-file. The
image file may be examined by dumpe2fs and debugfs, by using the -i option to those programs. This can assist an expert in recovering cat-
astrophically corrupted filesystems. In the future, e2fsck will be enhanced to be able to use the image file to help recover a badly dam-
aged filesystem.
If image-file is -, then the output of e2image will be sent to standard output, so that the output can be piped to another program, such as
gzip(1). (Note that this is currently only supported when creating a raw image file using the -r option, since the process of creating a
normal image file currently requires random access to the file, which cannot be done using a pipe. This restriction will hopefully be
lifted in a future version of e2image.)
It is a very good idea to create image files for all of filesystems on a system and save the partition layout (which can be generated using
the fdisk -l command) at regular intervals --- at boot time, and/or every week or so. The image file should be stored on some filesystem
other than the filesystem whose data it contains, to ensure that this data is accessible in the case where the filesystem has been badly
damaged.
To save disk space, e2image creates the image file as a sparse file. Hence, if the image file needs to be copied to another location, it
should either be compressed first or copied using the --sparse=always option to the GNU version of cp.
The size of an ext2 image file depends primarily on the size of the filesystems and how many inodes are in use. For a typical 10 gigabyte
filesystem, with 200,000 inodes in use out of 1.2 million inodes, the image file will be approximately 35 megabytes; a 4 gigabyte filesys-
tem with 15,000 inodes in use out of 550,000 inodes will result in a 3 megabyte image file. Image files tend to be quite compressible; an
image file taking up 32 megabytes of space on disk will generally compress down to 3 or 4 megabytes.
RESTORING FILESYSTEM METADATA USING AN IMAGE FILE
The -I option will cause e2image to install the metadata stored in the image file back to the device. It can be used to restore the
filesystem metadata back to the device in emergency situations.
WARNING!!!! The -I option should only be used as a desperation measure when other alternatives have failed. If the filesystem has changed
since the image file was created, data will be lost. In general, you should make a full image backup of the filesystem first, in case you
wish to try other recovery strategies afterwards.
RAW IMAGE FILES
The -r option will create a raw image file instead of a normal image file. A raw image file differs from a normal image file in two ways.
First, the filesystem metadata is placed in the proper position so that e2fsck, dumpe2fs, debugfs, etc. can be run directly on the raw
image file. In order to minimize the amount of disk space consumed by a raw image file, the file is created as a sparse file. (Beware of
copying or compressing/decompressing this file with utilities that don't understand how to create sparse files; the file will become as
large as the filesystem itself!) Secondly, the raw image file also includes indirect blocks and directory blocks, which the standard image
file does not have, although this may change in the future.
Raw image files are sometimes used when sending filesystems to the maintainer as part of bug reports to e2fsprogs. When used in this
capacity, the recommended command is as follows (replace hda1 with the appropriate device):
e2image -r /dev/hda1 - | bzip2 > hda1.e2i.bz2
This will only send the metadata information, without any data blocks. However, the filenames in the directory blocks can still reveal
information about the contents of the filesystem that the bug reporter may wish to keep confidential. To address this concern, the -s
option can be specified. This will cause e2image to scramble directory entries and zero out any unused portions of the directory blocks
before writing the image file. However, the -s option will prevent analysis of problems related to hash-tree indexed directories.
AUTHOR
e2image was written by Theodore Ts'o (tytso@mit.edu).
AVAILABILITY
e2image is part of the e2fsprogs package and is available from http://e2fsprogs.sourceforge.net.
SEE ALSO
dumpe2fs(8), debugfs(8)
E2fsprogs version 1.41.11 March 2010 E2IMAGE(8)
