Hi,
Yes, dd, tar, etc works, mt and mtx also without problems, only when I
use commands from amanda I have the problems, one other thing I forgot
to write, I have an error, but after some hours I can do the command
again without problems, for example
$ amlabel CONF LABEL01 slot 1 (OK)
$ amlabel CONF LABEL02 slot 2 (ERROR)
Some hours later
$ amlabel CONF LABEL02 slot 2 (OK)
That's the reason I changed the times in the configuration of the
changer, thinking was amanda trying to do something before the
changer/tape ended the previous operation.
Cheers,
Nuno
On 20/04/2026 11:38, Exuvo wrote:
Does basic usage with mt and dd work with the device?
// Anton "exuvo" Olsson
[email protected] <mailto:[email protected]>
On Mon, 20 Apr 2026, 11:46 Nuno Dias, <[email protected]
<mailto:[email protected]>> wrote:
Hi,
I'm using amanda for years, with a Tape Robot and LTO4 and LTO6
drives
without problems (excluding minor issues).
Now, I have a new Tape Robot with LTO9 drives, and I can't do
anything
with amanda, using amlabel or amtape for example, in the first
interaction work, but in the second interaction complains that tape "is
not a tape device".
In the logs I have this
Device tape:/dev/tape/by-id/scsi-3500308c44344e008-nst setting status
flag(s): DEVICE_STATUS_DEVICE_ERROR, and DEVICE_STATUS_DEVICE_BUSY
But nothing is using the tape.
I already extended the "times" in the configuration of the changer
property "load-poll" "200s poll 200s until 700s"
property "eject-delay" "200s"
property "unload-delay" "200s"
But this doesn't solve the problem.
I found a report in github https://github.com/zmanda/amanda/
issues/277 <https://github.com/zmanda/amanda/issues/277>
reporting the same problem, without any update from one year ago :(
Anyone have any ideia how to solve this? Amanda development it seems
stopped, but works very good until now, this is my last hope until I
move to other software :(
Thanks,
Nuno
--
Nuno Dias <[email protected] <mailto:[email protected]>>
LIP
--
Nuno Dias <[email protected]>
LIP