Summary: | udev-only and lvm2 fresh install with development-sources kernel 2.6.6-rc1 from livecd 2004.1 results in dead system after booting from hard drive | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Valmor de Almeida <val.gentoo> |
Component: | [OLD] Core system | Assignee: | Greg Kroah-Hartman (RETIRED) <gregkh> |
Status: | RESOLVED FIXED | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Valmor de Almeida
2004-05-25 14:12:26 UTC
If the device mapper is compiled as a module during the installation, and when booting in single user mode, the process does not go as far as the normal boot and the following message appears on the screen at the prompt (still frozen display and keyboard): ...top of the display... * Using /etc/modules.autoload.d/kernel-2.c as config: * Loading module dm-mod... * Autoloaded 1 module(s) * Setting up the Logical Volume Manager... /dev/mapper/control: open failed: No such file or directory Is device-mapper driver missing from kernel? * Checking all filesystems... Reiserfs super block in block 16 on 0x301... ...lines omitted... * Mounting local filesystems... mount: special device /dev/vg_fixed/usr does not exist mount: special device /deb/vg_fixed/opt does not exist ....lines omitted... There are as many "mount" complaints are there are file systems under LVM. Following the installation instuctions with the device mapper enabled in the kernel (2.6.6-rc1 from development-sources) as a module, results in the following warning during installation: Warning: couldn't create /etc/modprobe.conf upon running modules-update after adding dm-mod to the /etc/modules.autoload./kernel-2.6 file. Hi, I was about to report this as a bug, and I found this here. I believe I have extra info that can help. The problem is that UDEV does not know to create the /dev/mapper/control device node. Without that 'vgchange -a y' fails, and you get no LVM partitions. After some digging around, I discovered that the device-mapper package supplies a script called 'devmap_mknod.sh' which queries /proc and creates a device node with the dynamically assigned major and minor numbers. The comments regarding this script specifically state that it must be used on a non-devfs udev only system. This script needs to be called early in the boot process. I hacked my /sbin/rc to call it as part of the UDEV setup. That seems to have worked and solved my problem. Hope that helps, -Mark this isnt the way it should be done. this happens because you compile device mapper as module, and when you load, it doesent get to create the device quick enough. building device mapper in, makes the module be created faster, and the checkfs init script which enables logical volume manager will run vgchange properly. I had to add KERNEL="device-mapper", NAME="mapper/control" to /etc/udev/rules.d/50-udev.rules to make it work. that should be in there by default Should now be fixed with the latest version of udev. |