Sponsored Content
Top Forums UNIX for Advanced & Expert Users Linux EXT3 superblock recovery Post 302230023 by lochraven on Thursday 28th of August 2008 12:21:09 PM
Old 08-28-2008
I've tried that and here is what happens:

Code:
# fsck.ext3 -b 32768 /dev/sdb
Superblock has an invalid ext3 journal (inode 8).
Clear<y>?

I thought that command would update the superblock with a saved copy.

Is my interpretation of the man page correct?


If I answer 'y', then it says:
Quote:
*** ext3 journal has been deleted - filesystem is now ext2 only ***
Then it continues to try and fix additional inodes.

Does this mean that the superblock / filesystem is beyond recovering?

Last edited by Yogesh Sawant; 03-27-2011 at 02:11 PM.. Reason: added quote tags
 

9 More Discussions You Might Find Interesting

1. Linux

Help! Boot failure - corrupt superblock

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

How to corrupt a superblock?

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

superblock error

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

Linux HDD Recovery

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

linux system recovery after overriding connect() by "ld.so.preload"

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

Recovery of formatted ext3 partition

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

CentOS Error: Superblock

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

Superblock marked dirty

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

Linux bad superblock on /dev/mapper/VolGroup-lv_root

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
FSADM(8)																  FSADM(8)

NAME
fsadm - utility to resize or check filesystem on a device SYNOPSIS
fsadm [options] check device fsadm [options] resize device [new_size[BKMGTEP]] DESCRIPTION
fsadm utility checks or resizes the filesystem on a device. It tries to use the same API for ext2, ext3, ext4, ReiserFS and XFS filesys- tem. OPTIONS
-e, --ext-offline Unmount ext2/ext3/ext4 filesystem before doing resize. -f, --force Bypass some sanity checks. -h, --help Display the help text. -n, --dry-run Print commands without running them. -v, --verbose Be more verbose. -y, --yes Answer "yes" at any prompts. new_size Absolute number of filesystem blocks to be in the filesystem, or an absolute size using a suffix (in powers of 1024). If new_size is not supplied, the whole device is used. DIAGNOSTICS
On successful completion, the status code is 0. A status code of 2 indicates the operation was interrupted by the user. A status code of 3 indicates the requested check operation could not be performed because the filesystem is mounted and does not support an online fsck(8). A status code of 1 is used for other failures. EXAMPLES
Resize the filesystem on logical volume /dev/vg/test to 1000 megabytes. If /dev/vg/test contains ext2/ext3/ext4 filesystem it will be unmounted prior the resize. All [y|n] questions will be answered 'y'. fsadm -e -y resize /dev/vg/test 1000M ENVIRONMENT VARIABLES
TMPDIR The temporary directory name for mount points. Defaults to "/tmp". DM_DEV_DIR The device directory name. Defaults to "/dev" and must be an absolute path. SEE ALSO
lvm(8), lvresize(8), lvm.conf(5), fsck(8), tune2fs(8), resize2fs(8), reiserfstune(8), resize_reiserfs(8), xfs_info(8), xfs_growfs(8), xfs_check(8) Red Hat, Inc LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) FSADM(8)
All times are GMT -4. The time now is 10:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy