Hi.
Have a problem that i need som help with:
1. Have multipple raids working in a encrypted filesystem in CentOS 5.4 (i386):
script file, crypt.sh
modprobe cryptoloop
losetup -e aes /dev/loop0 /dev/md0
(inserting password here)
then run
mount -t ext3 /dev/loop0 /mnt/raid5
Have been using this in CentOS for a long time and works like a charm.
2. Raids is now moved to another server with ubuntu server 9.10 (64bit)
Raid is detected fine and working.
Do the same thing again and get:
sudo modprobe cryptoloop (ok)
sudo losetup -e aes /dev/loop0 /dev/md0 (ok)
sudo mount -t ext3 /dev/loop0 /mnt/raid5 (failes with the following msg)
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
ubuntu: cat /proc/crypto |grep aes
name : ecb(aes)
driver : ecb(aes-asm)
name : cbc(aes)
driver : cbc(aes-asm)
name : cbc(aes)
driver : cbc(aes-asm)
name : aes
driver : aes-asm
module : aes_x86_64
name : aes
driver : aes-generic
module : aes_generic
Is there compatible issues here?
Can it be that the old server was using i386 arch and the new is 64bit?
losetup version differs?
Any insight is appreciated.
On Thu, Jan 21, 2010 at 09:41:37AM +0100, Morten Sundstr?m wrote:> Hi. > > Have a problem that i need som help with: > 1. Have multipple raids working in a encrypted filesystem in CentOS 5.4 (i386): script file, crypt.sh > > modprobe cryptoloop >cryptoloop is depracated, and should not be used. Use dm-crypt instead, or if you have to, loop-aes. -- Pasi> losetup -e aes /dev/loop0 /dev/md0 > (inserting password here) > then run > mount -t ext3 /dev/loop0 /mnt/raid5 > Have been using this in CentOS for a long time and works like a charm. > > 2. Raids is now moved to another server with ubuntu server 9.10 (64bit) > Raid is detected fine and working. > > Do the same thing again and get: > sudo modprobe cryptoloop (ok) > sudo losetup -e aes /dev/loop0 /dev/md0 (ok) > sudo mount -t ext3 /dev/loop0 /mnt/raid5 (failes with the following msg) > mount: wrong fs type, bad option, bad superblock on /dev/loop0, > missing codepage or helper program, or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > ubuntu: cat /proc/crypto |grep aes > name : ecb(aes) > driver : ecb(aes-asm) > name : cbc(aes) > driver : cbc(aes-asm) > name : cbc(aes) > driver : cbc(aes-asm) > name : aes > driver : aes-asm > module : aes_x86_64 > name : aes > driver : aes-generic > module : aes_generic > > Is there compatible issues here? > Can it be that the old server was using i386 arch and the new is 64bit? > losetup version differs? > > Any insight is appreciated. > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos
I know about that. Is that the reason it wont work in ubuntu? If I switch to a new encryption i must copy all the data to a new raid wich is not possible at the moment. I need to get this mounted. /MS ----- Original Message ----- Fra: "Pasi K?rkk?inen" <pasik at iki.fi> Til: "CentOS mailing list" <centos at centos.org> Sendt: 21. januar 2010 09:57:24 Emne: Re: [CentOS] cryptoloop On Thu, Jan 21, 2010 at 09:41:37AM +0100, Morten Sundstr?m wrote:> Hi. > > Have a problem that i need som help with: > 1. Have multipple raids working in a encrypted filesystem in CentOS 5.4 (i386): script file, crypt.sh > > modprobe cryptoloop >cryptoloop is depracated, and should not be used. Use dm-crypt instead, or if you have to, loop-aes. -- Pasi> losetup -e aes /dev/loop0 /dev/md0 > (inserting password here) > then run > mount -t ext3 /dev/loop0 /mnt/raid5 > Have been using this in CentOS for a long time and works like a charm. > > 2. Raids is now moved to another server with ubuntu server 9.10 (64bit) > Raid is detected fine and working. > > Do the same thing again and get: > sudo modprobe cryptoloop (ok) > sudo losetup -e aes /dev/loop0 /dev/md0 (ok) > sudo mount -t ext3 /dev/loop0 /mnt/raid5 (failes with the following msg) > mount: wrong fs type, bad option, bad superblock on /dev/loop0, > missing codepage or helper program, or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > ubuntu: cat /proc/crypto |grep aes > name : ecb(aes) > driver : ecb(aes-asm) > name : cbc(aes) > driver : cbc(aes-asm) > name : cbc(aes) > driver : cbc(aes-asm) > name : aes > driver : aes-asm > module : aes_x86_64 > name : aes > driver : aes-generic > module : aes_generic > > Is there compatible issues here? > Can it be that the old server was using i386 arch and the new is 64bit? > losetup version differs? > > Any insight is appreciated. > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos_______________________________________________ CentOS mailing list CentOS at centos.org http://lists.centos.org/mailman/listinfo/centos