[arch-general] udev and/or device-mapper problem

[Thomas Bächler]

Am 10.02.2010 16:00, schrieb karolina.lindqvist at kramnet.se:
> I updated my system, and then on reboot it could not find the disk /dev/sda 
> anymore. A pity, since it hold the boot and root file systems. I have a custom 
> kernel, for various reasons, but now I could not get my custom kernel, of 
> 2.6.32 series, to work with the new udev features, and have no idea what it 
> can be.
> 
> (The stock kernel does recognize the disks, but instead crashes on my radeon 
> card, with or without the "fixes" described in the wiki. )
> 
> Without the /boot patition it was quite hard to get the system working again. 
> Kernel update/downgrade does not work. I tried to downgrade packages, one 
> after another, until I came to "udev", and after I downgraded it, the system 
> worked normally. So now udev  is locked it in a downgraded state.
> 
> What is going on? 

First, this is an entirely different problem from the original one,
which results from changes in udev rules concerning the device-mapper -
the latter is not usedin your setup at all.

Your custom kernel is misconfigured, the most likely candidate being:

$ zgrep CONFIG_SYSFS_DEPRECATED /proc/config.gz
# CONFIG_SYSFS_DEPRECATED_V2 is not set

If this option is set to yes, udev will fail to create devices properly.
If the option is unset in your kernel, we have to look for the reason
further.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-general/attachments/20100210/06bad7f8/attachment.bin>