[ltp] GRUB Geom Error
Jesper Schaumburg-Müller
linux-thinkpad@linux-thinkpad.org
Fri, 04 Jun 2004 23:05:32 +0200
--=-eNoOREs1pVmlCC3FJhXt
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Hi.
I think that GRUB and LILO are alternatives as bootloader. You have to
choose either to use GRUB or to use GRUB.
I use GRUB on my R50 Debian installation.
The GRUB behavior is determined by /boot/grub/menu.lst (appended to the
mail).
I don't know if you can use it. You will of course have to edit it
according to your configuration.
Regards Jesper
fre, 2004-06-04 kl. 22:25 skrev Sanne N:
> Hi all,
>
> I am trying Liniux for the first time, Suse 9.1 personal on my T40 237319G .
> I installed from the CD using default options (except for changing the
> keyboard layout). I never touched the IBM hidden partition.
> After the install, when trying to boot, the system hangs with 'GRUB Geom
> Error'. I tried restoring to factory settings from the Acces IBM menu. It
> seems to work, but when booting it gives the same result.
> I also tried installing Suse with LILO instead. It fails with:
>
> Error ocurred while installing LILO
> Warning: LBA32 addressing assumed
> Added Linux *
> Fatal: Image name, label or alias contains a blank character: 'windows 1'
>
> and then continues to boot with the same result as previously. So I tried
> modifying the lilo.conf file during setup. In the lines that goes:
>
> other = /dev/hda1
> ### Don't change this comment -YaST2 identifier:
> Original name: windows 1###
> label = windows_1
>
> other = /dev/hda2
> ###Don't change this comment -YaST2 identifier:
> Original name: windows 2###
> label = windows_2
>
> I changed 'windows 1' and 'windows_1' to simply 'windows1'. I did nothing to
> the windows 2 block.
> Now it fails with:
>
> Error Ocurred while installing LILO
> Added Linux *
> Added windows1
> Added windows_2
> Added Failsafe
> Fatal: open /boot/memtest.bin: No such file or directory
>
> and gives the GRUB error again on boot. Does anyone know what this is about?
> Does it look like a problem with the BIOS or the GRUB/LILO conf?
> Any help or suggestion will be much appreciated, as I clearly don't have any
> idea what I am doing...
> Sanne
>
> _________________________________________________________________
> Watch the online reality show Mixed Messages with a friend and enter to win
> a trip to NY
> http://www.msnmessenger-download.click-url.com/go/onm00200497ave/direct/01/
--
Jesper Schaumburg-Müller <schaumburg@johansen.tdcadsl.dk>
--=-eNoOREs1pVmlCC3FJhXt
Content-Disposition: attachment; filename=menu.lst
Content-Type: text/plain; name=menu.lst; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
# 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'.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 15
# 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 optons 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 specifiv 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=root=/dev/hda2 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,1)
## 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
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) 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
## ## End Default Options ##
##title Debian GNU/Linux, kernel 2.6.5-1-686
##root (hd0,1)
##kernel /boot/vmlinuz-2.6.5-1-686 root=/dev/hda2 ro
##initrd /boot/initrd.img-2.6.5-1-686
##savedefault
##boot
##title Debian GNU/Linux, kernel 2.6.5-1-686 (recovery mode)
##root (hd0,1)
##kernel /boot/vmlinuz-2.6.5-1-686 root=/dev/hda2 ro single
##initrd /boot/initrd.img-2.6.5-1-686
##savedefault
##boot
title Debian GNU/Linux, kernel 2.4.25-1-386
root (hd0,1)
kernel /boot/vmlinuz-2.4.25-1-386 root=/dev/hda2 ro
initrd /boot/initrd.img-2.4.25-1-386
savedefault
boot
##title Debian GNU/Linux, kernel 2.4.25-1-386 (recovery mode)
##root (hd0,1)
##kernel /boot/vmlinuz-2.4.25-1-386 root=/dev/hda2 ro single
##initrd /boot/initrd.img-2.4.25-1-386
##savedefault
##boot
title Windows XP
root (hd0,0)
#makeactive
chainloader +1
### END DEBIAN AUTOMAGIC KERNELS LIST
--=-eNoOREs1pVmlCC3FJhXt--