SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
After a relatively long period of uptime, I just updated my kernel to 2.6.26. I don't know if the kernel upgrade triggered this, or some patched package I had applied since my last boot was the culprit. Regardless:
On rebooting, I saw a massive list of errors relating to udev. Many complained of not being able to create symlinks in /dev because the files already existed. Deleting the listed devices and allowing udev to create its files and symlinks on the next boot solved some of the errors. Now I'm left with a handful of errors I cannot seem to eliminate.
Before udevd starts, there are a handful of cp errors, something like:
cp: create file /dev/stderr: Read-only file system.
Udev starts, then there are a bunch more errors that look something like
udevd: mkdir: cannot create /dev/.udev/queue: Read-only file system
udevd: rmdir: cannot remove /dev/.udev/failed: Read-only file system
over and over again. (The above errors are not exact. Neither dmesg nor syslog show them. If anyone really needs them letter-perfect, let me know and I'll write them down by hand.)
I tried booting with the root partition read-write, and I did not receive those errors, but they resurfaced when I started booting normally. Anyone experience this, or know the proper way to fix the problem?
If the system is running okay once it starts up then I would just ignore the error messages. I get a short list of errors from udev related to being unable to find the tape group. I don't have a tape device on the computer so the errors don't affect anything. This is one situation where "If it works don't fix it" applies.
If the system is running okay once it starts up then I would just ignore the error messages.
Well, that's no longer true. I don't reboot my laptop often, so it just started, but now there's an endless loop of these messages. I circumvented the problem temporarily by booting with root rw, but that's a temporary solution. I would love to know WHY I am getting these errors, and by extension, how to fix them.