cannot boot ubuntu 9.04 server... grub issue?

Igby · 05-11-2009, 08:34 AM

What does cat /boot/grub/menu.lst show you?

aus9 · 05-11-2009, 07:31 PM

hi

oops

ok reboot the live cd...to cat...display contents...it will be universal

Code:

su
mkdir /z
mount /dev/sda1 /z
cat /z/boot/grub/menu.lst

now if the mount fails for you....you might need to tell mount the filesystem format...eg ext3..xfs like this
mount -t ext3 /dev/sda1 /z

aus9 · 05-11-2009, 07:33 PM

duplicate post culled

hit1mn · 05-12-2009, 07:08 AM

Code:

# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default		0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout		3

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title		Windows 95/98/NT/2000
# root		(hd0,0)
# makeactive
# chainloader	+1
#
# title		Linux
# root		(hd0,1)
# kernel	/vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=900a5112-5162-4dea-bee1-19dfed99b54d ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=900a5112-5162-4dea-bee1-19dfed99b54d

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
##      lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
##      indomU=true
##      indomU=false
# indomU=detect

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title		Ubuntu 9.04, kernel 2.6.28-11-server
uuid		900a5112-5162-4dea-bee1-19dfed99b54d
kernel		/boot/vmlinuz-2.6.28-11-server root=UUID=900a5112-5162-4dea-bee1-19dfed99b54d ro quiet splash 
initrd		/boot/initrd.img-2.6.28-11-server
quiet

title		Ubuntu 9.04, kernel 2.6.28-11-server (recovery mode)
uuid		900a5112-5162-4dea-bee1-19dfed99b54d
kernel		/boot/vmlinuz-2.6.28-11-server root=UUID=900a5112-5162-4dea-bee1-19dfed99b54d ro  single
initrd		/boot/initrd.img-2.6.28-11-server

title		Ubuntu 9.04, memtest86+
uuid		900a5112-5162-4dea-bee1-19dfed99b54d
kernel		/boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST
ubuntu@ubuntu:~$

thanks

aus9 · 05-12-2009, 08:25 PM

hi

I am using grub2 at the moment so can not test hidden menu but I have some suggestions

1) using the live cd...mount and edit that menu to put a # in front of hiddenmenu

2) your menu has a separate line for UUID. I have not seen that before.
I could be wrong...but here is a link of a recent ubuntu agreeing with me...its a wee bit hard to read but is very gui.

http://www.howtogeek.com/howto/ubunt...fter-upgrades/

Note there is an overlap or overflow from one line to the next...so the line for kernel is showing as 2 lines ok?

a quick search shows an older menu but illustrates the issue clearer
http://ubuntuforums.org/showthread.php?t=278570

SUGGEST
you boot the live cd...mount the partition as previously discussed.

copy the first menu and rename its title...original

edit the original title...no uuid
and delete the entire line for uuid

edit
3) while in live cd mode...lets check that the UUID is correct

try looking at
/dev/disk/by-uuid

or use a terminal to try

Code:

blkid -s UUID
ls -l /dev/disk/by-uuid/
vol_id -u /dev/sda1

4) even if they are right....add a new entry
change the kernel line where it says root=uuid=string to root=/dev/sda1

and reboot to test if any work

good luck

hit1mn · 05-14-2009, 11:08 PM

[QUOTE1) using the live cd...mount and edit that menu to put a # in front of hiddenmenu
[QUOTE]

I saw this and made the change...nogo

Code:

ubuntu@ubuntu:~$ sudo blkid -s UUID
/dev/sda1: UUID="da66530c-a986-4f37-b436-c0fcc9498855"
/dev/sda5: UUID="ee56eb17-97d3-4969-b456-e9b907d2248e"
/dev/sdb1: UUID="cb262e48-aa6e-4ddd-b7ba-e4c4008ac211"
/dev/sdc1: UUID="3b1f3323-095c-45ec-aba4-afd200f22fad"
ubuntu@ubuntu:~$ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 2009-05-13 22:02 3b1f3323-095c-45ec-aba4-afd200f22fad -> ../../sdc1
lrwxrwxrwx 1 root root 10 2009-05-13 22:02 cb262e48-aa6e-4ddd-b7ba-e4c4008ac211 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2009-05-13 22:02 da66530c-a986-4f37-b436-c0fcc9498855 -> ../../sda1
lrwxrwxrwx 1 root root 10 2009-05-13 22:02 ee56eb17-97d3-4969-b456-e9b907d2248e -> ../../sda5
ubuntu@ubuntu:~$ sudo vol_id -u /dev/sda1
da66530c-a986-4f37-b436-c0fcc9498855
ubuntu@ubuntu:~$ -

I commented out the UUID and changed the kernel line to root=/dev/sda1

reboot, blinking cursor.

Whatever the logic why this isn't working is beyond me. I must say as an ex ms user I have never taken more than a few hrs to recover from a disaster.

I'm about to eat the data I have on here, pull this drive and use one of the other drives just so I can make this thing productive. Getting really frustrated with this now. I have used a few distro's of linux over the last several years with helpless success. I know there is an answer to the fix but it really shouldn't be this complicated.

sorry for the rant..thanks again aus9 for being patient w this

any other suggestions before I pull the disk?

edit
I am fully willing to bring this drive back to OEM config if someone can suggest how I can get there. Writing zeros across the drive didnt solving anything either.

I dont have access to the machine atm but would fdisk /mbr from DOS help?

thanks

hit1mn · 05-15-2009, 11:35 AM

Can any other gurus shed any light on this issue?

thanks

aus9 · 05-17-2009, 04:49 AM

sorry been busy

your uuid seem wrong don't they?

your menu was....900a5112-5162-4dea-bee1-19dfed99b54d

your independent test of sda1 was da66530c-a986-4f37-b436-c0fcc9498855

try reboot of live cd...mount as per before...edit so your first line as the bottom uuid and reboot to test.

without physically checking your machine I can offer no quick solutions.

if after this new test...it fails for you....use a live cd to mount the partition and copy any data off it then do a clean install.

BTW I am not a fan of ubuntu as a server.....I think slackware may be more stable