Ubuntu 10.04 fails to boot after successful install

Could you describe what happen at boot ?
You could try: https://help.ubuntu.com/community/Grub2#Reinstalling%20from%20LiveCD
But I need more detail

At boot nothing happens - I see the hard disk light flash for about 5 seconds and then absolutely nothing after.

I've been reading through the grub reinstallation directions but not getting very far. Since the system is still running from the initial boot I'm trying to verify the gub install.

fdisk -l lists the boot partition as /dev/sda1 with a message saying that "Partition 1 does not end on a cylinder boundary"

grub-probe -t device /boot/grub returns "/dev/sda1"

grub-probe -t fs_uuid /boot/grub returns "e0090e53-da96-4358-8c12-51f1079943bf"

When I try running:

grub-install /dev/sda1

... I get a warning about installing to a partition instead of the MBR being a BAD idea.

What more detailed information can I provide? As I said, I'm a Linux beginner.

Why are you running a desktop on the server OS. The WHOLE POINT of the server OS is that it is desktopless. The server kernel sucks for desktop environments as it is optimized for background services.

Why did you install the server OS when you so clearly wanted a desktop OS?

Thanks very much <actionparsnip> for attacking instead of helping answer my question.

I installed a desktop in a vain attempt to figure out what was going on. If you read my question I wanted a LAMP server which actually boots.

Now please refrain from adding noise to this thread and allow someone to contribute to answering.

If you hold down the shift key right after POST, that may force the grub screen to appear on single installation systems.
Try installing grub to sda instead of sda1 if it really is not already installed

No, holding down the SHIFT key does nothing.

I used the install disc to go through system recovery and successfully reinstalled GRUB to sda.

Now the system will load GRUB but I have no idea what to do at the grub> prompt.

How do I instruct grub to load Ubuntu?

Normally, installing grub should find all the operating systems and make a menu for you to choose one. Again, hold down the shift key to force the menu to show up. You have 10 seconds to hit an arrow key to prevent the default boot selection. Then type "e" to edit the default, and examine the commands. Installing from a cd, you should have the correct devices -- sda1 or a uuid. you can change an entry, and control x will boot with the changes. As soon as you get a successful boot, run
sudo update-grub to fix any problems permanently.

Normally I should. I believe that part. It doesn't.

Obviously it's a serious installer bug - repeatable and blocking successful install of the system. On a very generic Dell system, with all default installation options.

Unfortunately I am a beginner and after a full day of re-running the installer and reading umpteen pages about obscure grub commands it still doesn't work. So I give up. My options are to pick another distribution or find another computer.

No, holding the shift key does nothing. I can't find any way to bring up a grub menu. After re-installing grub where the installer failed it simply loads as far as the "grub>" prompt.

I simply shouldn't have to run any grub commands. That's not an acceptable answer.

So you don't have a blank screen, but ones with "grub>" prompt. Please be accurate and exhaustive when you report issue.
I apologize for actionsparsnip, but he is sometimes tired answering so many questions.
Instead of "grub-install /dev/sda1", you should have type "grub-install /dev/sda".
The list of commands should be (for reinstallation Grub from CD) in your case:
    sudo mount /dev/sda1 /mnt
    sudo grub-install --root-directory=/mnt /dev/sda
which means: BIOS load first the boot sector of disk, and will search boot files in /boot folder of sda1 partition
If it fails, could you follow this procedure:
---
provide data about boot configuration

There is a standard script provided to analyse boot configuration.

Could you download script at:

   http://sourceforge.net/projects/bootinfoscript/

Then in a terminal (Ctrl+Alt+T) run command:

    sudo bash boot_info_script055.sh

This will produce a file named: RESULTS.txt

Paste content of this file in http://paste.ubuntu.com/ and provide in this thread the link to Web page.

Please don't post file directly in thread, else it will make thread difficult to read.

Thanks for your patience delance.

The initial description is correct - after a successful install of Ubuntu 10.04 server the system boots the first time but then fails to boot for any successive attempts.

The behaviour at that point is about 5 seconds of hard disk activity but then nothing after and a completely blank screen.

