mode_sense ioctl failed i o error

[sumanreddy]

Hi ,

I am getting an error "mode_sense ioctl failed i o error" when is run the command robtest.

the drive are disappeared and when is excute the commmand tpconfig -d ,it show the drives are up .

I have restarted the services drives are working for some time and then drives are dissappeared from the activity monitor.
The service avrd.exe is not running.

Can any one suggest how to reoslve this issue.

Regards,
Suman

[Will_Restore]

can you see the drives in Device Manager?

any pertinent messages in Event Viewer?

[MOHAMED_PATEL]

Check if the library is online - does not report an error -

Has the library and drives been detected in device manager - assumption that this windows..

Are you getting the error when you start robtest or when you're typing in 's d' / 's s'?
There could be a tape stuck in the mouth of the drive whereby prohibiting the robot arm from moving further.

[Kevin_Good]

<INSTALL_PATH>\Volmgr\bin\scan.exe

[Nicolai]

In the SCSI protocol a mode sense is a request for status. If this request isn't returned you get a "mode_sense ioctl failed".

If drives and robot is connect via a SAN I suggest you check the health of the SAN. Set drive to do "fabric login" (aka F login)  and not "public loop" (aka FL login). Create separate zones for each HBA & drive. All drives in one zone can lead to intermittent loss of connectivity.

Inspect event log on  Windows system or syslog / message on UNIX hosts for messages related to the issue.

[Marianne]

Suman, which version of NBU and O/S? I have never seen devices 'disappearing' from the NetBackup GUI.
Please check Event Viewer Application log as well as System log for problems with hardware and possibly services stopping.

[sumanreddy]

Thank s for the response.

when i enter the tpconfig command it is showing tape drives are down.

But netbackup is not able to detect the drives when is reconfigure the drives.

Please suggest.

Regadrs,
Suman

[Marianne]

Suman, NetBackup as an application has no means of accessing devices directly - it relies on the O/S for device access. Any troubleshooting should therefore start at O/S level.
You need to check the following:
Device Manager
Event Viewer System Log
Event Viewer Application log.

Have a look at this TechNote for advice regarding diappearing devices:

http://seer.entsupport.symantec.com/docs/270183.htm

[Kevin_Good · Accepted solution]

Step 1.
What is the method of connection from the Media Server to the Tape Drives (SAN, SCSI, iSCSI, other?)

Step 2.
Assuming SAN connectivity, have you verified that the HBA is still logged into the fabric?

Step 3.
Have you verified that the HBA is zoned to see the tape drives, and that the zone is active?

Step 4.
Have you verified that the Operating System (Windows) can see the tape devices, in Device Manager?

Step 5.
Are the tape drives in a robotic library?
Does the OS see the library (Medium Changer in the Device Manager)?

Step 6.
Can the Media Server communicate over the data path to the tape drives?
Assuming the default location of the NetBackup Install:
"C:\Program Files\VERITAS\Volmgr\bin\scan.exe"
How many tape drives are listed
Do they report the following details:
Device Name, Host, Port, Target, LUN, Serial Number, Inquiry String
Does the Library report in the scan output
Does it have Drive locations with Serial numbers?

Step 7.
Delete the existing drive mapping for the tape drives from tpconfig.

Step 8.
run tpautoconf -a
"C:\Program Files\VERITAS\Volmgr\bin\tpautoconf.exe -a"

Step 9.
stop and restart ltid
"C:\Program Files\VERITAS\Volmgr\bin\stopltid.exe"
"C:\Program Files\VERITAS\Volmgr\bin\ltid.exe"

Step 10.
run robtest
"C:\Program Files\VERITAS\Volmgr\bin\robtest.exe"
select your robot from the list
if the mode sense still does not work, call support.
if the mode sense works, try sensing the drives
s d
if you see your list of tape drives, quit robetest
q
q
you should be back at a command prompt

Step 11.
Check tpconfig -d and vmoprcmd -d

Step 12.
try a backup