linux-ext4 - ext4 fs recovery

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <71330BF9-B4D0-4BDB-A9B7-655872791FA3@brillgene.com>
Date:	Sat, 10 Apr 2010 04:32:49 +0530
From:	Anshuman Aggarwal <anshuman@...llgene.com>
To:	linux-ext4@...r.kernel.org
Subject: ext4 fs recovery 

Hi all,
 I have an ext4 partition which is unable to find its superblock on e2fsck. 

#e2fsck -n /dev/VGdata/LVstore 
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/VGdata/LVstore

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>


# e2fsck -n -b 8193 /dev/VGdata/LVstore 
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Bad magic number in super-block while trying to open /dev/VGdata/LVstore

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>


Any ideas on how to proceed?

How I got here was due to a failed disk which I have ddrescued over but seems to have missing corrupt metadata.

Thanks,
Anshuman--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html