Re: loop-AES mount problem

Thank you Jari,  I have solved the problem using the command fsck
# fsck -t ext3 -f -y /dev/loop1
but I still don't know why has this problem and why it was solved by command
fsck?

Peter Wang

----------------------------------------------------------------------------------------------------------------------------------------------
From: [email protected] [mailto:
[email protected]] On Behalf Of Jari Ruusu
Sent: Tuesday, February 19, 2008 3:05 AM
To: [email protected]
Subject: loop-AES mount problem

Hi Peter Wang,

Normally I would include your email address as recipient, but this time I
can't. For some reason [email protected] sends me only some subset
of the mails posted to the list. Your post was one of those that wasn't
delivered, but I saw it listed on one of the archives. Archives don't
include real email addresses, so I can't include your email address as a
recipient.

One possible reason why a mount could fail like that is that the gpg
encrypted key file wasn't created properly, or more specifically, it was
created for version of loop-AES that you were NOT running at the time the
file system was created. loop-AES README section 7 attempts to explain this
problem.

You can try to force the on-disk version to v2 like this:

 gpg --decrypt </root/datakey.gpg | head -n 64 | ( sleep 60 ; gpg
--symmetric -a >/root/datakey-v2.gpg )
 mount -t ext3 /dev/sda8 /mnt/crypt -o
loop=/dev/loop1,encryption=AES256,gpgkey=/root/datakey-v2.gpg

Or, you can try to force the on-disk version to v1 like this:

 gpg --decrypt </root/datakey.gpg | head -n 1 | ( sleep 60 ; gpg --symmetric
-a >/root/datakey-v1.gpg )
 mount -t ext3 /dev/sda8 /mnt/crypt -o
loop=/dev/loop1,encryption=AES256,gpgkey=/root/datakey-v1.gpg

-- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD



On Feb 18, 2008 10:17 AM, Peter Wang <[email protected]> wrote:

> I have created a crypto partition using loop-AES , but this morning when I
> tried to mount the partition , I got  this message
> # mount  /mnt/crypt
> # mount: wrong fs type, bad option, bad superblock on /dev/loop1,
>        missing codepage or other error
>        In some cases useful info is found in syslog - try
>        dmesg | tail  or so
>
> my /etc/fstab is :
> /dev/sda8  /mnt/crypt ext3
> defaults,noauto,loop=/dev/loop1,encryption=AES256,gpgkey=/root/datakey.gpg 0
> 0
>
> have anyone had the similar problem? Thanks!
>