Displaying 4 results from an estimated 4 matches for "dump2ef".
Did you mean:
dump2efs
2002 Jul 25
1
(no subject)
...stem. Receive the following error message:
-- e2fsck: Bad magic number in superblock while trying to open /dev/sda1
-- Superblock could not be read or does not describe a correct ext2 filesystem.
Well it's not of type ext2 but of ext3. Tried using a different superblock value (was able to run dump2efs to determine backup superblocks) but still not successful with repairing the filesystem. I ran
tune2fs -j /dev/sda1
to make sure the filesystem has the journal inode and it does.
I'm at a lost and would like suggestions on possbile solutions. I've thought about copying the root files...
2002 Jul 25
0
root filesystem problem
...stem. Receive the following error message:
-- e2fsck: Bad magic number in superblock while trying to open /dev/sda1
-- Superblock could not be read or does not describe a correct ext2 filesystem.
Well it's not of type ext2 but of ext3. Tried using a different superblock value (was able to run dump2efs to determine backup superblocks) but still not successful with repairing the filesystem. I ran
tune2fs -j /dev/sda1
to make sure the filesystem has the journal inode and it does.
I'm at a lost and would like suggestions on possbile solutions. I've thought about copying the root files...
2007 Apr 04
1
fsck.ext3 reporting large file I cannot find
...journal? It is a large drive (500GB), so
maybe a large file got generated which normally might appear smaller on a
smaller drive.
I tried ls -sal and other flags with ls looking for the large file. I also ran
dump2fs, although the output can be somewhat complex.
I included the beginning of the dump2efs output below my fsck.ext3 output.
Thanks,
Edmond
-----
[root at localhost sbin]# /sbin/fsck.ext3 -f -v -n /dev/sda1
e2fsck 1.35 (28-Feb-2004)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts...
2008 Dec 21
2
corruption happening sometimes when I do a shutdown -r now
Hi all,
Apologies but this is going to be a long post.
I get a corruption sometime when I do a $sudo shutdown -r now
This is on an ubuntu 8.10 machine.
The only way to resolve the same I know is to do a sudo fsck -y /dev/sdb7
This is the output I got when I ran fsck through the Live CD
$ sudo fsck -y /dev/sdb7
fsck 1.41.3 (12-Oct-2008)
e2fsck 1.41.3 (12-Oct-2008)
/dev/sdb7 contains a file