If you try to amlabel the same tape again, does it successfully read the
label written by the first attempt?
Also, if you have dd, you can try something like:
mt -f /dev/nst0 rewind
dd if=amanda.conf of=/dev/nst0 bs=32k
mt -f /dev/nst0 rewind
dd if=/dev/nst0 bs=32k
This should spit out your amanda.conf (or whatever other file you specified)
as written to, and read from, tape.
> -----Original Message-----
> From: Jeremy Wadsack [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 07, 2001 2:55 PM
> To: Bort, Paul
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: Configuring an Exabute 10h
>
>
>
>
> $ /usr/local/sbin/amlabel daily daily0
>
> labeling tape in slot 0 (/dev/nst0):
> rewinding, reading label, not an amanda tape
> rewinding, writing label daily0, checking label
> amlabel: reading label: Input/output error
>
>
> Again, the error message is not very helpful....
>
> --
>
> Jeremy Wadsack
> Wadsack-Allen Digital Group
>
> Bort, Paul ([EMAIL PROTECTED]):
>
> > If you're using a Linux that understand RPMs, you can get
> > mt-st-0.5b-7.i386.rpm (or maybe a newer version) from a
> variety of places.
> > (gnu.org is great for getting source code, but not my first
> choice for
> > getting software working _today_.)
>
> > The error message you're getting is actually very good
> news. It means that
> > you have found a tape drive and that there is a tape in it.
> Before you can
> > amcheck, you have to amlabel at least one tape. amlabel
> writes a header to
> > the tape and creates an entry for it in the tapelist. Try
> to label the tape,
> > then try amcheck again, and let us know if there are any problems.
>
> > If you want to try something lower-level first, you can use
> `dd` to read and
> > write the tape, but you'll need mt in hand to do important
> things like
> > rewinds.
>
>
> >> -----Original Message-----
> >> From: Jeremy Wadsack [mailto:[EMAIL PROTECTED]]
> >> Sent: Friday, September 07, 2001 2:33 PM
> >> To: Bort, Paul
> >> Cc: '[EMAIL PROTECTED]'
> >> Subject: Re: Configuring an Exabute 10h
> >>
> >>
> >>
> >> Bort, Paul ([EMAIL PROTECTED]):
> >> > tapedev should point to the tape drive regardless of the type of
> >> > changer. If it's the only SCSI tape on the machine, it's probably
> >> > /dev/nst0, and a command like `mt -f /dev/nst0 status`
> should return
> >> > something meaningful about the tape drive in the
> changer. If there
> >> > is a tape in the drive, or you can convince someone to
> put a tape in
> >> > the drive, it would be a good idea to make sure AMANDA can label
> >> > that tape.
> >>
> >>
> >> Well, this computer doesn't have mt on it! And I can't
> seem to figure
> >> out where to get it. (You'd think
ftp://ftp.gnu.org/pub/gnu/mt/ would
>> be it, but apparently not.) So anyone know where mt is?
>>
>> However, I went ahead and set tapedev to /dev/nst0 (ignoring the
>> changer for now) and got this message from amcheck:
>>
>> ERROR: /dev/nst0: reading label: Input/output error
>> (expecting a new tape)
>>
>> If I try /dev/nst1, 2, or 3 I get 'no tape online' so I'm quite sure
>> that's the tape drive device.
>>
>> I don't know what to make of the "Input/outpu error" message though.
>> Could be that there's a problem in the tape drivers? Or something
>> else?
>>
>> Thanks,
>>
>> --
>>
>> Jeremy Wadsack
>> Wadsack-Allen Digital Group
>>
