Operating System - OpenVMS
1828413 Members
3408 Online
109977 Solutions
New Discussion

Re: digital alpha server 4100 booting problem

 
SOLVED
Go to solution
rajeesh k menon
Frequent Advisor

digital alpha server 4100 booting problem

hi all,

digital alpha server 4100

3gb mem,599mhz processor, firmware version 5.4

my server is starts booting but hangs in between , it only gives a blue screen and then nothing happens.I tried to get the console from serial port but couldnt. Is it a firmware problem? which part i should replace?
34 REPLIES 34
Karl Rohwedder
Honored Contributor

Re: digital alpha server 4100 booting problem

You say 'starts booting': do you mean starts booting VMS, i.e. the console starts correctly?

Then you should halt the system in the console (pressing the HALT button) and check the configuration (SHO CONFIG, SHOW DEVICE, SHO BOO*...). Are all devices present, is the boot setup o.k.?).

Has VMS displayed its version string?

Perhaps you could log the output using a laptop and attach it as a file.

regards Kalle
John Abbott_2
Esteemed Contributor

Re: digital alpha server 4100 booting problem

It may be that the 'console' variable is not set to what you desire.

Check with >>> SHOW console If you are indeed using a gfx connection then set this to graphics (>>> set console graphics). IT maybe that you're loosing the output part way through the boot if the output is being directed the the serial port.

PS. The latest console version for an a4100 is V6.1-1.

See http://ftp.digital.com/pub/Digital/Alpha/firmware/
for an update.

Regards,
John.
Don't do what Donny Dont does
Willem Grooters
Honored Contributor

Re: digital alpha server 4100 booting problem

Does the SRM specify SERIAL as console?
Just to be complete, this may not applicable, but nevertheless: If the system has 2 serial ports, be sure that you connected the right one.
Willem Grooters
OpenVMS Developer & System Manager
Robert_Boyd
Respected Contributor

Re: digital alpha server 4100 booting problem

The 4100 has an LCD display as part of the operator control panel -- what is the last thing displayed in the panel before it stops?

Also, when you have it at the >>> prompt, what do you get for SHOW BOOT* and SHOW DEVICE, and what is the current value of OS_TYPE?

All of these may be important clues to what is happening.

Robert
Master you were right about 1 thing -- the negotiations were SHORT!
sujiths
Occasional Advisor

Re: digital alpha server 4100 booting problem

I cant execute any kind of commands,I thinks it hangs.

VMS displayed its version string, after that nothing happens.I cant halt the system.
The LCD display shows alpha server 4100.

I think I have connected to the right serial port, becouse I was able to get the console before, and after this not.

Server just starts , will get the version string, then it will not take any input from keybord.
rajeesh k menon
Frequent Advisor

Re: digital alpha server 4100 booting problem

I cant execute any kind of commands,I thinks it hangs.

VMS displayed its version string, after that nothing happens.I cant halt the system.
The LCD display shows alpha server 4100.

I think I have connected to the right serial port, becouse I was able to get the console before, and after this not.

Server just starts , will get the version string, then it will not take any input from keybord.
Heinz W Genhart
Honored Contributor

Re: digital alpha server 4100 booting problem

Hi rajeesh

I attached a picture of a 4100. You can see the backside of this machine. In the left bottom corner of the machine are two 15 pin connectores. As You can see on the picture, the console connector is not the one at the bottom, but the one above it (see red arrow in picture)

After pressing the halt button, You should see the bootprompt ( >>> )
On this bootprompt you can enter the command
>>> set console serial
>>> boot -fl x,y disk

After doing this, the console should work

Hope that helps

Regards

Heinz
Heinz W Genhart
Honored Contributor

Re: digital alpha server 4100 booting problem

Hi rajeesh

here the attachement

Heinz
rajeesh k menon
Frequent Advisor

Re: digital alpha server 4100 booting problem

still I am not able to get the console.

I have halted the machine, but I didnt get the prompt, I have connected to the proper port.

can anybody tell me where the firmware module is?whether it is with processor board or with any other board?
Heinz W Genhart
Honored Contributor

Re: digital alpha server 4100 booting problem

Hi rajeesh

1. Press the halt button
2. power off the machine
3. power on the machine
4 if your console is connected to the proper port, then you should see how the machine initializes.
5. at the boot prompt enter SET CONSOLE SERIAL
6. release the halt button
7. enter the proper bootcommand eg.
boot -fl 0,0 disk

If that does not work, can you post the output of the console until the boot stops ...(use a laptop)

Regards
Heinz
Jan van den Ende
Honored Contributor

Re: digital alpha server 4100 booting problem

Rajeesh,

