From: Chris Mason <chris.mason@oracle.com>
To: 810d4rk <810d4rk@gmail.com>
Cc: "Jérôme Carretero" <cJ-ko@zougloub.eu>,
sander@humilis.net, linux-btrfs@vger.kernel.org
Subject: Re: btrfs encryption problems
Date: Wed, 30 Nov 2011 08:48:14 -0500 [thread overview]
Message-ID: <20111130134814.GW24338@shiny> (raw)
In-Reply-To: <CAAVfQjmmXnyCmXerCyymEQm-DhDxi0YSSo9sVSvkHE1WvJ4wYA@mail.gmail.com>
On Fri, Nov 25, 2011 at 10:40:00AM +0000, 810d4rk wrote:
> > My mistake, the same printks are printed when the encryption key is=
incorrect, I've seen that here.
> > It looks like you have some ugly hardware errors.
> > The kernel cannot read from the drive, so it cannot guess the file =
system on it.
> > If the data is valuable, you could try to ddrescue the drive to a b=
igger one.
> > =A0(>750GB... and that will take time...) and attempt to mount the =
rescued data.
> > If the drive is in an USB enclosure, you could plug it directly via=
SATA to the system (maybe it has issues?).
>=20
> The hard drive is brand new, I also plugged it directly via eSATA and
> checked the SMART data and run some tests and it succeeded in all, if
> I format the drive again I have a working file-system for sure but
> some of my data that is not on the backup disk will be gone.. I had
> some time ago on opensuse tumbleweed a encrypted btrfs system and it
> was gone some time ago like this external hard drive, I also had
> various btrfs hard drives without encryption and they never failed,
> and I will make a image of the disk but that will be later because I
> don't have a backup hard drive bigger than 750gb, maybe btrfs fsck ca=
n
> restore my disk when it is officially released?
If you plug it in directly with esata, do the IO errors go away? If so=
,
please post the kernel messages from that.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-30 13:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 10:38 btrfs encryption problems 810d4rk
2011-11-23 11:09 ` Sander
2011-11-23 19:38 ` 810d4rk
2011-11-24 20:56 ` 810d4rk
2011-11-24 21:06 ` Jérôme Carretero
2011-11-24 21:43 ` 810d4rk
2011-11-24 21:54 ` Jérôme Carretero
2011-11-25 10:40 ` 810d4rk
2011-11-30 11:36 ` 810d4rk
2011-11-30 13:48 ` Chris Mason [this message]
2011-11-30 22:15 ` 810d4rk
2011-12-13 6:52 ` 810d4rk
2011-12-13 6:56 ` Fajar A. Nugraha
2011-12-13 11:58 ` 810d4rk
2011-12-15 19:44 ` 810d4rk
2011-12-15 23:49 ` Mitch Harder
2011-12-23 14:25 ` 810d4rk
2012-03-13 15:50 ` 810d4rk
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=20111130134814.GW24338@shiny \
--to=chris.mason@oracle.com \
--cc=810d4rk@gmail.com \
--cc=cJ-ko@zougloub.eu \
--cc=linux-btrfs@vger.kernel.org \
--cc=sander@humilis.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).