Veritas/Symantec Netbackup Woes.

| August 5, 2007 | Reply

This weekend a veritas disaster was dumped on me. This is how I deleted, and recreated entries for the library robot, and it’s drives.To be honest, I don’t even know what the original issue was, but for some reason, Sun was called out to replace a card in our StorageTek L40 tape library. The card was replaced, and from that point forward, all of the drives in the library went down and we began recieving SCSI errors in our system log.

The errors looked something like this:

Aug 4 10:15:09 gcand715 tldcd[303]: [ID 359089 daemon.error] TLD(0) mode_sense ioctl() failed: No such file or directory

Aug 4 10:15:11 gcand715 tldcd[303]: [ID 832037 daemon.error] scsi command failed, may be timeout, scsi_pkt.us_reason = 1

Aug 4 10:15:11 gcand715 tldcd[303]: [ID 359089 daemon.error] TLD(0) mode_sense ioctl() failed: No such file or directory

Aug 4 10:15:11 gcand715 tldcd[303]: [ID 832037 daemon.error] scsi command failed, may be timeout, scsi_pkt.us_reason = 1

Aug 4 10:15:11 gcand715 tldcd[303]: [ID 769352 daemon.error] TLD(0) Mode_sense error, SCSI INTERFACE ERROR

Aug 4 10:15:12 gcand715 tldcd[303]: [ID 958280 daemon.notice] TLD(0) opening robotic path /dev/sg/c4t1l0

Aug 4 10:15:12 gcand715 tldcd[303]: [ID 832037 daemon.error] scsi command failed, may be timeout, scsi_pkt.us_reason = 1

Aug 4 10:15:13 gcand715 last message repeated 1 time

We called sun back out to look at the issue.
The card replaced on the tape library by the sun contractor was configured incorrectly. . I guess it is a similar sort of mistake as putting a battery the wrong way into a hearing aid. It is easily done but also easily corrected. The library was set in SCSI LVD mode rather than SCSI HVD. There was a jumper on the board that dictates this setting. We also noted that the previous engineer had neglected to configure the SCSI IDs for each drive. They were all set to unassigned.

So, we assigned SCSI id 0 to the tape library. Then we assigned SCSI id 1-4 to each of the drives inside.

After assigning the id’s, we did a reconfigure reboot
#touch /reconfigure
#reboot

When the box came up, the errors in /var/adm/messages changed a little.

Aug 5 03:10:41 gcand715 tldcd[324]: [ID 958280 daemon.notice] TLD(0) opening robotic path /dev/sg/c4t1l0
Aug 5 03:10:42 gcand715 tldcd[324]: [ID 985024 daemon.error] TLD(0) key = 0

Tags:

Category: Uncategorized

About the Author ()