Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.cis.okstate.edu!col.hp.com!nntp.coast.net!howland.reston.ans.net!nntp.crl.com!usenet From: "Eric J. Rossin" <ejr@nlc.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: FreeBSD2.1: Archive Python + UHA 34F problem Date: Sun, 31 Dec 1995 19:24:59 -0800 Organization: Next Level Communications / General Instrument Lines: 28 Message-ID: <30E7540B.41C67EA6@nlc.com> NNTP-Posting-Host: a121005.sts1.as.crl.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 2.0b3 (X11; I; FreeBSD 2.1.0-RELEASE i386) Hi all! I am running FreeBSD2.1 with no problems in general except that I cannot get an Archive Python, attached to the external connector of my Ultrastor 34F to work. details: on boot, the kernel "sees" the Python, and reports it as a "ARCHIVE Python 28388-XXX4.98" however, if I try to tar to it, i.e., "tar cvf /dev/rst0 foo", for instance, tar goes for awhile, then stops with the error tar: can't write to /dev/rst0 : Input/output error I have also tried to read a tape that I know has a tar file on it and all I get is the lights to blink. physically, I removed the terminators on the UHA34F, and the Python has active termination, so I think that is OK. My general question is am I doing something wrong with a set-up or device usage, or do I have a hardware problem. Also, if people suspect hardware, what is the easiest way to check if it is the 34F or the tape? thanks! -eric