"Mode_sense error" & "initialization failed: unable to sense robo

[JenniferCheng]

I use Exabyte autoloader and Netbackup server on Solaris 9 sparc station. When booting system, got following error information:

/pci@le, 60000/LSILogic, scsi@4/st@1,0(st31)
VXA-2 options value invalid bits set: 0x4000

ermesx tl8cd[322]: TL8(1)Mode_sense error
ermesx tl8cd[322]: TL8(1) Key 5h, ASC 24h, ASCQ 0h, INVILID FIELD IN CDB
ermesx tl8cd[314]: TL8(1) unavailable: initialization failed: unable to sense robotic device.

Your advice will be appreciated.

Jennifer

 

[estech25]

Hi,
I had the same problem some time ago with an ADIC autoloader and what I did after a while of searching was I had to update the device mappings file which solved the problem. On Windows, this file is located in the following directory:
<installpath>/netbackup/shared
On solaris, you can probably find out where your device mappings file is located somewhere in the media manader documentation (try looking in the Media Manager Admin Guide which comes with NBU). You have to download the latest device mappings file which contains a reference to your specific autoloader on the Veritas Support website (try support.veritas.com and then choose your product and platform and search for it) and then you have to replace the old mappings file with the new one
Let me if it worked

 

[JenniferCheng]

Hi estech25, thanks.
I have changed a new scsi controller. When install scsi driver, I met another problem. I will let you know if it works after update device mappings file.
Jennifer

 

[JenniferCheng]

I found out there is some problem with device mapping file.
The device changer is "EXABYTE VXA 1x10 1U" but I can not find it in device_mapping file.
After updating device mapping file, robot can not be detected. Looks like I need find a suitable device mapping file.

 

[JenniferCheng]

I updated mapping file again. Everything looks fine.
Thanks very much.

Jennifer