best@seas.gwu.edu (keith best) (02/14/90)
I need help from some Unix gurus out there....preferably those familiar with
AT&T's line of 3B2 computers. The library where I work has a 3B2/300 computer
that has not been used in about 4 years. I recently tried to set it up for someproductive use but I do not have the passwords for ROOT or SYSADM. Therefore, it is practically useless. The previous system administrators are no longer available.
I have all the original software and documentation (I hope) and would not discard the idea of deleting everything and reloading the system from scratch. I have followed the ROOT RECOVERY METHOD as outlined in the documents to the letter without success.
Previously when I tried to access the FIRMWARE mode, I got an NVRAM SANITY
failure: I have since replaced the battery, but now I get a SYSTEM FAILURE:
CONSULT YOUR SYSTEM ADMINISTRATION UTILITIES GUIDES. This guide does not mention this error message. The FLOPPY KEY disk gives the same error.
The system is running SYSTEM V Release 2.0 3B2 Version 2.0. We are way past
support from AT&T who donated the computer system so we would appreciate any
help from knowledgeable users out there.
Thanks in advance
Keith S. Best
Internet Address: best@seas.gwu.edunaim@eecs.nwu.edu (Naim Abdullah) (02/14/90)
best@seas.gwu.edu (keith best) writes about a 3b2/300: >Previously when I tried to access the FIRMWARE mode, I got an NVRAM SANITY >failure: I have since replaced the battery, but now I get a SYSTEM FAILURE: >CONSULT YOUR SYSTEM ADMINISTRATION UTILITIES GUIDES. This guide does not >mention this error message. The FLOPPY KEY disk gives the same error. >The system is running SYSTEM V Release 2.0 3B2 Version 2.0. We are way past >support from AT&T who donated the computer system so we would appreciate any >help from knowledgeable users out there. I am in exactly the same situation as Keith. I too, have an aging 3b2/300 that was being thrown out and I volunteered to take it over. We don't have the floppy key disk for the system. When I turn it on, it gives me the same NVRAM SANITY FAILURE mentioned by Keith. And yes, I replaced the battery too. I still get the same message. Any ideas from those who have tried to restore a 3b2/300 to life ? Your posting may help save the life of a 3b2. Write soon; operators are standing by... :-) Naim (naim@eecs.nwu.edu)
ram@attcan.UUCP (Richard Meesters) (02/15/90)
In article <1603@sparko.gwu.edu>, best@seas.gwu.edu (keith best) writes: > I need help from some Unix gurus out there....preferably those familiar with > AT&T's line of 3B2 computers. The library where I work has a 3B2/300 computer > that has not been used in about 4 years. I recently tried to set it up for someproductive use but I do not have the passwords for ROOT or SYSADM. Therefore, it is practically useless. The previous system administrators are no longer available. > I have all the original software and documentation (I hope) and would not discard the idea of deleting everything and reloading the system from scratch. I have followed the ROOT RECOVERY METHOD as outlined in the documents to the letter without success. > Previously when I tried to access the FIRMWARE mode, I got an NVRAM SANITY > failure: I have since replaced the battery, but now I get a SYSTEM FAILURE: > CONSULT YOUR SYSTEM ADMINISTRATION UTILITIES GUIDES. This guide does not mention this error message. The FLOPPY KEY disk gives the same error. > The system is running SYSTEM V Release 2.0 3B2 Version 2.0. We are way past > support from AT&T who donated the computer system so we would appreciate any > help from knowledgeable users out there. The System failure message is nothing to be overly concerned about. When that message comes up, you should enter your firmware password, (the default, as can be found in TFM is "mcp". If the password doesn't work, check the parity of your terminal. Try using 8 bit no parity or 7 bit space parity on the console terminal. Once you've entered firmware mode, you will probobly be more comfortable if you rebuild the system from scratch. There are two reasons for this. 1) If you don't know the configuration and setup of the system, it will start you out with a clean slate. 2) You will probably learn more about the system by setting it up yourself. If you have further questions, feel free to e-mail me. Regards, ------------------------------------------------------------------------------ Richard A Meesters | Technical Support Specialist | Insert std.logo here AT&T Canada | | "Waste is a terrible thing ATTMAIL: ....attmail!rmeesters | to mind...clean up your act" UUCP: ...att!attcan!ram | ------------------------------------------------------------------------------
josie@pegasus.ATT.COM (Jack Gross) (02/15/90)
In article <3540002@eecs.nwu.edu> naim@eecs.nwu.edu (Naim Abdullah) writes: >best@seas.gwu.edu (keith best) writes about a 3b2/300: >>Previously when I tried to access the FIRMWARE mode, I got an NVRAM SANITY >>failure: I have since replaced the battery, but now I get a SYSTEM FAILURE: >>CONSULT YOUR SYSTEM ADMINISTRATION UTILITIES GUIDES. This guide does not >>mention this error message. The FLOPPY KEY disk gives the same error. >>The system is running SYSTEM V Release 2.0 3B2 Version 2.0. We are way past >>support from AT&T who donated the computer system so we would appreciate any >>help from knowledgeable users out there. > >I am in exactly the same situation as Keith. I too, have an aging 3b2/300 >that was being thrown out and I volunteered to take it over. We don't have >the floppy key disk for the system. When I turn it on, it gives me the >same NVRAM SANITY FAILURE mentioned by Keith. And yes, I replaced the battery >too. I still get the same message. > >Any ideas from those who have tried to restore a 3b2/300 to life ? Your posting >may help save the life of a 3b2. Write soon; operators are standing by... :-) > > Naim > > (naim@eecs.nwu.edu) What you need to do is type in: mcp and return. The machine will not echo the characters back to you. If you get: SYSTEM FAILURE: CONSULT YOUR SYSTEM ADMINISTRATION UTILITIES GUIDE again then check to make sure that you have your terminal set up to 9600 baud no parity. You should then see: Enter name of program to execute [ ]: you type in unix and enter. Next you will see: Option Number Slot Name --------------------------------------- 0 0 FD5 1 0 HD30 Enter Load Device Option Number [1 (HD30)]: Type in 0 to boot from the first floppy of the core set. After a minute or so the machine will come up and ask you if you want to do a complete restore, partial restore, upgrade or dual disk upgrade. You should then type in: magic mode and return. You will then be get a shell so you can mount the hard disk and remove the password from root. To mount the hard disk type in /etc/mount /dev/dsk/c1d0s0 /mnt. Then cd /mnt/etc and use ../bin/ed to edit the passwd file. After you have done this you can cd / and /etc/umount /dev/dsk/c1d0s0. Next step is to type in /etc/uadmin 2 1 to get the machine to reboot. Jack Gross AT&T Bell Laboratories 307 Middletown Lincroft Rd. Lincroft NJ 07738 (201)576-3197
hcj@lzsc.ATT.COM (HC Johnson) (02/17/90)
In article <1603@sparko.gwu.edu>, best@seas.gwu.edu (keith best) writes: > I recently tried to set it up for someproductive use but I do not have the passwords for ROOT or SYSADM. Therefore, it is practically useless. If you have the boot disks used to install UNIX, you may be able to start the disk, excape (del, or ctl \ ) the install process and have a unix running. then mount the root partition, and zap the password in /etc/passwd. CAVIATE: This is how to do it on ATT UNIX for 386 machines. It may also work for you. Howard C. Johnson ATT Bell Labs =====NEW address==== att!lzsc!hcj hcj@lzsc.att.com