Anr8779e Unable To Open Drive Error Number
Contents |
tsm reserved 170 ANR8311E anr8355e RC 16 during read or anr8779e unable to open drive error 2 write Technote (troubleshooting) Problem(Abstract) A tape is mounted in a
Unable To Open Drive Error Number 2
drive by a Library Manager. A library Client writes to the tape and closes the anr8779e error number 5 linux tape. Later on, the ANR8779E error is received during dismount by the Library Manager and on retry, the dismount succeeds. Symptom In addition to receiving
Anr8779e Error Number 46
ANR8779E errors, the overall performance of the tape drive is affected. Cause Third-party software that scans hardware and interferes with the tape device driver. Environment Tivoli Storage Manager servers and storage agents running on Windows using Library Sharing. Diagnosing the problem A trace of the Tivoli Storage Manager server shows that anr8779e error number=79 access to the tape drive was denied. For example:
Reason: Access is denied.
path
An IBM device-driver trace captured at the same time shows that an OPEN call to the tape drive was performed by some program other than Tivoli Storage Manager. The device-driver trace might also show TEST UNIT READY and PERSISTENT RESERVE calls. For example:
Resolving the problem In this case, the following third-party software programs were interfering with the tape device driver: HP Insight Management WBEM Providers for Windows Server 2003/2008 Altiris Hardware Discovery service Altiris Agent (AeXNSAgent.exe) HP Insight Management WBEM Providers for Windows Server
IS NO DRIVE POLLING AND THE DRIVE DOES NOT GO OFFLINE AIX Fixes are available IBM Tivoli Storage
Anr8779e Error Number=16
Manager V6.1 Fix Pack 2 (6.1.2) Server Downloads IBM Tivoli Storage
Anr8779e Unable To Open Drive Error Number 46
Manager V6.1 Fix Pack 3 (6.1.3) Server Downloads Subscribe You can track all active APARs for this component. anr8779e error number=13 APAR status Closed as program error. Error description Actlog shows following error when a port on SAN switch is disabled. ANR8779E Unable to open drive /dev/rmtx, error number=xx. http://www.ibm.com/support/docview.wss?uid=swg21438554 There is no drive polling and drive does not go offline automatically when ANR8779E occurs. Tracing MMS PVR may show trace points similar to the following: 19:31:13.503 [192][mmsdrive.c][8007][MmsCheckTapeId]:Drive DRV3310_2 failed to open with existing path /dev/rmt1, error 60 19:31:13.503 [192][mmsdrive.c][12505][DiscoverNewPath]:Attemtping to discover a new path for drive DRV3310_2 (/dev/rmt1) with serial number of 1310071955. 19:31:13.503 [192][napath.c][1823][naResetInUse]:Reset path in http://www.ibm.com/support/docview.wss?uid=swg1IC60173 use for sourceName=SERVER1, destination=DRV3310_2, source type=2, destination type=1 19:31:13.503 [192][psdiscvr.c][249][psSanDiscovery]:SANDISCOVERY is set to OFF. 19:31:13.503 [192][mmsdrive.c][12514][DiscoverNewPath]:SAN discovery is either not supported or disabled. 19:31:13.504 [192][output.c][6377][PutConsoleMsg]:ANR8779E Unable to open drive /dev/rmt1, error number=5.~ IC58770 addresses the issue of errno 50 ENOCONNECT is not recognized by TSM as Hardware error and it is planned to be fixed in 5.5.2.1, 5.5.3 and 5.4.5. IC57753 address the other issue - ANR8779E WITH ERROR NUMBER=16 WHEN SAN DISCOVERY FAILS OR IS DISABLED. By the fix for APAR IC57753, the error is returned right away instead of doing drive polling and marking path offline if the SAN Discovery is OFF by option. So after installing the fix for IC57753 there is no drive polling and drive would not go offline. TSM Versions Affected: TSM 5.5.2.x on AIX Initial Impact: Medium Additional Keywords: zz61 SANDISCOVERY ANR8848W ANR8471E IC58770 PVR_TERMINATE_HW Local fix Set the drive path off line manually by update path command. Problem summary **************************************************************** * USERS AFFECTED: All TSM Server Users. * **************************************************************** * PROBLEM DESCRIPTION: See er
you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ https://adsm.org/forum/index.php?threads/anr8779e-with-error-number-5.19698/ BEFORE POSTING) Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts. Please Give Thanks to Those Sharing Their Knowledge Forum Rules (PLEASE READ BEFORE POSTING) ANR8779E with Error number=5 Discussion in 'TSM Installation, Upgrade and Configuration' started by rznadmin, Nov error number 27, 2009. rznadmin ADSM.ORG Member Joined: Feb 20, 2004 Messages: 67 Likes Received: 2 Hi, I'm facing problems probably concerning IBM device driver. After each reboot of our new installed TSM Server, a request to mount a tape is answered with ANR8779E unable to open drive \\.\tape0, error number=5 (or \\.\tape10, tape31 ...) Win2003 SP2 (new installation) TSM Server 5.5.2 Devdrvr: 6.2.0.4 Library: ACSLS VTL CentricStor VTA2000 32 Drives (configured as anr8779e error number LTO2) connected via Qlogic HBA QLE2462 (Version 9.1.4.15) LibAttach 1.4.2 What have I done so far: - installed Win2k3 SP2 - installed IBm DevDrvr ("install_exclusive.exe" - 6.2.0.4) - installed TSM 5.5.2 (without TSMdevdrvr) - define library .... : o.k. - define drive ... acsdrvid=1,1,1,0 : o.k. - define path ... device=\\.\tape0 ... : ANR8779E Errno=5 - running thru the "Update Driver" -wizzard for all drives (.. don't search ...) and installing "IBM Ultrium II tape Drive"-Driver : ALL pathes can be defined and all drives can be used without any problems - Rebooting the Server: each mount request leads again to ANR8779E err no=5 - Updating the drives thru the wizzard: everything's fine again ... until ... Well - any hints where to look? Thx sd rznadmin, Nov 27, 2009 #1 ADSM.ORG Sponsor Samuel ADSM.ORG Member Joined: Jul 9, 2008 Messages: 286 Likes Received: 1 yesterday, i have a similary problem, after multi test nok (cfgmgr, etc..). For resolved it, I does stop tsm on the server, stop electric the tapelibrary, restart the tape library, after few minutes, restart tsm on the server. I checked with smiity because my OS is AIX 5.3. Samuel, Nov 27, 2009 #2 johansen ADSM.ORG Member Joined: Dec 13, 2007 Messages: 123 L