C
CJT
I've got a couple of WD 1200AB drives in a server as master and slave
on the same cable (not that I think it matters, but for completeness).
I'm running Solaris 9. The machine is not heavily loaded. At random
intervals of 2-3 days, one or the other (usually the slave) will audibly
click a couple of times and drop off line. The log file will reflect a
series of timeouts followed by an indication that an error has occurred,
described as --
Sense key: aborted command
error code 0x3
Once it happens, I haven't found a way to get the disk to respond again
except hard rebooting, after which everything will appear fine for a
few days. When the slave goes down, the master stays up, and vice
versa.
They're not hot. The cables are good quality. There are two other
(Maxtor) drives on the other channel that don't exhibit the problem.
The motherboard is a Shuttle AK12A with an underclocked Athlon running
at 900 MHz. It seems pretty solid otherwise.
The disks in question are not used by the system (which has its own
SCSI disk) -- they're loaded with user files being served via Samba
and NFS shares.
Any thoughts?
--
After being targeted with gigabytes of trash by the
"SWEN" worm, I have concluded we must conceal our
e-mail address. Our true address is the mirror image
of what you see before the "@" symbol. It's a shame
such steps are necessary.
Charlie
on the same cable (not that I think it matters, but for completeness).
I'm running Solaris 9. The machine is not heavily loaded. At random
intervals of 2-3 days, one or the other (usually the slave) will audibly
click a couple of times and drop off line. The log file will reflect a
series of timeouts followed by an indication that an error has occurred,
described as --
Sense key: aborted command
error code 0x3
Once it happens, I haven't found a way to get the disk to respond again
except hard rebooting, after which everything will appear fine for a
few days. When the slave goes down, the master stays up, and vice
versa.
They're not hot. The cables are good quality. There are two other
(Maxtor) drives on the other channel that don't exhibit the problem.
The motherboard is a Shuttle AK12A with an underclocked Athlon running
at 900 MHz. It seems pretty solid otherwise.
The disks in question are not used by the system (which has its own
SCSI disk) -- they're loaded with user files being served via Samba
and NFS shares.
Any thoughts?
--
After being targeted with gigabytes of trash by the
"SWEN" worm, I have concluded we must conceal our
e-mail address. Our true address is the mirror image
of what you see before the "@" symbol. It's a shame
such steps are necessary.
Charlie