Date: Fri, 23 Jun 1995 20:30:42 -0500 From: sheeme@corpcomm.net (Steve Heemeyer) To: questions@FreeBSD.org Subject: Re: FBSD 2.xR: AIC7xxx driver vs. st() driver vs. tape drives Message-ID: <9506240130.AA23614@netris1>
next in thread | raw e-mail | index | archive | help
>
>>Greetings -
>>I sent e-mail on this problem to Justin, the author of the AIC7xxx
>>driver. He suggested I post my problems to this list:
>>
>>I've been running an Adaptec 1542B controller under FBSD 2.0 in a 486/50
>>EISA/VESA system for some time. I've never had a problem with my Archive
>>Viper QIC150 and Exabyte 8200 tape drives before. Last week, I got an
>>Adaptec 2742AT EISA dual-channel SCSI card, and have been unable to use
>>either tape drive since.
>>
>>Thinking that the new and improved 274x driver code in v2.0.5R might
>>solve the problem, I tried installing the new OS. The QIC150 tape install
>>failed with the same error I get under 2.0R whenever I try to access the
>>Archive Viper QIC150 drive.
>>
>>DEBUG: Notify: Attempting to extract from SCSI tape drive...
>>DEBUG: Executing command 'cpio -iBduVm -H tar -I /dev/rst0' (Magic 0)
>>st0(ahc1:2:0): ILLEGAL REQUEST
>>st0: Cannot set selected mode
>>st0: bad request, must be between 0 and 0
>>cpio: read error: Input/output error
>>DEBUG: Command 'cpio -iBduVm -H tar -I /dev/rst0' returns status of 1
>
>How was the Q150 tape made and what block size did you use? The
>tape install failed for me on a HP 1533C DAT tape drive when I
>made the tape with the default block size (for tar) of 20*512 bytes.
>When I remade the tape with a blocking factor of 1, it worked.
>I got an illegal block size message on the failed attempt, so
>that's probably not your problem - I'm just throwing it out there.
>
I am seeing a similar problem on an Ultrastor 34f controller and a Tandberg
3800 tape drive.
Jun 20 23:01:02 Fridmani /kernel: st0(uha0:6:0): ILLEGAL REQUEST \
csi:10,8,0,0 asc:24,0 Invalid field in CDB field replaceable unit: 2
Jun 20 23:01:02 Fridmani /kernel: st0: Cannot set selected mode
the tape drive appears to probe fine when booting, however any attempt to
access the drive results in the above error. One quick note, the tape drive
worked successfully until I upgraded to 2.0.5A via a fresh install.
[stuff deleted]
>>Any help or comments are much appreciated...
>>- Mike
>>--
>>--------------------------------------------------------------------------
>>Michael Borowiec Network Operations Tellabs Operations, Inc.
>>mikebo@TELLABS.COM 1000 Remington Blvd. MS109
>>708-378-6007 FAX: 708-378-6714 Bolingbrook, IL, USA 60440
>>--------------------------------------------------------------------------
>
>Dan Eischen
>deischen@iworks.InterWorks.org
>
Steve Heemeyer
sheeme@CorpComm.NET
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9506240130.AA23614>