Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!wizard.pn.com!Germany.EU.net!news.dfn.de!RRZ.Uni-Koeln.DE!se From: se@MI.Uni-Koeln.DE (Stefan Esser) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Archive Viper 150 (SCSI) Date: 26 Sep 1995 21:13:40 GMT Organization: Institute for Mathematics, University of Cologne, Germany Lines: 55 Message-ID: <449qe4$lkc@news.rrz.uni-koeln.de> References: <4476m8$qqs@fozzie.sun3.iaf.nl> NNTP-Posting-Host: sysiphos.mi.uni-koeln.de To: geert@sun3.iaf.nl In article <4476m8$qqs@fozzie.sun3.iaf.nl>, geert@sun3.iaf.nl (Geert Bosch) writes: |> I've some trouble getting my Archive tapestreamer to work correctly. |> When I installed my FreeBSD from tape it would only work when I didn't |> insert a tape during boot (from floppy), and not always then. After some tries |> I could install the system. |> |> Now I'd like to make backups using my streamer, but I get the following messages: |> |> st0(nrc0:2:0): ILLEGAL REQUEST |> st0: cannot select requested mode That's a message from the GENERCI SCSI code, which tells about the results of command that was correctly received by the tape, but it didn't like it for some reason ... |> Sep 25 00:42:23 waldorf /kernel: (ncr0:2:0): "ARCHIVE VIPER 150 21247 -011" type 1 removable SCSI 1 |> Sep 25 00:42:23 waldorf /kernel: st0(ncr0:2:0): Sequential-Access st0: Archive Viper 150 is a known rogue |> Sep 25 00:42:23 waldorf /kernel: density code 0x0, 512-byte blocks, write-enabled The probe worked well. |> What means 'Archive Viper 150 is a known rogue'? |> The drive works perfectly using OS/2 and Linux. This means the drive needs special care, or it will lock up or fail otherwise. In the case of the Viper you'll find that it has get ST_Q_NEEDS_PAGE_0 set. There is a comment in the code that checks for that flag: /* Tandberg tape drives returns page 00 * with the sense data, whether or not * you want it( ie the don't like you * saying you want anything less!!!!! * They also expect page 00 * back when you issue a mode select */ Well, and since your drive IS detected as a known rogue (i.e. ST_Q_NEEDS_PAGE_0 is set), and there is a problem accessing mode pages, you might try to replace the ST_Q_NEEDS_PAGE_0 by a the value 0. (Its found at line 126 of /sys/scsi/st.c). Perhaps you got newer firmware, which fixed the problem, and no longer accepts the workaround ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/staff/esser/esser.html <se@ZPR.Uni-Koeln.DE>