Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Robtest failed giving i/o error ioctl

Created: 26 Sep 2013 • Updated: 05 Dec 2013 | 12 comments
Shekhar D's picture
This issue has been solved. See solution.

While running robtest on media server this is robotic conrol hosts due to that all the media servers drives goes into AVR status.

robtest
Configured robots with local control supporting test utilities:
  TLD(0)     robotic path = /dev/sg/c0tw500507630f4a0454l1

Robot Selection
---------------
  1)  TLD 0
  2)  none/quit
Enter choice: 1

Robot selected: TLD(0)   robotic path = /dev/sg/c0tw500507630f4a0454l1

Invoking robotic test utility:
/usr/openv/volmgr/bin/tldtest -rn 0 -r /dev/sg/c0tw500507630f4a0454l1

Opening /dev/sg/c0tw500507630f4a0454l1
user scsi ioctl() failed, may be timeout, errno = 5, I/O error
user scsi ioctl() failed, may be timeout, errno = 5, I/O error
mode_sense ioctl() failed: I/O error

Enter tld commands (? returns help information)

 cat /etc/release
                   Oracle Solaris 10 1/13 s10s_u11wos_24a SPARC
  Copyright (c) 1983, 2013, Oracle and/or its affiliates. All rights reserved.
                            Assembled 17 January 2013:

Netbackup version

cat version
NetBackup-Solaris10 6.5.6
 

Please suggest.

Operating Systems:

Comments 12 CommentsJump to latest comment

revaroo's picture

This is a hardware issue / presentation issue to the OS. Nothing to do with NetBackup.

Try deleting the robot and reconfiguring it again.

Marianne's picture

Probably a good idea to power cycle the robot.

If that does not fix the problem, call your hardware vendor.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Shekhar D's picture

Hardware vendor from Library side ? it is using IBM 3584 library.Because library also rebooted

revaroo's picture

Yes. Try Mariannes suggestion. Power cycle the robot, then delete the robot from Netbackup and try reconfiguring it - if no luck then hardware vendor.

I/O errors are typically hardware errors - especially if it was working fine before!

Marianne's picture

Correct. If error persists after library power cycle, I suggest that you log a call with IBM vendor/support.

Have you checked /var/adm/messages for errors?

Probably a good idea to reboot robot control host as well and check boot messages in /var/adm/messages.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

mph999's picture

Did this every work ?

What is the WWN of the drive that is acting as the control path

What is the output of cfgadm -al -o show_FCP_dev

What is in the files :

/usr/openv/volmgr/bin/driver/sg.conf and sg.links

If the files do not exist run :

cd /usr/openv/volmgr/bin/driver

../sg.build all

This will recreate the files.

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Shekhar D's picture

WWN of drive which is having control path from the library is

Frame 6, Row 1 5005 0763 0F4A 0451 5005 0763 0F0A 0451

When i check with the sg.conf and sg.links file it shows as follows and i unable to get the wwn number under sg.links file but able to find under sg.conf please check

sudo cat sg.links
# begin SCSA Generic devlinks file - creates nodes in /dev/sg
type=ddi_pseudo;name=sg;addr=0,0;       sg/c\N0t0l0
type=ddi_pseudo;name=sg;addr=0,1;       sg/c\N0t0l1
type=ddi_pseudo;name=sg;addr=1,0;       sg/c\N0t1l0
type=ddi_pseudo;name=sg;addr=1,1;       sg/c\N0t1l1
type=ddi_pseudo;name=sg;addr=2,0;       sg/c\N0t2l0
type=ddi_pseudo;name=sg;addr=2,1;       sg/c\N0t2l1
type=ddi_pseudo;name=sg;addr=3,0;       sg/c\N0t3l0
type=ddi_pseudo;name=sg;addr=3,1;       sg/c\N0t3l1
type=ddi_pseudo;name=sg;addr=4,0;       sg/c\N0t4l0
type=ddi_pseudo;name=sg;addr=4,1;       sg/c\N0t4l1
type=ddi_pseudo;name=sg;addr=5,0;       sg/c\N0t5l0
type=ddi_pseudo;name=sg;addr=5,1;       sg/c\N0t5l1
type=ddi_pseudo;name=sg;addr=6,0;       sg/c\N0t6l0
type=ddi_pseudo;name=sg;addr=6,1;       sg/c\N0t6l1
type=ddi_pseudo;name=sg;addr=w500507630f4a0454,0;       sg/c\N0t\A1l0 5005 0763 0f4a 0454
type=ddi_pseudo;name=sg;addr=w500507630f4a0454,1;       sg/c\N0t\A1l1 5005 0763 0f4a 0454
type=ddi_pseudo;name=sg;addr=w500507630f4a0455,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500507630f4a0455,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w500507630f4a0456,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w500507630f4a0456,1;       sg/c\N0t\A1l1

