markl
Level 2
Joined 18 years ago
User Profile
User Widgets
Contributions
Re: LTO-3 in Mag 448 Library
Yes; I have done both of these things previous to my post; I did not attempt to reinstall the driver pack - but I had a different problem a while back that forced me to install that one. The "unknown" media changer option in windows management shows to be a M$ Driver dated 10-1-02 it looks to be the same driver type that was used with the instancein theMammoth2 EZ-17 Changer. This one does show to be using the Mag 448 instance in the advanced map point view. The bar-code rules did not exist for the LTO-3 tapes. I created a rule myself not knowing if there is a standard. If the drives didn't keep going off line, I'd say it was still a bar code rule error. I'm told that the labels being displayed, although they are recorded with L3 appending in the bar code scan, the drive has to write the label on the media before the library knows what type it is. The first one that I did, thought it was a cleaning media - most are showing up as unknown. I can right click the tape devices and assign the media type, it is available in the list of r/w media. Both tape drives are also enabled with BC Rules. We are having heavy T-Storms here. I think I'm headed out for the night. Thanks for the doc links, I will try to do some more work on this tomorrow. M307Views0likes0CommentsLTO-3 in Mag 448 Library
New install; looks like I may be having issues with bar code rules? Anyone have suggestions as to fix incompatible media messages - short of going to every tape in the library and labeling it as LTO-3 Type? My drives keep going off line due to the errors - maybe i do not have the correct library drivers in BE 11.d I still have exabyte-EZ- library installed and working - Thx307Views0likes3CommentsRe: BE 11d help with robotics library - after tape malfunction
Thanks for your suggestions; the problem was resolved but it went a little deeper that this. Your suggestions were right on the money, and worth every penny I might add. ;-) After powering down theserver and both attached libraries,re-seating all cables (both ends) and applying the latest driver library driver update, Idid haveto delete the robotic library definitions and after rebooting the server the Library devices were once again recognized and without the phantom tape identified in the drive. The devices were then re-labeled as they we re-numbered sequentially; First Library 1, First Tape Drive 2, Second Library 3, Second Tape Drive 4, and then re-associatedthe devicesto thejob profiles per media set and life is good again in the land of archival. The two libraries were identical, but one was set for emulation mode and the other was not. This caused two drivers to be loaded and one was a little older than the second. I guess when the tape failed, the drive did not know how to recover. Thanks for your assistance. I wish everyone had as good a result as I have had with Ver 11. Keep up the good work.201Views0likes0CommentsBE 11d help with robotics library - after tape malfunction
I'm upto date with live update patches and my 2 library M2 drives are recognized however after a tape failure during an operation the server thinks the server software reports the tape is still in the drive. The tapeis not occupied in the drive, but I manually had to remove the tape as it would not eject. When I go through the drive status on the LCD it tells me that the cart status is empty. Any ideas?200Views0likes3Comments