in the sequence above by Heinz,
add
2.5 wait (at least) 60 seconds (more won't hurt)

Proost.

Have one on me.

jpe

Don't rust yours pelled jacker to fine doll missed aches.
Robert_Boyd
Respected Contributor

Re: digital alpha server 4100 booting problem

Since you say that you are getting the VMS version string, I suggest that you add the following to your boot command:

>>> b -fl 0,20000

This will trigger the boot code print out some interesting debug information that will announce what is being done. You should be able to track just how far the system is getting before it hangs.

Also, you might want to boot into interactive boot mode to turn on STARTUP verification just in case it's actually getting into the STARTUP process:

>>> b -fl, 0,20001

SYSBOOT> set startup_p2 "VC"

This turns on STARTUP verification (V) and verbose mode (C)

Robert
Master you were right about 1 thing -- the negotiations were SHORT!
rajeesh k menon
Frequent Advisor

Re: digital alpha server 4100 booting problem

hi,

Now I am able to see the server is initializing but it is giving a keyboard error sothat I cant login, I cant input anything

rajeesh
Ian Miller.
Honored Contributor

Re: digital alpha server 4100 booting problem

unplug the keyboard. The system will boot without it. You can then connect to the serial console.
____________________
Purely Personal Opinion
rajeesh k menon
Frequent Advisor

Re: digital alpha server 4100 booting problem

hi all

I am attaching the initializing messages.Its a keyboard error now.
Heinz W Genhart
Honored Contributor

Re: digital alpha server 4100 booting problem

Hi Rajeesh

If You use the serial console connection, this error message is normal. You really dont have a keyboard connected. You should be able to enter commands over the serial line console connection (if you have connected a Laptop or a terminal eg. VT220).

Tipp: If you dont use a graphical device as console device, I would recommend to deinstall the graphic card from the 4100. If you don't need it, remove it. You will have less problem.

Regards

Heinz
Volker Halle
Honored Contributor

Re: digital alpha server 4100 booting problem

Rajeesh,

thanks for providing the console output. This helps to diagnose the problems.

As the CPU seems to be booting immediately, you seem to have the environment variable AUTO_ACTION set to BOOT or RESTART.

Press the HALT button to get to the console prompt >>>, then type >>> SET AUTO_ACTION HALT

This will cause the system to just remain sitting on the console prompt after power-up, so you can look at the config and environment variables before you start booting.

Now please show us what happens, if you try to boot OpenVMS...

Volker.
rajeesh k menon
Frequent Advisor

Re: digital alpha server 4100 booting problem

I am using graphical device as console,only for the troubleshooting purpose I took the serial console to the laptop

Now I can see the server initializing, but I really cant enter any command through serial console.The keyboard is connected to the server.

I temporarily deinstalled the graphic card from the server.
Volker Halle
Honored Contributor

Re: digital alpha server 4100 booting problem

Rajeesh,

it may be more effective for troubleshooting to just use the serial console and a laptop to capture all the output. Once everything works, you can switch back to using the graphics console.

To switch to serial console:

>>> SET CONSOLE SERIAL
>>> INIT

To switch to graphics console:

>>> SET CONSOLE GRAPHICS
>>> INIT

Then capture the output seen during init and boot with your laptop and show us, how far you get...

Volker.
rajeesh k menon
Frequent Advisor

Re: digital alpha server 4100 booting problem

hi,

I am using a windows hyperterminal to get the serial console on a laptop.

I can see the server initialization, but the charectors that I am typing is not coming to the console,and so I cant enter any command
rajeesh k menon
Frequent Advisor

Re: digital alpha server 4100 booting problem

hi,

I am using a windows hyperterminal to get the serial console on a laptop.

I can see the server initialising , but the characters that I am typing is not coming to the console,and so I cant enter any command
Heinz W Genhart
Honored Contributor

Re: digital alpha server 4100 booting problem

Hi Rajeesh

did you allready change the cable between the Laptop and the console connector ?

Heinz
Volker Halle
Honored Contributor

Re: digital alpha server 4100 booting problem

Rajeesh,

unless the system is at the console prompt '>>>', you can't enter anything anyway.

You are trying to type on the notebook keyboard, right ?!

Can you press the HALT button ? What happens on the console terminal ?

Volker.
Robert_Boyd
Respected Contributor

Re: digital alpha server 4100 booting problem

In all likelyhood you will need to make sure that the hyperterminal software is setting the port on the laptop to 9600 bps before connecting to the Alpha. If the bps setting does not match the settings on the Alpha, you will have difficulties with typing and seeing what output comes from the serial port. Also, you must use the correct cable. Are you using a null-modem cable or a straight through cable?

Robert
Master you were right about 1 thing -- the negotiations were SHORT!