home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!ames!agate!dog.ee.lbl.gov!nosc!pages!sean
- From: Sean_Church@pages.com (Sean Church)
- Newsgroups: comp.sys.next.sysadmin
- Subject: Re: System hangs after running UpgradePrep.app
- Message-ID: <1992Jul21.152823.203@pages.com>
- Date: 21 Jul 92 15:28:23 GMT
- References: <1992Jul20.020405.1257@proforma.com>
- Sender: sean@pages.com
- Distribution: na
- Organization: Banzai Research Institute
- Lines: 68
-
- In article <1992Jul20.020405.1257@proforma.com> jgg@proforma.com (J. G.
- Gregory) writes:
- > We have a system that we are trying to upgrade from 2.1 to 3.0(PR2). It is a
- > 68040 cube with a 1.2g hard disk.
- >
- > After running the UpgradePrep.app , the system will not boot. An attempt to
- > run the boot command manually hangs the machine immediately. We have tried:
- >
- > NeXT>b
- > NeXT>bsd
- > NeXT>b -s
- >
- > It hangs immediately after hitting return in all cases. We have no
- > UNIX-experienced sysadmin to understand the nasties of this; I didn't even
- know
- > what "booting single user" was until tonight.
- >
- > This was our second attempt to bring up 3.0(PR2). The first went off without
- a
- > hitch. The only difference between the machines is that the disk on the
- > now-hung machine is not a NeXT-supplied disk. The machine is being rented,
- and
- > we were not around when the disk was installed (and the owner is out of the
- > country!). The /usr/adm/messages report looks like this:
- >
- > Jul 19 19:05:29 proforma mach: SEAGATE ST41520N as sd0 at sc0 target 1 lun 0
- > Jul 19 19:05:29 proforma mach: Disk Label: DATA
- > Jul 19 19:05:29 proforma mach: Disk Capacity 1307MB, Device Block 512
- > bytes
- >
- > The last line bothers me, because there is a mention in /etc/disktab that the
- > block size must be 1024. Yet this disk is still working; we can boot off the
- > release 2.0 optical and the disk is there and useable.
- >
- > Does anyone know what could be wrong?
- >
- > Thanks in advance for any and all help. We have a boat anchor until we can
- > boot.
- >
- > --J Gregory
-
- Does it really hang right after you hit the return ?
- If so, you are still having the ROM start the machine at this point, and what
- is on the disk (3.0, 2.2, 2.1, 1.0, or whatever) has yet to be read in, so it
- doesn't matter.
-
- The disk itself could be hanging up the SCSI bus, but you would have seen this
- before upgrading (unless, of course, a hardware failure has occured at the time
- of boot-up).
-
- What exactly appears in the monitor screen when you type :
- bsd (return)
- in the monitor. I think that there is a hardware , or maybe it's in your
- options you can change (boot device, etc) from the monitor screen.
-
- Publish more info, or mail me, and we will see what the deal is.
-
- Also, the UpgradePrep.app mangles your sdmach kernal into the 3.0 way of being,
- so you can't run anything with out completing the upgrade procedure.
-
- Hum.... does your system have an MO disk on it ? What kind of NeXT is it
- exactly ? I wonder if 3.0 supports the MO, or if it will lock up if the circuit
- is there ....
-
-
- Sean
- sean@pages.com
- The company UNIX-experienced Sys Admin, and a whole lot more!
-