HP ux-11.11 can not start

[johnzw]

I have a HP-rp2470 UX11.11. When it startup, the following messages display:

Boot
: disk(0/0/1/1.15.0.0.0.0.0;0)/stand/vmunix
10190848 + 1769472 + 4551560 start 0x1fc0e8

alloc_pdc_pages: Relocating PDC from 0xf0f0000000 to 0x7fa00000.
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 6.

System Console is on the Built-In Serial Interface
Entering cifs_init...
Initialization finished successfully... slot is 9
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)

the start program was hang up and no any response.

Please help me, thank you.

[Kapil Jha]

was this server running before??
any activity done on it?

If you have alternate disk can you try to boot from alternate disk.

Cause the messages you gave are all fine we can not suspect anything from these.

completely power off and try booting from alternate disk.

BR,
Kapil+

[johnsonpk]

Hi John,

have you tried booting in single user mode?


on ISL prompt type hpux -is


Regards
Johnson

[johnzw]

Hi Kapil Jha

Yes, this server is running good before. User of this server told us, they last login this server at the last Friday, and did their job very well. User can't login this server at this morning via ssh. they told us they hadn't done any system change.

I login MP via a terminal, but there is no response when I switch to "console" by "co" command. So, after had a communication with user, I reset this server by "rs" command in MP. Then I got these aboving messages from the terminal display.

There isn't alternative boot disk in this server.

Hi johnsonpk

I tried to login by single user, but failed, the display information as the same as the aboving.

We tried to rescue this server by HP-UX recovery from a ignite-server.
some steps as follows:
Enter file system checking...
FILE SYSTEM CHECK MENU
..
..
..
select one of the following:
a. Run fsck -y
b. Prompt for the fsck run string on ..
c. Return to the 'HP-UX Recovery MENU.'

selection: a

/dev/rdsk/c1t15d0s1lvm
last ...
Phase 1 ...
Phase 2 ...
Phase 3 ...
Phase 4 ...
Phase 5 ...
64 files, 0 icont, 7613 used ...
*****marking file system clean*****

Hang up, no response

[Kapil Jha]

How long you have been waiting for this hang?
are you sure no error came before this.

Can you try to reignite it.
BR,
Kapil+

[johnzw]

hi Kapil Jha
Thank you for your replying.

you are right, there is going on to display some information after the "marking file system clean", maybe waiting for 30 mins.

diagnostic system warning:
The diagnostic logging facility has started receving 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.

[johnsonpk]

The diagnostic warnings probably means that some piece of hardware is malfunctioning

If you have a hardware contract ,place a call with HP , else try reseating i/o cards , disk,


you may try to skip the rc script execution by the key combination ( shift + cntl + | )

BTW have you tried booting from alternate boot disk ?


Johnson

[johnzw]

Hi johnsonpk, thank you for your help. I'll try to skip rc.
BTW, I haven't alternative boot disk.

[johnzw]

Update: the entire strat up messages (normal mutil-users startup):

*****************************************

************ EARLY BOOT VFP *************
End of early boot detected
*****************************************

Firmware Version 43.50

Duplex Console IO Dependent Code (IODC) revision 1

------------------------------------------------------------------------------
(c) Copyright 1995-2002, Hewlett-Packard Company, All rights reserved
------------------------------------------------------------------------------

Processor Speed State CoProcessor State Cache Size
Number State Inst Data
--------- -------- --------------------- ----------------- ------------
0 750 MHz Active Functional 750 KB 1.5 MB
1 750 MHz Idle Functional 750 KB 1.5 MB

Central Bus Speed (in MHz) : 120
Available Memory : 2097148 KB
Good Memory Required : 31708 KB

Primary boot path: 0/0/1/1.15
Alternate boot path: 0/0/2/1.15
Console path: 0/0/4/1.643
Keyboard path: 0/0/4/0.0


Processor is booting from first available device.

To discontinue, press any key within 10 seconds.

10 seconds expired.
Proceeding...

