Encrypted Root Filesystem (dm-crypt/loopAES +ext3fs) - Problem
I'm trying to install an encrypted root filesystem originally using loopAES with the following tools:
1. Slackware 10.1
2. Kernel 18.104.22.168
However, i found that, it reboots when my ramdisk trying to run "init" command:
If i run the program manually myself on the console:
exec /usr/bin/chroot current-parition new-partition
i.e. : exec /usr/bin/chroot . loader
It shows error:
/usr/bin/chroot: cannot run command 'loader/': Permission denied
When i switched to the next screen. The error shows:
-sh: /dev/null: Read-only file system
stderr is not a tty - where are you?
The ramdisk im using busybox 1.0 :)
I believe that it could be a bug in loopAES, therefore, i reimplement this encrypted root file system with dm-crypt which is readily available in kernel 22.214.171.124 with the following tools:
4. busybox 1.0
Any thing that i could have missed out?
It seems like the problem lies int the /sbin/init belonging to my real root filesystem. Once it's executed, it seems to do some processing 4 a while and KAPOOF-->
My system restarts AFTER MOUNTING /dev/loop0 to /mnt directory.
It just reboots with no error messages during ramdisk execution?
Yes , it just reboots.
Guys, i think this is obviously the patch(loop-AES-v3.0d.tar.bz2) i tried out is problematic on kernel 126.96.36.199
I tested the loop-AES-v3.0b.tar.bz2 with Kernel 2.6.10. These works perfectly fine. No a scratch of problem at all. Hmm, how am i gonna deal wiff this kernel 188.8.131.52 encryption....
Hahaha, boys and girls, ladies and gents,
I found the answer the problem. The problem actually lies in the encrypted root filesystems' /dev directory.
When i run cp -avx / /mnt/efs
This command copys all the files except the block devices files. That's why it reboots. This is becoz the kernel can't file the block devices to load. How stupid of me.
Now Kernel 2.4.29, 2.6.10, 2.6.12. 184.108.40.206 is all capable of doing loopAES as well as dm-crypt + LVM2.
Awesome man.... ;)
Very nicely done. cp doesn't handle devs well. Of course, one really ought to be using udev anyway, so the only real devs you need are /dev/null and /dev/console (needed for initial kernel boot before udevd is started)
Please tell me more bout this udev Matir. Im interested :)
Heh. udev is awesome. I have udev setup so that each of my jumpdrives ALWAYS gets the same symlink in /dev. For example, my blue jumpdrive can ALWAYS be called /dev/jumpdrives/blue. This makes it much easier to mount them in predictable places, and keep fstab simple. Check out http://www.kernel.org/pub/linux/util...tplug/udev-FAQ for more info.
|All times are GMT -5. The time now is 12:12 PM.|