[Veritas-bu] SCSI error

Hi all,

Joost, thanks for your reply :-)

I've checked the following:

- cabling and termination are OK
- robot arm has unique SCSI id
- robot arm is on separate SCSI bus and all drives are configured OffBus

I've added to the following lines to the master and media servers
(/etc/system):

forceload: drv/st
forceload: drv/sg

Still have the same errors :-(

regards,

Darek


Wiadomos'c' od Joost Mulders:
>>Feb 25 16:28:41 clasp tldd[25220]: [ID 832037 daemon.error] scsi command 
>>failed, may be timeout, scsi_pkt.us_reason = 7
>>Feb 25 16:28:42 clasp tldd[25225]: [ID 832037 daemon.error] scsi command 
>>failed, may be timeout, scsi_pkt.us_reason = 7
>>Feb 25 16:28:44 clasp tldd[25270]: [ID 832037 daemon.error] scsi command 
>>failed, may be timeout, scsi_pkt.us_reason = 7
>>Feb 25 16:28:45 clasp tldd[25284]: [ID 832037 daemon.error] scsi command 
>>failed, may be timeout, scsi_pkt.us_reason = 7
>>Feb 25 16:28:46 clasp tldd[25292]: [ID 832037 daemon.error] scsi command 
>>failed, may be timeout, scsi_pkt.us_reason = 7
>>Feb 25 16:28:47 clasp tldd[25302]: [ID 832037 daemon.error] scsi command 
>>failed, may be timeout, scsi_pkt.us_reason = 7
> 
> 
> 
> These messages come from tldd, the daemon controlling the robotic arm. 
> Because 
> you say that these messages appear when backups are running, I guess that the 
> robotic arm is on the same bus as one or more tape drives.
> 
> I would suggest:
>  -> Check cabling and termination of this SCSI bus.
>  -> Make sure the library (robot arm) has unique SCSI id on the bus
>     The librarie's SCSI id's can be set and seen on the lib's frontpanel
>  -> If the robot is on a scsi bus with one or more tape drives, make sure that
>     the "On bus" = On, on the lib's frontpanel. On bus = On means that the 
>     robot arm shares a scsi connection with one or more drives.
>     
> Regards, Joost