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: <4AF1F94B.5020108@redhat.com>
Date:	Wed, 04 Nov 2009 15:59:39 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	fabian-buettner@....de
CC:	linux-ext4@...r.kernel.org
Subject: Re: Corrupt superblocks

fabian-buettner@....de wrote:
>> 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>

Right, but:

# e2fsck /dev/a_file_that_i_made_up
e2fsck 1.41.4 (27-Jan-2009)
e2fsck: No such file or directory while trying to open
/dev/a_file_that_i_made_up

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>

all that means is /dev/vg/root doesn't exist and e2fsck can't even get
off the ground.  Note the "if the device is valid" part ...

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

so it sounds like your root vg isn't getting assembled properly in your
other situation, which is more of a block device / lvm problem than an
ext4 problem, I think.

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