On Wed, Jan 27, 2010 at 09:40:08PM +0100, Ferenc Wagner wrote: > Guido Günther <[email protected]> writes: > > > Could you try increasing udevs debug level (maybe capture via serial > > console)? > > Heh, booting with udev_log="debug" resulted in a 1.1M console log > file... Truly amazing. > > > Alternatively could you first check if the scripts called from > > > > /lib/udev/rules.d/60-kpartx.rules > > > > turn out the expected results? Maybe ENV{DM_STATE} != ACTIVE? or > > ENV{DM_TABLE_STATE}!="LIVE"? Running > > > > /lib/udev/dmsetup_env <major> <minor> > > > > Should already give a hint. > > # /lib/udev/dmsetup_env 254 0 > DM_UUID=mpath-360060160ec612000f6f237e09406df11 > DM_TABLE_STATE=LIVE > DM_STATE=ACTIVE > DM_NAME=nfs > > The problem is not this. It's much more basic: > > (initramfs) cd /lib/udev/rules.d > (initramfs) ls > 50-udev-default.rules 60-persistent-storage.rules > 55-dm.rules 70-persistent-net.rules > 56-lvm.rules 80-drivers.rules > 60-persistent-storage-dm.rules 91-permissions.rules > 60-persistent-storage-lvm.rules > > That is, 60-kpartx.rules is not present in the initramfs! > No wonder it does not work. :) Weird - I just bootstraped a kvm instance and 60-kpartx.rules ends up in the initramfs fine. -- Guido
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
