On Fri, 2008-06-27 at 01:23 +0200, Thomas Rabaix wrote:
ok, this is my partition table : sda1 and sda2 are ext3
/dev/sda1 9,9G 3,3G 6,1G 36% /
/dev/sda2 449G 709M 425G 1% /var
----
wow - all that space in /var - this a db server? You're barely using any
of the disk space allocated to /var
----
# e2label /dev/sda1
/
# e2label /dev/sda2
/var
Yes the file is located into /boot/grub/grub.conf. but there is not
specific partition for grub, can it be an issue, does grub know how to
read a etx3 partition ?.
# cat /boot/grub/grub.conf
default=0
timeout=50
title 2.6.25.6-27.fc8
root (hd0,0)
kernel (hd0,0)/boot/vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1
initrd (hd0,0)/boot/initrd-2.6.25.6-27.fc8.img
let's try to understand the last 3 lines
- root : " Set the current root device to the device device", so the
root here is sda1 so h0,0 in grub syntax
- kernel : "define the kernel to load", so we load the kernel from
disk h0,0 with read only attribute (not sure about the need of this,
does the system switch to rw after loading?) and we define the root to
the kernel as /dev/sda1 (look redundant as it is the same as the grub
one)
- initrd : "Load an initial ramdisk for a Linux format boot image and
set the appropriate parameters in the Linux setup area in memory." not
sure to get all the bytes, but I get that this file is use to load
specific module from the distribution
my only current doubt, is that the / and /boot are on the same
partition. So grub cannot access to /vmlinuz.... that's it why I add
(hd0,0)/boot/ to make sure grub can find the kernel. Am I wrong ?
So in your opinion does the grub configuration look fine ?
----
Probably going to need someone else to verify because I am uncertain.
Following this information
http://docs.fedoraproject.org/release-notes/f8/en_US/sn-Installer.html#sn...
read through this page...it's part of the installation notes for F8
you need to use labels in grub.conf - which is what I have been trying
to tell you.
thus I would think that this...
title 2.6.25.6-27.fc8
root (hd0,0)
kernel (hd0,0)/boot/vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1
initrd (hd0,0)/boot/initrd-2.6.25.6-27.fc8.img
should look like this...
title 2.6.25.6-27.fc8
root (hd0,0)
kernel /boot/vmlinuz-2.6.25.6-27.fc8 ro root=LABEL=/
initrd /boot/initrd-2.6.25.6-27.fc8.img
that's what I was trying to tell you.
What I can't tell you for certain if it will work without labels as you have it
presently configured...I simply don't know.
----
to g :
# lilo -v -t
LILO version 22.7.3 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 11-Aug-2006 and compiled at 20:26:28 on Aug 11 2006.
Reading boot sector from /dev/sda
Using MENU secondary loader
Calling map_insert_data
Boot image: /boot/vmlinuz-2.6.25.6-27.fc8
Mapping RAM disk /boot/initrd-2.6.25.6-27.fc8.img
Added 2.6.25.6-27.fc8 *
Boot image: /boot/vmlinuz-2.6.24.7-92.fc8
Mapping RAM disk /boot/initrd-2.6.24.7-92.fc8.img
Added 2.6.24.7-92.fc8
Boot image: /boot/bzImage-2.6.24.5-xxxx-grs-ipv4-32
Added linux
The boot sector and the map file have *NOT* been altered.
----
isn't that because you are running '-t' (test) instead of just
installing?
Craig