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
# 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 ?
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.
On Fri, Jun 27, 2008 at 12:05 AM, Craig White <craigwhite@xxxxxxxxxxx> wrote:
> I hope that's /boot/grub/grub.conf that you're showing us...but it
> doesn't look right.
>
> if /boot is /dev/sda1, then is /boot in the same partition as / because
> your 'kernel' line is using the same partition. Typically, grub will use
> the partition label and not the dev handle...
>
> # man e2label
>
> # e2label /dev/sda1
> /boot
>
> # e2label /dev/sda2
> /1
>
> This is what grub.conf looks like on my F8 system...
>
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to this
> file
> # NOTICE: You have a /boot partition. This means that
> # all kernel and initrd paths are relative to /boot/, eg.
> # root (hd0,0)
> # kernel /vmlinuz-version ro root=/dev/hda2
> # initrd /initrd-version.img
> #boot=/dev/hda
> default=0
> timeout=5
> splashimage=(hd0,0)/grub/splash.xpm.gz
> hiddenmenu
> title Fedora (2.6.25.6-27.fc8)
> root (hd0,0)
> kernel /vmlinuz-2.6.25.6-27.fc8 ro root=LABEL=/1 quiet rhgb
> quiet
> initrd /initrd-2.6.25.6-27.fc8.img
> title Fedora (2.6.24.5-85.fc8)
> root (hd0,0)
> kernel /vmlinuz-2.6.24.5-85.fc8 ro root=LABEL=/1 quiet rhgb
> quiet
> initrd /initrd-2.6.24.5-85.fc8.img
>
> Craig
>
> On Thu, 2008-06-26 at 23:53 +0200, Thomas Rabaix wrote:
>> Ok, I will do what you advice. Just to make there is no
>> misunderstanding, I do not have any more the FC4 on the systeme but
>> only F8 (after multiple upgrade)
>>
>> So grub-install will install grub into the bootloader, I need first to
>> convert the lilo.conf settings into a grub.conf settings. I have paste
>> and copy what it look good for me. Can you tell me if it look right
>> (sda1 => hd0,1) ? next, how do we know reboot will work, do we have a
>> way of testing the setup ?
>>
>> Thanks,
>> Thomas
>>
>> # cat lilo.conf
>>
>> prompt
>> timeout=50
>> default=2.6.25.6-27.fc8
>> boot=/dev/sda
>> map=/boot/map
>> install=/boot/boot.b
>> lba32
>> append=""
>> #serial=0,9600n8
>>
>> image=/boot/vmlinuz-2.6.25.6-27.fc8
>> label=2.6.25.6-27.fc8
>> read-only
>> root=/dev/sda1
>> initrd=/boot/initrd-2.6.25.6-27.fc8.img
>> image=/boot/vmlinuz-2.6.24.7-92.fc8
>> label=2.6.24.7-92.fc8
>> read-only
>> root=/dev/sda1
>> initrd=/boot/initrd-2.6.24.7-92.fc8.img
>> image=/boot/bzImage-2.6.24.5-xxxx-grs-ipv4-32
>> label=linux
>> read-only
>> root=/dev/sda1
>>
>> # cat grub.conf
>> default=0
>> timeout=50
>> title 2.6.25.6-27.fc8
>> root (hd0,1)
>> kernel /vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1
>> initrd /initrd-2.6.25.6-27.fc8.img
>>
>> title=2.6.24.7-92.fc8
>> root (hd0,1)
>> kernel /vmlinuz-=2.6.24.7-92.fc8 ro root=/dev/sda1
>> initrd /initrd-2.6.24.7-92.fc8.img
>>
>> title 2.6.25.6-27.fc8
>> root (hd0,1)
>> kernel /bzImage-2.6.24.5-xxxx-grs-ipv4-32 ro root=/dev/sda1
>>
>>
>> On Thu, Jun 26, 2008 at 11:19 PM, Craig White <craigwhite@xxxxxxxxxxx> wrote:
>> > Now that I see you are remote...I would suggest that you run
>> > grub-install and use that instead of lilo because lilo support was
>> > dropped.
>> >
>> > grub-install /dev/sda
>> > though if you're still booted on FC4, it might only work if you run
>> > grub-install /dev/hda
>> > (depending on whether you are using ATA or SCSI drives)
>> >
>> > Craig
>> >
>> > On Thu, 2008-06-26 at 23:02 +0200, Thomas Rabaix wrote:
>> >> Ok, my host install FC4 with lilo, so I update to F8. I suppose the
>> >> update script from Fedora keep lilo and don't use grub at all.
>> >>
>> >> Now how can I reinstall lilo to make boot.b appears. I have only one
>> >> chance :) (remote location)
>> >>
>> >> I am not sure that my system will reboot properly without this file,
>> >> am i right ?
>> >>
>> >> Thanks
>> >>
>> >> Thomas
>> >>
>> >> On Thu, Jun 26, 2008 at 8:42 PM, Michael Schwendt <mschwendt@xxxxxxxxx> wrote:
>> >> > On Thu, 26 Jun 2008 09:27:46 -0700, Craig White wrote:
>> >> >
>> >> >> On Thu, 2008-06-26 at 18:08 +0200, Michael Schwendt wrote:
>> >> >> > On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote:
>> >> >> >
>> >> >> > > watching this thread with interest.
>> >> >> > >
>> >> >> > > I have several Dell Optiplex 320's that will not boot with grub but will
>> >> >> > > boot with lilo and so I have lilo installed on them.
>> >> >> >
>> >> >> > Is this problem known upstream?
>> >> >> ----
>> >> >> very much so
>> >> >> https://bugzilla.redhat.com/show_bug.cgi?id=379201
>> >> >> https://bugzilla.redhat.com/show_bug.cgi?id=219715
>> >> >
>> >> > Those are about grub and the kernel. If you think grubby suffers from a
>> >> > bug when updating LILO installations, grubby is part of the "mkinitrd"
>> >> > package.
>> >> >
>> >> >> ----
>> >> >> >
>> >> >> > > Unfortunately though, kernel updates do produce the error above (unable
>> >> >> > > to open /boot/boot.b) generated by grubby. Is there any way around
>> >> >> > > getting grubby to re-run lilo to execute an update when new kernels are
>> >> >> > > installed?
>> >> >> >
>> >> >> > With LILO, no. LILO must be rewritten with every change in lilo.conf.
>> >> >> > GRUB, on the contrary, must not be rewritten after modifying grub.conf,
>> >> >> > because it can read the ext2/ext3 fs directly to load its config file.
>> >> >> >
>> >> >> > If you're interested in where grubby is executed, take a look at
>> >> >> > /sbin/new-kernel-pkg which is called by the "kernel" package scriptlets.
>> >> >> ----
>> >> >> been there...never could figure out what to change
>> >> >> as noted here...
>> >> >> https://bugzilla.redhat.com/show_bug.cgi?id=219715#c18
>> >> >
>> >> > Well, if you have reason to believe that grubby does something wrong,
>> >> > find out what it does wrong. Run it manually, it has a man page, too.
>> >> > And /boot/boot.b must exist when it is specified in lilo.conf. Do you
>> >> > say that grubby deletes that file by accident?
>> >> >
>> >> > And if you're really fed up with grubby, you could modify new-kernel-pkg
>> >> > to execute your own lilo-update script/program instead of grubby.
>> >> >
>> >> > --
>> >> > fedora-list mailing list
>> >> > fedora-list@xxxxxxxxxx
>> >> > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>> >> >
>> >>
>> >
>> >
>>
>>
>>
>> --
>> Thomas Rabaix
>> Internet Consultant
>>
>
>
--
Thomas Rabaix
Internet Consultant
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
