@glm, I suspect your problem booting is a separate issue from this one. After scanning through the comments here, I think this issue has become quite confused and that some of the comments reflect different issues. Just because an error message starts with "udevd-work" doesn't imply that it's the same issue. This one seems to be specifically related to /dev/null, so if you see an error message relating to another device you are likely seeing a different problem.
@tecknomage, can you explain why you described this as a mount problem? I haven't really seen anything to indicate that anything is trying to mount /dev/null, and doing so doesn't really make any sense as /dev/null cannot be mounted (it isn't even a block device). Can you also clarify exactly what your error message is? Does it look like this? udevd-work[xxx]: open /dev/null failed: no such file or directory Or is it something different? Getting an accurate error message is extremely helpful. If you are seeing the message above it doesn't indicate any serious problem with your system. Sometimes the udev rules indicate that udev should run a program in response to an event. As part of running the program udev tries to open /dev/null, and it appears in some cases this can happen before the /dev/null device node exists. This isn't a fatal problem though, and execution of the program will proceed even if /dev/null cannot be opened. So really that message is nothing to be concerned about. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/575333 Title: On boot keeps trying to mount "UDEVD-WORK..../dev/null" -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
