>
> One very important question: Have you run the btape tests, and did they
> report anything you didn't understand or even errors?
>
no i hadnt run the tests.

> >
> > i even tried putting the "real" device name in the config file "st0"
> > and that doesnt work either.
>
> I don't understand that sentence...
meaning in the configs it had /dev/nst0 and my drive is /dev/st0, even
though they both worked for some reason, i have it set to /dev/st0
now.

>
> > also when i try to label the tape i get:
> >
> > Enter new Volume name: BackupSet1
> > Automatically selected Pool: Default
> > Connecting to Storage daemon DDS-3 at mail:9103 ...
> > Sending relabel command from "BackupSet01" to "BackupSet1" ...
>
> Hmm. This looks like you issued a 'relabel' command, not 'label'.
well it wouldnt let me re-issue the command, so i did the relabel
command just to get the printed error again, it was the same on both
commands.

>
> > block.c:782 Read error at file:blk 0:0 on device /dev/nst0.
> > ERR=Input/output error.
>
> This looks like your SD can't use the tape drive. Start (again) with
> btape and tell us what the tests report.
>
> > 3000 OK label. Volume=BackupSet1 Device=/dev/nst0
> > Catalog record for Volume "BackupSet1", Slot 0  successfully created.
> > Old volume "BackupSet01" deleted from catalog.
> > Requesting to mount DDS-3 ...
> > 3001 OK mount. Device=/dev/nst0
> >
> > this has happened on two brand new tapes. it has an error, but then
> > goes along to actually complete the label, is this ok? is it just that
> > the tape doesnt spin up fast enough or something?
>
> No, there's no such thing as far as I know. Usually, when a labeled tape
> is mounted, you should see the volume name in the message. What did work
> in your output above is the catalog action, but that alone is not enough.
ok

>
> > ive googled about this and came up with a couple things related to
> > labeling the tape but none of them seemed to work.  do any of you have
> > any other suggestions on how to track down this problem?
>
> Yes, btape testing...
i have errors on the testing....where do i go from here?

This is an *essential* feature ...

10-Mar 14:54 btape: btape Error: block.c:552 Write error at 0:791 on
device /dev/st0. ERR=Input/output error.
10-Mar 14:54 btape: btape Error: Backspace file at EOT failed.
ERR=Input/output error
btape: btape.c:782 Error writing block to device.

after reading the documentation a little closer, i did do the following:

become super user
mt -f /dev/st0 rewind
mt -f /dev/st0 stoptions buffer-writes async-writes read-ahead
mt -f /dev/st0 defblksize 0
mt -f /dev/st0 defcompression 1

and re-ran the tests and got the same result.

could i have two bad tapes in a row? is there anything else it could be?

thanks for the help

Nick


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to