I rebooted, froze the screen, and copied it down (again, on my system it appears on the GSATA AHCI BIOS loader page); it shows:
ODD0: ATAPI DVD A DH20A4H
However, if the drive otherwise works, files, burning, etc., then, obviously, the BIOS is 'seeing' it!
If your BIOS is set (on the "Advanced BIOS Features" page) as follows:
"Hard Disk Boot Priority" to whatever - if it's booting OK, don't change this - it merely selects which HD to boot from, when you're to the 'boot from hard drive' loader - it's so you can pick a drive out of the normal BIOS sequence which is Intel SATA2_0, SATA2_1, through SATA2_5, then GSATA2_0 & 1, then (I believe - I've never had a hard drive on my IDE channel as I'm out of places to put the little buggers in the case) IDE master & slave;
"First Boot Device" to "CDROM";
"Second Boot Device" to "Hard Disk";
"Third Boot Device" to "Floppy" (if you have one, that is...);
Oh - and on the "Integrated Peripherals" page:
"Onboard SATA/IDE Device" to "enabled";
and "Onboard SATA/IDE Ctrl Mode" to "IDE" (but this one shouldn't matter, its setting doesn't affect the IDE channel - I'm set to AHCI, and it still 'sees' the IDE as IDE; and I think if either of these last two were wrong, you wouldn't be able to use the drive at all!)
you should be good to go! Might be time to call CyberPower...
Here's another test: I think this is common to all GBs, but I'm not absolutely positive - if you put the driver disk that came with it into the DVD drive, no matter how your boot sequence is set, I believe the BIOS boot routine should detect the existence of the XpressRecovery loader, and ask you if you'd like to run it... (This, by the way, is a really good idea to do once, when your system is booting OK - we surmise that the first run of XpressRecovery 'hides' a copy of your current BIOS and 'boot block' in the space on the first HD [won't work if that's a RAID, much to my chagrin!] between the MBR and the first partition, and has let a couple people recover systems which were otherwise 'bricked' by a bad BIOS flash.) One more BIOS pointer - never use the @BIOS facility to flash your BIOS, it's responsible for more GB RMAs than any other single cause!