considering the claims on the ultra-fast-boot in new Ubuntu versions, I think my 1-2 minutes boot on a brand-new laptop (SONY Vaio CW2C5E) is quite slowish. I noticed that before the Ubuntu splash screen comes up, the screens stays black for 30 seconds with a blinking cursor. I also found a 20-second gap in dmesg which I can't explain:
Code:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.35-7-generic (buildd@crested) (gcc version 4.4.4 (Ubuntu 4.4.4-6ubuntu2) ) #12-Ubuntu SMP Fri Jul 9 21:54:03 UTC 2010 (Ubuntu 2.6.35-7.12-generic 2.6.35-rc4)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.35-7-generic root=UUID=fe1a051b-27ef-43bd-88c8-fbfd8f3d4e7f ro quiet splash
I have installed "open-SUSE 11.4" on a "500GB Free Agent External Hard Drive". I didn't have any problem in booting since last week that I booted it from my laptop. Also I did it before several times from then when I try to boot it e.g. from an "Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz" PC the time between loading INITRD and starting boot sequence messages lasts nearly 30 minutes!(i didn't actually measure it but it take a long time in the same order). after starting boot sequence which is showed on monitor everything looks normal. e.g copy of files would be done by speeds between 2MB/s to 30 MB/s depending on the targets.I used to use the external hard derive to boot from different laptops and PC's from start but I didn't have such a problem anytime.
just start Ubuntu 9.04 said: File system chek failed a long is beging saved /var/long/fsck/checkfs if that location is writable Please repair the file systmen manually A maintenance shell will now be started Ctr+ D terminate this shell and resume system boot. Give root password for maintenance or type Control +D to continue. I did Ctr+D , and after login said , that can not find /home. I starte with the live cd:
Lately about half the time I boot up on 9.10 it stays at the tty & asks for my login & password. It will just stay there for about a minute or so & thenboot up normally whether I enter anything or not. I have it set for auto-login & it never was a problem before. Some times it boots up normally without going into the login screen at all. The only thing that is different is one of the 5 year old kids I let use the computer for the internet & the computer doesn't always get shut down right(turn the power off). I suspect that has caused the problem but it happens now even when I know its been shut down right.
I want to make my machine to PXE boot windows from another machine having RHEL5.2. I know the procedure to PXE boot linux, but I want to know is it possible to PXE boot your client machine with windows XP.
After I installed a new hard drive, when I booted up into Ubuntu, it would give me this error: "failed command: WRITE DMA". So I tried the workarounds and I guess it just covered the log with the Boot Splash, now it's taking a long time just to boot up.
I recently changed my computer so it would auto boot into Ubuntu, but if I hold down the shift key, I can bring up the GRUB menu so I can choose Windows in the rare times I use it[URL]Anyway, I noticed that when I did that, it actually took longer to boot. I timed it today and it took 45 seconds from the time I pressed the power button to get to the login screen! My friend uses Linux a lot and says even with Ubuntu (which he thinks is "too slow") it shouldn't take that long.
I'm running ubuntu on a macbook5,4, and I get a 30-second long pause during the boot sequence. (I have quiet turned off.) This shows up in dmesg as:
Code: [ 1.847208] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 2.000059] usb 4-1: new full speed USB device using ohci_hcd and address 2 [ 2.239138] hub 4-1:1.0: USB hub found [ 2.242107] hub 4-1:1.0: 3 ports detected [ 2.590102] usb 3-5: new low speed USB device using ohci_hcd and address 2 [ 2.672282] scsi 6:0:0:0: Direct-Access APPLE SD Card Reader 1.00 PQ: 0 ANSI: 0 [ 2.672863] sd 6:0:0:0: Attached scsi generic sg2 type 0 [ 2.674243] sd 6:0:0:0: [sdb] Attached SCSI removable disk [ 3.160035] usb 3-6: new full speed USB device using ohci_hcd and address 3 [ 3.492058] usb 4-1.1: new full speed USB device using ohci_hcd and address 3 [34.373586] udev[417]: starting version 163 [34.422599] lp: driver loaded but no devices found [34.503755] lib80211: common routines for IEEE802.11 drivers [34.503759] lib80211_crypt: registered algorithm 'NULL' [34.508256] wl: module license 'MIXED/Proprietary' taints kernel. [34.508260] Disabling lock debugging due to kernel taint
Details: Linux jagadai 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux Grub. Dual boot with OS X 10.6.4 using rEFIt. It shouldn't be at all relevant, but I'm using E17 on top of kdm.
I installed bootchart and uploaded an image of my latest boot on imageshack: [URL] but I do not know really how to interpret it. Bare in mind that I did not use to have this problem while running Karmic...back then the OS started twice as faster as it does now after the update (now it takes at least 75 seconds to boot) .
It's been a while since this problem started. I have an Acer Aspire 4720z laptop with Ubuntu 10.10 installed. My laptop takes a whole damn 1.5 minutes to boot up and login (measured according to bootchart; I have auto-login enabled) (The majority of this 1.5 minutes is taken up after boot up, so it might indicate a problem with Xorg.)I don't know whether this is relevant, but when I boot up, a message gets displayed: "ata4.01: failed to resume link (SControl 0)". Also, this problem started right around the time I upgraded from Lucid to Maverick, so it could be some problem with my upgrade.find the source of this issue.ATTACHED: bootchart image from last login.boot.log:
Code: fsck from util-linux-ng 2.17.2 udevd[370]: can not read '/etc/udev/rules.d/z80_user.rules'
I have a 5,2 macbook pro, and I use refit to boot my ubuntu partition. I do not have an OSX partition on the local drive at all. The only partitions that are on the drive are the EFI, ubuntu and swap. Refit lives on the EFI dos partition.I am experiencing a very long delay on power-on before the system will load refit (probably 20-30 seconds) Once it loads everything is normal.
I just want to find out if anybody else is having a similar issue before I start trying to disable services one by one. When I boot in to F15, everything runs fine up to were it starts loading the CUPS module then it hangs for about 2 to 3 minutes, the next thing to load is Samba shares. So it could be either of these or it could have nothing to do with them. Just to add that I made 100% sure that all my samba shares mount fine and are online and have no shares mounting in my fstab file.
I have just upgraded from 11.1 to 11.2. Many problems! Here's the first. During the boot sequence, my system stalls after rtc0: alarms up to one month, y3k, hpet irqs. and before device-mapper: uevent: version 1.0.3 The system waits for maybe 3 or 4 minutes before continuing the boot sequence, so one of those two commands is causing the problem.
I'm trying to track down a longggg delay during OpenSUSE 11.2 boot. It's 1 to 2 minutes long.
1. I upgraded the kernel to "vmlinux-2.6.31.12-0.1-desktop.gz" a while back, and I'm "kind of" thinking this is when it began. It seems in previous versions (I came from 10.3) that the grub menu always contained the previous version. That doesn't seem to be true in 11.2. Is there any way to tell OpenSUSE YaST/zypper to keep the previous version and leave the entry in grub?
2. What does this message mean: "BIOS EDD facility v0.16 2004-Jun-25, 2 devices found"?
I haven't pinpointed the error, and there is nothing really obvious in /var/log/messages. The drives are there, and the network is up. I'm sort of leaning towards the new kernel. What processes wait 60 seconds? If I watch the console closely for the message before the delay, it can vary.
I have a Macbook 5,2, on which I'm triple booting OS X - Linux - Windows, using bootcamp and rEFIt.I had a variation of Ubuntu 10.04 called Uber Student as the linux installation.I installed Ubuntu 11.04 AMD64 instead, by choosing the EFI boot option.Now this gave me some problems. When I shot down, the Macbook gives me a troubling long beep sound.When I start up, I'm still able to boot up into rEFIt and Grub2, but there is a big delay with the screen being black for about 30 seconds and the little white light in the left corner of the Macbook is blinking feverishly. I read something about a guy which had a similar problem and the process seemed to mess up the firmware on his Macbook, so he had to have his MB changed.
What's up with the scary beep sound and the long boot up delay?Secondly, when I want to do an update of the Ubuntu system, the update manager asks me to do a partial upgrade, which includes removing the grub-EFI, resulting in a system that won't boot...
It takes a few minutes to start during boot and I just did a fresh install in a virtual machine. Haven't touched sendmail so it has default config. Someone told me it could be a DNS issue, but I can do DNS lookups and navigate the web well.
I have a roughly 3-year old PC that I put together from parts (listed below) that has been running great with various flavors of Linux as the sole operating system. It is currently running Ubuntu 10.4. A couple of months ago, it started to have intermittent problems booting. The machine will hang before it gets to the Ubuntu "boot" screen with the dots that show progress as the machine boots. If I look at the power on messages from the BIOS, it fails at different points in the process - sometimes during the memory test, sometimes during the search for IDE drives. It fails about 2 out of every 5 attempts to boot. It sometimes takes 2-3 tries at booting before it actually works. Sometimes when it does boot, the Ethernet jack doesn't work and I see errors in syslog about there not being a carrier.
There are no syslog entries when the machine does not boot.The machine is plugged into a UPS. The UPS indicates that it is running at 13% of capacity at 123V/60Hz. I'm in the US.Once the machine boots normally, it will stay up without issues for days.I've checked the 4GB of RAM (I added 2GB to the original 2GB several months ago) using the memory testing application on the System Rescue CD and no errors were found.I've replaced the motherboard battery, which seemed to help for a few weeks, but then the problem returned.I've checked the hard drive for errors using the SMART diagnostics tool in System -> Administration -> Disk Utility and buy running fsck.The interior of the case is not very dusty and all the fans appear to be working.Are there things I can do to investigate and fix this issue other than starting to replace components - starting with the motherboard and the power supply?The parts of the machine:
CPU INTEL|C2D E6850 3G 65N 4M R - Retail (Qty=1, Price=$279.99) CASE ANTEC|P180B BLACK RT - Retail (Qty=1, Price=$114.99) MB GIGABYTE GA-P35-DS3L P35+ICH9 - Retail (Qty=1, Price=$111.99)
I recently broke down in the face of morbid curiosity and clicked that little version update button. it seems to run flawlessly (after i uninstalled the pesky touchpad) but it takes a long time to boot up now. at least a full minute. is this normal?
I will add also that it said my version of grub had been modified (which i dont remember doing, but may have) so i told it to leave the current one in place.
Since recently statd at the boot time takes, more then 30s or even more.
It is laptop configuration, no NFS server(?) lenny with few installs from backports (open office and .30 kernel - for Intel 5300) vmwware (7), as well firestarter firewall
Can I disable it or change the boot order (via sysv-rc-conf ), so I can speed up my boot time?
I use openSuse 11.xx and all was going fine until yesterday. When booting up now, I can't connect to the internet any more. I takes much longer to boot now as if openSuse tries to look for something that disappeared or got corrupt. All started with the latest safety update.
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 was upgrading our lab's dhcp server to Lucid and it totally died. I have it running on a Debian recovery cd right now. I ran into a bug in gtk which I seem to have fixed, but now I have more serious errors. If I boot without a CD, I get dumped into a busybox shell after the machine fails to boot. From the live CD, I tried dist-upgrading again and it dies trying to build and install rsyslog with a broken pipe error. I am at a loss as to what to do from here short of reinstalling (which is the last option as this server has a lot of custom configs on it)
Just the last day or so, I've noticed a long pause when I boot my laptop, with lots of disk activity. dmesg says:
[Code]...
Why would there be a 15-second pause (during which the disk is slammed) between mounting root and mounting swap? During this time I see nothing but a blank purple screen, there are no cycling dots or text scroll. Is this normal and I'm just freaking out over nothing because there's no indicator of progress? GRUB default boot options: quiet splash nomodeset video=uvesafb:mode_option=1920x1200-24,mtrr=3,scroll=ywrap vt.handoff=7
I am running Centos 5.3. I ran no updates, performed no installs, nor changed any configuration immediately prior to this issue. My problem is this: when I run the command startx (default runlevel 3), it is a long time (5-10 minutes) before Gnome startx, and once it does start applications will not run. Also, when I try to use sudo (from any environment, even ssh), it is a long time (5-10) before the command is executed.
I cannot say for sure, but it seems like this is an intermittent problem. Sometimes X takes a long time to start, but once it starts it will launch programs. Sometimes X takes a long time to launch, but once it starts it will only launch certain programs. Though presently X always takes a long time to start, and I cannot successfully launch any programs.
A while back a had a similar problem to this (x taking long time to start, sudo taking long time to execute) and it ended up being a DNS problem. Unfortunately, I cannot remember exactly what it was and I stupidly did not document it. Maybe this is also DNS related, I don't know.
I don't know what log files to look at for problems with X, Gnome, and sudo taking a long time to start.
When booting Fedora 11, my system hangs for a very long time on starting udev. Sometimes I get an I/O error. However, my hardware is fine. I do eventually get in to the system.
I had a dual boot machine with fedora 12 and windows vista and I could use grub boot-loader to switch between two. Few days ago windows got corrupt and I have to reinstall it. I put windows 7 now and as usual it erased grub. So to reinstall I put the fedora 12 installation CD on and followed some usual setup steps. When I got the command line I issued the command "grub-install /dev/sda" (sda not hda because It showed bunch of sda, sda1..) but surprisingly it said grub command not found. I remember doing it before while it worked fine.
I've tried every possible boot variant that is humanly possible and my machine for the life of it will not boot into linux. Ubuntu i386 likes to freeze right at the Logo and progress bar Ubuntu x64 gets all the way to gnome, but it's only a desktop and cursor gParted loves to spout "NTFS Volume version 3.1" while telling me it can't find its own files to load from. Tried both CD and DVD media and varying levels of speed gives the same results.Trying any of it from a LiveUSB boot gives me "Boot Error".Something I noticed is that my drive itself tends to stop reading the CD/DVD at the point of hang. No spin-up and my HDD light flickers at 1 sec intervals.
I upgraded from Ubuntu 9.10x64 to 10.04x64 today (figuring I'd get in before the rush tomorrow). I rebooted, got past grub, and all I got was a flashing cursor... To get a better idea of what was going on, I edited the line I was booting in grub ('e' on the line) and removed the "nosplash quite" options. The machine began to boot and I got the standard stuff that you'd expect to find in kern.log. The system then mounts my drives and that's it, no more output at all. If, however, I plug in a USB device I do get the USB plugged in kern.log message, but the machine never boots into Ubuntu.I'd really like to not reload the machine, it isn't a horrible problem as /home is a separate partition, but I have a lot of stuff I'd hate to have to reinstall. Does anyone have any ideas on how I might get into my installation?
