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.
9 More Discussions You Might Find Interesting
1. Solaris
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
2. Solaris
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
3. Solaris
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
4. Solaris
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
5. Solaris
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
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
7. Solaris
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
8. Solaris
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
9. Solaris
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
DRTEST(8) System Manager's Manual DRTEST(8)
NAME
drtest - standalone disk test program
DESCRIPTION
Drtest is a standalone program used to read a disk track by track. It was primarily intended as a test program for new standalone drivers,
but has shown useful in other contexts as well, such as verifying disks and running speed tests. For example, when a disk has been format-
ted (by format(8)), you can check that hard errors has been taken care of by running drtest. No hard errors should be found, but in many
cases quite a few soft ECC errors will be reported.
While drtest is running, the cylinder number is printed on the console for every 10th cylinder read.
EXAMPLE
A sample run of drtest is shown below. In this example (using a 750), drtest is loaded from the root file system; usually it will be
loaded from the machine's console storage device. Boldface means user input. As usual, ``#'' and ``@'' may be used to edit input.
>>>B/3
%%
loading hk(0,0)boot
Boot
: hk(0,0)drtest
Test program for stand-alone up and hp driver
Debugging level (1=bse, 2=ecc, 3=bse+ecc)?
Enter disk name [type(adapter,unit), e.g. hp(1,3)]? hp(0,0)
Device data: #cylinders=1024, #tracks=16, #sectors=32
Testing hp(0,0), chunk size is 16384 bytes.
(chunk size is the number of bytes read per disk access)
Start ...Make sure hp(0,0) is online
...
(errors are reported as they occur)
...
(...program restarts to allow checking other disks)
(...to abort halt machine with ^P)
DIAGNOSTICS
The diagnostics are intended to be self explanatory. Note, however, that the device number in the diagnostic messages is identified as
typeX instead of type(a,u) where X = a*8+u, e.g., hp(1,3) becomes hp11.
SEE ALSO
format(8V), bad144(8)
AUTHOR
Helge Skrivervik
4.2 Berkeley Distribution May 19, 1986 DRTEST(8)