Symptom: udev does not create /dev/disk folder, but it appears if manually doing 'udevadm trigger' or '/etc/init.d/udev restart' udev-mount and udev do start with system boot. Using: - udev-init-scripts-19-r1 - sys-kernel/openvz-sources-2.6.32.72.10 - genkernel initramfs - single root and swap partitions on lvm (except for boot) Kernel compiled with: - CONFIG_DEVTMPFS=y - CONFIG_DEVTMPFS_MOUNT=y - CONFIG_TMPFS=y Contents of /proc/mounts: http://pastebin.com/TN96w3zC Output of udev with debug http://pastebin.com/cHsr4DnM Contents of executing 'cat /proc/mounts' within start_pre() and start_post() of /etc/init.d/udev: http://pastebin.com/DAt0nrLr /dev/disk folder appears when using sys-fs/udev-171-r10 Reproducible: Always
Upgraded to sys-fs/udev-197, and modified init script to let it run with that version kernel. Udev starts, nothing changes about /dev/disk.
(In reply to comment #1) > Upgraded to sys-fs/udev-197, and modified init script to let it run with > that version kernel. > > Udev starts, nothing changes about /dev/disk. Clarification: nothing changes respect Eudev, udev-197 doesn't create /dev/disk.
I was helping someone through this a few days ago, they were using a genkernel initramfs. Is this the case here as well? Please attach emerge --info , as well as other system related config info (separate /usr , lvm2 being used, initramfs used and how it was built, etc. etc.) The specific issue at the time for this user was that /dev was being reported as a "read-only filesystem" when udev was first attempting to populate /dev. Could you check if this is your issue as well? Here's how to debug: 1 - enable 'udev_debug' via /etc/conf.d/udev 2 - reboot 3 - grep dmesg or /var/log/messages for all the udev debugging messages (for some reason the messages are NOT written to /run/udevdebug.log , so no point trying to look there). Here's a specific match that will help you: dmesg |grep -C 1 'dev/disk' if this reports something like: udevd[15634]: symlink '../../vda1' '/dev/disk/by-label/boot.udev-tmp' failed: Read-only file system ...then it is the same issue.
Created attachment 337106 [details] emerge --info
Wait, are you using initramfs? Does it include the binaries from udev in /lib/udev? /dev/disk needs the *_id binaries, like path_id So creating /dev/disk would fail if those binaries aren't in the initramfs too.
(In reply to comment #3) > I was helping someone through this a few days ago, they were using a > genkernel initramfs. Is this the case here as well? Please attach emerge > --info , as well as other system related config info (separate /usr , lvm2 > being used, initramfs used and how it was built, etc. etc.) emerge --info on comment #4 as explained on comment #1, system is on top of lvm, with single root (no separate usr). Initramfs is genkernel's one, created with genkernel all --lvm. All packages are on its stable version, it's a test vm with everything as stable and default as posible. Kernel config is the official kernel confing supplied for that specific version from openvz.org. > The specific issue at the time for this user was that /dev was being > reported as a "read-only filesystem" when udev was first attempting to > populate /dev. Could you check if this is your issue as well? Same issue, check on comment #1 where you can read udev's debug output (pastebin).
(In reply to comment #6) > (In reply to comment #3) > > I was helping someone through this a few days ago, they were using a > > genkernel initramfs. Is this the case here as well? Please attach emerge > > --info , as well as other system related config info (separate /usr , lvm2 > > being used, initramfs used and how it was built, etc. etc.) > > emerge --info on comment #4 > > as explained on comment #1, system is on top of lvm, with single root (no > separate usr). > > Initramfs is genkernel's one, created with genkernel all --lvm. "-o loop" mount it and check if the udev *_id binaries are in place no idea if genkernel does this right :/
(In reply to comment #7) > > Initramfs is genkernel's one, created with genkernel all --lvm. > > "-o loop" mount it and check if the udev *_id binaries are in place > no idea if genkernel does this right :/ there is not anything related to udev on initramfs.
Does the /dev from initramfs copy itself to the actual filesystem as /dev? If so, it's propably the missing udev support in the initramfs that causes this. Perhaps you could try the initramfs generated by dracut?
From irc #gentoo-eudev, prometheanfire _AxS_ tried to reproduce the problem without success, initramfs from genkernel, 2.6.32 kernel and eudev, and /dev/disk was created. This reflects some problem with my configuration.
