On Thursday 03 February 2005 10:24, Wim Zwitser wrote:
>thank you for your advice to reinstall amanda using the tarball.
>The installation was simple.
>I use chg-zd-mtx as the recommanded changer with barcodereader,
>both in rpm-amanda and in tar-amanda, but still without success.
>
>But suddenly I ran into another problem. I could unload or eject
>a tape from the drive into the original slot before, but since
>yesterday I get:
>
># mtx -f /dev/sg1 unload
>Unloading Data Transfer Element 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 = 3B
>mtx: Request Sense: Additional Sense Qualifier = 83
>mtx: Request Sense: BPV=no
>mtx: Request Sense: Error in CDB=no
>mtx: Request Sense: SKSV=no
>MOVE MEDIUM from Element Address 451 to 1 Failed
>
>I did not touch mtx, etc.
>I have no idea where the strange value 451 comes from.
>
>Do you have a suggestion?
>
>Wim
The only thing that quickly comes to mind is that in configuring
chg-mtx, the wrong device was chosen for the drive or robot. I'm not
familiar with either of course. When unloading a tape, my assumption
is that the command to eject would have to go to the drive, and the
command to store the tape would have to go to the robotics. That
however, could be builtin if the drive talks to the robot, and many
do.
Sometimes devices can move around from reboot to reboot, but thats
only a problem when using hotplug, or if the kernel is a different
one I think.
In the case quoted above, I'm puzzled, and I probably should have kept
my big know-it-all mouth shut. You might also search for a hung mtx
using ps too. I've never seen that (a hung mtx)
happen myself however.
Also, if using a redhat built kernel, they do not compile in the
option to make scsi do a 'scan all luns' at bootup, so if the robot
is at the same bus address but a higher lun than the drive, it will
not be found. But I toss that out only as a point of reference since
most will, when building their own kernel, turn that option on as a
matter of good practice. The few seconds of pause in the bootup is
not a major consideration in any case I know of except amigados,
which waits a full second for each lun to respond, so a full scan
there is a 49 second pause on a scsi-2 narrow bus.
One thing that can occasionally be illuminating is the contents of
the /var/log/dmesg file, which will often contain the data as to
whats what as it logs the discovery of attached hardware.
>Gene Heskett wrote:
>>On Tuesday 01 February 2005 11:22, Nick Danger wrote:
>>>Humm... mine does too. Using chg-scsi and have the the barcode
>>
>>I think I'd try and switch to chg-mtx as you've already noted that
>> mtx itself seems to support it. I used chg-scsi for quite a
>> while, but it has some problems that have never been addressed,
>> such is a (apparently, I was not able to make it work) missing
>> rewind function.
>>
>>>havebarcode 1 # Set this to 1 if you have an library with
>>> an installed
>>> # barcode reader
>>>
>>>Its working anyway, just does have to look at each tape. Where
>>> does amanda store barcode information?
>>
>>I do not know. Reading the srcs might be enlightening. I'd assume
>> it might become part of the tapelist's data, but never having had
>> a reader, thats just a SWAG.
>>
>>Mmm, I see below that you installed from rpms. Thats been known to
>>result in config difficulties. Generally, we recommend building
>> the tarball. Its not that difficult, or time consuming once you
>> have arrived at a working configure script. I post mine here as a
>> guideline from time to time so the archives should have a copy. I
>> can unpack a fresh snapshot in /home/amanda, become amanda and
>> copy my script into the new snapshots directory, cd to it, run the
>> script, become root and do a make install, & ldconfig in 5-6
>> minutes of an XP-2800 Athlon box.
>>
>>>-Nick
>>>
>>>Wim Zwitser wrote:
>>>>Hi,
>>>>
>>>>I try to install an amanda server on a Linux Enterprise pc with
>>>>the standard redhat rpms's. The pc is connected to an Exabyte
>>>> 230D DLT jukebox with 1 drive and 31 slots.
>>>>
>>>>As far as I can see the basics are running fine, except one
>>>> thing: I can not read the barcodes on tapes in the jukebox with
>>>> one of the am*-tools.
>>>>
>>>>The only tool which gives the barcodes is mtx. After "mtx
>>>> inquiry" the "mtx status" command lists barcodes.
>>>>
>>>>But "amtape <conf> show" starts to load all tapes one by one in
>>>>order to read an amanda label.
>>>>I like to see it reading the barcodes!
>>>>
>>>>Does anyone have an idea?
>>>>
>>>>Thank you in advance,
>>>>Wim
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.32% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
|
