On Friday 30 April 2004 10:57, 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 tape with "mt rewind", turn around and issue another
> amcheck fea, and the tape has an error on it. So, the amflush
> and/or amdump process is writing something to the tape that causes
> it to not be usable after that point.
>
>Is this sounding like a scsi error or some type ?
Possibly. Sometimes people forget that a scsi bus is a transmission
line, and as such is subject to echo's and other symptoms of vswr if
not properly terminated ON BOTH ENDS of the cable and ONLY AT THE
ENDS. Even 6" of cable hanging free and unused at the end of the
cable and all bets are off. You can sacrifice all the virgin
chickens in the hen house without fixing it in that case.
Term power should be jumpered such that the card is supplying it, even
in the tape drive if that can be arraigned. Most cards furnish this
thru an isolation diode, but if the diode isn't a schotkey, but is a
silicon diode, the .70 volt drop is too much. If the drive is
mounted internally to the server, then this diode on the controller
card should be removed and a jumper installed in its place, but don't
do this if the power supply isn't common, as would be the case for an
externally mounted drive/changer/robot.
>On Fri, 2004-04-30 at 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 !!
>>
>> 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.
|
