home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.amiga
- Path: sparky!uunet!infonode!lovealld
- From: lovealld@infonode.ingr.com (David Loveall)
- Subject: 2.1 won't boot or load from A2091 with A2090A and ST-251
- Message-ID: <1992Jul23.143750.6202@infonode.ingr.com>
- Reply-To: dave@xanadu.reston.ingr.com
- Organization: Intergraph Corp. Federal Systems Division, Reston VA
- Date: Thu, 23 Jul 1992 14:37:50 GMT
- Lines: 74
-
- Sorry if this is a re-posting - my first post didn't appear to make
- it out of my site...
-
- I'm (finally) a Amiga Unix user, and I have a couple of questions and
- observations (so far).
-
- First, my configuration:
- A2000/A2630(4MB)
- A2090A w/40MB ST-251
- A2091 w/Maxtor LXT-340S & 2MB
- SupraRAM 2000 w/4MB
- A2320 Display Enhancer
- Borrowed Archive Viper 2150S
-
- My intent was to retain the 2090A and Seagate for AmigaDos for now,
- and use the 2091+SCSI disk for Unix. I figured it should be no
- problem, as AmigaDos handles both controllers simultaneously. When I
- would try to load Unix, at the point where the scan for SCSI devices
- would occur, "No SCSI devices were found". The drive access lights
- never blipped. After two hours of puzzlement and a little irritation,
- I moved the LXT-340 from the 2091 to the 2090A. At that point,
- the Unix found the drive. I then temporarily removed the 2090A,
- moved the SCSI drive back to the 2091, and Unix found it again. At
- this point, I loaded Unix successfully (and watched the movie
- Backdraft in its entirety ;-)
-
- After several days of experimentation (playing) with Unix without
- incident, I put the 2090A back in so I could do some AmigaDos work.
- I then tried to boot Unix again from the boot menu and got this:
-
- S5mountroot VOP_OPEN
- WARNING: nfs_mountroot called
- PANIC: ufs_mountroot: cannot mount root: errno 89
- (dump info)
-
- Even with the ST-251 disconnected from the 2090A, as long as the 2090A is
- plugged in, Unix Panics trying to boot from the 2091. It appears I have a
- choice of 4 options:
-
- 1) Forget the 2090A and the ST-251. Partition the SCSI on the
- 2091 for Unix + AmigaDos. A waste of good (if old) equipment.
-
- 2) Forget the 2091, use the 2090A's SCSI port. Forget about
- using a ufs file system on root. Again, a waste.
-
- 3) Pull the 2090A when I want to run Unix. Yeah, right.
-
- 4) Please help me fill this one in! :-)
-
- Now, if the system failed to boot Unix at all, I could understand things
- little better. That it partially boots from the 2091 with the 2090A
- installed has me puzzled..
-
- As a separate observation, I might add that the 4MB of fast ram in my
- Supra memory board was merged with the 4MB of 2630 ram so Unix had 8MB
- available. Wish it was all 32-bit :-). Also a thanks to Frank Edwards
- for viper_kludge - worked great! Its mentioned in one of the addendums
- for 2.1, kind of towards the back..
-
- Its a nice package, now all I need is to back up the media... (its the
- most I ever paid for $35 of media and a few manuals ;-) Speaking of
- manuals, (I plan on getting the System Admin manual soon), what is the
- rationale for implementing ttymon as the port monitor instead of
- getty/uugetty? (I'm used to those in SVR3) The simplicity of having one
- program listen to ports seems to have been offset by pmadm. (Or should
- I be pursuing ttyadm?) I'm moving in the direction of UUCP with a SVR3
- system here..
-
- Thanks for any help & info..
- --
- David Loveall | "Invent a new Mexican Junk
- Intergraph Corp, Reston VA | food and the world will make
- dave@xanadu.reston.ingr.com | a run for YOUR border..."
- ..uunet!ingr!reston!xanadu!dave | - MST 3000
-