Carlos E. R. wrote:
If I run "yast2 bootloader" and request it to reinstate the boot code, or change it to boot from root partition, exit, run again, change nopw to boot from boot partition (which is the sequece to force yast to rewrite things), it fails to boot later, same as described above.
If I run the automated rescue (11.2 retail DVD), and indicate I want to correct the boot loader, it insists on checking the filesystem (which is entirely correct), then insists on repairing fstab, which was correct, and in fact, destroys some entries that worked, and now don't. I had to remake fstab by hand. And worse, it does not repair boot from partition #1.
How on earth can I FORCE Yast or grub to reinstall grub properly and sucesfuly? Short of reinstalling Suse, which is the only remaining idea, then replacing all files from backup.
Carlos, I had some trouble with grub recently. I confess I haven't read your post in detail and also I don't profess to be a grub expert. However I can mention one fascinating fact I observed during my tribulations. There are many options on the 11.2 DVD, reached by different paths, that look similar but actually result in a different environment (i.e. a different kernel running with the same file system). For example I found that entering the repair system by first going to the install menu and then selecting repair worked, whilst other routes to the repair system did not work. Perhaps that will help you sort out your problem. I found the whole menu system and the dialogs for managing grub to be too confusing. It seemed really difficult to be sure you'd selected exactly the correct options etc. So I concentrated on trying to get into a grub session and then doing everything from the grub shell. But you still need to watch for any drive mapping issues. HTH, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org