Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I am trying to boot from the OK prompt but I keep getting a message that says "Timeout waiting for ARP/RARP packet". This message keeps coming up on my screen and will not continue to boot. How do I interupt or break out of this cycle. Thanks, Paul.
If you type:
printenv
at the OK prompt, you should see the settings for the following EEPROM parameters:
diag-switch?
diag-device
You can either:
1. change the diag-switch? to false so that it won't try to boot from the diag-device (type: setenv diag-switch? false)
or
2. change the diag-device from net to disk (type setenv diag-device disk)
The above will stop the machine from looking to the network for a boot image.
As far as the root of the problem, your hard disk is not being found for booting. By default, the machine goes to the network for a boot image if it can't find the hard disk, unless you change the above EEPROM settings.
So, the fix is to verify your hard disk connections, power, jumper settings, etc., etc. If all that's good, boot on a bootable CDROM into single-user mode and check the disk.
type in:
boot cdrom -s
at the OK prompt, then when it's booted at the # prompt, type in:
format
and check the disk's partition. If no disk is found, something's defective or something is misconfigured.
0 
If I could get to the command prompt I would be all set. The system starts the boot process, checks the memory and then checks "Boot device" /iommui/sbus/ledma@f, 400010/le@f,c0000. After this I get the "Timeout..." message again and again and again..... It will not return to the #prompt or boot any further. It just keeps "timeout waiting for ARP?RARP". My question is, how do I break out of this boot loop so that I can correct the situation. Thanks to all.
0
If you hold down the [Stop] and the [A] keys at the same time while or before this timeout message, you should break out to an OK prompt.
0
I got back to the OK prompt at boot, "stop A" worked. I typed the wrong command at boot, "boot /iommui/sbus/ledma@f, 400010/le@f,c0000", by mistake. This apparently looked to boot from the network or something. What I was trying to do was to get my system to recognize my newly installed ethernet adapter upon boot. I have installed a T100 adapter but each time I boot I have to "ifconfig be0 plumb" and DHCP and "ifconfig be0 up" to recognize the adapter. What can I do to get my Sparc10 to recognize this Sun T100 adapter all the time? Thanks again, Paul.
0
Do you have a /etc/hostname.be0 file? It will need to be a text file with the hostname as the only entry. Also, the /etc/hosts file will need the IP and hostname (you may already have this in there). Did you already do a "boot -r" to find the new interface? These may be basic questions you've already taken care of, but they need to be asked.
0
I have some problems with the OK prompt not acting the way I thought it should.
First let me say that I am VERY VERY new to Sun hardware.
I have one Ultra5 running Solaris just fine. I haev a second running RedHat, and a third that is giving me trouble. Right from the get-go when I has Solaris installed I would get the boot message (((the file just loaded does not appear to be
executable))) Somone suggested to me that it was a corupt block in the boot sector. SO I tried to boot to the solaris CD (boot cdrom -s) It starts to boot (not reboot aka "dosnt shutdown first") then it either gives this cryptic timeout message ot just repeates the message (the file just loaded does not appear to be
executable) as if I were still trying to boot from the hard disk. The CDROM is brand new and I installed solaris on my other system just fine.For some odd reason it *WILL* boot to a mandrake cdrom that I burned myself (go figure) But after I installed mandrake I have to (boot disk0:b) in order to get it to boot......
Im very lost.
What I want to do:
I would like to wipe out that hard disk and install Solaris on it! But sense I can not boot to the cdrom and I dont know any other way to attempt this I am stuck.'Thanks in advance.
Jeff
0
On solaris 8, This will happen if you have a bad disk. When the disk fails it boots from net by default boot-device is “disk” then “net”.
This also happens sometimes if you turn off/lose power during some portions of the initial setup process.
If you are accessing the box via the LOM port you will need to send a break to the box during the memory count (while the little symbols are spinning). Some terminals do not have good support for this but I know that “tera term pro” does. This will send you to a prompt that says "ok" from here you can do "probe-ide" to get the IDE device status. If your boot device is not active then this is probably a bad drive/partition/etc.
diag-device and diag-switch both control the diagnostics. If diag-switch is on then it will try to send diagnostics to diag-device.
The default value for diag-device is net and if a net device is not ready and diag-switch is true it will timeout with "waiting for ARP/RARP" during boot time.
diag-device should be “net” and diag-switch should be “false” unless you want diagnostics.
boot-device should be disk unless you boot from the network.
Use “printenv” to get a list of environment variables and use "setenv " to set a variable.
I have had luck just skipping all this and doing “boot disk0” at the “ok” prompt and then sys-unconfig after it boots if it was just a problem where someone made a mistake on the initial setup and turned off the machine in the middle of the configure process to start over. This information may only apply to the netra x1 and sun blade boxes that I'm familar with but it's very likely that this applies to many other solaris boxes.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