sudo cat sg.conf
# Configuration file for SCSA Generic.
#
name="sg" class="scsi" target=0 lun=0;
name="sg" class="scsi" target=0 lun=1;
name="sg" class="scsi" target=1 lun=0;
name="sg" class="scsi" target=1 lun=1;
name="sg" class="scsi" target=2 lun=0;
name="sg" class="scsi" target=2 lun=1;
name="sg" class="scsi" target=3 lun=0;
name="sg" class="scsi" target=3 lun=1;
name="sg" class="scsi" target=4 lun=0;
name="sg" class="scsi" target=4 lun=1;
name="sg" class="scsi" target=5 lun=0;
name="sg" class="scsi" target=5 lun=1;
name="sg" class="scsi" target=6 lun=0;
name="sg" class="scsi" target=6 lun=1;
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005 0763 0f4a 0451";
name="sg" parent="fp" target=0 lun=1 fc-port-wwn="500507630f4a0451";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507630f4a0452";
name="sg" parent="fp" target=0 lun=1 fc-port-wwn="500507630f4a0452";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507630f4a0453";
name="sg" parent="fp" target=0 lun=1 fc-port-wwn="500507630f4a0453";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507630f4a0454";
name="sg" parent="fp" target=0 lun=1 fc-port-wwn="500507630f4a0454";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507630f4a0455";
name="sg" parent="fp" target=0 lun=1 fc-port-wwn="500507630f4a0455";
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507630f4a0456";
name="sg" parent="fp" target=0 lun=1 fc-port-wwn="500507630f4a0456";

mph999's picture

I forgot something, does the OS see the tape drives and robot correctly.

eg.

cfgadm -al -o show_FCP_dev

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
mph999's picture

So you first need to confirm if the operating system is seeing the devices correctly (robot and any drives it may have).  If not, you have an issue between the server and the devices, not a NBU issue.

The config files doen't look right to me, try this to recreate :

(But first you have to prove that the operating is seeing the devices correctly, don't just run this because I have provided it .... )

ksh
cd /usr/openv/volmgr/bin/driver
cp sg.conf sg.conf.old
cp sg.links sg.links.old
../sg.build all
modunload -i $(echo $(modinfo |grep "sg (SCSA" |awk '{print $1}'))
mv /kernel/drv/sg.conf /kernel/drv/sg.conf.old
/usr/openv/volmgr/bin/driver/sg.install
Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne's picture

See: http://www.symantec.com/docs/TECH130075

Solution

Rebooting the robotic tape library might return the tape library to functionality, but it will be a temporary solution at best.

This is not a Netbackup failure and there is nothing that can be done with Netbackup to cause or prevent it; it requires resolution from the hardware vendor of the robotic library, and possibly the SAN vendor or the server vendor.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

RohitNayal's picture

Hi Shekhar ,

Try to check in the Switch log on which this library is connected with the server .

Also share with us robot controller host /var/log/messages logs .

Regards,

Rohit

Marianne's picture

This post is more than 2 months old....

Hopefully the OP has managed to get issue resolved in the meantime!

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION