Re: [Bacula-users] LTO-8 tape report error

2024-06-24 Thread Marco Gaiarin
Mandi! Radosław Korzeniewski In chel di` si favelave... > It is best to use persistent device names instead of above. You should ask Sure. > udev (with udevadm info --query=all --name /dev/sg0) about it. > This device path never changes. But at least for my tape library, the name is still

Re: [Bacula-users] LTO-8 tape report error

2024-06-21 Thread Radosław Korzeniewski
Hello, czw., 20 cze 2024 o 12:56 Adam Weremczuk napisał(a): > OMG... > > The only reason the script started failing was a different device > assignment caused by a reboot: > > ls -al /dev | grep sg. > crw-rw 1 root tape 21, 0 Jun 19 12:25 sg0 > crw-rw 1 root disk 21, 1 Jun

Re: [Bacula-users] LTO-8 tape report error

2024-06-20 Thread Bill Arlofski via Bacula-users
On 6/20/24 4:54 AM, Adam Weremczuk wrote: OMG... The only reason the script started failing was a different device assignment caused by a reboot: ls -al /dev | grep sg. crw-rw 1 root tape 21, 0 Jun 19 12:25 sg0 crw-rw 1 root disk 21, 1 Jun 12 17:42 sg1 Once I've changed

Re: [Bacula-users] LTO-8 tape report error

2024-06-20 Thread Marco Gaiarin
Mandi! Adam Weremczuk In chel di` si favelave... > Any idea what's going on? Consider that there are vendor utility to do quick and extensive tape unit check; for HP unit, for example, there's LTT:

Re: [Bacula-users] LTO-8 tape report error

2024-06-20 Thread Adam Weremczuk
On 17/06/2024 18:50, Bill Arlofski via Bacula-users wrote: Hello Adam, Not sure if this will be any help at all, but I just checked and see that in my `mtx-changer-python.py` drop-in replacement script, to check for tape cleaning required messages, I am using: 8<  sg_logs

Re: [Bacula-users] LTO-8 tape report error

2024-06-17 Thread Bill Arlofski via Bacula-users
On 6/17/24 11:38 AM, Adam Weremczuk wrote: Hi Gary, I know what you mean by "hijacking a thread" now. I was reading that message when I decided to post my question from the same window. Today I cleared the tape drive with an official cleaning cartridge but it made no difference to the error:

Re: [Bacula-users] LTO-8 tape report error

2024-06-17 Thread Adam Weremczuk
Hi Gary, I know what you mean by "hijacking a thread" now. I was reading that message when I decided to post my question from the same window. Today I cleared the tape drive with an official cleaning cartridge but it made no difference to the error:

Re: [Bacula-users] LTO-8 tape report error

2024-06-13 Thread Gary R. Schmidt
On 13/06/2024 22:43, Adam Weremczuk wrote: 1. Are you suggesting running a round with a cleaning cartridge? The drive is not asking for it (by showing "C"). I've seen HP drives throw these errors which go away after a clean. It may be an indicator that the drive is dying or the head has gone

Re: [Bacula-users] LTO-8 tape report error

2024-06-13 Thread Adam Weremczuk
1. Are you suggesting running a round with a cleaning cartridge? The drive is not asking for it (by showing "C"). 2. I don't get what you mean. This is a new thread. On 13/06/2024 13:07, Gary R. Schmidt wrote: Any idea what's going on? 1 - Clean your heads. 2 - Don't hijack threads, start

Re: [Bacula-users] LTO-8 tape report error

2024-06-13 Thread Gary R. Schmidt
On 13/06/2024 21:12, Adam Weremczuk wrote: This was working until yesterday when I rebooted the Bacula/LTO server and now gives: -  sg_raw -o - -r 1024 -t 60 -v /dev/sg1 8c 00 00 00 00 00 00 00  00 00 00 00 04 00 00 00

[Bacula-users] LTO-8 tape report error

2024-06-13 Thread Adam Weremczuk
This was working until yesterday when I rebooted the Bacula/LTO server and now gives: - sg_raw -o - -r 1024 -t 60 -v /dev/sg1 8c 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 cdb to send: [8c 00 00 00 00 00 00 00 00