The test (weof) was same tape.
On Wed, Jun 26, 2019 at 8:50 AM Kern Sibbald wrote:
> 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
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 .
> The 2 drive is LTO5. The tape is LTO5.
Who manufactured the drives? HP or IBM? Can you find out the model
numbers?
Have you tried running the OEM diagnostics on them to see what
they say? The HP ones are particularly detailed and informative.
Cheers,
Adam.
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.
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
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.