From: Eric Sandeen <sandeen@redhat.com>
To: Mark Ballard <markjballard@googlemail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Corrupted superblock? But disk still mounts.
Date: Tue, 19 Aug 2014 09:36:43 -0500 [thread overview]
Message-ID: <53F360FB.1090809@redhat.com> (raw)
In-Reply-To: <CAMJSjjucoP1rGRYKECEb=eoLz29bZQ=z=GHgaz+TUYDf=815ng@mail.gmail.com>
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
next prev parent reply other threads:[~2014-08-19 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 18:14 Corrupted superblock? But disk still mounts Mark Ballard
2014-08-18 18:37 ` Eric Sandeen
2014-08-18 20:23 ` Mark Ballard
2014-08-19 14:36 ` Eric Sandeen [this message]
2014-08-22 14:19 ` Mark Ballard
2014-08-22 16:09 ` Eric Sandeen
2014-08-22 16:40 ` Mark Ballard
2014-08-22 17:19 ` Darrick J. Wong
2014-08-22 17:38 ` Eric Sandeen
2014-08-22 17:20 ` Eric Sandeen
2014-08-22 18:21 ` Mark Ballard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53F360FB.1090809@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=markjballard@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.