Sun V445 hangs before {0} ok prompt

Thread Tools Search this Thread
Operating Systems Solaris Sun V445 hangs before {0} ok prompt
# 22  
Old 12-12-2013
I don't know the equivalent (if there is one) for a PC keyboard.

Another thing I would do in this situation is power down, pull out the hard disks (all of them) from the backplane, and power up. This might just land you at the ok prompt. If it does we can discuss next steps.

(You mentioned earlier that "#." gave you ALOM login. To me this means that the boot process has progressed past the SC boot up and entered "autoboot" ie, looking at the hard disk. So let's pull out the disks to see if it gives an error like "can't access hard drive" and drops to "ok".)

Just an idea.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Install ext DLT Sun Tape drive on V445 Solaris 10

I have a SunFire V445 running Solaris 10 and am adding a Sun DLT tape drive. From the OK prompt the probe-scsi-all does see the drive and it is the proper target of 4. When I do the boot -- -r it does build the /dev/rmt directories correctly and the links to /devices appear correct as well. When I... (8 Replies)
Discussion started by: chastings
8 Replies

2. Solaris

Rebuild/Reset to default Sun v445

Hello, I'm quite new to Unix but I've got an old Sun v445 server that was previously used as a backup database server, these have since been moved to new hardware. The old admin who configured the box has since retired and left no notes about it, so i have no idea what the root password is and... (2 Replies)
Discussion started by: dbajtr
2 Replies

3. Solaris

Unable to move from rsc prompt to ok prompt

Hi, on sunfire v890 unable to move from rsc prompt to ok prompt, i have executed the command break. (9 Replies)
Discussion started by: manoj.solaris
9 Replies

4. Solaris

Failure to boot v445

Hi Guys, I have a small problem with a v445 which I have been informed will only boot with the reconfigure option enabled. It is attached to HP SAN storage using qla2300 FCA's with a Veritas encapsulated rootvoldg (No Laughing here please) when I try a reboot I get the following error. ... (5 Replies)
Discussion started by: gull04
5 Replies

5. Solaris

V445 unable to boot because of an error

This is what is displayed on the screen as the system tries to boot and then hangs: 0>Test CPU(s)....Done 0>Interrupt Crosscall....| SC Alert: DHCP negotiation failed, perhaps misconfigured or no DHCP server avail able Done 0>Init Memory....| SC Alert: Host System has Reset 'Done 0>PLL... (2 Replies)
Discussion started by: kenosongo
2 Replies

6. Solaris

XSCF prompt disappeared, Sun M5000

Hi, I've got an issue here: After I logon to the xscf prompt of this Sun M5000 and did 'XSCF> version -c xcp', the xscf prompt disappeared. I can't get it back and can't log out. exit rebootxscf logout #. #> #> ~# ~# exit sendbreak exit I tried to set the Mode Switch to the service... (3 Replies)
Discussion started by: aixlover
3 Replies

7. Solaris

How to get to the OK prompt without Sun keyboard

Hi all, I have just replaced the HDD on a Ultra 5 Spark machine, now I need to reinstall Solaris 9. The problem is: how do I get to the OK prompt without a Sun keyboard in order to boot from CD? At moment when I power on the machine I get the following error: Timeout Waiting for ARP/RARP... (13 Replies)
Discussion started by: sspirito
13 Replies

8. Solaris

How to get to a OK prompt on new SUN T5140

Hi, I have a brand new SUN T5140 machine. I am trying to install Solaris 10 on the box. When I go to the machine using a KVM session I can see a blank screen , how can I get to the OK prompt to start the installation. Thanks, Suresh (10 Replies)
Discussion started by: gunnervarma
10 Replies

9. Solaris

Jumpstart Solaris 8 on Sun Blade 150 Hangs

We had to replace a hard drive in one of our Sun Blade 150s, but now it hangs during the Jumpstart. It will show 1 or 2 Timeout for ARP/RARP messages and then start the spinning numbers. It always stops at 2ae00 and just hangs there. We have 1 combined jumpstart server and it is also our NIS+... (5 Replies)
Discussion started by: stottsja
5 Replies
Login or Register to Ask a Question
NDBOOTD(8)						    BSD System Manager's Manual 						NDBOOTD(8)

ndbootd -- Sun Network Disk (ND) Protocol server SYNOPSIS
ndbootd [-s boot2] [-i interface] [-w windowsize] [-d] boot1 DESCRIPTION
ndbootd is a server which supports the Sun Network Disk (ND) Protocol. This protocol was designed by Sun before they designed NFS. ND sim- ply makes the raw blocks of a disk available to network clients. Contrast this with the true namespace and file abstractions that NFS pro- vides. The only reason you're likely to encounter ND nowadays is if you have an old Sun 2 machine, like the 2/120 or 2/50. The Sun 2 PROMs can only use ND to boot over the network. (Later, the Sun 3 PROMs would use RARP and TFTP to boot over the network.) ndbootd is a very simple ND server that only supports client reads for booting. It exports a disk that the clients consider to be /dev/ndp0 (ND public unit zero). The disk is available only to clients that are listed in /etc/ethers and have valid hostnames. (Sun 2 PROMs don't do RARP, but they do learn their IP address from the first ND response they receive from the server.) boot1 is a file containing the mandatory first-stage network boot program, typically /usr/mdec/bootyy. The layout of the exported disk is: o block 0: normally a Sun disklabel (but ignored by the PROM) o blocks 1-15: the first-stage network boot program With the -s boot2 option, ndbootd will also make a second-stage network boot program available to clients, typically /usr/mdec/netboot. When boot2 is a filename, that file is the single second-stage network boot program to be served to all clients. When boot2 is a directory name, typically /tftpboot, ndbootd finds a client's second-stage network boot program by turning its IP address into a filename in that directory, in the same manner later Sun 3 PROMs do when TFTPing (i.e., if a client has IP address, ndbootd expects to find /tftpboot/C0A8010A.SUN2 ). When used in this last manner with an ND-aware first-stage boot program, ndbootd serves the same purpose in the Sun 2 netboot process as tftpd(8) serves in the Sun 3 netboot process. Any second-stage network boot program always begins at block 16 of the exported disk, regardless of the length of the first-stage network boot program. All first- and second-stage network boot programs must have all executable headers stripped off; they must be raw binary programs. The remaining options are: -i interface Only listen for ND clients on interface interface. Normally ndbootd listens for clients on the first non-loopback IP interface that is up and running. -w windowsize This adjusts the window size of the ND protocol. This is the number of 1-kilobyte packets that can be transmitted before waiting for an acknowledgement. Defaults to 6. -d Run in debug mode. Debugging output goes to standard error and the server will not fork. FILES
/etc/ethers /etc/hosts SEE ALSO
tftpd(8) BUGS
Whether or not there is a second-stage network boot program, the exported disk appears to all clients to have infinite length. The content of all blocks not used by the first- or second-stage network boot programs is undefined. All client reads of undefined blocks are silently allowed by the server. BSD
May 9, 2001 BSD