Failed on Signal(11)

[golilang]

Hi,

I have been running Networker 6.1.1 for sometime now and just recently networker started running into errors when working with the Jukebox.

The errors are directly related to commands issued to the autochanger "nsrjb"

"failed: Load operation failed on signal(11)"
"media alert: Label operation failed on signal(11)"
"media alert: Reset operation failed on signal(11)"

The nsr/cores/nsrjb is filled with core files.

I tried resetting the Autochanger, server, Networker software and have checked all scsi cables. I wonder if it's the HBA, Although I have not seen any errors being called out.

Any help is appreciated.

Hardware
Sun E4500
8x400MHz, 8GB memory
StorageTek L700
9840 (scsi) Tape drive

Legato Networker 6.1.1 build 238
Solaris 7

 

[wallace88]

did you look at /var/adm/messages?

 

[golilang]

Yes. The messages file is logging the signal 11 event but no details are provided as to point to an issue. I have also reviewed logs under nsr/logs.

 

[Serbtastic]

Try taking Networker out of the picture by loading a scratch tape into the tape drive and trying a tar to the tape.

 

[golilang]

I have had no problems writing to tape through Networker once the tape is in. I did test sending a tar file to tape with no issues.

The problem is the load, unload and reset commands issued by Networker.

 

[UnixSkunk]

Hello, Golilang..
I remember getting similar errors when one of our IBM LTO libraries had a tape jammed between the robot and the slot. We also received similar errors when the robot's control motor died. Have you tried exercising your tape library to make sure that everything is functioning correctly in the library?

UnixSkunk - Tux's Evil Nemesis

 

[golilang]

Well it seems that I have the autochanger working properly so far. Tried several things, even rebuilding the file and media db.

All the errors point to nsrjb commands being issued to the autochanger. Had stk do a thorough check of the L700 and no problems were detected (I've heard that before).

Anyway started running inquire on devices and found for one of the drives the device is available, but unidentifiable. Removing the device really did not help. Somehow my nsrjb.res file was having a problem so I rebuilt the nsrjb.res skipping the bad tape drive and it worked out.

Tested and configuring nsrjb.res with the bad tape drive again gave the signal(11).

The question of the day for me is why did a bad tape drive cause my whole library to come down?