CentOS 5 :: Udev Hangs After Upgrade To CentOS 5.4?
May 7, 2010
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'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.
i am trying to install centos 5.5 x86_64 as a guest OS in vmware server 2.0.2 using netinstall iso. Installation runs fine until the point, when it tries to install selinux-policy-targeted-2.4.6-279.el5.noarch, the whole virtual pc hangs at this.any ideas? i tried to google few things about this, but i have found nothing. this has happened 3 times in row, whole virtual pc always hangs at the same package. i dont have any other problems with vmware, gentoo runs and installs fine in it.i would prefer to do installation using netinstall.iso, it would take a lot of time to download all cds or whole dvd and all i require is a very basic set of packages.
My Dell poweredge server running CentOS 5.4 and booting kernel-2.6.18-164.15.1.el5. All boot processes seem okay and the graphical screens for CentOS operate, but just before the desktop loads the screen goes blank and the arrow/cursor is being circled by small spheres. This remains indefinitely. While the arrow is being circled, here are the results of 'getinfo.sh device'
Quote:==================== BEGIN uname -rmi ==================== 2.6.18-164.15.1.el5 i686 i386 ==================== END uname -rmi ====================
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!
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 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.
I have an intel DP35DP motherboard - ICH9 southbridge - set to AHCI mode. Working fine under 5.2. Yesterday I updated to centos 5.3, and got kernel 2.6.18-128.1.16 and now it can't boot. It hangs trying to read sata1 with DRDY errors and exceptions.So then I installed 5.3 from a DVD onto a new drive, and got kernel 2.6.18-128. This worked, most of the time, but occasionally gave me this error. I then updated my BIOS, and the error went away.Then I updated this new working drive to the latest kernel (yum update again) and got kernel 2.6.18-128.1.16, and now it wont boot again, with the same message.
have all ways been hiding in the background read not say a thinglets start well i look after 2 dell poweredge 2650 with 12 gig ram installed servers has been running fine onwell i though it was time to upgrade to 5 all went fine till reboot Memory for crash kernel (0x to 0x) not within permissible range ! well what i have been reading this is the norm for now What is mean by ignore it? LoLwell so i did the system keeps boot till i get to this linesbin/mingetty: /sbin/mingetty: cannot execute binary file alot, and it shows. INIT: Id "5" respawning too fast: disabled for 5 minutes ...so maybe its a memory issue so took 8 gig out left 4 in the system now it reboot alls good with only 4 gig of ram installed so is there a way to fix it to use all the ram can i get the system boot on 4 gig and then add the 8gig later on
I make upgrade from CentOS 5.4 to CentOS 5.5. Architecture is historical i386. On first boot my system was freezed by disabled earlier but not removed manualy writed xdm service. I disable it. But not found network. I see hardware address of card fe:ff:ff:ff:ff:ff. This address is not normal. But how to restore eeprom of this network adapter?
I don't think its trouble of new CentOS. I think this is random incident.Configuration of computer is Intel D510MO motherboard with integrated atom processor and realtek 8111dl nic. I know some trics about fix mac address in centos, but how to fix this address in bios?
there is a bug on the quad core B2 opteron cpu there is a beta patch available , but only for for 2.6.24 kernel i am very happy with my centos, and i would upgrade the kernel to try this patch i am new on linux, so i need a precise tutoriral to upgrade and keep the actual configuration of the kernel
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/126.96.36.199-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
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 just installed slack-13.1 on an acer aspire one netbook from a usb stick by booting the install kernel with noudev. I was able to do a complete install including lilo but upon rebooting my boot hangs when encountering my webcam.I see enough info to note the id as 0c45:62c0. This is a microdia webcam which I may be able to do something about later but in the first instance I'd like to be able to boot my system. The bios is very basic and there is no way to disable devices.
I need to set a new centos on an "old" box : PIV 1.8 1.5Gb
The Centos will run on a 40 Gb PATA Hard Drive set as main drive, The Box runs a another SATA Drive with 2 different windows installations.
The installer first hanged on the loading ata_piix driver screen so I restarted with the irqpoll option to complete the wizard. But I'm now stopped on the last X screen : starting installation process please wait.
I have changed the hard drive, the DVD drive, the Centos DVD, tried with a 5.3 and 5.4 with no success.
I'm attempting to install CentOS 5.3 on my IBM IntelliStation Z Pro 6221/37G, powered by some extra equipments as nVidia NV44 GeForce 6200 video card, MV88SX6041 SATA II Controller, 2x1GB DRAM.
The problem: CentOS 5.3 DVD i386 didn't install, the screen becomes unreadable because of vertical bars just after anaconda start running. Choosing at boot time different "linux resolutions" did not help, as well as the "text mode" still useless because Logical Volumes need to be created/handled and the graphical interface is mandatory.
Same result booting CentOS 5.2 Live CD. This sounds really strange to me. I checked iso images against their md5sum and are ok. Centos 5.3 x86_64 does not boot yet :"Your CPU does not support long mode", evem they are 2 x Xeon 2.8GHz / 512KB
I have a strange issue. The only time I have trouble with yum is when awstats is included in an update. When it is, it always hangs on it when it gets to it. Yum will not complete. I have to cancel out... kill the yum pid and do it again. Tonight I did a yum-complete-transaction to do some unfinished actions - one included the removal of an old awstats - it hung on that.
I'm not sure what's going on with this install, but I started with a fresh install on a 250GB IDE disk, assigning /dev/hda1 to linux, and the rest (/dev/hda2) to swap. when it tries to boot.. I just get GRUB hang. Should I have installed a small FAT32 partition in the first sectors of the disk for the bootloader?
The bios in this machine is very old (Dell 410 precision) and Dell offers no updates, so I suspect this has something to do with how the old bios is trying to boot, but ?? not sure how to fix it. try lilo, or alternate bootloader???? Just looking for a fix to the boot problem. I would prefer to boot from the disk, booting from cd/floppy/pxe not so desirable.
I have a centos 5.5 server which hangs with yum update. i did a yum clean all. removed the rpm en /_.rd een did a rebuild. In the logs there are no errors. If there is another update except these to he works just fine. Disk space is enough free. Any ideas? i am runnung yum update as root . when i do a full report of yum i get this:
I am trying to boot the CentOS live cd off of usb. I used unetbootin to put CentOS on my 8gb usb drive after downloading the DVD iso. During boot it loads the image and continues until it reaches this point.
>Linux agpgart interface v0.101 (c) Dave Jones >Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
After this it hangs and won't continue. I am using a Compaq evo n800w and the bios is just updated to the latest version.
I had a spare computer (Dell Optiplex GX270) which I had installed Centos 5 on and have been setting up asterisk (telephony) on it. My main computer has broken down and I need to load Windows XP back on to the Optiplex.
I put the Windows XP disk in the drive and directed the bios to boot from the cd. I get the message "Please wait while windows inspects your current hardware configuration" and then after about 10 seconds the screen goes blank (the cd also slows down and then stops) and then the systems seems to just hang.
If I take the cd out and boot from the hard drive Centos loads normally; therefore I'm assuming my problem is not a defective hard drive.
I've spent quite a bit of time searching online for a solution and although there seems to be several different situations where the above can occur, I'guessing that my ssues are related to either partions/mbr and or the bios/cmos. I'm really new to Linux and not knowledgable on partitions and cmos so I'm hoping someone could help me out here.
I've checked in the bios and could not find an option to restore the settings to factory defaults. Should I pull the csmos datterry out? Does this restore the bios settings to factory defaults?
With the 5.3 CDS I started an install got through to 98% of CD 3 but I was called away. Came back this morning and the box was on, but had frozen. Every time I reboot, cold boot, I come up with black screen. Vers 0.97 <grub> Minimal BASH-like line editing is supported. TAB etc. Is there a way I can get to CD 4 and continue the install, or am I back to the top again?