IDE write disk errors during gigabit network transfers

[rbdmg]

Problem - getting disk errors such as:

Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 11
Date: 11/30/2004
Time: 3:32:05 PM
User: N/A
Computer: BASEPC
Description:
The driver detected a controller error on \Device\Harddisk0\D.


PC with Gigabyte 6VX7-4X motherboard (Via Apollo Pro 133A chipset) P III
800EB, 512MB ECC, running WinXP pro.
WinXP software and all device drivers are up-to-date.
All hardware otherwise working ok with no device manager conflicts.
Have swapped out disk drives - problem persists.
Have tried installing VIA 4in1 - no changes.


The problem only occurs when copying data across the local gigabit network
to the IDE fixed disk drives in this PC. Happens both pulling and pushing
data. Happens when writing to both the C: and D: drives. Happens with
source PCs with both 1Gb and 100Mb NICs.

PC NIC is Netgear GA311NA Gigabit PCI card with latest drivers from Realtek.
(Netgear doesn't keep their driver downloads up to date.)
Local connects are via Netgear GS105 switch with Cat 5E cables.

Can write to IDE DVD+R with no problems. (direct write only - if files are
cached, the pre-record cache writes cause the IDE disk errors),

Can write to USB/Firewire disk drives with no problems.

Had no problems when using previous 100Mb NIC.

So, problem seems to be IDE/NIC related.

Would like to keep gigabit NIC, since I do large file transfers between PCs.

Any suggestions on how to correct?

 

[Guest]

Try switching 0 and 1 drive (C: and D to the secondary IDE cable,then switch
secondary devices to primary,see what results come from it.If none are
present,
you probably have a bad controller,you can try locating the controller in
device
mgr.,then select,update drivers.Or go to mfg web site to see if any exist,P
lll
based board is somewhat obsolete.

 

[Malke]

Problem - getting disk errors such as:

Event Type: Error
Event Source: Disk
Event Category: None
Event ID: 11
Date: 11/30/2004
Time: 3:32:05 PM
User: N/A
Computer: BASEPC
Description:
The driver detected a controller error on \Device\Harddisk0\D.


PC with Gigabyte 6VX7-4X motherboard (Via Apollo Pro 133A chipset) P
III 800EB, 512MB ECC, running WinXP pro.
WinXP software and all device drivers are up-to-date.
All hardware otherwise working ok with no device manager conflicts.
Have swapped out disk drives - problem persists.
Have tried installing VIA 4in1 - no changes.


The problem only occurs when copying data across the local gigabit
network
to the IDE fixed disk drives in this PC. Happens both pulling and
pushing
data. Happens when writing to both the C: and D: drives. Happens
with source PCs with both 1Gb and 100Mb NICs.

PC NIC is Netgear GA311NA Gigabit PCI card with latest drivers from
Realtek. (Netgear doesn't keep their driver downloads up to date.)
Local connects are via Netgear GS105 switch with Cat 5E cables.

Can write to IDE DVD+R with no problems. (direct write only - if files
are cached, the pre-record cache writes cause the IDE disk errors),

Can write to USB/Firewire disk drives with no problems.

Had no problems when using previous 100Mb NIC.

So, problem seems to be IDE/NIC related.

Would like to keep gigabit NIC, since I do large file transfers
between PCs.

Any suggestions on how to correct?

Since the problem persists with different hard drives, you know the
drives are OK. Your motherboard is probably going and it's time to buy
a new one. Yours is elderly. You can keep the NIC, of course and use it
with a new m/b. You can keep the drives, but will need to do a Repair
Install of XP after you put in the new m/b.

Malke

 

[rbdmg]

Malke & Andrew - thanks for the reply.

Have no problems replacing the motherboard. Since I can still get "new"
motherboards that will use my existing CPU and memory, this would be my
first choice. But these "new" motherboards use the same VIA chipsets as my
current motherboard. I was hoping someone knows if this is a generic problem
related to the use of gigabyte nics and the VIA 133A chipset/IDE controller.

Yes, the system is somewhat obsolete, but the 800 CPU and 512MB memory gets
the job done.
The strange thing is the errors occur only during network transfers and
direct WINXP writes. For example, writes to a DriveCrypt encrypted file
system on the same drives (either encrypted partition or encrypted file)
work just fine during network transfers. And I have never actually found a
damaged file, even when the error messages are logged. Still, it is not a
problem that I am willing to let continue.

rb