Hard disk failures, missing docs, no dev system; Help!

Brad Allen ulmo at ssyx.ucsc.edu
Mon Feb 27 20:03:37 AEST 1989


Recently we obtained a used AT&T 7300 and a used 3B2.  Problems:

No documentation for either one.  (Not so bad.)

No software or dev system for 3B2.  Old version of SysV.  (Horrible.)
Where can these be obtained?  [This is what we're most interested in.]


The 3B2/300 came with the apparently standard CDC 30MB.
The battery was dead, now it is better.  Errors include:
- Red "Diagnostic" light.  When does this go off?
- CDC 30 is insane.  It was working fine (running Unix) until it started
  giving SANITY CHECK ERROR and BOOT FAILURE.
  The system asks us what type of drive it is.
  Is this simple to fix?

We want to put a MiniScribe 63MB in this.  Is this possible?
Can the 3B2 support two HD's?


The AT&T 7300 worked fine until last night.
It came with the software (floppies), SysV 3.51.
 - Who would be in EST anyway?  We told it PST, but the kernel still likes EST.
   How do we fix this?  (This is nonvital.)
 - Funny "find" process started by a mysterious uucico.  It was taking lots of
   time to complete.  This find seemed to be owned by uucico.
   There was no modem connection.  The LOGFILE and SYSLOG files mysteriously
   disappeared.  The system was rebooted because it was acting funny
   ("ls" not found, "rehash" in shell necessary; etc.)
   Shutdown didn't work, so it was sync'd and powered.  It started uucico.
   Then, after about 3 hours of UUCPing some largish files (GNU Emacs)
   the uucico was aborted by the other host.  Half an hour later,
   the computer was going very slow with periodic disk hits, for
   apparently no reason*.  A normal shutdown worked.

   However, after bringing up the system, something very very bad happened:
   The MiniScribe 64MB hard disk wouldn't boot; it had bad reads like mad,
   about half a minute into the boot.

   Bootstrapping from floppy didn't get past this section in the HD.

Questions ...
   - is there a way to boot totally from floppy on the 7300?
     (this would greatly help)
   - is this possibly software, or is it just the drive going bad?

   A MiniScribe 20MB still works fine in the system, however needs to be
   bootstrapped from the floppy (I forget which) first.


  *Another strange thing happened ... I was in /var/spool/uucppublic on a Sun 3
   running SunOS 4.0.1, and spooled my uucp's thusly:
      uucp -dC EMACS/large.files.of.tar the7300!~
   I was hoping that "EMACS/large.files.of.tar"
   would be placed into the7300!~uucp such as:
      the7300!/usr/spool/uucppublic/EMACS/large.files.of.tar
   so that I wouldn't have to worry about the /var vs. /usr problem.
   However, a very odd thing -- the first file I spooled (which got sent 1st)
   was a ~100 byte file called "EMACS/%EMACS.TAR.README".
   After (I believe) the 3hour transfer, the %EMACS.TAR.README had ~1M in it.
   From what my friend told me, this was in ~uucp, I'm not sure.
   Is this incorrect uucp usage?  Could this have surfaced any errors,
   and caused the hard disk trouble?
   [space shouldn't have been a problem.]


Any answers would be highly appreciated,
Brad Allen <Ulmo at SSYX.UCSC.EDU>

P.S.  CHEOPS.CIS.OHIO-STATE.EDU seems to have a nice anonymous ftp dir --
      ~ftp/pub/archives/att7300.  Are there other 7300/3B1/3B2 FTP hosts?



More information about the Comp.sys.att mailing list