GA-EP45-UD3R No IDE recognition

[certwert]

I recently bought this motherboard and it does not recognize IDE devices at all. I have tried with two hard drives, multiple jumper settings and my IDE DVD burner, but it never shows up.

I know its not a cable problem, because the drives show up fine in Windows 7 and I can access one of the hard drives and everything. I also have a SATA 1TB drive that works great. But no matter what I do, whether I change the boot order, disconnect everything but the CD drive, etc. it simply won't see the drives or boot to them.

These are my settings:
Sata RAID/AHCI Mode: Disabled )(tried Raid and it didn't work)
SATA Port0-3 Native Mode: Disabled
Onboard Sata/IDE Device: Enabled
Onboard Sata/IDE Ctrl Mode: Raide/IDE

I've changed the wires, changed the jumpers and tried it out of the case to see if it was a grounding issue. Do I have to change settings in the Bios? Is my motherboard defective? It recognized my ubuntu drive once two days ago, then I shut it down improperly and changed jumpers and bios settings trying to get my Sata drive to work, and it hasn't recognized an IDE device since, even though like I said, windows 7 finds them right away. I can feel that the drives are running and the boot CD spins, so its not a power issue either. Any help would be greatly appreciated.


If it is a defective motherboard, it is unfeasible for me to go without the computer for a few days so I'm looking for other options:
Is there anyway to like idk install a bootloader on the sata drive and have it boot to the IDE drive? like I said Windows can see the other drives, so I wonder if this would work?

 

[bilbat]

These are my settings:
Sata RAID/AHCI Mode: Disabled )(tried Raid and it didn't work)
SATA Port0-3 Native Mode: Disabled
Onboard Sata/IDE Device: Enabled
Onboard Sata/IDE Ctrl Mode: Raide/IDE

The first one:
Sata RAID/AHCI Mode: Disabled )(tried Raid and it didn't work)
has nothing to do with your IDE channels, they are 'hung off' the ancillary jMicron drive contoller; this setting controls your first six (yellow) SATA connectors; if you have a SATA drive (or drives) plugged into the yellow ports, this needs to be "Enabled"

Thelast two run the IDE and the pair of 'purple' ports;
on the "Integrated Peripherals" page of the BIOS, you want:

"Onboard SATA/IDE Device" to "Enabled"
and
"Onboard SATA/IDE Ctrl Mode" to "IDE"

You might also need
"SATA Port0-3 Native Mode" at "enabled" - the documentation is terribly unclear about this; what it does is turn on interrupt sharing for the OS - if you're not running Windows ME (the last version that did not support IRQ sharing) or earlier, this needs to be on, and may be responsible for the whole 'no seeum' problem...

Just in case you're a bit unclear about IDE cabling/jumpering:

Here's an IDE cable:
M|----------|------|D
M1---------2------3D
The 'M' end is the motherboard connector; the 'D' end goes to the drives.
There are two kinds of cables: 'standard' (on which the drives are jumpered to identify them), and 'cable select' (on which the cable itself sorts out the drive IDs).
If there are no labels (often, a large plastic or fabric 'pull-tab') saying 'master' and 'slave' on connectors 2 and 3, you have a 'standard' cable - jumper as follows:
it doesnt matter what connector goes to what; your primary (boot) HDD will need to be jumpered as 'master' [MSTR] on the drive; your secondary (or ODD) gets jumpered as 'slave' [SLV] on the drive.
If there are labels saying 'master' and 'slave' on connectors 2 and 3, you have a 'cable select' cable - jumper as follows:
Both drives get jumpered as [CSEL] on the drive; your primary (boot), or only, in the case of just one, goes on connector 3, which should be labeled 'master'; your secondary (or ODD) goes on connector 2, which should be labeled 'slave'; connector 1 goes to your MOBO IDE port...

 

[certwert]

These are my settings:
Sata RAID/AHCI Mode: Disabled )(tried Raid and it didn't work)
SATA Port0-3 Native Mode: Disabled
Onboard Sata/IDE Device: Enabled
Onboard Sata/IDE Ctrl Mode: Raide/IDE

The first one:
Sata RAID/AHCI Mode: Disabled )(tried Raid and it didn't work)
has nothing to do with your IDE channels, they are 'hung off' the ancillary jMicron drive contoller; this setting controls your first six (yellow) SATA connectors; if you have a SATA drive (or drives) plugged into the yellow ports, this needs to be "Enabled"

Thelast two run the IDE and the pair of 'purple' ports;
on the "Integrated Peripherals" page of the BIOS, you want:

"Onboard SATA/IDE Device" to "Enabled"
and
"Onboard SATA/IDE Ctrl Mode" to "IDE"

You might also need
"SATA Port0-3 Native Mode" at "enabled" - the documentation is terribly unclear about this; what it does is turn on interrupt sharing for the OS - if you're not running Windows ME (the last version that did not support IRQ sharing) or earlier, this needs to be on, and may be responsible for the whole 'no seeum' problem...

Just in case you're a bit unclear about IDE cabling/jumpering:

Here's an IDE cable:
M|----------|------|D
M1---------2------3D
The 'M' end is the motherboard connector; the 'D' end goes to the drives.
There are two kinds of cables: 'standard' (on which the drives are jumpered to identify them), and 'cable select' (on which the cable itself sorts out the drive IDs).
If there are no labels (often, a large plastic or fabric 'pull-tab') saying 'master' and 'slave' on connectors 2 and 3, you have a 'standard' cable - jumper as follows:
it doesnt matter what connector goes to what; your primary (boot) HDD will need to be jumpered as 'master' [MSTR] on the drive; your secondary (or ODD) gets jumpered as 'slave' [SLV] on the drive.
If there are labels saying 'master' and 'slave' on connectors 2 and 3, you have a 'cable select' cable - jumper as follows:
Both drives get jumpered as [CSEL] on the drive; your primary (boot), or only, in the case of just one, goes on connector 3, which should be labeled 'master'; your secondary (or ODD) goes on connector 2, which should be labeled 'slave'; connector 1 goes to your MOBO IDE port...

Wow thanks a lot for the really detailed reply. I appreciate it. Unfortunatly the problem continues. It must be a faulty motherboard.

So is there a way to circumvent this with a bootloader? I understand I wouldn't be able to use boot disks but, at least I could use the two hard drives...

 

[bilbat]

if this didn't help, I'm still a bit confused...
You say:

it does not recognize IDE devices at all

but you go on with:

the drives show up fine in Windows 7

This is where it gets unclear; what, exactly, do you mean by:"does not recognize IDE devices at all?"
Are you getting drive icons in 'My Computer' that are not accessible when you double-click on them?
Here's the deal: more syptoms = better (or, at least, more accurate) diagnosis!
It might help if you posted a list of:
what drives (by size, connection type [IDE or SATA], actual connector number used, and what's on them [say, Win7 boot disk]) are actually connected; and which ones do you 'see', and where (or, conversely, where not) do you see/not see them...
A little more explanation will aid my trying to help here...
If you're not seeing some drives at all in the BIOS, I doubt a bootloader (BTW - I use one, BootItNG here:
http://www.terabyteunlimited.com/downloads-bootit-next-generation.htm )
will help; on the other hand, if you want to get various 'flavors' of Windows to co-exist without 'messing with' each other, or want to have more than four partitions on a drive, it's excellent!

 

[certwert]

Sorry what I meant by that was that when I look at the drives in the Bios the only thing that ever shows up is the Sata Drive. They show up in Windows 7 when I want to use the CD drive, it works fine, and the IDE hard drives show up in My Computer as well. I have used the partition editing tool in Windows 7 to see the drives as well, but one can't be accessed as it isn't NTFS. Gigabyte support suggested I update my chipset which i did but it didn't help.

Here's my configuration

1tb Western Digital Sata drive NTFS Windows 7 Works Great

160GB Seagate IDE drive NTFS Windows Vista: can be seen in Windows 7 when connected as slave. Can't be seen in Bios.

80GB Western Digital IDE drive FAT(32?) Ubuntu Jaunty Jackalope. Can't be seen by bios. In the partition editor I can see this drive but can't open it or access it because Windows 7 only deals with NTFS and exFAT.

DVD Burner: IDE can't be seen by Bios but works fine with Windows 7.

All my crucial data is on the 80GB Ubuntu drive. If I could find a computer with SATA and IDE I would even consider copying that drive onto a partition on my 1TB Sata with Norton Ghost or something like that. My old motherboard which had that capability broke and I have two other computers which only accept IDE so I'm kind of stuck to making this one work.

 

[bilbat]

Thanks for the extra info - something is nagging at me here, just below the actual level of conciousness - there's a familiar glimmer to this - I'm gonna let it percolate through for a bit, and likely go into my boot manager and risk turning some things visible in my boot manager to different OSs, to see how they react - I have a hunch, but it will take some oddball work to confirm...

 

[bilbat]

Thought of two things:

80GB Western Digital IDE drive FAT(32?) Ubuntu Jaunty Jackalope.

are you sure it's 'FAT-something' and not EXT3 or ReiserFile?
try a peek here:
http://www.fs-driver.org/
or here:
http://yareg.akucom.de/

Another - once it's mounted, if you can see it but are refused access, copy this:

[cpp]Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\*\shell\runas]
@="Take Ownership"
"NoWorkingDirectory"=""

[HKEY_CLASSES_ROOT\*\shell\runas\command]
@="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"

[HKEY_CLASSES_ROOT\Directory\shell\runas]
@="Take Ownership"
"NoWorkingDirectory"=""

[HKEY_CLASSES_ROOT\Directory\shell\runas\command]
@="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"[/cpp]

into notepad, save it as, say, TakeOwn.reg...
Double click on it, you'll get a UAC query whether it's good, say "OK", next a Registry Editor warning, say "Yes", next a Registry Editor confirmation, say "OK", and reboot.
Now, when right clicking on an object or a directory, you'll see a new item "Take Ownership", once you 'own' an object (including the pesky stuff that windows7 wants to 'protect' you from accessing), it's all magically available...

 

[pcangeldust]

I just got the exact same motherboard today. It recognises both my hard drives. One is sata the other ide. Just put on optimal default settings and see if it works. The bios is quite confusing so many settings.

 

[bilbat]

If you want help with BIOS optimization, and perhaps a 'mild' easy-on-the-hardware overclock, post back - always glad to help!

Bill

 

[pcangeldust]

I think my processor is f'ed. I bought this motherboard because i thought the other one was the problem but am still getting same problem of the processor details not showing up in boot up. It works but the processor details dont come up and there is no beep. Some times it boots normally with a beep and the details come up but mostly it doesnt.

 

[bilbat]

Have you done the obligatory "Load Optimized Defaults"? This is a required first step with every Gigabyte board...

 

[pcangeldust]

Yh i have, am pretty sure the processor is faulty. Not completely damaged as it still works.

 

[bilbat]

It's possible, but not likely; the chances of a CPU being damaged, while still working somehow 'marginally' are infinitesimal. The boot speed/sequencing of the POST display varies - sometimes it appears to 'skip through', sometimes (especially after a 'cold' boot), it will display CPU and memory specs - does not affect operation in any way. If, however, you are having problems 'in' the BIOS, a much more probable problem is incorrect mechanical seating of the land grid array - the mechanical specs:
http://download.intel.com/design/processor/designex/320837.pdf - seventy-two pages...
are infinitely 'picky'; you might try 're-seating' your CPU - but, once again, if your concern is simply the appearance of 'specs' on your POST screen - it matters not at all!