After I upgraded 10.3 to 11.0 I have been unable to get grub to boot the system for me.
The installer complains about some error message when it tries to set up grub (ok, so I should write it down - lazy me) resulting in a system that dumps me into grub failure messages when I boot.
Now, I have searched a bit around on the net and found myself a workaround which basically amounts to doing “root (hd0,1)” “kernel /boot/vmlinuz” “initrd /boot/initrd” “boot” from the grub command line whenever I power up. I’m actually not certain what the “root (hd0,1)” part actually does, but that seems to be the stumbling block.
I’d like to ask for a bit of help on how I can get grub to do what I do manually, and if there is some way to get OpenSUSE to handle this correctly?
There might be something buried in here about how the boot process changed between 10.2 and 10.3 (I think it was those two)?
I think you had an earlier post and perhaps are dual booting or have upgraded to 11? If you are getting the GUI and level 5, just use Yast. If you don’t know your partitions, you can also use the partitioner to see what your partitions are.
If you spend some time in the GRUB Page, you’ll see that you can do much of this from the GRUB console, including re-installing GRUB.
I had a 6-7 duplicate entries that I took out. I changed all (0,0) references to (0,1) but for some reason they are now gone - the '()'s and all inside them I mean.
And it still fails. It tries to find a file at (0,0) somewhere says the error, then I get a text boot selector that contains totally different boot options (namely my Dragonfly and others I’ve had around for a while).
I think the trouble is that there are two different booting mechanisms in place here. One that came from 10.1 and the other from 11.0 (or perhaps 10.3 really?).
I had a faint hope I wouldn’t need to get a dark coloured belt in booting to get this going.
I have 3 disks with different OSes on. This 11.0 started out as 10.1 and has gone through 10.2 and 10.3.
My system disk partition is a software mirror raid ReiserFS (that misses one disk after the repair utilities thought it wise to repair them separately - but that is another topic altogether).
I have a box with 3 HDs and the first is XP, 2nd and 3rd usually have 2 - 4 Linux distros each. But, SUSE. Debian, Ubuntu, Xubuntu, Mint, Berry and Fedora all seem to find the partitions when the installer runs.
Now you’ve mentioned RAID and and software mirror, etc, the situation is somewhat more complex.
Now that Hans is in prison, I think most distros plan to drop ReiserFS so you might want to plan accordingly. From the sounds of things, might as well do the change now. (joke)
I think you have some work ahead of you. However, the bootloader gui in Yast can work it all out if you have it take another look, suggest, whatever. You should know where each OS has its image? I always write them down (and lose the note).
To be able to help, we need a lot more information. What are the disk layouts? What is installed where? Which instance do you want to boot from? Which partitions are in the RAID array, and what is installed on the array? So . . .
The md0 array is comprised of sda1/sdb1, md1 is sda2/sdb2, and md2 is sda4/sdb4, right? And md1 is RAID 1?
At least one reason grub is failing is that it is looking for the kernel on sda1 - note the “root (hd0,0)” in menu.lst. When you give it (hd0,1), you are pointing grub to sda2. Grub needs to boot from one of the two identical partitions in the array.
If you must also change the kernel and initrd lines for the boot to work, then the kernel & initrd file names in menu.lst may be incorrect. When you give grub “/boot/vmlinuz” and “/boot/initrd”, the vmlinuz and initrd are symlinks in /boot which always point to the actual current file name.
So, you can get into a text editor as root and change menu.lst, the “root (hd0,0)” to “root (hd0,1)”. And you can either change the vmlinuz and initrd lines to show the actual file names (if the names now there are wrong), or you can just change the lines to use the symlinks.
By the way, why do you have swap in an array? AFAIK there is no value in that. There is additional overhead and, performance wise, it would be better to break that array and use the partitions separately for swap.