Quote:
Originally Posted by waelaltaqi
have you tried to reinsatll ubuntu? it should detect the exesting installation. Also, install boot loarder GRUN on MRB instead of the first sector on the partition. It sounds like the BIOS can't find the sectors that GRUB has been installed on. If you install GRUB on MBR, it will surly find it.
those are my guesses but there might be something else causing this.
|
Something is really screwy about this. This is what I found out browsing around with my live cd. I found /boot/grub/menu.lst attached to a 'disk-1' which is mounted, but I don't know where. I have reinstalled Ubuntu 3 times and each time it installs in a more reduced space, without erasing prior installations. My setup is motherboard Intel chip 945, 2 disks SATA 2 in Raid 0, each one 320MB, Windows XP installed in partition of 20GB. My GRUB menu.lst at present is as follows:
# 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 change this entry to 'saved' 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 10
## 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=cc6de823-9e89-43a9-ba98-2794fe8ee0aa ro
## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd1,0)
## 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
## 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
## ## End Default Options ##
title Ubuntu, kernel 2.6.20-15-generic
root (hd1,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=cc6de823-9e89-43a9-ba98-2794fe8ee0aa ro quiet splash
initrd /boot/initrd.img-2.6.20-15-generic
quiet
savedefault
title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
root (hd1,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=cc6de823-9e89-43a9-ba98-2794fe8ee0aa ro single
initrd /boot/initrd.img-2.6.20-15-generic
title Ubuntu, memtest86+
root (hd1,0)
kernel /boot/memtest86+.bin
quiet
### END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda1.
title Ubuntu, kernel 2.6.20-15-generic (on /dev/sda1)
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=7f4b6ad8-6f2f-4318-aed5-764d3007aef0 ro quiet splash
initrd /boot/initrd.img-2.6.20-15-generic
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda1.
title Ubuntu, kernel 2.6.20-15-generic (recovery mode) (on /dev/sda1)
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=7f4b6ad8-6f2f-4318-aed5-764d3007aef0 ro single
initrd /boot/initrd.img-2.6.20-15-generic
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda1.
title Ubuntu, memtest86+ (on /dev/sda1)
root (hd0,0)
kernel /boot/memtest86+.bin
savedefault
boot
As you can see there is a mess here and I don't know how to solve it. I am thinking of erasing everything and start from zero, but I'm afraid that will not solve anything. I have the growing feeling that is my hardware what is the problem here. I also have an XFX Ge Force 7600GT and I'm not sure is supported by linux. I tried to install Suse 10.2 and all went well until we got to the graphics; there I ended up without a screen. Your ideas will be much appreciated.