might be an awkward one to get this, I have just jumpstarted a server, and it boots ok untill it gets to loading Solaris Volume Manager, it gets this far and then just sits there, any ideas what might cause this, have rejumped the machine twice now lol.
The following is the output I get
Boot device: disk File and args:
SunOS Release 5.9 Version Generic_112233-11 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: forceload of misc/md_trans failed
WARNING: forceload of misc/md_raid failed
WARNING: forceload of misc/md_hotspares failed
WARNING: forceload of misc/md_sp failed
The system is coming up. Please wait.
checking ufs filesystems
starting rpc services: rpcbind done.
Setting default IPv4 interface for multicast: add net 224.0/4: gateway
syslog service starting.
volume management starting.
some info had to be removed due to the nature of my work :rolleyes: but the main part is there.
If it's printing "volume management starting.", I suggest you change the startup script for volume management to echo "volume management completed" - this way you will find out if volume management is hanging or if it's the next startup script that is hanging. Not all startup scripts announce they are starting.
Can you boot into single user mode? If so, then run the scripts in order in /etc/rc2.d and then /etc/rc3.d and find the one that hangs. Then you can post back or may know what to fix already.
Just to inform people in case they come across this problem, I have sorted it out now.
on SunFire v120's when there isn't a cdrom drive, the controller and target numbers are changed, it was this that caused the problem as the jumpstart script was looking for say "c0t1d0", and when there isn't a cdrom drive in a v120 (or that family of machines), the server changes the adressing, say "c0t0d0".
So volume management was trying to mount a cdrom drive on c0t0, when because of the machine being a fudge (my new word for things), there was actually a hard disk in the normal cd controller address lol.
This problem also causes the startup to say "cannot mount route", i think this is as a result of the addressing aswell!!
Think I explained that well... if not SHOUT at me lol