I read up on Grub 2 enough to follow the commands you mentioned after booting into recovery mode from the CD:

    sudo mount /dev/sda1 /mnt
    sudo grub-install --root-directory=/mnt /dev/sda

On rebooting after those commands the system loads as far as the "grub>" prompt.

I've repeated this scenario close to a dozen times. Yes, that's the definition of insanity - repeating the same thing expecting a different outcome. I suppose it's just because I expect a booting operating system to be a reasonable outcome.

As for providing more data about the boot configuration, I'd love to help someone address this bug but I'm somewhat at a loss as to how to complete those steps with a non-booting system.

How can I copy that shell script to a non-booting system?

Assuming I manage that, how can I upload the result file from the command line?

My best guess is:

- Re-install the system one more time (just did that)
- Download script from the command line (I don't know how to do that)
or
- Copy from USB key (I don't know how to do that)
- Upload RESULTS.txt file from the command line (I don't know how to do that)
or
- Copy to USB key
- Run to capture boot configuration after successful install
- Reboot computer. Watch it fail once again
- Boot from server CD in recovery mode
- Mount installed file system (not exactly sure how to do that)
- Run shell script again, capture result file
- Run grub-install
- Run shell script once more, capture result file
- Reboot once more and watch in frustration as it merely boots to the friendly "grub>" prompt

I'm willing to go through those steps to try to characterize this bug if someone is willing to fill in the "I don't know how to do that" holes so I can accomplish those steps. And also willing to look at the RESULTS.txt to figure out where the installer is going wrong in the first place.

Because none of this will appear to get me a bootable system.

Just to try one more thing I downloaded and burned a Ubuntu Server 10.10 CD and tried installing that. It failed installing the basic operating system - packages it was downloading were reported as corrupted. But that's a different problem.

My final question is how can I best get a bootable operating system? Chuck the Dell box I have in the recycling and buy a different machine because the Ubuntu installer obviously doesn't like this machine. Or pick a different distribution to try? The simple task I'm trying to accomplish is installing a LAMP server.

Thanks very much. I hope I've been detailed enough.

To run procedure:
1-Boot on Ubuntu CD/USB stick
2-Choose "Try". A file system is build into RAM
3-Open Firefox and connect to Launchpad
4-Download file
5-Run file
6-Open paste web site and copy contents of RESULTS file
7-Post returned link in Launchpad
8-You could save file on USB stick (optional)
9-Shutdown computer

Grub from the boot block does not see any of its files. For older machines, it was usually necessary to have the kernel etc. within the first 1024 cylinders, so the trick was to make a small (50Meg) boot partition at the beginning of the disk. Try making a small first partition, use it as "/boot" (in addition to whatever else you set up on the disk) and see if that fixes the problem.

Well, this problem looks like a much more serious bug than I initially thought.

I purchased a different machine to use as my server because I spent far too much time on the Dell box.

I picked up a used P4 HP/Compaq desktop with a 40 GB hard drive. Dead standard box.

Ran through the Ubuntu 10.04.1 server install with all default selections and the same thing happens:

Boots once after install

Log in, type "sudo reboot", system shuts down and fails to boot.

Each attempt to boot it shows hard drive activity for 5 seconds, then a blank screen.

Holding <shift> key down does nothing.

Only thing in common with these two machines is they previously had Windows XP installed. I simply booted from the CD-ROM to install Ubuntu 10.4 server.

This is a straight forward scenario I've reproduced on two different machines.

I ran the CD-ROM verification and it checks out fine. I burned a second CD-ROM from the ISO and it does the same.

Can anyone suggest a different distribution which actually works?

I've run the boot_info_script055.sh script and pasted the result here:

  http://paste.ubuntu.com/565592/

This is from the second computer I reproduced this problem on.

The sequence of events:

- Install Ubuntu server version 10.04.1 with all default options, no additional software
- System reboots successfully
- log in
- sudo reboot
- system will not boot - blank screen after 5 seconds of hard disk activity
- booted from Ubuntu LiveCD
- downloaded and ran boot_info_script055.sh
- posted contents of RESULTS.txt

Odd, the paste info showed no /boot for holding the kernel, initial ramdisk, or grub directory. Does server really do this? Before instantly rebooting after the next install, when you (first) successfully login, run
sudo update-grub
That tends to fix some device errors, on the kernel lines -- that /dev/mapper... business will be replaced with root=UUID=xxxxxx
Do you get any errors before the grub prompt, like kernel not found?

I installed one more time and tried:

sudo update-grub

after the initial successful boot. No change in behaviour, still boots to a blank screen after 5 seconds of hard disk activity.

No, when I run grub-install I don't see any errors before the grub> prompt.

This is failing on two different computers. Is there a server installer available that actually works?

Help! All I want is a simple LAMP server and I've been spinning wheels for more than two days on this.

The boot_info_script did not pick up your /etc/fstab. It should contain a line for mounting /dev/sda1 on /boot. The other thing I don't know about is the use of LVM instead of just type 83 for the big partition. Maybe I'll do a server download and see what I get.

Can you please file a bug report? I also recommend asking for further assistance in #ubuntu-installer during EU work hours.

Just a few observations:

The most important thing to me is simply installing a running server. I'm no closer to that in spite of purchasing a second computer which exhibits the exact same problem. Some suggestions to point me in that direction would be helpful.

I think I've emphasized at least three separate times I'm a complete beginner to running Linux. I don't know the first step towards filing a bug report and most likely would only frustrate by getting too many details wrong. I also have no idea what is meant by "#ubuntu-installer".

If you are a complete beginner to running Linux, why did you use Logical Volume Manager, which will prevent me to help you? Except if you didn't realize you did it.
LVM is a good tool for professional administrator who wants to merge many physical disks into a huge virtual one. But as I'm a developer, I don't manage this kind of configuration. I simply know that in this case, a way to reduce probability of issues is to make a little "/boot" partition before LVM. But in your case, I presume best way is reinstalling server without this functionality. The question about which kind of partitioning is asked near start of installation.

Simple answer: Because it was the default option and I haven't a clue what a LVM is.

So the install might have a chance of succeeding if I select an option other than LVM?

Yes, a big chance!

Unfortunately I re-installed selecting "entire disk" instead of LVM and I see the same behaviour.

I uploaded another boot info script output.

In this case this is after the following sequence:

- Install Ubuntu server 10.04 (without LVM)
- Boot first time successfully
- sudo update-grub
- reboot (stops at blank screen)
- Booted from LiveCD to run boot info script

Is there anything else I can try or any other information that would be helpful?

Thanks.

I uploaded another boot info script output.

In this case this is after the following sequence:

- Install Ubuntu server 10.04 (without LVM)
- Boot first time successfully
- sudo update-grub
- reboot (stops at blank screen)
- Booted from LiveCD to run boot info script

http://paste.ubuntu.com/566033/

Is there anything else I can try or any other information that would be helpful?

Thanks.

I missed main issue: you was able to boot one time after installation.
There is a uncommon bug known as impossibility re boot Linux after having booting Windows, but you don't have Windows. Dell is known to have done (as HP) some nasty things on boot sectors, which works with XP but not on Grub which has a longer installed bootloader in 64 first sectors of disk. It's too late for me. I will try to have a look tomorrow.
There is a well known "black screen" issue, but you should had it at first reboot.
Could you rerun boot_info_script055.sh before and after first Ubuntu reboot, to see if the script detects some issue ? Else I will provide you tomorrow a command to dump first 64 first boot sectors.

I did my first server install and things worked for me -- What occurred to me is WHERE EXACTLY are you specifying to the script the location to install grub? The examples give a lot of inappropirate locations on partitions instead of as the MBR of the target disk. Another clue is your first info paste showed TWO UNKNOWN boot blocks on your two disks -- i.e. no grub? The install should go to some disk like /dev/sdc , not some partition like /dev/sdc1

In the original question I either misread an example or read the wrong example. Since then I've been trying the install-grub commands suggested by delance:

    sudo mount /dev/sda1 /mnt
    sudo grub-install --root-directory=/mnt /dev/sda

To be clear the first boot info script I posted was from the HP/Compaq machine. The second one I posted today was from the Dell machine.

This last time after re-installing grub I actually get the grub menu. It shows Linux as an operating system choice: "Ubuntu, with Linux 2.6.32-24-generic-pae". But when I try booting to it I simply get a blank screen.

If Dell and HP put strange things in their boot sectors can I do some low level format on the drive to clean that up? Can that be done from the LiveCD? If so, what are the commands.

I'm certainly willing to help characterize this issue, but my main goal is still to build a working server. And help with that will be most appreciated, because I'm still getting nowhere.

I will try gathering additional boot info scripts as per delance's request, though I'm not quite certain how to gather it before the first successful boot. Should I power off the machine just before it reboots and boot to LiveCD instead? Seems a little tricky timing-wise.

Thanks.

Progress... must have had something to do with the logical volumes. Try the nomodeset command line arg as the below link suggests:
http://www.ubuntugeek.com/how-to-fix-ubuntu-10-04-lts-lucid-blank-screen-at-startup.html
Scan the answers for "blank screen" for other suggestions

One minor detail: Ubuntu desktop installs and boots (more than just once) on this same machine fine. No problems at all.

Here's the paste from the boot info script after installing the desktop:

http://paste.ubuntu.com/566076/

Does this get me any closer to installing a server?

To ubfan's suggestion, I'm assuming the nomodeset is related to video mode? I don't think that's related in any way - it's not just a blank screen, it's no system activity whatsoever. It's simply not booting.

After successfully installing Ubuntu desktop 10.10 I tried re-installing Ubuntu server alongside desktop.

Result was that I can boot into desktop from the grub menu but not into server. It simply stops after 5 seconds of hard drive activity.

So the boot loader works. Sort of. Here's the boot info script after installing server alongside desktop:

http://paste.ubuntu.com/566099/

I installed one more time and captured the boot config script output before booting for the first time. The new install is in sda8.

http://paste.ubuntu.com/566119/

Unfortunately I was never able to boot into this new install after booting to the desktop and capturing the boot info script results.

Actually was able to boot once successfully. Unfortunately whatever changed isn't captured by the boot info script. The results are identical after booting once but the scenario repeats - unable to boot a second time.

Result of the later run of the boot info script is here:

http://paste.ubuntu.com/566128/

Did you explicitly check the virtual terminals (CTL-ALT F1 to go the first virtual terminal when in the X environment, after that, just ALT-Fn where n is 1-6, and 7 goes back to the X server.
Five seconds seems too fast, but the server really isn't setting up too much, and it is on a hard disk. You should get a login prompt if the server is running.

One possibility is kernel issue, as on your PC, Desktop and Server installation don't use same version.
In /boot folder, you will find kernels image.
Could you copy images of Desktop installation into /boot folder of Server installation, rerun "sudo update-grub".
You will get a menu with both kernels for Server installation. Please select new kernel, and report if issue is fixed.

And for the moment, forget about Grub corruption.

Similar problem -

1x 320GB /dev/sda
1x 320GB /dev/sdb

nVidia RAID ( hardware )
2x 320GB
2x 320GB

I have installed 12.04 LTS several times ( lost count ) on this machine. No problems with boot.
Last install used the partition manger to configure all the drives.
Upon completion the system will not boot.
Using the "recovery" option on the install (USB) I found that I could boot from /dev/sda1.
So I believe at this stage I have eliminated hardware as a problem.
Check of /dev/sda1 showed it was a bootable partition.

next attempt - ( this corrected the boot problem )

all drives
MBR is erased
now /dev/sda - sdf
no RAID

only going to configure one drive at installation.
( I believe this is where it started to go wrong earlier )

in previous windows installs the hardware RAID could be booted.
This doesn't seem to operate correctly here, will try again next install. ;)

I believe this problem happened in the MBR. There were some manufacture/OEM installs that did some odd things at sector 0 and in BIOS. If you can kill the MBR on /dev/sda it may solve this problem.

Possibly this is a dead thread - posts are kind of old.