Kernel update on LUKS and LVM encrypted Slackware, mount fails
Hi everyone!
I did a fully encrypted installation (execept /boot) of Slackware (2.6.29.6) on my netbook using this nice howto > http://slackware.osuosl.org/slackwar...ADME_CRYPT.TXT (starting at section "Combining LUKS and LVM "), which works just fine. Now I found out, that my Broadcom wireless chip only works with the b43 drivers on kernel 2.6.32.x (the original linux drivers from Broadcom work, but won't let me put the card in monitor mode). So I updated to 2.6.32.7 using the config-generic-smp-2.6.29.6-smp from the boot folder and 'make oldconfig', because it looks like you can not use the 'huge' kernel with an initrd image. Now, when I boot into the new kernel, he finds and activates the encrypted volumes, but fails to mount them. Code:
Enter LUKS passphrase for /dev/sda2: This was my first kernel update and I was not sure about some things, It seems like at some point I messed up. Here is what I did after 'make oldconfig' and 'make modules_install': copied the kernel and System.map to /boot Code:
cp arch/i386/boot/bzImage /boot/bzImage Code:
mkinitrd -c -k 2.6.32.7-smp -m ext2 -f ext2 -r /dev/cryptvg/root -C /dev/sda2 -L Code:
cd /etc/rc.d Code:
image = /boot/bzImage Any help is appreciated. :) |
Try
Quote:
|
I don't see an error popping out. I would suggest to use a config file from Slackware current though. I had the same problem and cannot say what exactly made the mount fail, but with the newer config file it worked like a charm. ftp://slackware.mirrors.tds.net/pub/...rent/source/k/
|
Quote:
|
Quote:
|
This looks a bit fishy
Code:
Command successful: You might find that -r /dev/cryptcg/root on the mkinitrd might get you up and running, but your lvm looks like it needs some further diagnosis / attention to resolve this inconsistency. |
Quote:
|
Quote:
Chris |
Ahh, ok. I assumed that was a cut/paste so wasn't expecting the possibility of a typo. No worries.
Can you confirm that your rootfs is really on /dev/cryptvg/root? That device should be created within the initrd when it does the vgchange -ay so you shouldn't be seeing device not founds on the mount. Also are you sure its an ext2 and not a 3 or 4? |
It's not anything to do with the initrd= in lilo.conf Chris. The fact that he's getting as far as this shows that the initrd is already loaded.
Most likely, it's the -m -f or -r that is wrong. |
Quote:
|
Quote:
And it's definitely ext2 (I read somewhere that ext2 would be easier on the flashdrive since ext3 writes more often to the disk because of the journaling). I also suspect that I made a mistake while creating the initrd, may the -k option was wrong... |
Deleted
|
Deleted.
|
I agree that it is not a initrd in lilo.conf issue.
Try # depmod 2.6.32.7-smp # I assume you have a /lib/modules/2.6.32.7-smp # mkinitrd -c -k 2.6.32.7-smp -m ext2 -f ext2 -r /dev/cryptvg/root -C /dev/sda2 -L I hope this helps. |
All times are GMT -5. The time now is 06:39 PM. |