Perhaps the write tab on the cassette
is in the read-only position.
On 6/26/19 2:11 AM, Jose Alberto wrote:
Hi.
The 2 drive is LTO5. The tape is LTO5.
S/O Debian 9 .
mtx -f /dev/nst0 weof (OK on Drive 1).
unload, and load drive1
mtx -f /dev/nst1 weof (Result= read-only).
Same tape
btape and tapeinfo show same configuration.
.... And view "interesting" config on WEB Tape. is:
Drive0 is Bridge. and Drive1 is not Bridge.
from the rest I see no difference between the drives.
unless at the hardware level it is already defective.
Hello,
You
did not mention whether or not you are using Bacula. For
Bacula there is no license blockage. Often writing of
older LTO formats (e.g. writing LTO-3 on an LTO-5) drive
is not supported by the drive manufacturer. In your case,
I suspect that the problem is in your OS where the drive
device filename is not defined to have write permission.
chmod
+w <drive> might solve the problem.a
Best
regards,
Kern
On
6/20/19 8:02 PM, Jose Alberto wrote:
Hi. I have an Oracle SL150 library of 2
Drive LTO5 and 96 Slot.
One of the 2 Slots does not write. weof show me result:
read-only
The other drive if you write without problems.
It is possible that at a physical level there is some
blockage by license to be able to use the 2 drives
completely.
Regars.
--
#############################
# Sistema Operativo: Debian #
# Caracas, Venezuela #
#############################
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
#############################
# Sistema Operativo: Debian #
# Caracas, Venezuela #
#############################
|
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users