On Mon, 2012-10-15 at 09:54 +0200, Hans Witvliet wrote:
Hi all,
I had to reinstall one of my systems, as it didn't get up any more. After reinstalling from dvd, i powered cycled to test grub.
Then powered down, reconnected data-didks, and powered up again. Did an online update, i presume there were kernel packages, as yast wouldn't let me activate nfs-server: it complained i had to reboot again.
So i did, and got no further then just: "grub" ;-( Unfortunately, the dvd does not contain the "repair" option, which might be handy with the new grub2.
Disconnecting the data-drives and reboot doesn't help either.
After restarting in "rescue-mode" from the dvd, it looks like the fs is ok, after mounting it manually i caninspect parts like /boot/grub2/grub.cfg.
Question remains why it went wrong after the update?
The manual just says: ""Bootloader Configuration after a Kernel Update
Every time a new kernel is installed, the perl bootloader writes a new bootloader configuration file using the defaults specified in /etc/sysconfig/bootloader. If you are using a customized set of kernel parameters, make sure to adjust the relevant defaults in /etc/sysconfig/bootloader according to your needs. ""
But i requested nothing fancy from grub2, just let yast2 do the installation.
Any suggestions (to repair and to avoid it the next time) are welcome...
Some further info..... After rebooting i got to "GRUB", but not into the grub shell, system just seems froozen,... So next i booted from the installation dvd, and selected "rescue" Somewhere i read that i should try "grub2-install /dev/sda" But all i got was: "mkdir: can not create directory []/boot/grub2/i386-pc[] : read-only file system" Which is a bunch of crap, as i could mount it manually, create files, fill them with text, write back to that directory and remove them. next i did: mount /dev/sda3 /mnt (sda1 is swap, sda2 is sles11sp2) mount -o bind /proc /mnt/proc moutt -o bind /dev /mnt/dev mount -o bind /dev/pts /mnt/dev/pts mount -o bind /sys /mnt/sys chroot /mnt and: grub2-install /dev/sda This time no warnings or errors, and after a reboot the system is back. powered down, reconnected data-drives and after a reboot everything still seems to work ... Don't know if anybody else came across it, but this seems to be a work-around... Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org