CentOS 5 :: Failing On Boot At 'Starting Udev' On ESXi4?
May 12, 2010
Have just installed 5.4 64 bit on an AMD64 x2 system with 4 GB ram running ESXi4.Text based install went fine, but on reboot starting up it gets as far as 'Starting udev' and just hangs. Checking the performance in ESXi it appears to be using 100% cpu.I have left it for half an hour and it does not progress and the only thing to do is to power cycle the VM.I have searched and found a few suggestions for kernel parameters but they did not make any difference. I can't even get in to a command line as it doesn't boot up far enough.I have reinstalled it several times and also checked the MD5 of the downloaded file and all appears Ok.
I have done a fresh text-only installation of Fedora 10 on a Dell Dimension E521 for the purpose of setting up a server. After installation I ran yum update to bring the system up to date. After the update, I rebooted the computer, but the boot process froze. I recycled power and pressed "I" after the Dell BIOS screen and the GRUB bootloader appeared. I selected the most current version, edited the kernel line by deleting "rhgb quiet" and replacing it with "3." After making this change, I continued with the boot and the computer stopped at "Starting udev:" I have two fedora 10 revisions showing in the GRUB bootloader, the original installation and the update after running yum.
I repeatedly tried rebooting both versions and, after about 30 attempts, the computer finished booting and got me to the command prompt. Reading through the forums indicated there might be some issue with my nVidia GeForce 6150 onboard video and fedora 10. So, when I got to the command prompt, I followed the instructions in the forums [URL] to load the rpmfusion drivers. This appeared to be successful and when I looked at /etc/X11/xorg.conf it appeared to be correct for the new nVidia drivers. After loading these new drivers I tried rebooting. Unfortunately, I have been trying now over and over to get back to the command prompt, but simply can't get past "Starting udev."
I'm trying to configure gpsd 2.96 to start automatically from udev rule on a Slack 13.37 box.1. I've compiled and installed gpsd from sources and made sure it starts manually.2. I've copied the /lib/udev/gpsd.hotplug and /lib/udev/gpsd.hotplug.wrapper scripts in their places from the source tree and made them executable.3. I've copied the gpsd.rules file from sources into /etc/udev/rules.d4. I renamed it 99-persistent-gpsd.rules to run late in the bootup process.5. I've copied the /etc/default/gpsd file from sources and made sure it has the right settings inside.
Now, for the results. If I plug the gps usb dongle in while the system runs, it starts gpsd if it is not started, and it connects to it just as it should. But if I start the system with the dongle in, gpsd doesn't get started during boot. I can't find any relevant message in /var/log/syslog or /var/log/messages for boot time. There is stuff there from when I plug the dongle in while the system is running though. It's like udev ignores the rules for it at boot time.Is there something in the Slackware boot scripts that would prevent running those scriptssd.hotplug.wrapper which in turn runs /lib/udev/gpsd.hotplug which is a Python script)?Here is the contents of 99-persistent-gpsd.rules (ignore the comments referring to Debian, it was meant for a Debian box). My usb gps adapter is the first one - the Prolific chipset one:
I have Dell rack server. With the network card of five network ports. But I am just using first one (eth0).
Now the problem:
Its connected the internet and the internet is working fine. I also got update using yum.
When I do ifconfig to check its dynamic IP. It also shows the IP(something like: 192.168.x.x), but if I go to services and try to start DHCPd service its fails. Its not starting at all. And If I go to other computer (Windows 7) and try to ping the dell servers IP, I cannot ping it. So since I cannot ping it from other computer, so no one we can have remote access to the dell server.
I dont understand without starting DHCPd how the dell server is getting the IP address.
So I thought maybe DHCP is corrupted so I removed it using yum and reinstalled it using yum, but no luck so far.
Fedora 12 randomly crashes after a fresh install.Everything is left at its default during the installation except I install KDE and not Gnome.When I try to boot I hit esc at the splash screen to see where it hangs, but it never hangs at the same spot twice. Sometimes it hangs and sometimes it restarts. Its crashed everywhere from starting udev to the login screen.
I've been using kubuntu for the past year because I have the same problem with F10 and F11. I dual boot with Windows 7 for games.
System specs: Motherboard: MSI P45 Platinum Processor: Intel Core 2 Duo E8500 Video Card: Radeon HD4850 Memory: 4GB (2x2GB) Patriot HDD: Main: 250GB SATA Western Digital code....
I'm hoping someone knows about this one... I'm running the latest CentOS 5.4 with kernel 2.6.18-164.15.1.el5 (x86_64).When I boot the machine, it gets to the udev starting bit, hangs for like 5 minutes, then prints a message "Failed, will continue in the background." Then it boots OK after that.I tried booting again with the kernel option (from grub) "udevdebug", and what I saw when it tried again was a million messages saying it was waiting for "/sbin/pam_console_apply" to return, but I guess it wasn't returning... ;) Again, after 5 minutes, it gave up and finished booting.Now, this host is an LDAP client.
I figured that may have something to do with it as it is likely that pam_console_apply tries to make an LDAP lookup, which is wrong, because networking hasn't even started yet. If I disable LDAP (by removing ldap lookups in nsswitch.conf), I get no pam_console_apply errors from udev and it boots quickly. But that's a bummer, I need LDAP on this box, and I don't want my boot time to be 7-8 minutes. ;)Presumably before, when LDAP was enabled and it waited 5 minutes and then notified me that it will "continue in the background", that it was eventually successful after networking started. LDAP otherwise works fine on this box, just like all the other servers we have.This is new behavior, I've not seen it with CentOS 5.3 and below. Has anyone seen this? Any hints on what I can do to avoid it? It seems like a pam bug or something, but I don't know for sure.
Installed FC-8 (DVD) on old dell 866mhez desktop years ago; works like a champ. Inherited dimension 2400, used same DVD. No errors loading (std config). Reboot and linux starts. Gets to 'Set clock - ok' and hangs on 'starting UDev'
Celeron 2.4G bus speed 400M L2 cache 128kb 384 DDR SDRAM FC-8 220.127.116.11-42 on the DVD.
I know FC-12 is out, but with older HW, trying to stay compatible.
I want to try the new 11.1. When I start the installation (x86_64 DVD), the startup is hanging. The last message is "Starting udev...". Keyboard is completely frozen, only reset button is working. Mobo is an Intel DG965WH with 4GB RAM and ATI Graphic card (ASUS1950pro). My opensuse 11.0 runs without any problems.
I have a SSH box which is command line only and no X, this will be used remote and i'm trying to get the wireless network configured to start at boot. I'm using wpa_supplicant as the access point is secure with WPA2 At present if I send the following commands the machine will connect to the wifi and be reachable via ssh
I just finished installing CentOS 5.2 x86_64 on a Dell Dimension 3100 (Pentium 4 with 64-bit support). On the first boot, after completing the final config steps (firewall, SELinux, time server, etc), the boot hangs on "Starting xend:". I have completed a successful installation on another Dell machine (different processor), with the same installation options (I recorded all of the steps and followed them for the second installation).
where the install hangs at the "Starting udev..." and nothing seems to be able to get the system to run the install. I have tried starting the install with edd=off, apci=off, noapic, apci=ht, and a variety of other options listed on posts. I have tried versions 11.0, 11.1, 11.2, and 10.2 with no success with any of these. With 10.2 it does not hard lock the system so I am able to Alt-F4 to see some debugging info and I am getting the following "it trap divide error rip:2b6b0c281123 rsp:7fff9e95fdf0 error 0". With any of the version 11 installs the system completely hard locks with "Starting udev..." I have verified the installation media of all distros, re-downloaded the iso files, and burned using the slowest setting all with the same results. I have gone into the bios of my machine and disabled the APCIMCFG, High Precision Event Timer, SW Mem Hole Remap, and UnGanged Enabled. I have also tried to enable this IOMMU option for the memory but still nothing. I have tried using just one of the SATA drives by unplugging the other 5 and same results. I did notice that from time to time I see something from squashfs.ko saying "Clocksource tsc unstable"
I have encountered the same problem as indicated in this post: "udev hang after upgrade from 5.3 to 5.4"[URL]... I'm testing the upgrade path to centos 5.4 on several virtual machines prior to upgrading our production systems. I have upgraded centos 5.2 --> centos 5.4 and centos 5.3 to centos 5.4. In both cases udev hangs after the upgrade. The following message is displayed on the console: "Starting udev: Wait timeout. Will continue in the background [FAILED]"
I found another related post: "udev hangs on boot for a long time, suspect pam_console_apply"[URL]..So, I booted by VMs using the "udevdebug" option to grub and received the same error message - "udevd-event [###]: run_program: Waiting ## seconds for output of '/sbin/pam_console_apply /dev/..."
In my /etc/ldap.conf file "bind_policy hard" is commented out. I added a line "bind_policy soft" as described in the post and my VMs booted fine. NOTE: This problem is not encountered with a fresh install of CentOS 5.4 and the "bind_policy hard" option in the /etc/ldap.conf is commented out as in the upgraded systems. What is really causing this problem and how do I get it addressed? I have a couple hundred systems to update from various releases of CentOS 5 to the latest current version 5.4. It would be nice to get this bug squashed..
I am booting centos 5.3 on x86-64 machine. The system hands at line "Starting xend:". Is there any way to skip starting xend service during boot or disable it during boot so the system finally reboots.
I'm trying to arrange my 4 NIC's on CentOS 5. Two of them are build-in motherboard nic's and the others are PCI-E Dual Intel card. I'm wondering if someone succeed with udev renaming rule based on BUS location like ID=="0000:03:00.0" ... etc
I'm trying to disable TCP Segmentation offloading across the board in our datacenter to improve performance. Reading the history in the CentOS Bugzilla and the upstream's Bugzilla, they recommend doing this within the udev rules. See:[URL].. So, I created a new udev rules file that looks like this, as filename /etc/udev/rules.d/50-eth_tso.rules:
Can anyone out there figure out just what I'm doing wrong - I've been struggling with this for about 2 hours trying to make it work, and simply can not figure it out - and would like to not resort to hacking the problem and adding the ethtool commands to /etc/rc.d/rc.local!
I haven't updated my centos box for almost about a year, my theory is if it ain't broke don't fix it.These last two weeks I've been replacing hardware, a motherboard, memory, processor, and a hard-disk. Everything worked fine with the current 2.6.18-128.1.10, but I decided that I should upgrade to the latest along with all the new packages. But in doing so I would need to recompile the driver module for the raid controllers, rr1740. So I recompiled them using the 2.6.18-164.1 build while I was in kernel 128. When I was done, I restarted the machine and when it booted to the new 164 kernel, it came back very long error messages but here's what I can remember off the top of my head.
During the boot process the machine (Fujitsu Celsius M470) hangs about 4 min at udev:loading drivers. After that it continues and I can work with the OpenSuse 11.2 system without problems.I activated the debug log in /etc/udev/udev.confthen I see that it is doing a lot in that time, at the end I see the message:udevadm settle timeout queue contains: a long list of pci/usb entries (no entries in any log for this)
in the logfile I find:udevd-work: '/sbin/modprobe' (stderr) 'FATAL: Error inserting ipmi_si (/lib/modules/18.104.22.168-0.1-desktop/kernel/drivers/char/ipmi/ipmi_si.ko): No such device'there is no ipmi. how can I deactivate the loading of this module?
udevd-work: '/sbin/modprobe' (stderr) 'FATAL: Module input:b0019v0000p0001e0000_e0,1,k74,ramlsfw not found.' Mar 17 11:35:36 mira udevd-work: '/sbin/modprobe' (stderr) 'FATAL: Module
In Ubuntu 910 on my Asus EEE-PC1005HA, I notice that during boot, when the screen is dark between the plain Ubuntu logo and the animated purple screen, there is a brief message:udev cannot read file (rest of message goes by too fast for me)This doesn't seem to hurt anything. My system has been working just fine for a long time. I don't know how long the message has been there. Perhaps it merely lengthens boot time? Should I care? If I should care, where might the message be logged (so that I don't have to photograph the screen)?
I'm writing for my brother who was running Karmic on a Microtel desktop.He'd been having trouble with blank cds (data cds and dvds didn't cause this problem) crashing his box so he uninstalled and then installed udev package.Now when he tries to boot the box goes into a memory test and then reboots into the memory test over and over. He tried to check the installed kernels to choose one that might boot but there are none listed (he pressed "esc" to see the list-it's empty).He tried booting from a live cd and that won't work either. The cd drive spins but nothing else.
This morning I had the courage to run an apt-get autoremove which took some 275 packages off my hard drive, and now I am experiencing a delay of about 40 seconds at boot, after grub, before the plymouth splash appears. The cursor blinks on a black screen while the hard drive churns away. Finally two error messages appear too quickly to be read, and then the bootsplash kicks in. I can find the instant in the dmesg where the delay happens, but can't locate the cause. Here's what my dmesg looks like:
The laptop is an Acer Timeline X 3820TG, with the dual GPU "switchable graphics." These dual graphics cards have given me enough trouble in the past that I wouldn't be surprised if they were the problem. But the hard drive action sounds like a 'fsck,' and seems to be contemporaneous with the dmesg notice that the root partition is mounted.
Incidentally, my boot wasn't all that fast before; I would not be surprised if this delay was preexisting, but used to happen after the plymouth boot screen was already on screen. Still, if I can get rid of this one ugly delay, I can have a fast (c. 10 secs) boot time.
I am trying to make gentoo boot faster and in my searching I came across this article http://lwn.net/Articles/299483/. One of the things they did was revert to a "persistent, old-school /dev directory so that boot doesn't depend on udev". I would like to know how to do this, but when I searched for disabling udev all the forums say that its a bad idea. All I want to know is how to make a static /dev directory.
I've been having problems with start_udev on my machine post kernel 2.6.18-162 on my CentOS machine. A previous install would work on the old kernelut not the newer ones. I recently did a completely fresh install of CentOS 5.5o see if maybe there was a orruption in my install when it upgraded,t I still have the problem of udev hanging on startup.Using the rescue option on the disk, I've managed to track the problem down to the 50-udev.rules file. Through trial and error, I moved all the .rules files out of the rules.d directory, and added them back one at a time to see which one(s) caused the system to hang, and which ones it carried on booting as normal with. The only one that causes it to hang is the 50-udev.rules.
From what I can tell, this rules file is responsible for letting udev check various pieces of hardware. I think that it is failing whent runs modprobe on a pci device address.Only problem is I don't understand the rules file syntax, so I don't know if I can simply comment out or change a line in this file to skip the device that its looking for.Can anybody help me track down the specific device/line that is doing this?(I've kept the file out of the folder for now and my system appears to continue operating, but I get the occasional problem that for all I know could be due to udev not having a complete start up).
i'm heaving the following message at boot time: "Starting udev: udevd: unknown key 'DEVTYPE' in /etc/udev/rules.d/70-cups-libusb.rules:6", i guess it's something about usb printing support but i am not sure, and i don't know how to fix it, does any of you guys know what this exactly means and how to fix it