redwood
Guru
Joined: 27 Jan 2006
Posts: 306
|
 Posted: Thu Jan 31, 2013 9:43 pm Post subject: device-mapper problem |
 |
|
My System:
x86-3.3.8-gentoo
openrc-0.11.6
genkernel-3.4.5
dracut-024-r4 DRACUT_MODULES="mdraid dm lvm gensplash crypt crypt-gpg"
udev-171-r9
lvm2-2.02.98
cryptsetup-1.4.3
| Code: |
# grep -v '^#' /etc/dracut.conf|grep -v '^$'
logfile=/var/log/dracut.log
fileloglvl=6
add_dracutmodules+="usrmount"
add_drivers+="nvidiafb"
hostonly="yes"
mdadmconf="yes"
lvmconf="yes"
install_items="/sbin/v86d"
|
My initramfs built with:
| Code: |
dracut --hostonly initramfs-dracut-x86-3.3.8-gentoo 3.3.8-gentoo
# ls -sh /boot/initramfs-dracut-x86-3.3.8-gentoo
4.9M /boot/initramfs-dracut-x86-3.3.8-gentoo
|
My grub.conf:
| Code: |
title=Gentoo Linux (3.3.8-gentoo DRACUT)
root (hd0,0)
kernel /boot/kernel-genkernel-x86-3.3.8-gentoo root=UUID=d8d8f71f-0a8d-46ef-86f6-da15a49732a5 vga=0x318 video=v86d:ywrap,mtrr,1024x768-32@72 splash=silent,fadein,theme:livecd-2006.0,tty:12 quiet CONSOLE=/dev/tty1
initrd /boot/initramfs-dracut-x86-3.3.8-gentoo
|
Entering Interactive mode in openrc,
services are loaded in the following order
- udev
- hwclock
- modules
- mdraid
- lvm
- device-mapper
- dmcrypt
- ...
If I let device-mapper start, it creates mapping for crypt-swap, crypt-tmp, crypt-home-backups
then when dmcrypt starts, it tries and fails to create the same encrypted volumes,
then fsck fails and the encrypted crypt-tmp, crypt-home, etc volumes don't get mounted.
It also creates some mappings for some logical volumes which I no longer have, eg. vg-oldhd.
So, I have /dev/mapper/vg-oldhd
BUT NOT /dev/vg/oldhd
"lvs vg" correctly shows the mappings in /dev/vg/*
If I manually skip over device-mapper,
dmcrypt seems create the encrypted volumes, fsck them, and mounts them.
And I can then let openrc continue booting and finally get a working system
(from which I am writing this post).
But, device-mapper isn't running, and if I now try to manually start it:
| Code: |
# /etc/init.d/device-mapper start
* Setting up device-mapper volumes:
* Creating volume: crypt-backups ...
* Error creating volume: crypt-backups [ !! ]
* ERROR: device-mapper failed to start
|
which seems to be trying to create encrypted volumes using /etc/conf.d/cryptfs
which I no longer use since I use /etc/conf.d/dmcrypt with cryptsetup LUKS:
| Code: |
# grep crypt-backups /etc/conf.d/*
cryptfs.old:target=crypt-backups
dmcrypt.bak:target=crypt-backups
|
I don't boot that often, but it's still annoying to have to manually step through openrc
to skip starting device-mapper.
Since I've just gotten dracut's initramfs working and I'd like to "emerge -uvDN world"
and let udev update, cross my fingers, and hope init with separate usr still works,
I'd like to get the device-mapper issue solved (one less thing to fret about) on my test machine
before updating udev/initramfs on half-dozen other systems.
Thanks for any suggestions. |
|
Kernel & Hardware
