Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 08-08-2008, 11:14 AM   #1
Registered: Sep 2003
Distribution: Slackware64 13.1
Posts: 52

Rep: Reputation: 15
Red face boot errors with udev on slack 12

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[1061]: mkdir: cannot create /dev/.udev/queue: Read-only file system
udevd[1061]: 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?

Old 08-09-2008, 08:51 PM   #2
Senior Member
Registered: Dec 2005
Location: Massachusetts, USA
Distribution: Ubuntu 10.04 and CentOS 5.5
Posts: 3,873

Rep: Reputation: 332Reputation: 332Reputation: 332Reputation: 332
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.
Old 09-02-2008, 11:05 PM   #3
Registered: Sep 2003
Distribution: Slackware64 13.1
Posts: 52

Original Poster
Rep: Reputation: 15
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.


boot, udev

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
boot errors - slack 11.0 - kernels > 2.6.19? The_Outlander Slackware 4 05-17-2007 08:15 PM
udev errors tobyl Slackware 15 01-04-2007 12:42 AM
udev in slack-11 with digikam justwantin Slackware 2 11-12-2006 08:45 PM
/etc/udev/permissions.d on Slack ? Kocil Slackware 3 11-29-2005 02:57 AM
Udev, Konsole, funky errors atrain Linux - General 16 02-08-2005 05:26 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:20 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration