Red HatThis forum is for the discussion of Red Hat Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've had the same issue as is being reported in numerous other forums. I installed CentOS 5.3, and ran an update to go to 5.5. After the update, the system stalls on Starting udev.
Thankfully, Grub can still boot into the old version, which does not stall. I've seen plenty of solutions presented on this, and have tried as many as I can find, but none have helped.
I've been running udev in debug mode to see the log, and it appears to be stalling on a process somewhere, but due to the event based output, the log stalls at a different point of output, so it's proving tricky to see which process is stalling.
The grub loader seems to have two different .img files that it uses to load the configurations, can I use those to find what has been changed?
I'm not sure how common this issue is. On my CentOS 5.5 install; I did a similar thing to you in that I upgraded using yum.
I am running the 2.6.18-194.8.1.el5 kernel; and there's no issues with starting udev.
If you have found other locations showing this as a commonly occurring fault please post them here; as well as the troubleshooting that you've done thus far.
If you have found other locations showing this as a commonly occurring fault please post them here; as well as the troubleshooting that you've done thus far.
I pretty much typed "CentOS Starting udev" into Google, and followed the first page of links.
Quote:
... so how is it related to an Udev problem?
Aside from the fact that one works and the other doesn't.... if I knew the answer to that I wouldn't be asking.
Quote:
GRUB "just" loads the kernel...
Interesting, didn't know that. Thought each entry was an entire system config or something.
Quote:
You should also install and try 2.6.18-194.3.x kernels as well as centosplus ones.
Ah, didn't know I could just uninstall the updated kernel and grab an older one. I've gotten rid of the old one, and am now trying a different version.
Thanks for the help, guys, I think this is just me not understanding how modular linux actually is.
You can have multiple kernels installed at the same time (watch for available space on /boot partition) and choose any of them every time you start your PC. yum update will never the less suggest to remove older ones by default, but that can be avoided with "yum update -x kernel*" first, and then play with kernels as you see fit.
So do not uninstall any of the kernels, just install another one, referencing by full name and version number:
Code:
yum install kernel-2.6.18-194.3.1.el5.centos.plus
and do the same if you need kernel-devel kernel-headers, etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.