CentOS 5 :: Slow Boot - "Waiting For Driver Initialization"
Sep 23, 2009
I have a question about the CentOS boot process. During boot, following the initialization of the software RAID drivers, I get the message "Waiting for driver initialization", and the boot process hangs for about 20 seconds. It's not a big deal because I don't have to reboot often, but I'd like to know - is there a way to disable the functionality that causes this, whatever that is?
I run many 5.2 virtual machines inside of VMWare ESX3.5 I've updated a couple of test VMs from 5.2 to 5.3. The thing that stands out is that during boot time, the sequence gets to this stage:
device-mapper: dm-raid45: intialized v0.2429 Waiting for driver initialization.
Here it takes about 3 times longer than the previous Centos 5.2 (about 9 seconds instead of 3). Whereas inside a physical box the wait in 5.3 is the same as it was in 5.2
Up until very recently I've had a wired network, and at boot I'd see messages about DHCPREQUEST and DHCPOFFER and stuff as it set up the wired network.
Now I've just got wireless working instead, but it still tries to use DHCP on the no-longer-existing wired network. So it says "DHCPDISCOVER on eth0..." and waits for a bit, then again and waits again, and all the time the boot is waiting for a reply to its DHCP requests and it's not going to get one. It doesn't seem to do any harm, because once it's given up and proceeded with the boot then the wireless does seem to work fine, but I'd like to speed up the boot a little by cutting out this needless waiting. Has anyone got an idea how I can stop it? I tried in Preferences-Network connections and in Administration-Network, and in System Tools-Network tools, and also from the network icon in the task bar, but I can't find anything which lets me configure the wired network eth0 or disable it or disable the DHCP.
This is a standard install, just like I've done dozens of times before.
Plain vanilla, just installed.
When I boot, I get to the splash screen and it doesn't go into the default selection.
Could this be a Hardware thingy? The reason I ask is because I've had this issue happening with 5.2 on the same machine. I just formatted it completely and installed a fresh 5.3 i386 on it and I get the same behavior.
[root@server ~]# cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that
My boot time seems to be relatively slow & looking through the log file I notice that "ppdev: user-space parallel port driver" takes about 25 seconds to load.Is this normal/necessary to load? My laptop is a toshiba satellite pro running 10.04.
I have added a new network card on my Cent OS machine. This is a RTL-8139/8139C/8139C+ card. When the machine boots or I start the network it displays "eth1 does not seem to be present,delaying initialization."I have gone through different posts on the forum with similar problems and have posted output of some of the commandsOutput of lspci is
I'm running CentOS 5.2 on an ASUS M2NPV-VM motherboard. This motherboard includes an NVIDIA nForce 430 built-in Gigabit MAC (network interface). I've also installed a second PCI network interface card (NC100 Network Everywhere Fast Ethernet 10/100). The PCI-based card was configured as eth0, while the built-in NIC was configured as eth1. The machine is used as my firewall/router, so eth0 is my internal interface, while eth1 is my external interface. I've had some intermittent problems with the built-in (eth1) NIC. When booting the machine and it attempts to bring up the interface, I get the following message: forcedeth device eth1 does not seem to be present, delaying initialization From that time forward, there is no eth1, and so no external network, etc. If I try running /etc/sysconfig/network-scripts/ifup eth1 (from that directory), it results in the same error.
Originally, I was getting this error when installing the operating system on the machine. At that time, I was using a 75' ethernet cable (as I was working on the machine in my office, and the external ethernet jack was in another part of the house). As soon as I moved the machine to its permanent location (which is within 2 feet of the ethernet jack), the problem went away. However, I just updated the kernel (via yum) from 2.6.18-92.1.22.el5 to 2.6.18-128.1.6.el5, and now it fails 9 out of 10 times. I'm not even sure what I can do to debug this. I'm assuming there is some kind of timing problem with the initialization. Is there a configuration parameter I can set to allow more time for the initialization to do what it needs to do, to prevent this error?
Is there is a way to specify a static IP address in the parameters supplied to the Linux kernel at boot time? I know that I can do it with a start-up script called from my rcS file but it would be really convenient to specify it in my boot parameters.
So I installed the Unison synch software with sudo apt-get install unison-gtk. When I set up the two directories for synchronization it looks like this: $ unison ssh:\SERVER\pathpath /var/www/path/path/path
I am getting this error in terminal Uncaught exception Gtk.Error("GtkMain.init: initialization failed ml_gtk_init: initialization failed") Fatal error: exception Util.Fatal("Error in getLogch: /home/path/.unison/unison.log: No such file or directory"
I'm working on a kickstart install to automate a lot of monotony doing installs. When i use the kickstart install i get an error on boot saying "File based locking initialization failed" "no volume groups found". Then it proceeds to boot up with no issues and appears to work just fine. Below is the section of my ks.cfg for creating the partitions: %include /tmp/partition.cfg is included where the partition info usually occurs. The user is prompted in the pre script for how large they would like the partitions to be and then the script below creates the included file with partition info
When I boot off of Debian Kernel 2.6.26-2-686. This is what happens. It stops at attached scsi generic sg5 type 0 After 4 or 5 minutes it comes back and says.
Gave up waiting for root device. Common problems Boot args (cat /proc/cmdline) Check Root= (did the system wait for the right device) Missing modules (cat /proc/modules; ls /dev Alert /dev/sdd8 does not exist dropping to shell /bin /sh: can't access tty; job control turned off If I boot off Debian Kernel 2.6.26-2-686 (single user mode) Then use Control-D it boots fine.
I installed Debain Lenny as a dual boot with ubuntu 10.10. Chose not to install Grub legacy in the mbr or in any partition because I thought grub2 could handle it. All went well, updated grub2 in ubuntu and it found Debian, but when I try to boot into Debain it hangs at - waiting for root filesystem. I've searched, but can't fathom why this is happening, much less how to fix it without just reinstalling it.
I've just upgraded my wife's netbook to UNR 9.10. This seemed to go well and the netbook has been working fine since. Yesterday my daughter used the netbook with out any issues, but when my wife tried it halted during boot with:
Swap waiting for UUID: xxxxxxxxxxxxxx
After a couple of reboots it started working fine, but looking at /etc/fstab the entry for swap is different to the UUID shown in blkid Do I just update fstab with the UUID from blkid?
The case is that I've got 2 harddisks. On the one windows xp(slave) - and on the other one ubuntu (master). During the boot I get these errors... "Gave up waiting for boot device" "Boot args(cat /proc/cmdline)" "Missing modules (cat /proc/modules; 1s , dev)" "/dev/disk/by-uuid/f96603ce - does not exist"
These problems occured because of this: After using ubuntu I tried to reset my bios, because else it couldn't have found the disk with xp. And I didn't disconnect the disk with xp while resetting the bios. And now the system can't find the disk with xp any more when booting. Is there a way to finding the disk..? And I'm in doubt about IF I've resetted the bios at all. I miss a manual for PCCHIPS M851. May be it can take 20 minutes for the bios to be resetted? The shop where I bought the motherboard doesn't exist any more... and don't know the manufacturer. Could I damage the motherboard if I tried rebooting lots of times to get it work?
all is well on my headless Lucid server until a recent apt-get upgrade && shutdown -R now ... it did not come back up? after i moved a screen to the other side of the house, i found fcsk waiting for input during the boot process errors on / ... (I)gnore / (F)ix " ...so i had to attach a keyboard just to push <F> i could change /etc/fstab so it never runs fsck, but this doesn't seem wise. how can i make it <F>ix automatically ? ( or maybe after Xsec )
ubuntu 9.10 is not booting shows Gave up waiting for root device.", (initramfs). how to boot normally from this problem. The problem is coming from installed system.
I recently installed Ubuntu 10.04. I'm trying to become familiar with the file system. I noticed my MP3 player (USB) is not mounted automatically when I plug it into the USB cable. I searched Google to find out how to auto mount this device and it worked. However, I didn't give this enough thought to what I was doing I guess. Now if the MP3 player is not connected to the USB cable the boot process stops at the splash screen waiting for the device. The window on the screen states the following:
The disk drive for /media/sdc1/ is not ready or not present. Continue to wait or press S to skip mounting or M to manual recovery.
I don't remember what I did to start this whole mess so I don't know how to undo it? Could someone please help me undo this? I would like the device to auto mount ONLY if it's plugged in if this is possible.
I've installed squeeze and wheezy on an old Toshiba Satellite 210 CS laptop with 48MB RAM and a 20GB IDE harddrive.Grub2 won't boot at all and stops with a "error: cannot allocate real mode pages". The solution to that is to use the grub-legacy package.The boot then fails with "waiting for root device" and drops to an initramfs shell.
just installed ubuntu 10.10 on my external usb hdd from my 8gb flash drive doing this on a laptop, my primary hdd (internal) is running windows (230gb of 250gb used) so i got an external hdd (2tb) and I decided to install ubuntu on it
I had to reinstall 10.04 because I got an error, waiting for root device. And I figured I knew why I got this error: I changed my xconf.cfg (or whatever the file is in /etc/x11/) -- So this time I downloaded the 64 bit, because I have a 64 bit computer, so though, might as well get it! I've narrowed the problem down to this:
After I install nvidia settings (the x server or whatever?) And change my view to TwinView (I have my laptop monitor and an external monitor), and save the config file, this happens. I will do some more testing, but here is the whole error message: Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline) - Check rootdelay= (did the system not wait long enough?) - Check root= (did the system wait for the right device? - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/bcb49367-8554-4116-8e4d2b39d92415cf does not exist. Dropping to a shell!
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash) Enter 'help' for a list of built-in commands.
I am attempting to load CentOS 5 on an Acer 6900 desktop and I'm not even getting out of the starting gate. I am familiar with using linux but not the install procedure which is why I am beginning to dive into this. However, when I bring the system up off the Linux boot disk and go to install it's not even giving me the option of the controller so I can begin installing the os from the dvd-rom. This is what acer lists as the controller for the 6900: ich8 serial ata storage controller 2820 linux driver. I cannot find this driver for linux anywhere.
i upgrade a machine running centos 5.4 to 5.5 this morning. After the update the X start i saw the pointer and a black backgroud only the desktop doesn't appear.The machine is a barebone with this configuration
I upgraded to -current last night hoping to improve my Intel 845G graphics controllers functioning in X, I've had to use the vesa driver for stability. The upgrade was completed but KDE seems as slow as ever. Here's some snippets from Xorg.0.log:
X.Org X Server 1.7.5 Release Date: 2010-02-16 X Protocol Version 11, Revision 0 Build Operating System: Slackware 13.1 Slackware Linux Project Current Operating System: Linux speedy 2.6.33-smp #2 SMP Sat Feb 27 20:12:16 CST 2010 i686 code....
It seems I'm still using the vesa driver, any ideas on why the intel isn't being used and how to fix it?
I have Centos5.4 loaded on a late 2008 MACBOOK Pro and would like to get wireless working. I've attempted to download the broadcom driver and create a driver module with no luck.
I have an MSI K9A2 Platinum mobo, which has a 10/100/1000 Fast Ethernet Realtek 8111B built-in, a D-Link DIR-655 Router and a DSL modem. Compared to Windows Visya and other Linux distros ( Fedora 11, Suse 11.1, Mandriva 2009.1 ) access to the internet is much slower. It seems there is a noticeable delay when running CentOS 5.3. before internet access kicks in each time I am surfing the web or updating my system.
Is there any way I can speed things up, or determine why CentOS 5.3 seems much slower ?
Anyone know why my fresh installation of centOS server is so slow? Seems like it takes over a minute to execute a command, im not doing anything complicated either. Secondly, how come at times when I type reboot the machine starts to beep, one long loud annoying beep.
i have a working Windows 7/xp dual boot prior and post to having installing ubuntu, after installation i removed the usb thumb drive then preformed a reboot. when i got to boot loader where i normally pick Win7/Xp/Linux and pick linux it then runs grub. I get the boot loader screen, select Ubuntu 10.10 "Gave up waiting for root device. Common problems:
- boot args (Cal /proc/cmdline) - check rootdelay= ( Did the system wait long enough?)
From booting back of live usb
[Code]...
i tried hitting e and changing (there was more before this)linux /vmlinuz root=/dev/sdd1 ro quiet splash which kicked me back to same point saying it could not find it at sdd1