linux-ext4 - Re: Corrupt superblocks

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200911042256.50250.fabian-buettner@gmx.de>
Date:	Wed, 4 Nov 2009 22:56:49 +0100
From:	fabian-buettner@....de
To:	sandeen@...hat.com
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Corrupt superblocks

> Why do you say you have a corrupted superblock?

Because of this message: fsck.ext4: No such file or directory while trying to 
open /dev/vg/root
/dev/vg/root: The superblock could not be read or does not describe a correct 
ext2 filesystem ... at the end of this message i am told to run e2fsck -b 
8193 <device>

> I suppose I'd try booting a live/rescue cd, and just manually run e2fsck
> against your root device, as a starter - and capture any interesting
>  output.
> 
> Any sort of kernel or fsck logs indicating more of what actually went
> wrong would be Very helpful here.

I just booted into a rescue cd and run e2fsck /dev/vg/root.
surprisingly it said: /dev/vg/root: clean

- fabian
--
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