Board index Solaris

Problem booting Solaris 2.2 from CDROM on SUN 4/260

Problem booting Solaris 2.2 from CDROM on SUN 4/260

Post by John Cart » Wed, 27 Jul 1994 22:39:44



I am trying to install Solaris 2.2 on my 4/260 with little success.

My machine:

        Sun 4/260
        3 - 8 Meg memory cards
        Internal SCSI card
        Xylogics 450 SMD disk controller
        2 Fujitsu M2333 (280 Meg) disks

        The system has been running SunOS 4.1.2 for over a year with no
        problems.  SunOS 4.1.2 was installed from the CDROM in the same
        manner that I am trying now.

Output from boot sequence:

Quote:>b sd(0,30,1)

Boot: sd(0,30,1)
si: peek failed
si: peek failed
si: peek failed
SunOS .... blah, blah, blah
Copyright .... blah, blah, blah
FPU Version 0 Present byt not supported


Panic vfs_mountroot: cannot mount root

Reboot

Then the system reboots.

1. The 'peek failed' message comes up every time I boot anything, and hasn't
   caused any problems.

2. I seem to remember that Solaris will not support the older FPU's but that
   it will run on those systems and just not use the FPU.

3. The real problem seems to be the 'Cannot assemble drivers' message.  Can
   anyone shed any light on this one for me?

Any help will be greatly appreciated.  

Thanks,

John

--


Orlando, Florida  |                           | over public relations, for
                  |                           | Nature cannot be fooled."
                  |                           | -- Richard P. Feynman

 
 
 
Top

1. Unable to boot 2.2 on 4/260 from CDROM on IPC

HELP!!!!!!

I am an experienced SunOS 4 (and SunOS 3) sysadmin trying to learn about SVR4.

We have a new (2nd hand) 4/260 which we want to try out Solaris 2 on.
All attempts to boot it from the network have failed.
It seems to tftp the kernel from the remote server (4.1.3 Sun IPC)
and then attempt to mount the root directory from the remote CD-ROM.
The messages I get are:

...
root directory: /cdrom/export/exec/kvm/sparc.sun4.Solaris_2.2
RPC: Unable to send.
prom_panic: Could not mount filesystem.

Abort at PC xxxxxxx

Doing an etherfind from a third machine, shows the request to mount
the root directory about three times and with responses (which I believe from
my decoding of the XDR to be valid file handles, ie successful mounts).

I changed the entry for the ethernet address in the NIS ethers map to
point to another 4/260 we have and this machine was able to mount the
disk with no problem.

I am starting to suspect there might be something wrong with the ethernet
connection (either inside or outside the CPU board).
I ahve tried three different transceivers (2 different manufacturers)
without success.

Has anyone seen anything like this?  Any suggestions (straws to clutch at
gratefully accepted!).

Thanks in advance.
johng
--
John Gibbins                           The Western Australian Research Institute
The University of Western Australia      for Child Health Ltd     ,-_|\

Phone:  +61-9-3408547                  PERTH  W.A. 6001          *_,-._/
Fax:    +61-9-3883414                  AUSTRALIA                      v
"Nothing is foolproof as fools are so ingenious"

2. Virtual terminals without X ?

3. 4/260 CDROM boot problem...

4. HELP! SunRiver Multiconsole SCO_SV OS 5.0.2

5. Looking for the elusive Sun 4/260 SunOS boot tapes.....

6. How does the kernel communicates with a user process?

7. Can't Install Solaris 2.4 on Sun 4/260

8. stdout problem

9. Solaris 2.1 on a Sun 4/260

10. Can't Install Solaris 2.4 on Sun 4/260

11. 7043-260 RS/6000 43P-260

12. unable to boot Solaris 2.2 from cdrom on 6/690MP

13. FBSD 2.2.1R -> 2.2.2R cdrom upgrade problem


All times are UTC
Board index