On Sat, 2005-08-27 at 07:52 +0000, Kahn Seidl wrote:
> > > /dev/hda1 1 1912 15358108+ 7 HPFS/NTFS
> > > /dev/hda2 1913 1925 104422+ 83 Linux
> > > /dev/hda3 * 1926 3850 15462562+ 83 Linux
> > > /dev/hda4 3851 7296 27679995 5 Extended
> > > /dev/hda5 3851 7296 27679963+ 8e Linux LVM
> > >
> >
>
>
> Ok, hda1 is for win xp
> hda2 is boot
> hda3 is what fc4 was installed on
> hda4/5 is the lvm which fc3 is installed on.
>
> i still have access to the lvm through fc4. when I tried pointing grub to
> hda5 it said cant mount partition.
>
> I installed fc4 because fc3 wasnt working, I want to get fc3 back and
> uninstall fc4.
>
> Here is my grub.conf
>
> default=0
> timeout=5
> splashimage=(hd0,2)/boot/grub/splash.xpm.gz
> hiddenmenu
The above 2 lines can be commented out if you wish.
> title Fedora Core (2.6.11-1.1369_FC4)
> root (hd0,2)
> kernel /boot/vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ rhgb quiet
> initrd /boot/initrd-2.6.11-1.1369_FC4.img
This looks OK for FC4, and if you are able to boot then it certainly is.
> title fc3
> root (hd0,1)
> kernel /vmlinuz-2.6.9-1.667 ro root=LABEL=/ rhgb quiet
This line will not work if FC3 is in the LVM.
Mine has this for my FC3 system using LVM
kernel /vmlinuz-2.6.12-1.1372_FC3 ro root=/dev/VolGroup00/LogVol00 \
rhgb quiet
Note that the root part has to specify the device name with the volume
group name as well as the logical volume name. It is likely that yours
may have it specified exactly the same.
> initrd /initrd-2.6.9-1.667.img
> title Other
> rootnoverify (hd0,0)
> chainloader +1
>
If you are trying to use the kernel lines you have above, and you happen
to have 2 partitions (LVM or otherwise) with the same label then that
cannot be easily done. Grub will get confused if it sees 2 partitions
with the same label and you use the LABEL statement in the kernel line.
If FC4 is on /dev/hda2 then I would change that line to "root=/dev/hda2"
Similarly, if FC3 is in the LVM on hda5 then you will need to use the
full LVM name similar to what I showed above to access FC3 for booting.
> I have tried several different variations on that, but always get the kernel
> panic.
>
> Martin
>
>
