I have just rebooted for the first time for ages and received these messages:

* Setting up the Logical Volume Manager ...
The link /dev/vg00/rootfs should had been created by udev but it was not found. Falling back to direct link creation.
The link /dev/vg00/home should had been created by udev but it was not found. Falling back to direct link creation.
The link /dev/vg00/var should had been created by udev but it was not found. Falling back to direct link creation.
The link /dev/vg00/tmp should had been created by udev but it was not found. Falling back to direct link creation.
The link /dev/vg00/portage should had been created by udev but it was not found. Falling back to direct link creation.
The link /dev/vg00/swap should had been created by udev but it was not found. Falling back to direct link creation.

Everything proceeds OK but naturally I would like to get to the bottom of this. Searching shows other people get these messages but it is not clear why. I changed all my /etc/fstab entries from /dev/vg00/part to /dev/mapper/vg00-part but that made no difference. Looking at /etc/udev/rules.d I can see nothing to do with lvm. I tried re-emerging lvm2 and udev to see if there were new config files but dispatch-conf showed no changes. I have lvm2-2.02.73-r1 and udev-162. Any ideas?

TIA_________________"Ship me somewheres east of Suez, where the best is like the worst,
Where there ain't no Ten Commandments an' a man can raise a thirst"
from "Mandalay" by Rudyard Kipling

I get that same message using lvm. I noticed it only occurs on my system for the volumes I activate in my initramfs. I was using "vgchange -ay" and I'd get that message for all of my logical volumes. Then I switched to " lvchange -ay <group>/<rootfs>" and i only get it for the rootfs. I thought that was the issue as to why the link wasn't created, volume is already active and since it has a fallback method i didn't see any harm.

I was using "vgchange -ay" and I'd get that message for all of my logical volumes. Then I switched to " lvchange -ay <group>/<rootfs>" and i only get it for the rootfs.

How do you do that? You roll your own initrd? I am using genkernel for the ramdisk._________________"Ship me somewheres east of Suez, where the best is like the worst,
Where there ain't no Ten Commandments an' a man can raise a thirst"
from "Mandalay" by Rudyard Kipling

How do you do that? You roll your own initrd? I am using genkernel for the ramdisk.

Yes, I have my own initramfs. Basically all it does is activate and mount rootfs which is on lvm and dumps me in a "rescue shell" if something goes wrong. Nice instructions here.
No idea how to make genkernel do that. Of course you can probably just ignore those warnings, the fallback method takes care of the link so i don't see the harm.

In my opinion it's harmless. I've never noticed anything wrong because of it. I think it is more of a "just so you know" type of warning in case for example you weren't using an initrd and udev should have created the link. But like it says, udev didn't create the link so it did. Which makes sense since the volume was activated in the initrd before udev was started.

# lvcreate -L 15G -n /dev/vg00/arch
/dev/mapper/vg00-arch not set up by udev: Falling back to direct node creation.
The link /dev/vg00/arch should had been created by udev but it was not found. Falling back to direct link creation.
Logical volume "arch" created

There are numerous hits on this and they all talk about missing udev rules. I have the latest udev and lvm which provide all the rules, so what is wrong?

Edit: Using -vvvv I get this message, which is reported in other reports I found