On 1/29/2014 13:59, Chris Murphy wrote:
...
Anyway, if you're for sure convinced it's corrupt then reformat the partition.
Use blkid to get the new volume UUID to insert into /etc/fstab so it gets mounted
when you next boot. And then mount root, boot, (boot/efi if this is a UEFI machine), and
use:
mount -B /dev /mnt/dev #where /mnt is where rootfs is mounted
mount -B /proc /mnt/proc
mount -B /sys /mnt/sys
chroot /mnt
yum reinstall kernel #grubby will probably complain due to lack of grub.cfg
grub2-install /dev/sdX
grub2-mkconfig -o /boot/grub2/grub.cfg
Chris,
After several weeks of schedule hell, I was finally able to work on
this. The upshot is that the previously installed kernels weren't
available (so I had to pull the more recent available one), I got some
errors on the grub2 commands, and when rebooting into the new kernel I
get several errors:
When entering GRUB:
error: file `/grub2/locale/en.mo.gz' not found
After selecting kernel from the grub menu:
error: invalid magic number.
Loading initial ramdisk...
error: you need to load the kernel first
These were similar errors to the ones I was getting when the problem
first appeared - and yet now things should be installed into the boots
directory on the / partition rather than the separate /boot partition
that seems to have become unloadable.
Does this make any sense?
-Don