home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #16 / NN_1992_16.iso / spool / comp / sys / sgi / 11579 < prev    next >
Encoding:
Internet Message Format  |  1992-07-29  |  1.4 KB
  1. Path: sparky!uunet!dtix!darwin.sura.net!mips!sdd.hp.com!usc!rpi!bu.edu!dartvax!coos.dartmouth.edu!waugh
  2. From: waugh@coos.dartmouth.edu (Jim Waugh)
  3. Newsgroups: comp.sys.sgi
  4. Subject: SCSI cmd=0x28 Errors
  5. Message-ID: <1992Jul29.125655.29381@dartvax.dartmouth.edu>
  6. Date: 29 Jul 92 12:56:55 GMT
  7. References: <1992Jul29.055000.5453@bacchus.esa.oz.au>
  8. Sender: news@dartvax.dartmouth.edu (The News Manager)
  9. Organization: Dartmouth College, Hanover, NH
  10. Lines: 19
  11.  
  12.  
  13.    Does anyone know the implication of the following message
  14. lines in my 4D/80GT's /usr/adm/SYSLOG file? (4.0.1 IRIX)
  15.  
  16. Jul 28 14:57:06 iris1 unix: sc0,1,0: cmd=0x28 timeout after 30 sec.
  17.                                      Resetting SCSI bus
  18. Jul 28 14:57:09 iris1 unix: dks0d1s6: retrying request
  19.  
  20.    What does cmd=0x28 signify? The messages generally appear when
  21. disk-to-tape activity is performed, e.g. bru backups, tar tape archive
  22. creations, etc. The tape drive has been repeatedly cleaned, and no
  23. other abnormalities have been observed, like users complaining of
  24. corrupted files, etc. (If I redirect the output of bru/tar to
  25. /dev/null, the msgs still appear so I don't think it's the tape unit.)
  26. An overnight run of fx's exercising the disk w/random read-compare
  27. activity revealed no disk errors.
  28.    Thanks for anyone's insight.                    7/29/92
  29. -Jim Waugh, Dartmouth College, Hanover, NH
  30.             a.k.a. jim.waugh@dartmouth.edu
  31.