errors getting on a Preloaded system

[rana786]

Hi all,
I am getting following errors during opening a preloaded HP-UX system (rp4440). System stops on following lines and then displays following warnings.

/sbin/auto_parms: DHCP access is disabled (see /etc/auto_parms.log)

DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.

Best regards,
Mostafa

[Abhijit P.]

It also may occur after the system is configured due to an error in the
/sbin/auto_parms script.

The file that must be examined and edited is
"/etc/rc.config.d/netconf".


The comments contained in the "/etc/rc.config.d/netconf" file are:
# DHCP_ENABLE Determines whether or not DHCP client functionality
# will be enabled on the network interface (see
# auto_parms(1M), dhcpclient(1M)). DHCP clients get
# their IP address assignments from DHCP servers.
# 1 enables DHCP client functionality; 0 disables it.


Change this value to "0" (zero) so that the system will not attempt to
acquire the IP address from the DHCP server.

Examples:
DHCP_ENABLE[0]=0 Disabled
or
DHCP_ENABLE[0]=1 Enabled

After making the above change or ensuring that DHCP_ENABLE is set to 0, do
the following commands:

cd /sbin
chmod -x auto_parms

This disables the auto_parms script from trying to start DHCP.

After this change, reboot the system


Please check this , Post the configured value

Regards,
Abhijit

[rana786]

Hi Abhijit,

Can you please give me the steps to edit this file? I can only access the system in single user mode. Please help.

Rgds,
Rana

[Abhijit P.]

Hi ,

You can continue botting at this stage by hit 'Shift-cntl-\'the system will boot normally then edit the file & check the file

Regards,
Abhijit

[Kent Ostby]

The diagnostic warnings probably means that some piece of hardware is loose or got broke in transit.

If you are comfortable with hardware, shut down the box and reseat the boards and cables and power it back up.

If you're not comfortable with that then place a hardware support call with HP to have their techs troubleshoot the diagnostic logs and see which device is giving the problem. If its under warranty, this shouldn't be a problem.

[Kent Ostby]

On the other hand, the end of support date for a D390 is January 1, 2003 so finding parts for it will be more difficult.

[rana786]

Hi Abhijit,

No way, I am still in there.

/sbin/auto_parms: DHCP access is disabled (see /etc/auto_parms.log)----After getting this line I press ctrl+ shift+\ But still I got following warnings and hanged.

DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.

Is there any alternative solution?

Best rgds,
Rana

[Abhijit P.]

Hi...

You can try with cntl+Break or only "dot" on numpad system can boot.

Regards,
Abhijit

[rana786]

Hi Abhijit,
In single user mode, mounting lvol7 & lvol8 can be edited the netconf file. Am I right? cntl+break does not work either.

rgds,
Mostafa

[Kent Ostby]

Oh .. sorry .. to get past this:

shift-cntl-|

That will skip the RC scripts and get you to a shell login.

[Abhijit P.]

Hi ..

Yes you can mount it in single user mode
using mountall and then edit the file.

Regards,
Abhijit

[rana786]

Hi Abhijit,

Now it skipped but it stucks at the diagnostics warnings.

The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.

What can I do now. Please help.

Rgds,
Rana

[Abhijit P. · Accepted solution]

Have you tried with editing the file from Single user mode.

If this server is under warranty /contract better register call with HP this seems to be a I/O Subsystems Issues.

Regards,
Abhijit