FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 06-03-2011, 03:40 PM
Mervyn Zhang
 
Default LUKS-partition-failed-to-mount

Well, it was at first the debian-installer commands(options in the
text expert mode, I don't know the exact ones):

making /dev/sda5 a ext2, /boot partition and making /dev/sda6 a lvm
one on top of a LUKS crypted partition.

When I was about to boot arch, the grub commands should be:

root (hd0,2)
kernel /vmlinuz26-lts root=/dev/mapper/cryptpool-cryptroot
cryptdevice=/dev/sda4:cryptpv resume=/dev/mapper/cryptpool-cryptswap
ro
initrd /kernel26-lts.img
boot

(where the "cryptpool" is the name of the VG, "cryptpv" is PV)

2011/6/3, Cal Leeming [Simplicity Media Ltd]
<cal.leeming@simplicitymedialtd.co.uk>:
> Please show us the commands you are trying to execute, in order.
>
> On Fri, Jun 3, 2011 at 4:07 PM, Mervyn Zhang <karboninnov@gmail.com> wrote:
>
>> Hi all, I'm a debian newbie who are previously using archlinux. I've a
>> disk with the following layout:
>>
>> sda1 pri - Windows partition;
>> sda3 pri - archlinux /boot
>> sda4 pri - archlinux LUKS partition (with lvm in it, the rest
>> partitions /, /var, swap and most important /home)
>> sda5 logic - debian /boot
>> sda6 logic - debian LUKS partition (with lvm in it, where a base
>> just-installed system lies)
>>
>> My two arch partitions remained untouched during the installation of
>> debian, and no bootloaders was installed since I've already a grub
>> installed in the MBR.
>>
>> But when I tried to boot my arch again, the crypt hook reported that
>>
>> "ERROR:Failed to open encryption mapping: The device /dev/sda4 is not
>> a LUKS volume and the crypto= parameter was not specified."
>>
>> So what can I do now to re-access to at least my data? Thank you VERY
>> MUCH since I forgot to backup them first....
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmaster@lists.debian.org
>> Archive:
>> http://lists.debian.org/BANLkTi=tFf3QGR7k4Ma=LxYOeEXFn2-V+Q@mail.gmail.com
>>
>>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTi=4MkJjJxpiNVvAuKA6kdkrrmm0CA@mail.gmail.com ">http://lists.debian.org/BANLkTi=4MkJjJxpiNVvAuKA6kdkrrmm0CA@mail.gmail.com
 
Old 06-03-2011, 03:41 PM
"Cal Leeming [Simplicity Media Ltd]"
 
Default LUKS-partition-failed-to-mount

Ah, I've never used crypt on the system partition before.. sorry, can't help

On Fri, Jun 3, 2011 at 4:40 PM, Mervyn Zhang <karboninnov@gmail.com> wrote:

Well, it was at first the debian-installer commands(options in the

text expert mode, I don't know the exact ones):



making /dev/sda5 a ext2, /boot partition and making /dev/sda6 a lvm

one on top of a LUKS crypted partition.



When I was about to boot arch, the grub commands should be:



root (hd0,2)

kernel /vmlinuz26-lts root=/dev/mapper/cryptpool-cryptroot

cryptdevice=/dev/sda4:cryptpv resume=/dev/mapper/cryptpool-cryptswap

ro

initrd /kernel26-lts.img

boot



(where the "cryptpool" is the name of the VG, "cryptpv" is PV)



2011/6/3, Cal Leeming [Simplicity Media Ltd]

<cal.leeming@simplicitymedialtd.co.uk>:

> Please show us the commands you are trying to execute, in order.

>

> On Fri, Jun 3, 2011 at 4:07 PM, Mervyn Zhang <karboninnov@gmail.com> wrote:

>

>> Hi all, I'm a debian newbie who are previously using archlinux. I've a

>> disk with the following layout:

>>

>> sda1 pri - Windows partition;

>> sda3 pri - archlinux /boot

>> sda4 pri - archlinux LUKS partition (with lvm in it, the rest

>> partitions /, /var, swap and most important /home)

>> sda5 logic - debian /boot

>> sda6 logic - debian LUKS partition (with lvm in it, where a base

>> just-installed system lies)

>>

>> My two arch partitions remained untouched during the installation of

>> debian, and no bootloaders was installed since I've already a grub

>> installed in the MBR.

>>

>> But when I tried to boot my arch again, the crypt hook reported that

>>

>> "ERROR:Failed to open encryption mapping: The device /dev/sda4 is not

>> a LUKS volume and the crypto= parameter was not specified."

>>

>> So what can I do now to re-access to at least my data? Thank you VERY

>> MUCH since I forgot to backup them first....

>>

>>

>> --

>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org

>> with a subject of "unsubscribe". Trouble? Contact

>> listmaster@lists.debian.org

>> Archive:

>> http://lists.debian.org/BANLkTi=tFf3QGR7k4Ma=LxYOeEXFn2-V+Q@mail.gmail.com

>>

>>

>
 
Old 06-03-2011, 04:16 PM
"tv.debian@googlemail.com"
 
Default LUKS-partition-failed-to-mount

03/06/2011 17:07, Mervyn Zhang wrote:
> Hi all,
Hi,

I'm a debian newbie who are previously using archlinux. I've a
> disk with the following layout:
>
> sda1 pri - Windows partition;
> sda3 pri - archlinux /boot
> sda4 pri - archlinux LUKS partition (with lvm in it, the rest
> partitions /, /var, swap and most important /home)
> sda5 logic - debian /boot
> sda6 logic - debian LUKS partition (with lvm in it, where a base
> just-installed system lies)
>
> My two arch partitions remained untouched during the installation of
> debian, and no bootloaders was installed since I've already a grub
> installed in the MBR.
>
> But when I tried to boot my arch again, the crypt hook reported that
>
> "ERROR:Failed to open encryption mapping: The device /dev/sda4 is not
> a LUKS volume and the crypto= parameter was not specified."
>
> So what can I do now to re-access to at least my data? Thank you VERY
> MUCH since I forgot to backup them first....
>
>

First you could try to access your luks partitions from a live cd (use
one with cryptsetup on board, or install it on the live-cd):

(as root)

cryptsetup luksOpen /dev/sda4 cryptarch


then you partition will be available on /dev/mapper/cryptarch, you can
create a mount point and try to mount it there:

mkdir /mnt/cryptarch
mount /dev/mapper/cryptarch /mnt/cryptarch

If this doesn't work, try to gather informations on you luks with:

cryptsetup status cryptarch

You can also try to work with UUID rather than devices name, as UUID
will remain stable (see cryptsetup luksUUID).

There is always the possibility that partitions names got mixed-up
during Debian installed, and you overwrite you arch partitions (bad), or
the luks headers got corrupted somehow, equally bad if you never made a
backup of the headers. In both cases your data would be lost (hope it's
just a partition address problem).


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4DE908C1.2060606@googlemail.com">http://lists.debian.org/4DE908C1.2060606@googlemail.com
 

Thread Tools




All times are GMT. The time now is 04:19 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org