Paul Howarth wrote:
On Tue, 2006-07-11 at 14:56 -0500, Mikkel L. Ellertson wrote:
Patrick Nelson wrote:
FC4 yum updated
I have a system that has /boot as its own partition (/dev/sda1). The
rest of the fs is in a lvm volume group.
the /dev/sda1 is having some problems which were shown by
- boot off of rescue cd, mount FC4 instance and chroot to it, then re
login as root
- umount /boot
- fsck -c /dev/sda1
and I want to move /boot back onto the "/" fs in the volume group, which
I have done by:
- boot off of rescue cd, mount FC4 instance and chroot to it, then re
login as root
- removed the /boot reference in fstab
- copied /grub dir from old /boot to the new dir
- because the kernel files were corrupted I added the kernels (I usually
keep 2 -> current and 1 version back) back with:
-- rpm -ivh --force --noscript kernel-2.6.17-1.2139-FC4.i686.rpm
-- rpm -ivh --force --noscript kernel-2.6.17-1.2141-FC4.i686.rpm
This appears to have put the files back into the new /boot location. So
my question is what is the next step to tell the system that it needs to
use the new /boot directory?
Or any other comments?
Does Grub know how to handle LVM volume groups? I thought part of
the reason for having a separate /boot partition was for Grub
access, but I could be wrong. In any case, you will have to
re-install Grub to the MBR. Depending on the changes you have made,
you may have to update the device map as well.
You're not wrong. AFAIK grub cannot boot from an LVM volume. It needs to
be a separate partition.
Paul.
Well then I guess I better get another partition going. Thanks for the
info!
