Re: How to install LVM partition? --related --success --problem solved

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

 



>Tim said:

>Simple answer:  If you manage to access the second drive, just copy the
>part in its /boot/grub/grub.conf file for booting its fedora (the four
>ines starting from the "title" one) into the first drives grub.conf
>file.  The hardest part about that for a newcomer is how to access that
>file.

Thank you Tim, Anil Kumar Sharma, and everyone. A simple answer but
clear, and understandable.

I used the rescue cd. On the command line:

chroot /mnt/sysimage

then:

nano /boot/grub/grub.conf

I copied (the four lines starting from the "title" one) into the first
drives grub.conf
file. This is what I found:

(snip)

title  Fedora Core 5 (2.6.15-1.2054_FC5)
	root (hd1,0)
	kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=/dev/VolGroup01/LogVol00 rhgb quiet
	initrd /initrd-2.6.15-1.2054_FC5.img

(/snip)

This is the /boot/grub/grub.conf file on the first drive after I
finished copying and adding the  new Fedora Core 5 entry:

(snip)

# 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/sda
default=0
timeout=20
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title Memtest86+ v1.65
       kernel /memtest86+-1.65
title Fedora Core 3 (2.6.11-11_FC3asl)
       root (hd0,0)
       kernel /vmlinuz-2.6.11-11_FC3asl ro root=/dev/VolGroup00/LogVol00
       initrd /initrd-2.6.11-11_FC3asl.img
title  Fedora Core 5 (2.6.15-1.2054_FC5)
	root (hd1,0)
	kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=/dev/VolGroup01/LogVol00 rhgb quiet
	initrd /initrd-2.6.15-1.2054_FC5.img

(/snip)

On a 2 drive sata, 2 os (one on each drive), using LVM partitions this
works. It seems grub reads all the grub.conf files on all /boot
parttions on all the hard drives but bases the grub boot screen info
from the first drive. In my case:

boot=/dev/sda

See the header at the top of the grub.info file.

anaconda wrote:

(snip)

# 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/sda

(/snip)

All the other boot partition

  /boot/grub/grub.conf

files point to the first with a "chainloader" entry like this:

(snip)

title Fedora Core 3
	rootnoverify (hd0,1)
	chainloader +1

(/snip)

I hope I'm correct and this helps others.

-ron-


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux