linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jérôme Carretero" <cJ-ko@zougloub.eu>
To: 810d4rk <810d4rk@gmail.com>
Cc: sander@humilis.net, linux-btrfs@vger.kernel.org
Subject: Re: btrfs encryption problems
Date: Thu, 24 Nov 2011 16:54:29 -0500	[thread overview]
Message-ID: <20111124165429.10496040@Bidule> (raw)
In-Reply-To: <CAAVfQj=gM7ikTzdFmi=yNpo9guukQwFyKfdu7jD=z-J2PwrZEg@mail.gmail.com>

On Thu, 24 Nov 2011 21:43:50 +0000
810d4rk <810d4rk@gmail.com> wrote:

> > These printks indicate that the encryption or password is not the same as used when creating the device.
> > So at this stage, this has nothing to do with btrfs.
> 
> No, Ive decrypted the volume with the password, I can confirm it and
> also I haven't change it, BTW I have some new output from the kernel
> when trying to mount it:
>
> [21754.913248] usb 2-1.1: new high speed USB device number 20 using ehci_hcd
> [21755.119495] scsi45 : usb-storage 2-1.1:1.0
> [21757.616505] scsi 45:0:0:0: Direct-Access     WDC WD75
> 00BPVT-22HXZT1   01.0 PQ: 0 ANSI: 5
> [21757.633275] sd 45:0:0:0: Attached scsi generic sg4 type 0
> [21757.634765] sd 45:0:0:0: [sdc] 1465149168 512-byte logical blocks:
> (750 GB/698 GiB)
> [21757.635789] sd 45:0:0:0: [sdc] Write Protect is off
> [21757.635798] sd 45:0:0:0: [sdc] Mode Sense: 43 00 00 00
> [21757.637434] sd 45:0:0:0: [sdc] Write cache: disabled, read cache:
> enabled, doesn't support DPO or FUA
> [21757.727481]  sdc: sdc1
> [21757.730497] sd 45:0:0:0: [sdc] Attached SCSI disk
> [21757.737422] sd 45:0:0:0: [sdc]  Sense Key : Recovered Error
> [current] [descriptor]
> [21757.737438] Descriptor sense data with sense descriptors (in hex):
> [21757.737443]         72 01 04 1d 00 00 00 0e 09 0c 00 00 00 00 57 00
> [21757.737462]         00 00 00 00 00 50
> [21757.737472] sd 45:0:0:0: [sdc]  ASC=0x4 ASCQ=0x1d
> [21757.868565] sd 45:0:0:0: [sdc]  Sense Key : Recovered Error
> [current] [descriptor]
> [21757.868580] Descriptor sense data with sense descriptors (in hex):
> [21757.868585]         72 01 04 1d 00 00 00 0e 09 0c 00 00 00 00 00 00
> [21757.868604]         00 00 00 00 00 50
> [21757.868614] sd 45:0:0:0: [sdc]  ASC=0x4 ASCQ=0x1d
> [21777.246960] EXT3-fs (dm-1): error: can't find ext3 filesystem on dev dm-1.
> [21777.283216] EXT2-fs (dm-1): error: can't find an ext2 filesystem on dev dm-1.
> [21777.338992] EXT4-fs (dm-1): VFS: Can't find ext4 filesystem
> [21777.456509] REISERFS warning (device dm-1): sh-2021
> reiserfs_fill_super: can not find reiserfs on dm-1
> [21777.503417] XFS (dm-1): bad magic number
> [21777.503428] XFS (dm-1): SB validate failed
> [21777.622915] FAT-fs (dm-1): bogus number of reserved sectors
> [21777.622926] FAT-fs (dm-1): Can't find a valid FAT filesystem
> [21777.663109] FAT-fs (dm-1): bogus number of reserved sectors
> [21777.663120] FAT-fs (dm-1): Can't find a valid FAT filesystem

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 bigger one.
 (>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?).


++
-- 
cJ

  reply	other threads:[~2011-11-24 21:54 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 [this message]
2011-11-25 10:40           ` 810d4rk
2011-11-30 11:36             ` 810d4rk
2011-11-30 13:48             ` Chris Mason
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=20111124165429.10496040@Bidule \
    --to=cj-ko@zougloub.eu \
    --cc=810d4rk@gmail.com \
    --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).