home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!mips!odin!fido!zola!zuni!anchor!olson
- From: olson@anchor.esd.sgi.com (Dave Olson)
- Newsgroups: comp.sys.sgi
- Subject: Re: Exabyte
- Message-ID: <oirvpao@zuni.esd.sgi.com>
- Date: 14 Aug 92 20:37:05 GMT
- References: <31815@adm.brl.mil>
- Sender: news@zuni.esd.sgi.com (Net News)
- Organization: Silicon Graphics, Inc. Mountain View, CA
- Lines: 33
-
- In <31815@adm.brl.mil> beyer@bflsgu.fl.bs.dlr.de (R. Beyer) writes:
- | Dave Olson answers:
- | | I don't know how to verify what the firmware rev is of the Exabyte unless it's
- | | that 4 digit number at the end of the Device line of an mt stat command. 4 of
- | | our Exabytes have the string "425A", the other one (used above) has the string
- | | "251X".
- |
- | 425A and 252T are the only firmware revs SGI has shipped.
- |
- | I just installed a replacement Exabyte sent by SGI which gives the following
- | status information:
- |
- | Controller: SCSI
- | Device: EXABYTE: EXB-8200 2647
- | Status: 0x262
- | Media : READY, writable, at BOT
-
- Hmm. Perhaps they have qualified a new rev I haven't heard about,
- or somebody at Exabyte and receiving slipped up on their checks.
-
- I'll have to look into this.
-
- | I only replaced the Exabyte system from an otherwise functioning backup
- | environment and now the Exabyte produces a new error
- | failed I/O error: guest@bflsgu:/dev/nrexa feom 1
- | although this command presented no problems before.
-
- Is it possible that the tape is blank? That might give this
- error.
- --
- Let no one tell me that silence gives consent, | Dave Olson
- because whoever is silent dissents. | Silicon Graphics, Inc.
- Maria Isabel Barreno | olson@sgi.com
-