> Hi Maurice, > > >> > There is/was a long-term fix in the works, but obviously there is a lot > >> > of scope for this going wrong if it were deployed to lots of machines! > > > > Wasn't there an update release to address this? > > It's fixed for new Scientific Linux based BlueOnyx installs, as I worked > that into the CD installer. This happened earlier last year (April > 2012?) or thereabouts. > > However, I didn't release a YUM update to fix it automatically on older > SL based BlueOnyx installs. While the fix is trivial, I'm not really > keen to push out an update that has the small chance that hundreds of > servers might not come up after their next reboot. > > I have seen isolated cases where /etc/grub.conf (which usually is > perfect) didn't contain all the needed entries, were missing the actual > kernel or had other kernel parameters than the faulty copy in > /boot/grub/grub.conf. So just copying over grub.conf and placing a > symlink might work for 98.5% of the cases. But I can't risk the > potential damage for those where it might not work. > > -- > With best regards > > Michael Stauber
Apparently, I'm one of the 'lucky' 1.5%. I still have a virtual machine that won't boot - because the initial start kernel in /boot can't load the correct driver to mount & access the LVM partition with /root in it. So apparently, the /boot/grub/grub.conf did not get correctly updated. If I could just mount that LVM partition, I could copy over the /etc/grub.conf. But I can't figure out how to get into that LVM partition using a Rescue CD image, or using a Knoppix Live CD image. :-( I still need to get this 5107R VM to boot - there is data on it that we don't have a backup. And it would cost us a lot to recreate! Anyone have any idea how to mount a LVM partition using a Live CD?? Chuck
_______________________________________________ Blueonyx mailing list [email protected] http://mail.blueonyx.it/mailman/listinfo/blueonyx