Trying Primary Boot Path
------------------------
Booting...
Boot IO Dependent Code (IODC) revision 1


HARD Booted.

ISL Revision A.00.43 Apr 12, 2000

ISL booting hpux

Boot
: disk(0/0/1/1.15.0.0.0.0.0;0)/stand/vmunix
11218944 + 2281472 + 11461568 start 0x200f68




alloc_pdc_pages: Relocating PDC from 0xf0f0000000 to 0x7fa01000.
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: nfs3_link(): File system was registered at index 3.
NOTICE: autofs_link(): File system was registered at index 4.
NOTICE: cachefs_link(): File system was registered at index 5.

System Console is on the Built-In Serial Interface
Entering cifs_init...
Initialization finished successfully... slot is 9
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)

[johnzw]

Hi johnsonpk
I'm sorry that I didn't understand your mean about alternative boot path.
yes, this server have a alternative boot path, but when I input "bo alt", system report a error, "bad LIF magic". So, it looks
as my alt boot is bad.

[AVV]

Hello,


Do you have an ignite image for the system ?

(Not jumping into but to know :( )

1. You tried to boot from single user mode and could not.
2. There is no mirroring avail.
3.Tried to skip the start-up process.


Running a recovery shell will help here ???

[johnzw]

Hi ajesh v v
the following display by HP-ux recovery shell:

FILE SYSTEM CHECK MENU

The file system check 'fsck -y /dev/rdsk/c1t15d0s1lvm'
will now be executed.

Select one of the following:
a. Run fsck -y.
b. Prompt for the fsck execution string on c1t15d0s1lvm.

m. Return to the 'HP-UX Recovery MENU.'

Selection: a
Loading /sbin/fsck...

** /dev/rdsk/c1t15d0s1lvm
** Last Mounted on /stand
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
64 files, 0 icont, 7613 used, 119218 free (154 frags, 14883 blocks)
***** MARKING FILE SYSTEM CLEAN *****

wait for 30-40 mins

diagnostic system warning:
The diagnostic logging facility has started receving 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.

As the all above messages and posts, I thnik maybe it is hardware fault.

[V. Nyga]

Hi,

seems to be a hardware failure.
Can you test the disk in another HP?
Just hang it in and do a 'dd to /dev/null' test.

HTH
Volkmar

[johnzw]

hi V. Nyga, thanks for your reply, it's very hard to test disk in another server, because this server rp2470 is very old, and we haven't the same machine to do this test.

[Kapil Jha]

HI John,

I think you should ask HP to replace the disk and ignite it again.

the last option I see is to re-ignite with same disk [which most prob wont work]

BR,
Kapil+

[V. Nyga]

Hi again,

do you have a list of the disks you have in this server?
Are there important, not back-uped datas?
You can either replace the primar boot disk or try to install os at the alternate boot disk. The question is - do you have important datas at the alternate boot disk or is it really 'only' a second boot disk.

>when I input "bo alt", system report a error,
>"bad LIF magic". So, it looks
as my alt boot is bad.

It also could be a data disk - 'alt disk' only means that there's a second disk, where you could boot from. The system doesn't know if there's a boot sector at it.

Have you tried the logtool utility in stm to determine which I/O subsystem is logging excessive errors?

Volkmar

[Viktor Balogh]

>I login MP via a terminal, but there is no response when I switch to "console" by "co" command.

did you press some enter? maybe there weren't any activity on the console and that's why you didn't see anything. A reset in this case is a little bit rough solution, I would have checked the system state in the VFP menu and so on... RS should have been the last resort.

[johnzw]

Hi all, thanks for your help, and this problem was caused by hardware fault.
We plan to move disk to another server to test and backup data.

[johnsonpk]

Good luck with that ..if solved ..pls update the thread with resolution and close the thread...

Rgds!
johnson

[johnzw]

I moved disk to another server,however it can't start up too, so we can determine the disk has malfunction.
Thank you for your help again, close this post.

[johnzw]

Closed