What exactly is this transport error?
sd47 Soft Errors: 0 Hard Errors: 0 Transport Errors: 24

What brand of scsi drives are the most durable? Whch are the worst?

Personally I have experienced more failure rates with Seagate and the
least with IBM which is now Fujitsu.

BN wrote:

> What exactly is this transport error?
> sd47 Soft Errors: 0 Hard Errors: 0 Transport Errors: 24
>
> What brand of scsi drives are the most durable? Whch are the worst?
>
> Personally I have experienced more failure rates with Seagate and the
> least with IBM which is now Fujitsu.

IBM's actually now Hitachi and I'd agree with that - I've also had good
luck with Quantum drives (Atlas and Viking).

P.

BN <BN@BN.COMO> writes:

>What exactly is this transport error?
>sd47 Soft Errors: 0 Hard Errors: 0 Transport Errors: 24

A transport errors is generally an error like a SCSI parity error;
so not a disk error but an error between the disk and the controller.

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

Casper H.S. Dik wrote:
> BN <BN@BN.COMO> writes:
>
>
>>What exactly is this transport error?
>>sd47 Soft Errors: 0 Hard Errors: 0 Transport Errors: 24
>
>
> A transport errors is generally an error like a SCSI parity error;
> so not a disk error but an error between the disk and the controller.


The other drive on the same controller is working fine. Does this mean
perhaps the controller on the drive itself is bad? Are there any quick
remedies that can be that can be used to rectify this short of replacing
this drive?

The drive is totally inaccessible and hangs the system I attempt to
access it.



>
> Casper

In article <11jlqcd1ckos007@news.supernews.com>, BN <BN@BN.COMO> wrote:
>Casper H.S. Dik wrote:
>> BN <BN@BN.COMO> writes:
>>
>>
>>>What exactly is this transport error?
>>>sd47 Soft Errors: 0 Hard Errors: 0 Transport Errors: 24
>>
>> A transport errors is generally an error like a SCSI parity error;
>> so not a disk error but an error between the disk and the controller.
>
>The other drive on the same controller is working fine. Does this mean
>perhaps the controller on the drive itself is bad? Are there any quick
>remedies that can be that can be used to rectify this short of replacing
>this drive?
>
>The drive is totally inaccessible and hangs the system I attempt to
>access it.

A problem with the cabling or termination can cause funny problems,
including one drive working and one failing. For a single ended
bus, the length limit is something like 3 feet. The bus must have
a terminator at each end and nowhere else. The controller normally
has automatic termination, so if the controller is at one end of the
bus you only have to worry about the other end. Some disks can supply
a terminator if the correct jumper is set. Some cables come with a
terminator attached to the end. If the drives are in external boxes,
you would attach a terminator to the second connector of the last drive
if the drive is not set to terminate the bus.
It is also possible to have a bad drive. Most dirve problems involve
a problem with the media (the disk platters or heads or the connections
to the heads). Much less often, you can have other problems such as a
bad scsi bus driver.
>
>>
>> Casper


--
Tom Schulz
schulz@adi.com

In article <11jlqcd1ckos007@news.supernews.com>, BN@BN.COMO says...
> Casper H.S. Dik wrote:
> > BN <BN@BN.COMO> writes:
> >
> >
> >>What exactly is this transport error?
> >>sd47 Soft Errors: 0 Hard Errors: 0 Transport Errors: 24
> >
> >
> > A transport errors is generally an error like a SCSI parity error;
> > so not a disk error but an error between the disk and the controller.
>
>
> The other drive on the same controller is working fine. Does this mean
> perhaps the controller on the drive itself is bad? Are there any quick
> remedies that can be that can be used to rectify this short of replacing
> this drive?
>
> The drive is totally inaccessible and hangs the system I attempt to
> access it.
>
>
>
> >
> > Casper
>
Just a hint:
Check with prtconf -vP command for SCSI board, if the Sync-Speed is the
one it should be for your SCSI type. 20MB, 40MB....
Ususally, when there is problem with cabling, Sync-speed drops down.