Wait a sec - look at this again:

# mtx -f /dev/sg4 status
   Storage Changer /dev/sg4:1 Drives, 8 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 4 Loaded):VolumeTag =
CMR921L6
       Storage Element 1:Full :VolumeTag=CMR904L6
       Storage Element 2:Full :VolumeTag=CMR933L6
       Storage Element 3:Full :VolumeTag=CMR902L6
       Storage Element 4:Empty
       Storage Element 5:Full :VolumeTag=ARC954L6
       Storage Element 6:Full :VolumeTag=ARC946L6
       Storage Element 7:Full :VolumeTag=ARC943L6
       Storage Element 8:Full :VolumeTag=ARC939L6

It says data transfer element full with the tape from slot 4. Is that still
the current status? Maybe there is a tape stuck in the robot's tape changer!

I suggest doing
mtx -f /dev/sg4 status
See what it says now. Maybe it was in the middle of moving the tape, but if
it still says that, then the tape might be stuck.

Also,
<Snip>
mtx: Request Sense: Error Code=70 (Current)
mtx: Request Sense: Sense Key=Illegal Request
...
mtx: Request Sense: Additional Sense Code = 53
mtx: Request Sense: Additional Sense Qualifier = 03
</Snip>

Chatgpt 4 says that this error code with qualifying sense codes means the
tape library believes it's physically impossible to remove the media.
Usually caused by mechanical issues, misalignment, jammed media, or
physically damaged tape or drive. Maybe a sticker came off the tape and
it's jammed?

Chatgpt 4:
"MTX Load/Unload Failure: The mtx command failure with the sense key
"Illegal Request" and the additional sense code of 53 03 indicates a "Media
load or eject failed". This usually happens because the tape drive believes
it is physically impossible to load or unload the tape, potentially due to
mechanical issues, a misalignment, or a physically damaged tape or drive."

I am unable to find a cross reference to validate chatgpt's claim about the
meaning of the error code. On my phone right now, so limited access to
systems I administer.



Robert Gerber
402-237-8692
r...@craeon.net

On Tue, May 7, 2024, 10:57 AM Rob Gerber <r...@craeon.net> wrote:

> Checking simple stuff:
>
> What output for 'lsscsi'?
>
> What output for 'ps aux| grep -i bacula'?
>
> Try removing tape, physically sliding tape protection slider all the way
> closed (write protected), then all the way open (not write protected). I
> think should maybe be a click each direction?
>
> Take different known blank tape with definitely no useful information on
> it, try same mt commands.
>
> Remember that after rewind / writing eof you must relabel the tape. Since
> existing tape has same name in bacula catalog (assuming you name with
> barcodes), will need to delete old volume with same name to allow
> relabeling as that name. BE CERTAIN YOU DELETE CORRECT VOLUME.
> Alternatively, can rename as oldname-1. I think it is better to delete old
> volume since rewind / writing eof definitely makes recovery of data on that
> tape impossible without specialized firmware on tape drive.
>
> Good idea to remove all tapes with important information from the tape
> changer prior to doing any destructive operations like mt rewind/ write eof.
>
> Remember, after manually moving tapes around in changer, should update
> bacula's knowledge of the tape changer inventory by doing update slots. Be
> sure to update slots 1-24 or how ever many you have (0 does not mean "all
> slots").
>
> I have typically done Volume deletes, labeling, update slots, etc, in
> Bacularis / baculum.
>
> Robert Gerber
> 402-237-8692
> r...@craeon.net
>
> On Tue, May 7, 2024, 10:42 AM Stefan G. Weichinger <li...@xunil.at> wrote:
>
>> Am 07.05.24 um 17:04 schrieb Stefan G. Weichinger:
>>
>> > Could it be related to something like blocksizes?
>> >
>> > These tapes were used with Amanda before.
>> >
>> > trying another tape now
>>
>> I really get lost here. Wanted to re-label a tape to start over:
>>
>> # systemctl stop  bacula-sd
>> # mt -f /dev/st0 rewind
>> # mt -f /dev/st0 weof
>> /dev/st0: Input/output error
>> mt: The tape is write-protected.
>>
>> The physical "slider" is set to non-protected.
>>
>>
>>
>> _______________________________________________
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to