1* It could be that the bios is not reading the info correctly as SL does dig deep into hardware info or something that is why grub list the hd's as 4537895237-8435857-834732566-824478 instead of just /dev/sda3 , check asus website for latest bios and update if needed.http://usa.asus.com/products2.aspx?l1=3&l2=-1
This is the closest to specs I could find , looks like they use the marvell as a standard chip in most of their newer boards:http://www.debianhelp.org/node/9176http://www.google.com/search?hl=en&clie ... tnG=Search
Might check yours using lspci in any linux distro and if same as above then you can end up installing the driver in the google search above.
2* Could be GAG that the grub in SL does not know how to interpret GAG or gag writes it own funny info to the MBR and is the cause of the problems.
3* It could be some hd's does not want to be on the same eide / ata cable as a dvd or the jumper settings on the hd is incorrect , check manufctr. website for correct jumper settings , should be master on ata /eide cable. Then try below cheat.
4* Cheat that might just work.
You might want to try a good stable partition software like UBCD http://www.ultimatebootcd.com/
then you know the partition must work by default and is correct , browse to lower part of link for the info and possibly run a hd check overnight on the 80gb to make sure it is okay.
Disconnect the sata hd's leaving only 80gb , partition to 1 big partition /set active the boot part / format the 80gb to fat32 , boot from SL and see if it recognizes the hd. Not sure what partition program you use but stick to old school / old standard settings no fancy 64k ntfs just standard fat32. Using say the WD software if a WD drive and prepare the hd also works and can again be partitioned later in linux.
If it does read the hd then install as if this would be the only hd and no fancy gag boot loader only default grub /auto options and software selection you want / need and restart making sure it loads and works normally.
5* Then reconnect the sata hd's and enter GAG and edit the partition to boot the device then being /dev/hda3 possibly or however it is labeled to start the hd containing SL. Do not write gag to SL hd / partition as SL does not have it installed so no idea what the effects could be jsut "chainload +1" if needed.
6* Google for grub boot loader and "chainload + 1"
More than this you might have to return the motherboard and or have the hd tested as I have received mad motherboards before where the ata controller even in windblows rubish has issues and had to return for replacement = bad batch of products.
This bug over several distro's is not normal at all.
Hope something here helps.