Strangly enough, i did get fsck to work by deleting the loop, then re-running the S07losetup startup script again.
Like i said earlier, the loop still exists when i simply unmount as i can remount without password prompt, but fsck couldn't get a clue about the FS until loop was deleted and re-created.
The commands i used are correct as they worked fine now. Its probably just another debian thing :\
s07losetup "echo "foopass" | losetup -p 0 -e AES256 /dev/loop2 /dev/md0
Another thing though, i've had no swapspace since the "2.4.19 or 2.4.20 breaks encrypted swap" thread at the start of the year, has this been fixed now? Does newest loop-aes fix it or must i use 2.4.21?
Thanks, Brad.
_________________________________________________________________ Tag MSN Hotmail med dig på mobilen http://www.msn.dk/mobile
- Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
