I still haven't change anything to solve this problem, for different
reasons, but I make the summary:
1st of all thanks to all who replied
I think that my problem is caused by a disk which is dying, I get all the
messages, scsi transport failed and bad blocks from the same scsi chain.
I'll put in this message all the reply I got:
NEERAJ VERMA [email@example.com]
Generally this problem will come if you are using a shared scsi bus
configuration connecting two or more machines to a shared scsi bus
through a shared storage device.
Once the other machine is rebooted you will get the message,
SCSI transport failed.
Alessandro Forghieri [firstname.lastname@example.org]
Dal bus SCSI. ;-)
Forse un cavo/connettore marcio...
Derrick Lim [email@example.com]
This is normally the sign of hard disk failure. Try to identify which is
the actual hard disk that is giving problem if you have more than one
i assume you should have done a proper backup in order to prevent from
Patrick Shannon [pshannon@Schwab.COM]
scsi device is having problems...or it could be the scsi bus. In my
this means a disk is going bad. The error message should be grouped with
address information in /var/adm/messages.
It will probably be the long disk address, so use the output of format to
sounds like you removed a scsi device from the system without removing the
Arora, Samir [firstname.lastname@example.org]
Check the Power Supply for the disk and disk itself .May be bad disk is
causing resetting of your SCSI Bus.
Also Check if it is due to any new addition of disk/tape drive on your
This error normally comes when you are accessing a SCSI device which is
slow /not responding after several tagged queues requests and thereby
holding your SCSI Channel. So SCSI master issues a SCSI reset command to
clear the buffer
John Reynolds [email@example.com]
SCSI resets usually mean either a SCSI device's interface going
bad, or the SCSI chain having problems. The message will usually
give the SCSI address of the device having problems; you can
try to test it on another machine. You should also check
cables, connectors, and terminators.
Ronald Loftin [firstname.lastname@example.org]
Probably a disk drive is dying, or a bad SCSI cable.
Tom Vayda [email@example.com]
Hardware as you know. Try reconnecting cables, resetting the device it
applies to. Then do a probe-scsi-all at the OK prompt IF this does not
help, you will probably need to replace whatever device it is.
Brent Parish [Windows/admin/bparish]
I used to get that error when running a mixed stack of drives - some slower
and running an older firmware than others. When we separated them on
different SBUS scsi chains and/or ran the same speed drives, everything was
Sai Ganesamoorthi [firstname.lastname@example.org]
1) scsi cable
2) scsi controller
3) root disks
D. Stewart McLeod [email@example.com]
I would check the SCSI cables and terminators. Perhaps the length of
your cables may be reaching the threshold (5 meters??).
Is this an external or internal device? If it's external, check the SCSI
cable connections to ensure they are not loose or the pins damaged.
If it's internal, you might try shutting the system down, and reseating the
device (pull it out then put it back in again). Otherwise, it may be a
Is it a disk? What type/size, which system?
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:34 CDT