Re: Bacula or Drive problem?
"Dr. Thorsten Brandau via Bacula-users" <[email protected]>
| Newsgroups | gmane.comp.bacula.user |
|---|---|
| Message-ID | <[email protected]> |
Bill Arlofski via Bacula-users schrieb am 13.06.25 um 19:48: > On 6/12/25 10:32 AM, Dr. Thorsten Brandau via Bacula-users wrote: >> >> Hi Bill >> >> thank you for your as always helpful insights. > > You are more than welcome, Thorsten. :) > > >> I was not aware of the conflict between the libraries and baculas >> autoclean feature. Immediately I turned the one of the lib off. >> >> I test drove some time ago the alternate MTX script. It worked well >> for some time but I ran in some kind of problem I do not remember. >> Last but not least, the original script worked well after an update. >> I believe it something to do with python on my system, which pretty >> effectively was kind of broken (Suse Tumbleweed). > Funny, because the original `mtx-changer` combination bash & perl > script has not been touched by developers in many years. Not sure what > update you are thinking of. :) > > >> What is the advantage of the alternate tapealert? From first >> impression of your github I do not see any... > > On https://github.com/waa/bacula-tapealert see the two secti > ons "THE PROBLEM", and "THE SOLUTION": > > - Much better logging > - Automatic /dev/sg node detection (this is one of the most important > I think) > - Email an admin when TapeAlerts are reported > > >> (and running it manually tries to log into an non-existing >> directory, might be abetter idea to log in standard to /var/log >> instead). > > Good point. It was written on a system running Bacula Enterprise, and > of course, /opt/bacula/log is the default location for logs. But, > logging is disabled by default, and of course this is simply fixed by > using the `-f` option to specify the exact path and filename you would > like to log to. ;) > > >> The mtx command gave the following reply: >> 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: Field in Error = 00 >> mtx: Request Sense: BPV=no >> mtx: Request Sense: Error in CDB=yes >> mtx: Request Sense: SKSV=yes >> mtx: Request Sense: Field Pointer = 00 00 >> READ ELEMENT STATUS Command Failed >> >> >> So, what does this mean? > Your tape library is either broken, is not compatible with mtx (lol, > not likely), or you are pointing to the wrong device node (also not > likely). > > Your library will never work with Bacula until and unless you are able > to get mtx status outputs from the command line, and can load/unload > tapes using mtx too. > > > Best regards, > Bill okay, let's solve the hardware issue first. I am a bit pissed because I just had to spend several thousands of EUR for a new tape, when the Tandberg one broke and the extenden warranty was nilled. And it is broken again... I don't think I have the wrong device, as I a) only have one tape/lib attached and b) all the other sg* deviced turn out more error messages ;-) Thanks. I will give probably your scripts another go after solving this. Cheers T _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users