Well, it turns out this was a pretty simple fix (and obvious). With that
number of drives, termination is an issue, so placing a terminator on the
external SCSI connector on back of the IO board made the problem go away
(thanks to Sun for the hint).
Thanks to Dan email@example.com who wrote:
>No docs, but I would check:
>1.Total bus length (keep it under 3 meters)
>2. Ensure that ALL of your disks have the same MAX throughput (I have seen
this with Seagate 10K disks, there are 2 different throughput rates)
>On the plus side this should straighten itself out and the server should stop
complaining after the couple at boot.
Original post follows:
>> Does anyone have a FAQ for me to look at? I'm trying to find a reason for
some errant SCSI behavior. On an >>E3000 with 10 4.2G Seagate Ultra/Wide SCSI
(ST34371WC) drives installed. Several give "connected command >>timeout"
errors on boot. Haven't been able to find this documented (yet) but have heard
it mentioned in general before.
Adrian Stovall Adrians@solarsystems.com
Solar Systems and Peripherals Inc. http://www.solarsystems.com
An authorized Sun( Reseller 1 (800) 253-5764
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:35 CDT