SCOUG-HELP Mailing List Archives
Return to [ 03 |
December |
2007 ]
<< Previous Message <<
>> Next Message >>
Content Type: text/plain
Most SCSI problems are cable or termination -related.
Especially if it was running acceptably before.
Try one device at a time if you have the time and patience.
SCSI bus signal integrity deteriorates the more devices
you have on the bus.
Try to maintain the specified device-to-device spacing and
keep the bus as short as possible. You can get away with
a lot on a short bus. I might even _consider_ cutting off
an end connector and moving everything back by one,
to shorten the cable length.
Still, flaky cabling, connectors or termination is, far and away,
the most prevalent cause of SCSI problems.
+++++++++++++++++++++++
On 12:20 AM 12/2/2007, Steven Levine wrote, in part:
>....
>
>Offhand, the failures you describe have all the marks of being a cable or
>termination issue. However, it could be the HBA or just a side effect of
>the failing MB. >....
>Steven
>----------------------------------------------------------------------
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 03 |
December |
2007 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
|