linux-ext4 - Re: Corrupted superblock? But disk still mounts.

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: <53F360FB.1090809@redhat.com>
Date:	Tue, 19 Aug 2014 09:36:43 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Mark Ballard <markjballard@...glemail.com>
CC:	linux-ext4@...r.kernel.org
Subject: Re: Corrupted superblock? But disk still mounts.

On 8/18/14, 3:23 PM, Mark Ballard wrote:
>> I'm guessing that it's the encryption getting in your way.
> 
> Cheers, Eric. Does rather look that way. But for the sake of a user report...
> 
>>
>> How is /dev/sdb1 encrypted?  Usually this is done with something like dm-crypt.
>> Or is it hardware encryption managed in the bios?  Did you unlock it?
> 
> Done with crytpsetup using luks.
> 
>>
>> What does "blkid /dev/sdb1" say?
>>
> 
> It says Luks.

and not ext4 - so you need to unlock it via mumblemumbleLuksStuffmumblemumble
before you can operate on it with e2fsprogs tools.

# cryptsetup luksOpen /dev/sdb1 <name>... or something.  Sorry, I'm not a LUKS
expert...

Anyway, not an ext4 problem.  Your superblock isn't corrupted, it's encrypted.  :)

-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