View previous topic :: View next topic |
Author |
Message |
binro l33t
Joined: 06 May 2005 Posts: 724 Location: Bangkok, Thailand
|
Posted: Mon Sep 27, 2010 4:36 pm Post subject: lvm2 warning messages at boot |
|
|
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 |
|
Back to top |
|
|
rh1 Guru
Joined: 10 Apr 2010 Posts: 501
|
Posted: Mon Sep 27, 2010 4:50 pm Post subject: |
|
|
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. |
|
Back to top |
|
|
binro l33t
Joined: 06 May 2005 Posts: 724 Location: Bangkok, Thailand
|
Posted: Mon Sep 27, 2010 4:59 pm Post subject: |
|
|
rh1 wrote: | 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 |
|
Back to top |
|
|
rh1 Guru
Joined: 10 Apr 2010 Posts: 501
|
Posted: Tue Sep 28, 2010 2:37 pm Post subject: |
|
|
Quote: | 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. |
|
Back to top |
|
|
ConiKost Developer
Joined: 11 Jan 2005 Posts: 1365
|
Posted: Sun Oct 31, 2010 12:52 am Post subject: |
|
|
Are there any news on this?
I am also using my own initrd, as my gentoo is crypted with luks.
Is there any way to fix those warnings? |
|
Back to top |
|
|
rh1 Guru
Joined: 10 Apr 2010 Posts: 501
|
Posted: Sun Oct 31, 2010 2:45 am Post subject: |
|
|
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. |
|
Back to top |
|
|
whywhy n00b
Joined: 20 Jul 2010 Posts: 40
|
Posted: Mon May 09, 2011 8:06 am Post subject: |
|
|
This is can resolved by adding the following in the file /lib64/rcscripts/addons/lvm-start.sh
udevadm trigger --action=change --attr-match=dm/name
This will cause udevd to create the proper link
Code: | if [ -d /proc/lvm ] || dm_in_proc ; then
ebegin "Setting up the Logical Volume Manager"
#still echo stderr for debugging
# Extra PV find pass because some devices might not have been av
ailable until very recently
/sbin/pvscan --config "${config}" >/dev/null
# Now make the nodes
udevadm trigger --action=change --attr-match=dm/name
/sbin/vgscan --mknodes --config "${config}" >/dev/null
|
|
|
Back to top |
|
|
katabami n00b
Joined: 11 Jul 2009 Posts: 40
|
Posted: Tue May 10, 2011 1:55 am Post subject: |
|
|
Is it worth risking wrong edits? It's not once, but you may have to do 'dispatch-conf' in the future.
By the way, there's also shutdown time message. I ignore it too, but the above fix may make you get rid of it. |
|
Back to top |
|
|
marc2gentoo n00b
Joined: 04 Sep 2011 Posts: 14
|
Posted: Sun Oct 09, 2011 4:49 pm Post subject: |
|
|
Now I have the exact same "problem". I will test the solution "whywhy" suggested, but before i'll make a backup.
Any News about this behaviour?
Thanks
Marc
PS:
What I've done?
Grub2+LVM2+GPT+RAID5
-> root with boot on lvm
Booting with Grub2 from a BIOS-Boot-Partition. |
|
Back to top |
|
|
lkraav Tux's lil' helper
Joined: 13 Oct 2004 Posts: 129 Location: Estonia
|
Posted: Sun Oct 09, 2011 5:01 pm Post subject: |
|
|
aidecoe has tinkered with this with his work on dracut, but afaik with no success. |
|
Back to top |
|
|
marc2gentoo n00b
Joined: 04 Sep 2011 Posts: 14
|
Posted: Sun Oct 09, 2011 5:46 pm Post subject: |
|
|
@Ikraav
thx for reply
Do you know something about the solution from "whywhy"? Maybe this could be a durable solution?
#Marc |
|
Back to top |
|
|
lkraav Tux's lil' helper
Joined: 13 Oct 2004 Posts: 129 Location: Estonia
|
Posted: Sun Oct 09, 2011 6:02 pm Post subject: |
|
|
marc2gentoo wrote: | @Ikraav
Do you know something about the solution from "whywhy"? Maybe this could be a durable solution?
#Marc |
it's lowercase L-kraav actually.
i pointed aidecoe to this thread, he tried the workaround, but reportedly did not have success with it. neither did i. |
|
Back to top |
|
|
marc2gentoo n00b
Joined: 04 Sep 2011 Posts: 14
|
Posted: Sun Oct 09, 2011 6:27 pm Post subject: |
|
|
sorry
Quote: | i pointed aidecoe to this thread |
I really appriciate that, I'm very new to gentoo... (no contacts to devs, few experience about linux/gentoo)
Quote: | he tried the workaround, but reportedly did not have success with it. neither did i. |
So I will keep my hands off that... |
|
Back to top |
|
|
marc2gentoo n00b
Joined: 04 Sep 2011 Posts: 14
|
Posted: Sun Oct 16, 2011 5:36 pm Post subject: |
|
|
Any News on this topic?
Maybe I should change to dracut basically...
I'm afraid to go on with the cluster (drbd and so on)...
The mdraid is not shutting down, until the lvm did not stop...
#Marc |
|
Back to top |
|
|
lkraav Tux's lil' helper
Joined: 13 Oct 2004 Posts: 129 Location: Estonia
|
Posted: Sun Oct 16, 2011 7:58 pm Post subject: |
|
|
marc2gentoo wrote: | Any News on this topic?
Maybe I should change to dracut basically...
I'm afraid to go on with the cluster (drbd and so on)...
The mdraid is not shutting down, until the lvm did not stop...
#Marc |
dracut is probably a good idea regardless, but this problem also exists on dracut. |
|
Back to top |
|
|
binro l33t
Joined: 06 May 2005 Posts: 724 Location: Bangkok, Thailand
|
Posted: Fri Jan 11, 2013 5:00 pm Post subject: |
|
|
I just created a new lv and I got this:
Code: |
# 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
#ioctl/libdm-iface.c:1721 Uevent not generated! Calling udev_complete internally to avoid process lock-up.
_________________ "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 |
|
Back to top |
|
|
|