On Friday 30 April 2004 10:49, 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
>
>
>Could I have a hard ware error of some kind ?  I just rebooted the
>system to make sure it was not that.  Just yesterday I labeled 25
> tapes !!
>
Verify each tape has the right header on it with this non-amanda 
sequence:

1. load the tape, which should leave it at BOT when its been 
recognized by the drive.

2. prompt#> dd if=/dev/st0ENTER

This should spit out to the screen, the first block of the tape which 
contains the label followed by a date string that amanda doesn't yet 
use (that I know of).  The label string should be what you had 
amlabel write to it, and the date string should match the date the 
label was last written.  Note that this IS updated when amanda uses a 
tape.

3.  Since we used the "rewind on close" /dev/st0 entry or whatever it 
is on your system, the tape should be rewound and you can do it again 
if you'd like.

4. issue whatever commands it takes to make the tape label match, and 
goto #2 if corrective action was taken.
 
5. eject that tape and insert the next one

6. goto 2.

When done, if you had to rewrite labels, go remove any duplicates in 
the /config_name/tapelist to prevent amanda from getting confused.

>On Fri, 2004-04-30 at 10:07, James D. Freels wrote:
>> Hello Amanda-Users !
>>
>> I have duplicated my previous amanda backup setup from an existing
>> machine to a new machine.  The new machine has a different tape
>> drive which I changed the tapetype entry in amanda.conf to:
>>
>> define tapetype TDK-DC4-150 {
>>     comment "Seagate Scorpion 40 drive with DSS-4 tape and
>> compression" length  30000 mbytes
>>     filemark    1 kbytes
>>     speed    4800 kps
>> }
>>
>> All other entries are the same.
>>
>> I have also labeled new tapes for this tape drive.
>>
>> The amcheck says the tape label is good and is the next tape to be
>> used in the backup.  The amcheckdb and amadmin configid tape
>> 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 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:
>>
>> ERROR taper no-tape [not an amanda tape]
>>
>> The amtapetype ran OK.
>>
>> The tar command runs OK completely independent of amanda to backup
>> files to tape that way so I know the tape drive works OK.  This
>> machine is a dual-Xeon running Linux 2.4.26 on the
>> Debian/Woody/Stable distribution with plenty of memory, etc.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.