Ok, this rewind error isn't going away.
I've tried changing the sleep timer to 180 in mtx-changer. No luck..
Connecting to Storage daemon ULTRIUM at backup2.harrow.gov.uk:9103 ...
Sending label command for Volume 000106L2 Slot 4 ...
3301 Issuing autochanger loaded drive 0 command.
3302
Beren Gamble wrote:
Ok, this rewind error isn't going away.
I've tried changing the sleep timer to 180 in mtx-changer. No luck..
Connecting to Storage daemon ULTRIUM at backup2.harrow.gov.uk:9103 ...
Sending label command for Volume 000106L2 Slot 4 ...
3301 Issuing autochanger loaded drive 0
On Friday 11 November 2005 13:35, Beren Gamble wrote:
Ok, this rewind error isn't going away.
I've tried changing the sleep timer to 180 in mtx-changer. No luck..
What version of Bacula are you running?
What OS version? Specifically the kernel.
There was a change in how the Linux kernel
Kern, Florian, Thanks for your help!
I've learnt a lesson.. I should've inspected the media. The end of the tape has
gone right inside itself, so it would probably just spin forever.
Thanks for your help guys. Never thought it would be a physical error.
Kern Sibbald [EMAIL PROTECTED]
Bacula is asking for a tape which is already in the library.
You have messages.
*m
10-Nov 10:52 backup2-sd: 3301 Issuing autochanger loaded drive 0 command.
10-Nov 10:52 backup2-sd: 3302 Autochanger loaded drive 0, result is Slot 4.
10-Nov 10:52 backup2-sd: HOSTDATA-Daily.2005-11-09_21.00.10
Most likely you do not have a long enough wait in your mtx-changer script,
and so Bacula is attempting to access the drive before the autochanger has
had enough time to load the tape.
This is described in the script and in the Autochanger chapter of the manual.
On Thursday 10 November 2005
Thanks Kern,
It's funny, it's never been a problem in the past. Our Scalar i2000 has been
rock solid with Bacula..
I'll try it anyway.
Cheers
Kern Sibbald [EMAIL PROTECTED] 10/11/2005 12:05:20
Most likely you do not have a long enough wait in your mtx-changer script,
and so Bacula is
On Thursday 10 November 2005 15:41, Beren Gamble wrote:
That didn't fix it...
Can I make it use a different tape somehow?
Yes, of course, simply use the update volume=xxx command and mark it Used or
Full.
I think you should run the btape test program, and if it doesn't ask you be
sure to
