topic Re: problem whit new system in Operating System - HP-UX

problem whit new system

F Verschuren — Fri, 26 Aug 2005 01:18:43 GMT

Hi Ijust installed a rp4440 whit a ignite tape, normaly tis was working fine but now I got the folowing message whit starting up, can somebody tell me what to do to fix this problem?
Tanks
ISL> hpux -is

Boot
: disk(0/1/1/0.1.0.0.0.0.0;0)/stand/vmunix
12599296 + 2777088 + 7887864 start 0x2007e8

alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3f900000.
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.
0/4/2/1: Fibre channel host port is OFFLINE, can not scan

0/5/2/1: Fibre channel host port is OFFLINE, can not scan

System Console is on the Built-In Serial Interface
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - can't open device
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
mountfs:opend

linkstamp: Thu Aug 25 22:47:25 METDST 2005
_release_version: @(#) $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????

PC-Offset Stack Trace (read across, top of stack is 1st):
0x003bf828 0x004b6f88 0x0050968c
0x0061b304 0x00509978 0x0017ab3c
0x00200de4
End Of Stack

Firmware Version 45.11

Duplex Console IO Dependent Code (IODC) revision 1

Stored message buffer up to panic:
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.
0 sba
0/0 lba
0/0/1/0 asio0
0/0/1/1 asio0
0/0/2/0 hcd
0/0/2/0.1 hub
0/0/2/1 hcd
0/0/2/1.1 hub
0/0/2/2 ehci
0/0/3/0 side_ba
0/0/3/0.0 side
0/0/3/0.0.0 tgt
0/0/3/0.0.0.0 sdisk
0/0/3/0.0.7 tgt
0/0/3/0.0.7.0 sctl
0/0/3/0.1 side
0/0/3/0.1.7 tgt
0/0/3/0.1.7.0 sctl
0/1 lba
0/2 lba
0/4 lba
fcd: Claimed Dual Port 2Gb HBA Port 0 at 0/4/2/0
0/4/2/0 fcd
fcd: Claimed Dual Port 2Gb HBA Port 1 at 0/4/2/1
0/4/2/1 fcd
0/4/2/1: Fibre channel host port is OFFLINE, can not scan

0/5 lba
fcd: Claimed Dual Port 2Gb HBA Port 0 at 0/5/2/0
0/5/2/0 fcd
fcd: Claimed Dual Port 2Gb HBA Port 1 at 0/5/2/1
0/5/2/1 fcd
0/5/2/1: Fibre channel host port is OFFLINE, can not scan

0/6 lba
8 memory
16 ipmi
128 processor
129 processor
136 processor
137 processor
144 processor
145 processor
152 processor
153 processor

System Console is on the Built-In Serial Interface
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - can't open device
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
mountfs:opend

System Panic:

linkstamp: Thu Aug 25 22:47:25 METDST 2005
_release_version: @(#) $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????

PC-Offset Stack Trace (read across, top of stack is 1st):
0x003bf828 0x004b6f88 0x0050968c
0x0061b304 0x00509978 0x0017ab3c
0x00200de4
End Of Stack

sync'ing disks (0 buffers to flush): (0 buffers to flush):
0 buffers not flushed
0 buffers still dirty

*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to

Re: problem whit new system

Leif Halvarsson_2 — Fri, 26 Aug 2005 01:24:24 GMT

Hi,
Are you booting from a SAN volume ?

Re: problem whit new system

F Verschuren — Fri, 26 Aug 2005 01:28:59 GMT

I touch I was booting to lokal storage (becase I only saw two disks. but if i look to the hartware path 0/1/1/0.1.0.0.0.0.0 it looks like a fibre disk... (I din't see the hartware m self)

Re: problem whit new system

F Verschuren — Fri, 26 Aug 2005 01:33:44 GMT

I am booting the other server in multy user mode but that one seems to be hanging on:

Primary boot path: 0/1/1/0.1
Alternate boot path: 0/1/1/1.0
Console path: 0/0/1/1.0
Keyboard path: 0/0/4/0.0

Processor is booting from the 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 3

HARD Booted.

ISL Revision A.00.43 Apr 12, 2000

ISL booting hpux

Boot
: disk(0/1/1/0.1.0.0.0.0.0;0)/stand/vmunix
12599296 + 2777088 + 7887864 start 0x2007e8

alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3f900000.

Re: problem whit new system

F Verschuren — Fri, 26 Aug 2005 02:09:42 GMT

both systems are now in a reboot cicle...

Re: problem whit new system

Leif Halvarsson_2 — Fri, 26 Aug 2005 02:15:52 GMT

Hi,
When you installed the Ignite image, which disk did you installed on, an local disk or a SAN volume ?

Have you tried to disconnect the fibre and then boot ?

Re: problem whit new system

F Verschuren — Fri, 26 Aug 2005 02:41:41 GMT

It looks like lokal divices.
to discontect the fibre, I dint try jet.
I fount a other disk where hp installed there os on that one is bootbe.

disconect the fibre do you mean pull out the fibre carts, ore only the fibre cable or can it be done remotly?

Re: problem whit new system

Leif Halvarsson_2 — Fri, 26 Aug 2005 02:56:04 GMT

Hi,
Yes, I meant disconnecting physically but, it can also be done with configuration in the FC switch. But, is you are sure that you installed on local disk, it is perhaps not necessary. The reason for my questions was that I have seen problems when trying to boot from SAN volume when Secure Path 3E was installed. Without Secure Path installed, booting from SAN is not any problem.

Re: problem whit new system

Borislav Perkov — Fri, 26 Aug 2005 03:18:01 GMT

Hi,
I have similar problem. It was SCSI cable problem. You have to disconect any external storage and try to boot only with system disks, maybe in single user mode. If it works then it is probably FC connection problem. If it does not works than you have problem with the internal SCSI, for the local disks. But anyway you have to isolate the problem.
Regards,
Borislav

Re: problem whit new system

Borislav Perkov — Fri, 26 Aug 2005 03:23:41 GMT

Can you send the display of seltest messages?
You have to interrupt the boot process, pressing anykey when it is shown on the scereen while booting. Then enter in information menu typing in, and WA in information menu.

Re: problem whit new system

F Verschuren — Fri, 26 Aug 2005 03:39:26 GMT

Information Menu: Enter command > wa

Information Menu: Enter command > wa

do logging... I am reinstalling one of the tho servers via the instalation cd, but because it is not clear if this wil resolve the problem I will ask a colega of me to try to isolate the problem on the other node.

Re: problem whit new system

F Verschuren — Fri, 26 Aug 2005 03:40:40 GMT

disk used:
HP_73.4GST373454LC 0/1/1/0.1.0 70007

Re: problem whit new system

Borislav Perkov — Fri, 26 Aug 2005 03:45:56 GMT

In 95% of the cases it is connectivity problem either in internal connections or external connections to disks or storage.

Re: problem whit new system

F Verschuren — Fri, 26 Aug 2005 03:50:11 GMT

tanks
we will go to check the externel contactions on one system, the other one I am going to reinstall because I was albe to boot on a recovery disk.

if one of the two works we will do the smae on the other server.

Re: problem whit new system

Michael Duthie — Fri, 26 Aug 2005 04:12:33 GMT

A few Questions.

What model of server did you create the IUX tape on? And which spec of CPU?

Which version of HPUX are trying to install? what hardware enablement bundle is on the IUX tape?

I would be suprised if you had 2 faulty systems, sounds like a HUPX version or missing driver problem to me.

MD

Re: problem whit new system

Bob_Vance — Fri, 26 Aug 2005 13:56:43 GMT

FYI

disk(0/1/1/0.1.0.0.0.0.0;0)

*is* the default internal disk for an rp4440,
so the install did properly go to the internal disk. (Ignite install changes the default boot path to that of the disk to which the system was installed.)

I would try to do a minimal install from CD to this system to see whether it works. You don't need to include any extra software (such as Online Diags or the QPK patches). Just get something small installed on it.

bv

Re: problem whit new system

Torsten. — Fri, 26 Aug 2005 14:16:10 GMT

the most important question for me at this time:

Where the ignite tape come from?

Re: problem whit new system

Kent Ostby — Fri, 26 Aug 2005 18:56:02 GMT

Freek -- The panic message above generally means that the lvlnboot definitions have not been set up.

Boot into maintanence mode:

boot -lm

ONce there activate the root vg:

vgchange -a y /dev/vg00
lvlnboot -r /dev/vg00/lvol3
lvlnboot -s /dev/vg00/lvol2
lvlnboot -d /dev/vg00/lvol2
lvlnboot -b /dev/vg00/lvol1
lvlnboot -R /dev/vg00
lvlnboot -v

make sure that it looks like this:

Boot: lvol1 on: /dev/dsk/c2t0d0

Root: lvol3 on: /dev/dsk/c2t0d0

Swap: lvol2 on: /dev/dsk/c2t0d0

Dump: lvol2 on: /dev/dsk/c2t0d0, 0

The /dev/dsk/c2t0d0 may differe but the first part of each line should look like that. The line order doesn't matter.

After this completes, type: reboot and you should come up fine.

Re: problem whit new system

F Verschuren — Sun, 04 Sep 2005 05:26:36 GMT

Tanks for the responses, it seems to be that the ignite restore tape din't have enauf drivers for this system, When I reinstalled the systems via a install cd, they where working fine. Kind regarts,

Freek Verschuren

Re: problem whit new system

F Verschuren — Sun, 04 Sep 2005 05:27:24 GMT

reinstallation via CD