loop-Aes mount problem HELP ;\ - Linux
This is a discussion on loop-Aes mount problem HELP ;\ - Linux ; Hi
I have just updated FC4 to FC5 and my problems begin.
I can't mount partition.
I have compiled linux-2.6.16.1 kernel with CONFIG_BLK_DEV_LOOP = n
I've installed loop-AES-v3.1c.tar.bz2 and util-linux-2.12r.tar.gz patched.
Everything seems to be ok
[root@fox src]# uname -r
...
-
loop-Aes mount problem HELP ;\
Hi
I have just updated FC4 to FC5 and my problems begin.
I can't mount partition.
I have compiled linux-2.6.16.1 kernel with CONFIG_BLK_DEV_LOOP = n
I've installed loop-AES-v3.1c.tar.bz2 and util-linux-2.12r.tar.gz patched.
Everything seems to be ok
[root@fox src]# uname -r
2.6.16.1
[root@fox loop-AES-v3.1c]# make tests
....
md5sum test-file1 >test-file2
echo "e12fd55fbae9fc0e03517593e253e239 test-file1" | cmp test-file2 -
cmp test-file3 test-file4
make[1]: Leaving directory `/usr/src/loop-AES-v3.1c'
rm -f -r test-file[1234] test-dir1
*** Test results ok ***
--- fstab ----------------
/dev/hda4 /mnt/szyfr ext2
defaults,noauto,user,loop=/dev/loop0,encryption=AES128,gpgkey=/home/keyfile.gpg
0 0
--- fstab ----------------
Unfortunately when I make
[root@fox loop-AES-v3.1c]# mount /mnt/szyfr/
Password:
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Password is ok I'm sure.
What is wrong ?
Have I forgotten about something?
regards
vr
-
Re: loop-Aes mount problem HELP ;\
vr wrote:
>
> Hi
> I have just updated FC4 to FC5 and my problems begin.
> I can't mount partition.
>
> I have compiled linux-2.6.16.1 kernel with CONFIG_BLK_DEV_LOOP = n
> I've installed loop-AES-v3.1c.tar.bz2 and util-linux-2.12r.tar.gz patched.
> Everything seems to be ok
>
> [root@fox src]# uname -r
> 2.6.16.1
>
> [root@fox loop-AES-v3.1c]# make tests
> ...
> md5sum test-file1 >test-file2
> echo "e12fd55fbae9fc0e03517593e253e239 test-file1" | cmp test-file2 -
> cmp test-file3 test-file4
> make[1]: Leaving directory `/usr/src/loop-AES-v3.1c'
> rm -f -r test-file[1234] test-dir1
> *** Test results ok ***
>
>
> --- fstab ----------------
> /dev/hda4 /mnt/szyfr ext2
> defaults,noauto,user,loop=/dev/loop0,encryption=AES128,gpgkey=/home/keyfile.gpg
> 0 0
> --- fstab ----------------
>
> Unfortunately when I make
>
> [root@fox loop-AES-v3.1c]# mount /mnt/szyfr/
> Password:
> mount: wrong fs type, bad option, bad superblock on /dev/loop0,
> missing codepage or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
>
> Password is ok I'm sure.
>
> What is wrong ?
> Have I forgotten about something?
A module you need to load, perhaps?
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
-
Re: loop-Aes mount problem HELP ;\
Bill Davidsen wrote:
> vr wrote:
>
>>
>> Hi
>> I have just updated FC4 to FC5 and my problems begin.
>> I can't mount partition.
>>
>> I have compiled linux-2.6.16.1 kernel with CONFIG_BLK_DEV_LOOP = n
>> I've installed loop-AES-v3.1c.tar.bz2 and util-linux-2.12r.tar.gz
>> patched.
>> Everything seems to be ok
>>
>> [root@fox src]# uname -r
>> 2.6.16.1
>>
>> [root@fox loop-AES-v3.1c]# make tests
>> ...
>> md5sum test-file1 >test-file2
>> echo "e12fd55fbae9fc0e03517593e253e239 test-file1" | cmp test-file2 -
>> cmp test-file3 test-file4
>> make[1]: Leaving directory `/usr/src/loop-AES-v3.1c'
>> rm -f -r test-file[1234] test-dir1
>> *** Test results ok ***
>>
>>
>> --- fstab ----------------
>> /dev/hda4 /mnt/szyfr ext2
>> defaults,noauto,user,loop=/dev/loop0,encryption=AES128,gpgkey=/home/keyfile.gpg
>> 0 0
>> --- fstab ----------------
>>
>> Unfortunately when I make
>>
>> [root@fox loop-AES-v3.1c]# mount /mnt/szyfr/
>> Password:
>> mount: wrong fs type, bad option, bad superblock on /dev/loop0,
>> missing codepage or other error
>> In some cases useful info is found in syslog - try
>> dmesg | tail or so
>>
>> Password is ok I'm sure.
>>
>> What is wrong ?
>> Have I forgotten about something?
>
>
> A module you need to load, perhaps?
>
In some cases useful info is found in syslog - try "dmesg | tail" or so