GigaRAID on GA - 8KNXP

I'm having an issue with the GigaRAID on the 8KNXP

I'm loosing connectivity with the two HDDs connected as NORMAL ATA drives
connected to the GigaRAID port - both on the one BUS.

When I loose the connection, I can hear what sounds like the HEADS ONLY
'clicking' into their rest-track, and I don't notice any change in the
'spin' sound of the drives, although these are extra quiet Western Digitals.
I don't normally hear the heads move, even during a defrag, or other heavy
disk usage.

Explore cannot do any functions with the drives, and frequently the screen
will freeze.

Also on re-booting, I frequently get the GigaRAID IDE SCAN to re-recognize
the drives, but sometimes not. Disabling and re-enabling in the BIOS may or
may not result in any changes. Sometimes unplugging the power helps, but
not always.

The *FINAL* solution that regularly works is pull the CMOS BATTERY and
short the connectors.

It is highly annoying, happening randomly

I thought it may have had something to do with a DRIVE UPDATE from M$, which
resulted in Event Viewer reporting ITE errors a few days after the update,
but I've re-installed the original driver. Device Manager does not, and
has never noted any warnings.

stumpted geezer

 

Unless you have several drives in your system, the 'reccomended' method is
to use the IDE1 connector for normal IDE HD's, and IDE2 for optical drives.

 

Yes - 4 drives, 2 on IDE 0 = Primary, CD-ROM on IDE 1 = Secondary, and 2
more on the one port of the GigaRAID (2) and hoping to put more on the 2nd
GigaRAID (3) ...

One thing that seems to be settling down is the re-installation of the
driver that came with the MoBo CD.

About a week ago, on an UpDate visit at M$, a driver was suggested, and
starting around the 30th of Jan (a number of days after the UpDate visit)
event viewer started to log errors with the ITE - which is the GigaRAID
driver.

The lockups have slowed down, but not stopped. Also the Event Viewer has
stopped reporting that the "FIRMWARE is old"

I'm hoping that it was the testing & logging of the events that were
triggering the loss of contact -- it seems -- at the BIOS level..




"Timothy Drouillard"

Unless you have several drives in your system, the 'reccomended' method is