Archived from groups: microsoft.public.windowsxp.hardware (More info?)
I have a 4-bay external firewire enclosure, with Oxford Semiconductor
911 chipset. I have 4 drives connected (a couple of Maxtors, a Western
Digital and a Hitachi). Every so often (many times a day) I get
"Delayed write failed" error on one or more of the disks (usually the
Hitachi or one of the Maxtors), even though the disk is inactive.
I'm running Windows XP SP2 on a machine with an Athlon K7T266Pro
board. I have write caching DISABLED (the disks are "optimised for
quick removal"), so I can't see why there should be any delayed write
activity at all, let alone when I'm not actually using the disks.
I've seen alot of messages concerning the "delayed write" problem,
particularly with XP SP2, but would be keen to understand why I get
these errors when I'm not actually trying to write to the disks.
I've tried plugging the same enclosure into a different PC (an Acer
T120) and get exactly the same problem. This is also running XP SP2.
I've seen a recommendation to change the PCI latency in the BIOS, but
this option doesn't seem to be available in my BIOS settings.
I've also run a utility from the BUSTrace site to check whether write
packet sizes are an issue, but it didn't generate any failures.
Does anyone know why I would get these errors when the disks are not
being used??? Better still, can anyone suggest a workaround??
TIA for any feedback
Ian
I have a 4-bay external firewire enclosure, with Oxford Semiconductor
911 chipset. I have 4 drives connected (a couple of Maxtors, a Western
Digital and a Hitachi). Every so often (many times a day) I get
"Delayed write failed" error on one or more of the disks (usually the
Hitachi or one of the Maxtors), even though the disk is inactive.
I'm running Windows XP SP2 on a machine with an Athlon K7T266Pro
board. I have write caching DISABLED (the disks are "optimised for
quick removal"), so I can't see why there should be any delayed write
activity at all, let alone when I'm not actually using the disks.
I've seen alot of messages concerning the "delayed write" problem,
particularly with XP SP2, but would be keen to understand why I get
these errors when I'm not actually trying to write to the disks.
I've tried plugging the same enclosure into a different PC (an Acer
T120) and get exactly the same problem. This is also running XP SP2.
I've seen a recommendation to change the PCI latency in the BIOS, but
this option doesn't seem to be available in my BIOS settings.
I've also run a utility from the BUSTrace site to check whether write
packet sizes are an issue, but it didn't generate any failures.
Does anyone know why I would get these errors when the disks are not
being used??? Better still, can anyone suggest a workaround??
TIA for any feedback
Ian