I think this got side tracked I know now why the status doesn't work on the tape drive but only on the autochanger. However I am trying to trouble shoot the tape drive because I cant get it working with bacula. I run the btape test which errors out and looks like;
17-Sep 11:25 btape JobId 0: Error: block.c:568 Write error at 0:0 on device "Ultrium 4-SCSI" (/dev/nst0). ERR=Input/output error. 17-Sep 11:25 btape JobId 0: Error: Error writing final EOF to tape. This Volume may not be readable. dev.c:1681 ioctl MTWEOF error on "Ultrium 4-SCSI" (/dev/nst0). ERR=Input/output error. btape: btape.c:827 Error writing block to device. When I run the status on the changer I show that in my case that the 1st slot is empty where a tape was placed and slot 2 the other slot I placed a tape is full and shows the tape barcode number. I can only assume the tape is in the drive. -----Original Message----- From: John Drescher [mailto:dresche...@gmail.com] Sent: Thursday, September 17, 2009 4:20 PM To: Watson, Joe; bacula-users Subject: Re: [Bacula-users] Creating a Volume on a tape times out On Thu, Sep 17, 2009 at 4:58 PM, Watson, Joe <isjoe...@oklahomacounty.org> wrote: > Product Type: Tape Drive > Vendor ID: 'HP ' > Product ID: 'Ultrium 4-SCSI ' > Revision: 'W24W' > Attached Changer API: No > SerialNumber: 'HU19215LV5' > MinBlock: 1 > MaxBlock: 16777215 > SCSI ID: 4 > SCSI LUN: 0 > Ready: yes > BufferedMode: yes > Medium Type: Not Loaded > Density Code: 0x46 > BlockSize: 0 > DataCompEnabled: yes > DataCompCapable: yes > DataDeCompEnabled: yes > CompType: 0x1 > DeCompType: 0x1 > BOP: yes > Block Position: 0 > Partition 0 Remaining Kbytes: 800226 > Partition 0 Size in Kbytes: 800226 > ActivePartition: 0 > EarlyWarningSize: 0 > NumPartitions: 0 > MaxPartitions: 0 > > -----Original Message----- > From: John Drescher [mailto:dresche...@gmail.com] > Sent: Thursday, September 17, 2009 3:56 PM > To: Watson, Joe > Cc: bacula-users@lists.sourceforge.net > Subject: Re: [Bacula-users] Creating a Volume on a tape times out > > On Thu, Sep 17, 2009 at 4:30 PM, Watson, Joe > <isjoe...@oklahomacounty.org> wrote: >> I am adding that I ran; >> sudo mtx -f /dev/sg0 status >> >> to get this; >> 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 = 20 >> mtx: Request Sense: Additional Sense Qualifier = 00 >> mtx: Request Sense: BPV=no >> mtx: Request Sense: Error in CDB=no >> mtx: Request Sense: SKSV=no >> READ ELEMENT STATUS Command Failed >> >> I did some googling and found that the additional sense code is "Occurs >> when the command operation code received by the device is not >> supported." >> >> >> >> >> -----Original Message----- >> From: Watson, Joe [mailto:isjoe...@oklahomacounty.org] >> Sent: Thursday, September 17, 2009 11:51 AM >> Cc: bacula-users@lists.sourceforge.net >> Subject: Re: [Bacula-users] Creating a Volume on a tape times out >> >> >> I put in brand new tapes is there something I am missing this is the >> result of testing the tape drive using btape >> >> Using btape to test the drive /dev/nst0 I get this error >> 17-Sep 11:25 btape JobId 0: Error: block.c:568 Write error at 0:0 on >> device "Ultrium 4-SCSI" (/dev/nst0). ERR=Input/output error. >> 17-Sep 11:25 btape JobId 0: Error: Error writing final EOF to tape. This >> Volume may not be readable. >> dev.c:1681 ioctl MTWEOF error on "Ultrium 4-SCSI" (/dev/nst0). >> ERR=Input/output error. >> btape: btape.c:827 Error writing block to device. >> >> >> -----Original Message----- >> From: Alex Chekholko [mailto:ch...@pcbi.upenn.edu] >> Sent: Thursday, September 17, 2009 10:50 AM >> To: Watson, Joe >> Cc: bacula-users@lists.sourceforge.net >> Subject: Re: [Bacula-users] Creating a Volume on a tape times out >> >> Hi Joe, >> >> Before dealing with bacula, make sure you understand how to use the >> commands 'mt', 'mtx', 'tapeinfo' and then make sure that they are >> working correctly. Then see how 'mtx-changer' uses 'mtx' to do its >> business. >> >> E.g. try: >> cat /proc/scsi/scsi (this will show you the devices, 0,1,2,..) >> tapeinfo -f /dev/sg2 (if there is a device 2) >> mt -f /dev/nst0 status >> mtx -f /dev/sg0 status >> >> After all that works as expected, run through the btape tests as per >> the manual: >> http://www.bacula.org/en/dev-manual/Testing_Your_Tape_Drive.html >> >> Regards, >> Alex >> >> On Wed, 16 Sep 2009 14:32:42 -0500 >> "Watson, Joe" <isjoe...@oklahomacounty.org> wrote: >> >>> 3995 Bad autochanger "unload slot 2, drive 0": ERR=Child exited with >>> code 1 >>> Results=Unloading drive 0 into Storage Element 2...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 = 53 >>> mtx: Request Sense: Additional Sense Qualifier = 03 >>> mtx: Request Sense: BPV=no >>> mtx: Req3301 Issuing autochanger "loaded? drive 0" command. >>> >>> I get this when I try mounting it after I changed the tape to >> /dev/nst0 >>> > > Please post the output of > > tapeinfo -f /dev/sg0 > The problem with the mtx status command you did is /dev/sg0 is the tape drive and not the changer. Find the correct device for the changer using tapeinfo. Run it one by one for /dev/sg0 ... Here is my output for my autochanger: dev6 ~ # tapeinfo -f /dev/sg5 Product Type: Medium Changer Vendor ID: 'EXABYTE ' Product ID: 'MAGNUM 224 ' Revision: 'C112' Attached Changer: No SerialNumber: '000089000435' SCSI ID: 3 SCSI LUN: 1 Ready: yes At minimum the Product Type should be the same for your autochanger John ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users