INIT C440

[Paul Thomson_2]

Hi there

INIT C440 normally refers to the fact that is an issue initialising the stable storage console path. Or someone has gone into CM without entering CO to get out of console mode.

Normally CTRl D resolves or replacing the console.

However, can anyone advise if HP US 9000 servers running 10.20 / 11i can be configured so they do not need the console to be active to re boot. My main query is we have 60 plus servers in an office which do not have consoles attached at all and yet re boot no problem.

Can anyone advise ?

Cheers
Paul

[Ravi_8]

Hi, paul

Console is not necessary to reboot the m/c.
If you have dual boot in a m/c you can use setboot to change over to another OS

[Paul Thomson_2]

Ravi

Hi,

Just to confirm then, if a server has a console attached but it is switched off or the console shows CM>. The server will not boot.

But if there is no console attached what so ever, the server will boot up, as it will detect no console attached ?

Thanks
Paul

[Christopher Meenan]

Ravi

Hi,

Just to confirm then, if a server has a console attached but it is switched off or the console shows CM>. The server will not boot.

But if there is no console attached what so ever, the server will boot up, as it will detect no console attached ?

Thanks
Paul

Paul,

The answer is it depends upon which type of 9000 server you are using. Newer systems, such as N,L,A, will boot whether or not the console is at CM>.

Older systems, such as K class will hold and never boot if at the CM> prompt. On those systems you would have to then type CM>co to get the system to boot. The best way to ensure that your system boots for K class is just to make sure you are not accessing the GSP (not at the CM> prompt). You can leave the console on and it will make no difference. The server will boot fine with no interaction if this is the case.

Regards,

Chris

[Paul Thomson_2]

Christopher. Will this also be the case for D class as many of our offices still use this dated machine.

In that D class' are the same booting as the K class.

[tsf_1]

"INIT C440" indicates the system could not initialize the console during boot up. This can happen if the terminal itself is in an incorrect mode or for other reasons.

To fix the problem:

1. Reset system console by turning off console.

2. Hold down the 'D' key and continue to hold the key down while powering on the console, wait 10-15 sec, release key and a message should pop up in lower left hand part of screen 'default configs used press return to clear'

3. Press return and the display on the computer should start to go through the self-tests.

[tsf_1]

Not advisable to boot without a console. In case of problems, there will be a limited support if the system cannot be accessed via the console.
Some technical notes appears that a system console is not mandatory, however we need to warn about such configuration
because this is unsupported .

[Xavier Gutierrez_1]

Hi, Paul.

The old HP9000 systems cannot boot without a console attached to them and there is no workaround for this (sorry).

The error you are getting could be caused by a faulty console. But it also could be caused by console being left in CM mode or by not having the remote option disabled.

Try to change your console configuration to enable remote.

Regards.

Xavier.

[Jeff Schussele]

Hi Paul,

I disagree.
I have dozens of K systems that boot w/o a console. You should check the autoboot value.
Run setboot & check value of Autoboot. Must be ON. If not, run
setboot -b on
to set it to on.

Earlier responses are correct in the fact that if the console IS attached & not set or cabled properly, you can get a hang on boot.

So check the Autoboot value & the console setup & one of those should solve your problem.

Rgds,
Jeff

[Paul Thomson_2]

Jeff,

Hi

That is the sort of answer I was after..

All out servers are set via setboot as
# setboot
Primary bootpath : 10/4/4.6.0
Alternate bootpath : 10/4/4.12.0

Autoboot is ON (enabled)
Autosearch is ON (enabled)

So if a K/D class has a console attached it will not boot if there are issues with say the console, cable issue or the console is on CM> mode.

But without a console attached or even the cable hooked into the console port, as long as setboot is set ON the server will boot.

This was my understanding, am I correct ?

[Jeff Schussele]

Hi (again) Paul,

Yes sir - that's correct.

Although we here turn autosearch off because we'll frequently turn autoboot off when we WANT to not come completely up. Then we don't have to babysit the box to catch the 10-second warning. IF you leave autosearch ON & turn autoboot OFF the system will still boot because it'll search for a boot device & use it.

Rgds,
Jeff

[doug hosking]

Depending on your configuration, security needs, etc. you could also use a remote serial line console scheme. Down the hall from my office there's about 22 D-class systems in a loud, cold machine room. Not one has a physical console on it. They're all connected to a Lantronix ETS32PR, which lets us telnet to the consoles of any random system of ours in the machine room when we need to reboot systems, reconfigure, etc. Depending on the model of D-class system, you may need to buy a special card to allow ^B on the console to work properly, but otherwise the configuration is quite simple. That scheme has worked so well for us that many people who have been employees for years have no idea where their machine physically resides. That way you can choose to have whatever autoboot, etc. settings you need, without having to make special concessions for not having a physical console on the system.