Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Most of the time when I turn on my laptop (Compaq Presario 2105us with Ubuntu Jaunty on it) Grub will not start and my computer then goes into a PXE. It appears to be attepting to boot from a LAN. In the BIOS the LAN is the last option in the boot sequence so I am not sure why this is happening.
Eventually I can get the computer to come on by just turning it on and off until it boots correctly (usually about 5-10 attempts) I don't think this is good for the components though and would like to find a solution to the problems.
I tried to re-setup Grub from the live CD, but that didn't seem to help, in fact I believe it made it worse as I used to be able to get the computer to come on after 3-5 attempts but now it is 8-10 attempts.
It could be either your drive taking a long time to spin up, or your drive controller taking a long time to initialise. Instead of power-cycling, try the three-finger-salute (ctrl+alt+del)
It could be either your drive taking a long time to spin up, or your drive controller taking a long time to initialise.
Is there a way to remedy this? I have read that this could be an indication of the hard drive starting to fail, but I don't believe this is the case because the computer only started doing this when I installed Ubuntu. So how can I get the drive to spin up faster or getting the drive controller to take less time?
IMHO it could be coincidental that your problems started when you installed Ubuntu. The BIOS is still in control of the boot process and for the reasons already stated moves to the next device. If it was a MBR or bootloader problem I would of expected some type of boot error message. Running smartctl or the drives manufactures diagnostics tools will help determine if you have a HDD that is about to die.
Why don't you change Hard Drive to be the first option.
Also, how old is your computer, how did you install Ubuntu, how many partitions you have there, have you tried to run any other distro, did you use fsck, have you tried to reinstall Ubuntu, was the md5sum OK?
Running smartctl or the drives manufactures diagnostics tools will help determine if you have a HDD that is about to die.
steven@steven-laptop:~$ sudo smartctl -H /dev/sda
[sudo] password for steven:
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Why don't you change Hard Drive to be the first option.
Also, how old is your computer, how did you install Ubuntu, how many partitions you have there, have you tried to run any other distro, did you use fsck, have you tried to reinstall Ubuntu, was the md5sum OK?
I guess I could make it my first option. Sometimes I like to mess around with a live CD of Damn Small or Puppy so I have my CD ROM ahead in the boot order.
My computer is from 2003, I have 1 partition, I haven't installed to HD any other distro, but I have played around with live CD's.
I will run fsck from Knoppix since I get a message that tells me that I could damage my system by fsck on a mounted filesystem
I did not reinstall Ubuntu. I was hoping to find a solution without having to do that. (Plus isn't that the easy way out :-) )
The md5sum was fine and I checked for disk errors when I installed from the CD.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,644
Rep:
You could also try to enter the BIOS boot menu at start, then chose your harddisk manually. Maybe this gives the controller the (eventually) extra time to get up
How to do this depends on the make and model of your `BIOS', but in general, either you select space while the device list is shown to disable the device, or +/- or PgUP/PgDn, etc. . . As I said it really depends on your make and model of `BIOS'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.