I'm posting here in the in the hope that someone can help (Jari?)
In any case, I was running loop-AES on two separate machines, my laptop and my
workstation (loop-aes 3.0a, loop-aes-ciphers 3.0a, aespipe 2.3a,
loop-aes-utils 2.12p, all built as debs) on kernel 2.6.9. I recompiled the
kernels on both, removing loop and cryptoloop, as stated in the
loop-AES.README. I created a partition (/dev/vg00/lv_crypt) and followed
example 2 from the loop-AES.README. Mounted the partition, set up keys (65
keys, gpg encrypted, stored on my USB thumb drive). Was able to mount the
partition and copy my data over. Everything was copecetic, until I upgraded
the machines to 2.6.10. Now when I try to mount
the encrypted partition, I get
[storm@volga ~]$ mount ../docs/
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
dmesg tells me
ReiserFS: loop0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs
on loop3
Even if I boot back into 2.6.9, the same indications occur. I upgraded to
3.0b, and am getting the same indications. Anyone know why
this is happening or a method to recover the info on the partition? Nothing
changed on the machines other than the kernels and the loop-aes modules with
the kernels.
Regards,
--
--Brad
========================================================================
Bradley M. Alexander |
IA Analyst, SysAdmin, Security Engineer | storm [at] tux.org
Debian/GNU Linux Developer | storm [at] debian.org
========================================================================
Key fingerprints:
DSA 0x54434E65: 37F6 BCA6 621D 920C E02E E3C8 73B2 C019 5443 4E65
RSA 0xC3BCBA91: 3F 0E 26 C1 90 14 AD 0A C8 9C F0 93 75 A0 01 34
========================================================================
I'm not into working out. My philosophy is no pain, no pain.
--George Carlin
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
