I suggest you open up a terminal session, type in su and the root password and then the command fdisk -l:
Capture the output and post it here. When you capture text it is best to highlight the whole thing in your message here and then press the code option in the editor (#). That keeps the editor from modifying it and allowing for large amounts of text to take less room in your message. That is what I am using in this message.
It would also be nice to see your Grub menu.lst file and device.map file. To read and capture these use the KDE Run Command.
Then, I did find it elsewhere and the problem had something to do with booting from an external hard drive. Oddly, I do this all of the time with openSUSE. I don’t know what is wrong in your case, but perhaps the above files will help find the problem. I am hoping it does not indicate a hard drive problem.
The previous suggestions by jdmcdaniel3 might yield some additional information, and can be accomplished by booting with the install / Live CD which will allow you to run fdisk, mount the drive and access the menu.1st files - however I really think your issue lies in other areas, almost certainly related to BIOS limitations.
Is this an older PC? How old? How large of drive is this? I am suspecting this is a pretty old PC and the BIOS is unable to read the kernel beyond cylinder 1023 - this was a very, very common issue in the early days of Linux, and why (to this day) many people and distros still create a separate /boot partition - though there are other reasons to have this, it is largely un-needed these days. But perhaps necessary in yours.
Also, did you take this drive out of another computer and put it in this one? Was it booting correctly before, or is this a new install?
Please see these two links which provide a fair amount of into on this error and possible reasons:
Sort of solved it
This morning it did not boot at all. Grub menu did not appear.
The Hardware is about 2 years old. The Gigabyte Motherboard has a dual Bios. So I could easily reload the defaults, set the boot sequence and it worked. What I found was that the bios stores the last 4 (that was displayed) successful boots.
What I suspect is, when you do a number of installs (which I did), the bios runs out of space. There may be other reasons. If anyone has an idea, I would be interested to know.
Thanks for the comments and help!
Well otto_oz, if your system is working properly, then that is a good thing. Looking at your posts do not show anything obvious that is wrong. It appears you are booting from /dev/sda1 (ata-WDC_WD1500HLFS-01G6U1_WD-WX51C10P0408) with three partitions. /sda2 is swap and /dev/sda3 may be your /home folder. /dev/sdb & /dev/sdc, each 500 GB may be part of a raid drive which shows up as something else, but I can’t tell from this information. As for /dev/md0, not sure, but fdisk does not think that it is a valid drive partition. When you are in openSUSE, how many partitions do you have files on?