08-28-2008
I let the fsck continue, answering 'y' to everything.
When it was finished I was able to mount the filesystem as ext2 and all data was still there.
9 More Discussions You Might Find Interesting
1. Linux
Hi everyone,
OK, I've made a monumental fsck-up of my linux installation AND I did not backup my data properly (idiot!), so I'm really up the proverbial without a paddle here.
Basically the problem is I re-sized my /home partition (hda13) using Partition Magic 8.0, after doing so my mandrake... (0 Replies)
Discussion started by: alarmcall
0 Replies
2. Solaris
I need to corrupt a superblock of a mounted device in a soalris m/c and check recovery from an alternate superblock. How can this be done? (2 Replies)
Discussion started by: sujathan
2 Replies
3. Red Hat
can anybody help me to recovermy superblock , the recent power crash has done some stuff on my linux redhat 9 box .
when i startup the machine iam getting the following error:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it... (2 Replies)
Discussion started by: ppass
2 Replies
4. Filesystems, Disks and Memory
Hello,
I have my backup disks here because my server got hacked and we didn't like how liquidweb made the things. So we ask them to ship us the disk. They ran photorec and they got lots of .gz files from it. All accounts I would say. But 50% of them the .tar.gz files came corrupt. And is lefting... (2 Replies)
Discussion started by: asturmas
2 Replies
5. UNIX for Advanced & Expert Users
dear fellows;
i have used ld.so.preload file to override connect() function, dynamic library overriding, it did worked really fine ......
but i went on to struck in a situation ... within the overrided connect() i have used printf once to see IP and Port to whom the connect request is being... (1 Reply)
Discussion started by: mzeeshan
1 Replies
6. Filesystems, Disks and Memory
Hi!
I have a really big problem right now. I (accidently) formatted a ext3 partition with "mkfs.ext3 /dev/sda1". The problem is that I REALLY need some files from there. The partition had a size of about 4GB, after accidently formatting it, I accidently rewrote Grub on it :wall: I hope I didn't... (3 Replies)
Discussion started by: al0x
3 Replies
7. Linux
Hi Guys,
I really don't know where to put my query about this. And as a newbie, I think CentOS is closest to Ubuntu. Anyway, here's my dilemma. I have installed a VMWare - ESX 3.5 and installed CentOS 6 and cloned the CentOS 6. The first CentOS was working fine, when i cloned it, and the cloning... (2 Replies)
Discussion started by: init6_
2 Replies
8. UNIX for Advanced & Expert Users
Good morning!
I met a problem on a FS with AIX 5.3
It's not possible to mount the FS because of a dirty superblock.
I tried few things without success. I need your help to solve my problem guys. Do you have any idea please?
Thanks a lot
drp01,/home/root # mount /GSPRES/data
Replaying... (9 Replies)
Discussion started by: Castelior
9 Replies
9. Red Hat
Hi Friends . my linux try to start very slowly after give it this error:
mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup-lv_root,
missing codepage or helper program, or other error
in some cases useful info is found in syslog - try
dmesg : tail or so
Kernel panic... (3 Replies)
Discussion started by: blackjuan
3 Replies
DUMPE2FS(8) System Manager's Manual DUMPE2FS(8)
NAME
dumpe2fs - dump ext2/ext3/ext4 filesystem information
SYNOPSIS
dumpe2fs [ -bfghixV ] [ -o superblock=superblock ] [ -o blocksize=blocksize ] device
DESCRIPTION
dumpe2fs prints the super block and blocks group information for the filesystem present on device.
Note: When used with a mounted filesystem, the printed information may be old or inconsistent.
OPTIONS
-b print the blocks which are reserved as bad in the filesystem.
-o superblock=superblock
use the block superblock when examining the filesystem. This option is not usually needed except by a filesystem wizard who is
examining the remains of a very badly corrupted filesystem.
-o blocksize=blocksize
use blocks of blocksize bytes when examining the filesystem. This option is not usually needed except by a filesystem wizard who is
examining the remains of a very badly corrupted filesystem.
-f force dumpe2fs to display a filesystem even though it may have some filesystem feature flags which dumpe2fs may not understand (and
which can cause some of dumpe2fs's display to be suspect).
-g display the group descriptor information in a machine readable colon-separated value format. The fields displayed are the group
number; the number of the first block in the group; the superblock location (or -1 if not present); the range of blocks used by the
group descriptors (or -1 if not present); the block bitmap location; the inode bitmap location; and the range of blocks used by the
inode table.
-h only display the superblock information and not any of the block group descriptor detail information.
-i display the filesystem data from an image file created by e2image, using device as the pathname to the image file.
-x print the detailed group information block numbers in hexadecimal format
-V print the version number of dumpe2fs and exit.
BUGS
You need to know the physical filesystem structure to understand the output.
AUTHOR
dumpe2fs was written by Remy Card <Remy.Card@linux.org>. It is currently being maintained by Theodore Ts'o <tytso@alum.mit.edu>.
AVAILABILITY
dumpe2fs is part of the e2fsprogs package and is available from http://e2fsprogs.sourceforge.net.
SEE ALSO
e2fsck(8), mke2fs(8), tune2fs(8). ext4(5)
E2fsprogs version 1.44.1 March 2018 DUMPE2FS(8)