RP 8400 Not Booting

[The Tiger]

When i switch on my RP 8400, its not booting after the following message.

NOTICE: autofs_link(): File system was registered at index 4.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 6.
td: claimed Tachyon TL/TS Fibre Channel Mass Storage card at 0/0/8/0/0
td: claimed Tachyon TL/TS Fibre Channel Mass Storage card at 1/0/8/0/0

System Console is on the Built-In Serial Interface

Kindly help me to solve the issue.

[Murat SULUHAN]

Hi


There is not enough log to find out problem

Best Regards
Murat

[The Tiger]

what all are the details u want to analyse the problem..

[Murat SULUHAN]

Hi Sree80

complete console log will be very good, please attach as file

Best Regards
Murat

[The Tiger]

Dear Sir,

Right now i dont have the CL logs. But i have SL logs. attaching the same.

The server is booting from the default path and i am getting the following messages in console. After that the server stops and not giving any messages or prompt in console.

MP> co


Partitions available:



# Name

--- ----

0) Partition 0

Q) Quit


Please select partition number: 0


Connecting to Console: Partition 0

(Use ^B to return to main menu.)

[A few lines of context from the console log:]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

NOTICE: autofs_link(): File system was registered at index 4.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 6.
td: claimed Tachyon TL/TS Fibre Channel Mass Storage card at 0/0/8/0/0
td: claimed Tachyon TL/TS Fibre Channel Mass Storage card at 1/0/8/0/0

System Console is on the Built-In Serial Interface


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



Same time i tried to boot from CD but that too hangs with the below message.






Boot IO Dependent Code (IODC) Revision 3


Boot Path Initialized.


HARD Booted.

ISL Revision A.00.43 Apr 12, 2000

ISL booting hpux (;0):INSTALL

Boot
: disk(0/0/0/2/1.2.0.0.0.0.0;0):WINSTALL
9740288 + 1683456 + 2553344 start 0x2019e8

[Murat SULUHAN]

Hi Sree80

These are my recommendations.

Boot from mirror disk, if you have
Boot without fiber connections, (just unplug the fc cables) after you power recycle
Boot into single user
Boot into LVM maintenance mode,

I hope you have backup or ignite (ignite is better)

Best Regards
Murat

[Javed Khan_1]

Hi,

This could be due to i/o failure on one of the disk, system is waiting for i/o.

did you assign any new LUN to system ?

try to boot the system after removing fiber cables.Also its good idea to keep system patch level up to date

Cheers

Javed Khan

[Matti_Kurkela]

Are you booting with "hpux -lq"? If one side of your mirrored system disk has failed, this is required to boot successfully.

I noticed your SL error log contains repeated INLET_OVERTEMP and AC_UNDERVOLTAGE alarms.

The latest AC_UNDERVOLTAGE was on 01/16/2009 13:21:33 (UTC), and based on the log, it seemed to cause the server to switch itself off to protect itself.

INLET_OVERTEMP means the server room air sucked in by the server is already so hot that it cannot provide adequate cooling to the server.

Looks like your server room may have inadequate cooling and power stabilization. This may well be the root cause of your problems.

MK

[The Tiger]

Hi Murat / Javed Khan / MK,

Thanks for your immediate response.

Root VG doesnt have a mirror so there is no ALT boot path.

I tried to boot with

-is, -lq, -lm
w/o FC Interface Cards
with 1 cell
with single mp

but getting the same message and after that server did not respond.

As we have back of the data, i tried reinstallation of OS, but i am not able to boot
thru CD also. If i boot thru CD, i will get the below msg and then no response.

Boot IO Dependent Code (IODC) Revision 3


Boot Path Initialized.


HARD Booted.

ISL Revision A.00.43 Apr 12, 2000

ISL booting hpux (;0):INSTALL

Boot
: disk(0/0/0/2/1.2.0.0.0.0.0;0):WINSTALL
9740288 + 1683456 + 2553344 start 0x2019e8


There was a problem with the AC , that could be the reason for INLET_OVERTEMP.

CL, SL ( E AND A ) attached for ur reference.

[Murat SULUHAN]

Hi Sree80

Can you submit PS output from MP/GSP

Best Regards
Murat

[mostefai mourad_1]

Hi,

I think you have to restart your external storage and try to boot again your server.

regards.