Re: Creating the symbolic links in the /boot and /boot/grub/

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



> And here are the contents of grub.conf:
>
> # 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/VolGroup00/LogVol00
> #          initrd /initrd-version.img
> #boot=/dev/hdc
> default=0
> timeout=5
> splashimage=(hd0,0)/grub/splash.xpm.gz
> hiddenmenu
> title CentOS (2.6.9-100.EL)
>      root (hd0,0)
>      kernel /vmlinuz-2.6.9-100.EL ro
> root=/dev/VolGroup00/LogVol00 rhgb quiet
>      initrd /initrd-2.6.9-100.EL.img

OK, the file listing of /boot from your last mail and now grub.conf, they
look quite good. grub.conf has been updated by the kernel update, and also
a new initrd-2.6.9-100.EL.img has been created, so that doesn't look bad.

The only thing I'm not really sure is if grub is installed correctly now.
Maybe you have to run grub-install again to be sure but I'm just not so
sure about grubs internals. Maybe someone can tell you more about this.

As someone else mentioned, it's a very good idea to have a current CentOS
4.8 disk at hand so you could boot into rescue mode with 'linux rescue' at
the boot prompt if somethings goes wrong.

Simon

>
> Todd
>
> On 3/9/2011 12:23 AM, Simon Matter wrote:
>>> I inadvertently missed using the list...here are my recent messages.
>> As Nico suggested, download the kernel but also grub and redhat-logos,
>> like so
>> wget
>> http://mirrors.kernel.org/centos/4.9/updates/i386/RPMS/kernel-2.6.9-100.EL.i686.rpm
>> wget
>> http://mirrors.kernel.org/centos/4.9/os/i386/CentOS/RPMS/redhat-logos-1.1.26-1.centos4.4.noarch.rpm
>> wget
>> http://mirrors.kernel.org/centos/4.9/os/i386/CentOS/RPMS/grub-0.95-3.8.i386.rpm
>>
>> Then do a
>>
>> rpm -Uvh --replacepkgs --replacefiles kernel-2.6.9-100.EL.i686.rpm
>> redhat-logos-1.1.26-1.centos4.4.noarch.rpm grub-0.95-3.8.i386.rpm
>>
>> And the show us the contents of 'ls -laR /boot' and 'cat /etc/grub.conf'
>>
>> Simon
>>
>>>
>>> On 3/8/2011 8:39 PM, Nico Kadel-Garcia wrote:
>>>> On Tue, Mar 8, 2011 at 11:31 PM, Todd Cary<todd@xxxxxxxxxxxxxxxxxx>
>>>> wrote:
>>>>> reinstall is not an option for yum.  I ran "yum install kernel" and
>>>>> it
>>>>> completed without errors however there are no links created.
>>>> Oh, dear. Can you grab the RPM and do "rpm -U -replacepkgs
>>>> [kernel-whatver].rpm"? You should be able to use "yum remove" on the
>>>> old kernel packages, consistent with freeing up the space, and now
>>>> install your new kernel with yum.
>>>>
>>>>> Would this be the correct ln command for vmlinuz-2.6.9-89.35.1
>>>>>
>>>>> # /boot/vmlinuz-2.6.9-89.35.1 /boot/vmlinuz
>>>>>
>>>>> Todd
>>>>>
>>>>> On 3/8/2011 7:04 PM, Nico Kadel-Garcia wrote:
>>>>>> On Tue, Mar 8, 2011 at 9:58 PM, Todd Cary<todd@xxxxxxxxxxxxxxxxxx>
>>>>>> wrote:
>>>>>>> I started a new thread since the original one is getting rather
>>>>>>> long.
>>>>>>>
>>>>>>> I have retrieved the files I deleted in /boot and /boot/grub,
>>>>>>> however I need to make links for
>>>>>>>
>>>>>>> /boot/System.map  (System.map ->     System.map-2.6.9-89.35.1)
>>>>>>> /boot/vmlinuz  (vmlinuz ->     vmlinuz-2.6.9-89.35.1)
>>>>>>> /boot/grub/menu.lst (menu.lst ->     ./grub.conf)
>>>>>> Instead, re-install your kernel. "yum reinstall kernel". This should
>>>>>> regenerate your symlinks correctly, except possibly the grub.conf.
>>>>>>
>>>>>>> If it was not so important to get it correct, I would appreciate
>>>>>>> the syntax for the command.  Usually I would figure it out.
>>>>>>>
>>>>>>> Since I have restored the files (I will double check to make sure
>>>>>>> they are all there), do I need to run grub-install?
>>>>>> i think yes. The old location of the boot loader is listed in
>>>>>> /boot/grub/grub.conf, and should be used as the argument to that
>>>>>> command. grub is much smarter than LILO used to be, but I think the
>>>>>> bootstrap procedure relies on knowing details of where the fiddly
>>>>>> bits
>>>>>> of grub live on the relevant ex2 compatible filesytem.
>>>>>>
>>>>>>> My apologies for bothering everyone with such a dumb error on my
>>>>>>> part.
>>>>>>>
>>>>>>> Todd
>>>>>>>
>>>>>>> --
>>>>>>> Ariste Software
>>>>>>> Petaluma, CA 94952
>>>>>>>
>>>>>>> http://www.aristesoftware.com
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> CentOS mailing list
>>>>>>> CentOS@xxxxxxxxxx
>>>>>>> http://lists.centos.org/mailman/listinfo/centos
>>>>>>>
>>>>> --
>>>>> Ariste Software
>>>>> Petaluma, CA 94952
>>>>>
>>>>> http://www.aristesoftware.com
>>>>>
>>>>>
>>> --
>>> Ariste Software
>>> Petaluma, CA 94952
>>>
>>> http://www.aristesoftware.com
>>>
>>> _______________________________________________
>>> CentOS mailing list
>>> CentOS@xxxxxxxxxx
>>> http://lists.centos.org/mailman/listinfo/centos
>>>
>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS@xxxxxxxxxx
>> http://lists.centos.org/mailman/listinfo/centos
>>
>>
>
> --
> Ariste Software
> Petaluma, CA 94952
>
> http://www.aristesoftware.com
>


_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos


[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux