Hi Richard, Have you tried updating inventory on the changer *via the firmware command*? I have seen this type of discrepancies appearing every time I power cycle my changer and it loses its inventory list stored on the device.
Best, Ivan On Friday, January 11, 2019 2:58:46 PM EST Richard Couture wrote: > How odd > > [root@LTOMag ~]# mt -f /dev/st0 offline > [root@LTOMag ~]# mtx -f /dev/sg3 unload 1 0 > Data Transfer Element 0 is Empty > > Now says the tape drive is empty > > HOWEVER > > [root@LTOMag ~]# mtx -f /dev/sg3 status > Storage Changer /dev/sg3:1 Drives, 30 Slots ( 5 Import/Export ) > Data Transfer Element 0:Empty > Storage Element 1:Empty:VolumeTag= > Storage Element 2:Full :VolumeTag=000002L7 > Storage Element 3:Full :VolumeTag=000003L7 > Storage Element 4:Full :VolumeTag=000004L7 > Storage Element 5:Full :VolumeTag=000005L7 > Storage Element 6:Full :VolumeTag=000006L7 > Storage Element 7:Full :VolumeTag=000007L7 > Storage Element 8:Full :VolumeTag=000008L7 > Storage Element 9:Full :VolumeTag=000009L7 > Storage Element 10:Full :VolumeTag=000010L7 > Storage Element 11:Full :VolumeTag=000011L7 > Storage Element 12:Full :VolumeTag=000012L7 > Storage Element 13:Full :VolumeTag=000013L7 > Storage Element 14:Full :VolumeTag=000014L7 > Storage Element 15:Full :VolumeTag=000015L7 > Storage Element 16:Full :VolumeTag=000016L7 > Storage Element 17:Full :VolumeTag=000017L7 > Storage Element 18:Full :VolumeTag=000018L7 > Storage Element 19:Full :VolumeTag=000019L7 > Storage Element 20:Full :VolumeTag=000020L7 > Storage Element 21:Full :VolumeTag=000021L7 > Storage Element 22:Full :VolumeTag=000022L7 > Storage Element 23:Full :VolumeTag=000023L7 > Storage Element 24:Full :VolumeTag=000024L7 > Storage Element 25:Full :VolumeTag=000025L7 > Storage Element 26 IMPORT/EXPORT:Full :VolumeTag=CLN005CU > > Storage Element 27 IMPORT/EXPORT:Full :VolumeTag=CLN004CU > > Storage Element 28 IMPORT/EXPORT:Full :VolumeTag=CLN003CU > > Storage Element 29 IMPORT/EXPORT:Full :VolumeTag=CLN002CU > > Storage Element 30 IMPORT/EXPORT:Empty:VolumeTag= > > > syas that the tape was not returned to slot 1 > > and just for fun > > [root@LTOMag ~]# mtx -f /dev/sg3 unload > Data Transfer Element 0 is Empty > [root@LTOMag ~]# mtx -f /dev/sg3 next > Loading media from Storage Element 2 into drive 0...mtx: Request Sense: > Long Report=yes > mtx: Request Sense: Valid Residual=no > mtx: Request Sense: Error Code=70 (Current) > mtx: Request Sense: Sense Key=Illegal Request > mtx: Request Sense: FileMark=no > mtx: Request Sense: EOM=no > mtx: Request Sense: ILI=no > mtx: Request Sense: Additional Sense Code = 21 > mtx: Request Sense: Additional Sense Qualifier = 01 > mtx: Request Sense: Field in Error = 07 > mtx: Request Sense: BPV=yes > mtx: Request Sense: Error in CDB=yes > mtx: Request Sense: SKSV=yes > mtx: Request Sense: Field Pointer = 00 02 > MOVE MEDIUM from Element Address 4097 to 256 Failed > > And physically checking; No tape in Slot 1, it remains in the drive > > > > Richard > > On 1/11/19 1:01 PM, Jeffrey R. Lang wrote: > > I have run into tape libraries that require the tape to be unloaded from > > the drive before performing an unload command. > > > > The mtx-changer script supports this feature. You need to change the > > .../etc/mtx-changer.conf file, specifically the line > > > > # Set to 1 if you want to do offline before unload > > offline=0 > > > > In the example from below > > > > mtx -f /dev/sg3 load 1 0 > > mtx -f /dev/sg3 unload 1 0 > > > > add a command to unload the tape from the drive between the two lines > > > > mt -f <tape device> offline > > > > -----Original Message----- > > From: Sebastian Suchanek <bac...@suchanek.de> > > Sent: Friday, January 11, 2019 12:53 PM > > To: bacula-users@lists.sourceforge.net > > Subject: Re: [Bacula-users] mtx and mtx-changer not functioning > > > > ◆ This message was sent from a non-UWYO address. Please exercise caution > > when clicking links or opening attachments from external sources.> > > Am 11.01.2019 um 14:49 schrieb Richard Couture: > >>> Does mtx work when you explicitly specify the slots? I.e.: > >>> > >>> mtx -f /dev/sg3 load 1 0 > >>> mtx -f /dev/sg3 unload 1 0 > >> > >> No > > > > Then, in my opinion, the problem is somewhere outside of Bacula. > > My best guess is that either your library and your version of mtx are > > incompatible or your library is broken (e.g. faulty firmware). > > > > > > Best regards > > > > Sebastian -- Ivan Adzhubey, Ph.D. Instructor Division of Genetics, Dept of Medicine Brigham & Women's Hospital Harvard Medical School New Research Building, Room 0464C 77 Avenue Louis Pasteur Boston, MA 02115 tel.: (617) 525-4728 fax: (617) 525-4705 web: http://genetics.bwh.harvard.edu/wiki/sunyaevlab/ The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail. _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
