home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sgi
- Path: sparky!uunet!sun-barr!ames!kronos.arc.nasa.gov!iscnvx!news
- From: cunning@arthur.msd.lmsc.lockheed.com (Dave Cunningham)
- Subject: Re: Problem attaching Exabyte
- Message-ID: <1992Aug19.010323.6813@iscnvx.lmsc.lockheed.com>
- Sender: news@iscnvx.lmsc.lockheed.com (News)
- Organization: Lockheed Missiles and Space Co.
- References: <1992Aug16.155546.24668@iscnvx.lmsc.lockheed.com> <olu5hl4@zuni.esd.sgi.com>
- Date: Wed, 19 Aug 92 01:03:23 GMT
- Lines: 45
-
- In article <olu5hl4@zuni.esd.sgi.com> olson@anchor.esd.sgi.com (Dave Olson) writes:
- >In <1992Aug16.155546.24668@iscnvx.lmsc.lockheed.com> cunning@arthur.msd.lmsc.lockheed.com (Dave Cunningham) writes:
- >| I'm trying to attach an Exabyte 8200 to an 4D25, and having some
- > ... stuff omitted...
- >| when I try to start the system it hangs up somewhere between
- >|
- >| "Starting the system..."
- >| and
- >| "Irix 4.0.3..."
- >| I can load sash with no problems, boot ide from there, and even boot
- >| unix with -n and get indications that it loads; it just won't run.
- >
- >You didn't by any chance change the kernel or the system disk at
- >the same time did you? Perhaps the kernel is trashed or the wrong
- >one. I'd try loading a miniroot and see if that works (or booting
- >another 4D25 kernel over the net (from PROM monitor or sash, try
- >bootp()somemachine:someunixfile ; the pathname must be allowed by
- >tftpd on the server, see comments in /usr/etc/inetd.conf).
- >
- >If you disconnect the Exabyte, will the system boot normally? If
- >not, you probably have a bad /unix.
-
-
- No, I didn't change the kernel or system disk. Since my last posting
- I built a new kernel with lboot, and got the same behavior. Also, it
- turns out that the problem is not just the third party exabyte. I get
- the same behaviour when I attach an SGI cdrom drive with SGI
- cable/terminator- everything looks normal but unix dies somewhere
- between loading (I can see that happen if I load sash and boot unix
- from there) and the "Irix 4.x..." announcement. I also loaded a working
- kernel across the net and got the same behavior. With only the
- (internal) system disk on the bus everything works fine.
-
- I didn't mention it before, but my 4D25 is actually a 4D25S server- and
- my problem seems similar to one posted today concerning booting 4.0.4 on
- a 4D20S. Is there some other obvious candidate as a corrupted file that
- I could replace before I re-install everything ?
-
-
-
- --
- #include <standard_disclaimer.h>
-
- Dave Cunningham cunning@arthur.msd.lmsc.lockheed.com
- Lockheed Missiles and Space Co. O/81-10, B/157-5E, (408)-756-1382
-