/run/udev not writable error message
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udev (Ubuntu) |
Invalid
|
Low
|
Canonical Foundations Team |
Bug Description
Binary package hint: udev
I upgraded from natty to oneiric, rebooted a couple times, and noticed this error message:
udevd[79]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
I booted with a natty kernel and still saw the error, so am guessing it's not being printed by the kernel.
Although some people in the comments are having boot problems, I think this error message isn't related to boot failures, it's just that it's the only thing you see, so you assume it must relate to the failure. But I see it with successful live environment boots as well.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: udev 168-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-
Architecture: i386
Date: Tue May 17 11:38:27 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0d3d:0001 Tangtop Technology Co., Ltd HID Keyboard
MachineType: Intel Corporation SandyBridge Platform
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: udev
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: ASNBCPT1.
dmi.board.
dmi.board.name: Emerald Lake
dmi.board.vendor: Intel Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: SandyBridge Platform
dmi.product.
dmi.sys.vendor: Intel Corporation
tags: | added: iso-testing |
This might be a separate problem, as I saw it only on the oneiric kernel, not on the natty kernel (well, not yet anyway). On reboot the console was filled with many screens of spewed timeout errors trying to kill modprobe.