from taper: TAPE-ERROR [not an amanda tape]
from the amdump log files:
driver: result time 326.960 from taper: TAPE-ERROR [writing label:
Input/output error]
from the log. files of the amdump run:
ERROR taper no-tape [writing label: Input/output error]
from the log. files of the amflush run
in the subject line and
repeated here for both the amdump and amflush commands.
from the amflush log files:
driver: result time 0.022 from taper: TAPE-ERROR [not an amanda tape]
from the amdump log files:
driver: result time 326.960 from taper: TAPE-ERROR [writing label:
Input/output
James D. Freels wrote:
Whoa ! Now I am going back to relabel my tapes. I have issued the
amlabel command and receive a
rewinding, reading label, not an amanda tape
rewinding, writing label fea01
amlabel: writing label: Input/output error
Do you have the NON-rewinding device in amanda.conf ?
, I receive the error message shown in the subject line and
repeated here for both the amdump and amflush commands.
from the amflush log files:
driver: result time 0.022 from taper: TAPE-ERROR [not an amanda tape]
from the amdump log files:
driver: result time 326.960 from taper
I am writing to the non-rewinding device as always, /dev/nts0.
If I changed the blocksize, how would I have done so ? If I have the
incorrect tapetype, will this do it ? How can I correct the blocksizes,
etc. ?
On Fri, 2004-04-30 at 10:56, Paul Bijnens wrote:
James D. Freels wrote:
Whoa !
James D. Freels wrote:
OK. Stranger by the minute. I removed the first tape (01) and set it
up to use the second tape(02). I issued a amcheck fea and it said my
second tape was OK and that I should be able to backup. I then issued
an amflush and it came back with an error. I then rewind the
Now I had to use another tape in the sequence.
the 2st mt -f /dev/st0 before amcheck or amflush:
drive type = Generic SCSI-2 tape
drive status = 637534720
sense key error = 0
residue count = 0
file number = 0
block number = 0
Tape block size 512 bytes. Density code 0x26 (unknown).
Soft error
James D. Freels wrote:
Now I had to use another tape in the sequence.
the 2st mt -f /dev/st0 before amcheck or amflush:
drive type = Generic SCSI-2 tape
drive status = 637534720
sense key error = 0
residue count = 0
file number = 0
block number = 0
Tape block size 512 bytes. Density code 0x26
On Fri, Apr 30, 2004 at 11:15:49AM -0400, James D. Freels wrote:
Now I had to use another tape in the sequence.
the 2st mt -f /dev/st0 before amcheck or amflush:
You were asked if you are using the NON-rewind tape device
but never responded.
I think this is the rewind on close device.
You
Hello, and thank you for your email.
I shall be out of the office until Tuesday 4th May. Should your email
require urgent attention, the please contact David Adams or email
[EMAIL PROTECTED]
Regards,
William Hargrove
OK. I changed the blocksize to fixed at 32768 and sure enough, I was
able to flush. I will now go back and make things more generic as you
suggest to a blocksize of 0 for variable.
I also looked at all the info you referenced on this problem before and
using the stinit.def file to define the
commands all indicate everything is working OK.
An amdump works by sending all backup files to the holding disk.
However, I receive the error message shown in the subject line and
repeated here for both the amdump and amflush commands.
from the amflush log files:
driver: result time 0.022 from
.
An amdump works by sending all backup files to the holding disk.
However, I receive the error message shown in the subject line
and repeated here for both the amdump and amflush commands.
from the amflush log files:
driver: result time 0.022 from taper: TAPE-ERROR [not an amanda
tape
13 matches
Mail list logo
