Greetings!
I just installed OS12.3 amd64 as my main OS. I used the KDE Live image for installation and set the boot loader to install to mbr, as well as root. The system installed fine. (plus I’m writing from within)
HOWEVER!
There is a very strange and ANNOYING bug, which is the following:
Upon starting the system, right after verifying the DMI pool data, GRUB2 comes into the picture - taking over the boot procedure as it should, but it says it cannot find the device it should boot from and is going into grub rescue. I made extra care to NOT mount partitions by UUID, but device name instead (well it’s actually the default setup).
I can’t handle grub rescue more than typing ‘ls’, so that doesn’t work for me.
Now you could say: "Then how are you writing from within the OS?"
Well, if I boot from the install DVD and select boot from hard disk, it works as it should and even without the disk, if I fire up the system and request a boot selection menu with the F12 key and select the appropriate hard drive. it boots JUST FINE.
Now isn’t that strange? It boots when the drive is selected manually, but not automatically, because of some device id-stuff?
If you (who’s reading this) can figure anything out, please don’t keep it inside… this is the most stupid OS bug I’ve ever faced…
Else: memtest86+ from the install disk is working as intended, but selecting it from the main menu results in a nice “too small lower memory” message. Any ideas? This also happened to me with Debian.
[FONT=century gothic]**Please delete the thread, it was a mistake on my part:
Boot order in BIOS was messed up. **[/FONT]:shame:
That was probably your mistake. The default is to mount by device-id.
id /dev/disk/by-id/ata-SAMSUNG_HD642JJ_S1JNJ90QA04749-part1
name /dev/sda1
The device name can change. In your case, perhaps the name depends on whether you are booting from a DVD.
(edit) I saw your followup post only after I had posted my reply. I’m glad you have it working.
Compare the details of the boot entry in /boot/grub2/grub.cfg
with what you see in /etc/fstab
AFAIK there is no bug. Well I must have install 12.3 over 100 times and never had anything like this.
We’ll not delete it
People can learn from such mistakes
I agree with @nrickert
**Thanks for the replies! **You’re right, it might help someone. On the other hand, it happened because:
Boot order in BIOS:
1. CD-ROM
2. USB-HDD
3. Hard Disk
Harddisk order:
1. Bootable add-in cards
2. Samsung 160GB IDE (openSUSE)
3. WD 500GB SATA2 ACHI (data)
4. Samsung 200GB SATA ACHI (data)
So it was set to look for a bootable cd/dvd, then a bootable usb stick/memcard (I have SLAX on my 8GB SDHC :)) and last but not least, the hard drives in that specific order. Now I don’t understand why, but when the hard drive was second to any usb device, GRUB failed to start-up properly and the mentioned problem happened, even though there was no USB device plugged in, neither an optical disc inserted.
And to correct myself, mounting was based on the default device-ID, I just didn’t remember the term. 
So I don’t really understand why that happened, as I think this shouldn’t happen, but oh well, it works now is all that matters.
If it is of interest in this topic, my motherboard is a GIGABYTE GA-MA770-UD3 rev1.0 with F9G BIOS, which used AWARD BIOS.
By the way: Each time I boot, I see ata3 (and ata4): device softreset failed (device not ready)
right before plymouth appears. This isn’t a suse bug, happened with Debian Wheezy too. Any ideas?