|Do you see anything else on the screen besides that?|
Do you have any bootable hard drives connected to it?
If so, is the mboard booting from one?
If so, and if it's not botting from it, did you check the Boot Order or similar settings in the bios Setup?
If you have more than one hard drive connected, at least one is bootable, and it's not booting, did you look in the bios Setup to see which one is listed first? There's a list of hard drives somewhere - the first one in the list has to be bootable.
"Apparently that has a raid/SCSI controller. If that's enabled it has it's own bios and may give that error if nothing is attached. Check your motherboard manual.
Could also happen if you've added a SCSI card."
Good points, but usually you get a message along the lines of ......
"JMicron Technology Corp. PCI-E to SATA-II IDE RAID Controller Bios V1.06.54
Detect drives done. No any drive found. "
(obviously English is not their first language)
The name of the controller - bios version
No drives detected. Bios not loaded.
(If the controller is capable of RAID and a drive is connected to it and isdetected, you often get a message "Press xxx to set up RAID" or similar - that times out after a few seconds, the computer continues to boot.)
Some mboards have an added on drive controller built into the mboard, in addition to that built into the main chipset.
E.g. an Asus A7V-133 I had, had one of those.
The controller's bios for that attempts to load before anything else while booting (same for the above SATA/IDE PCI-E X1 card on a newer mbioard)
If no drives are connected to the secondary controller, the bios for it does not need to load, and you get some sort of message.
For the A7V-133, there was no way of disabling the secondary controller's bios from trying to load in the bios Setup settings - you just ignored the message, the computer continued to boot, if the Boot Order settings or similar in the bios were correct, and if there was a bootable hard drive detected, it would boot that.