Mixing LTO1 and LTO3 in the same library is possible within the restrictions that have just been posted this week on another thread.
I don't see where you specified the ELEMENT= for the define drive. An interesting command: SHOW SLOTS <libraryname> gives the scsi element numbers for all the drives (and lots more information) in that library. As long as you've done the def libr and def path to the library. I know the default is ELEMENT=AUTODETECT, and call me a control freak, but I always specify the element numbers. Bill Boyer "Some days you're the bug, some days you're the windshield" - ?? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of goc Sent: Friday, September 09, 2005 7:33 AM To: [email protected] Subject: LTO1 , LTO3 tapes - drives , mixing story hi all, okay after i noticed that mixing of lto1 and lto3 drives/tapes is not possible in one 3584 library except to partition the library i did the logical partitioning 12 old lto1 drives are okay and fully occupied as usual :-) , i retested them and double checked the hom element, rmtX, serial numbers and WWN-s just to be sure that this is the real situation, it's little complicated coz i connected odd and even drives to different brocades but nevermind that ... you know DRIVE2 is /dev/rmt9 LOL ... okay back to the point the library was successfuly partitioned and on specailalist there is nothing odd, but when i want to create a drive in newly created logical library it wouldnt let me, the drives are phisicaly in other frame which is second logical library ... ANR2017I Administrator GORAN issued command: DEFINE DRIVE LTO_LIB01G3F2 drive01g3f2 WWN=500507630046D811 SERIAL=0007803769 CLEANFREQUENCY=ASNEEDED ANR8404I Drive DRIVE01G3F2 defined in library LTO_LIB01G3F2. ANR2017I Administrator GORAN issued command: DEFINE PATH TSM01 drive01g3f2 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=LTO_LIB01G3F2 DEVICE=/dev/rmt7 ANR8972E DEFINE PATH: Unable to find the element number for drive DRIVE01G3F2 in library LTO_LIB01G3F2. the home elemet is fine visible in specialist, and i know the exact device special file everything seems to be normal but still ... any clues ? thanks for every answer goran
