In 1.38.x your mxt-changer script must return the correct number of slots, and
it looks like it is returning zero. If I remember right, the manual explains
how you can manually check this. Probably something like:
mtx-changer /dev/sg0 slots 0 dummy 0
It should print the correct number of sl
Sorry i made a stupid little mistake...
The user bacula has no right to execute the mtx-changer script!
The problem was, that doing an "update slots" or "mount" command there
was no
hint.
But now i run "umount" which says that it has no permission.
Sorry!
Timo Eissler schrieb:
Hello,
i ha
Hello,
i have just upgraded from 1.36.0 to 1.38.2.
And now i can“t do an "update slots" command for my autochanger, because
i will only get
*update
Using default Catalog name=MyCatalog DB=bacula
Update choice:
1: Volume parameters
2: Pool from resource
3: Slots from autochanger
Choose catalog