Forum Discussion

Sreejith_nair's avatar
18 years ago

unable to mount the catridge to tape library- Error 26C9

Hi ,

Plz help me out, while taking daily backup (veritas 5.1 netbackup) when the drive tries to mount a free catridge, it was not successful. I got this error on the screen of Quantum ATL M1500 tape library "Error 26C9". When I check the Device monitor it show up that the drive is down and catridge mount is still pending. When I selected the drive up and resubmit the pending jon ( mounting catridge to library) It again gives the same error and same info on Device monitor.


Please I tried manually mounting the tape using the menu from Tape library but thats also not successfull. Plzzz guide me.
  • If you have already tried mounting it manually and you were unsuccessful, there is noting much you can do (assiuming you have connectivity to drive and there were no changes made in terms of connections between host and drive). I suggest you call your tape library/drive support vendor and have them take a look at drive.
  • Sreejith,
    I'd recommend downing all services in Netbackup. Then, from a command line, invoke the robtest command. It's located here: install_path\veritas\volmgr\bin
    so in command line type robtest and then type 's d' without the parenthesis. I'm curious if robtest will show you all of your drives. Also, when is the last time you cleaned your tape drive? I'd recommend that, too. How long has yoru drive been exhibiting this behavior?
  • Thanks a lot to all, This problem also happend on last month too, then when I did a drive clean and did a restart the next day everything came fine( not on the same day) , Same thing instead of a drive clean I retarted the library yesterday and suddenly it starts accepting the catridge. I know this is not a permanent solution to the problem. Is it the problem with tape library ?. Please comment on it
  • I know that some drives will push out a media error when they need a cleaning. When this happens the drive will appear in a 'downed' state. Then you have to run a cleaning of the drive. You shouldn't have to restart; but I suppose it is different on each hardware config...
    If you clean the drive and dont' restart does your hardware still show that the drive is producing an error?