Operating System - HP-UX
1748233 Members
3326 Online
108759 Solutions
New Discussion юеВ

NEED HELP! Server failed to startup, ISL prompt: "Could not open vmunix"

 
SOLVED
Go to solution
swaintee
Occasional Advisor

NEED HELP! Server failed to startup, ISL prompt: "Could not open vmunix"

Pls check the following booting information, server cannot bootup with errors, does anybody know about this case?



fs0:\EFI\HPUX> hpux
No boot vol information found in LABEL file.

(C) Copyright 1999-2008 Hewlett-Packard Development Company, L.P.
All rights reserved

HP-UX Boot Loader for IPF -- Revision 2.037


Press Any Key to interrupt Autoboot
\efi\hpux\AUTO ==> boot vmunix
Seconds left till autoboot - 10
Type 'help' for help

HPUX> boot -is
Could not open file vmunix to check for a directory
Could not open vmunix

loading failed

HPUX> ls -l
total 1374
-rwxrwxrwx 1 -12289 root 256 Apr 19 2006 AUTO
-rwxrwxrwx 1 -12928 root 262144 Apr 19 2006 HPUX
-rwxrwxrwx 1 -12800 root 61952 Apr 19 2006 ISL
-rwxrwxrwx 1 -23951 root 2048 Jul 16 18:56 LABEL
-rwxrwxrwx 1 -12290 root 375808 Apr 19 2006 PAD


when I boot to recover mode with ignite server
mount the vg00, chroot to the system
excute the "lvlnboot -v"

# lvlnboot -v
lvlnboot: Couldn't query physical volume "/dev/dsk/c6t1d5s2":
The specified path does not correspond to physical volume attached to
this volume group

although I had the /dev/dsk/c6t1d5s2 for mirror, but boot from it is also failed

use the command lvlnboot -r / -b / -s / -d also failed with the same error.

# lvlnboot -b /dev/vg00/lvol1
lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c6t1d5s2":
The specified path does not correspond to physical volume attached to
this volume group
lvlnboot: Warning: couldn't query all of the physical volumes.
14 REPLIES 14
Matti_Kurkela
Honored Contributor

Re: NEED HELP! Server failed to startup, ISL prompt: "Could not open vmunix"

> Could not open file vmunix to check for a directory
> Could not open vmunix

This means the bootloader cannot find the /stand/vmunix file.

Try booting with the previous kernel version:

HPUX> boot backup/vmunix

If that does not work either, there is some serious problem in your /stand filesystem (critical files missing, or worse).

Do this again:
> when I boot to recover mode with ignite server
> mount the vg00, chroot to the system

Then run "ls -l /stand".

If it's empty, make sure /stand is mounted, then try again. If it's still empty, you've lost the contents of /stand. In that case, the next question is, do you have a backup of /stand?

MK
MK
swaintee
Occasional Advisor

Re: NEED HELP! Server failed to startup, ISL prompt: "Could not open vmunix"

hi, Matti Kurkela

files under /stand is normal

# ls -l /stand
total 132688
drwxr-xr-x 5 root sys 8192 Jul 8 00:16 backup
dr-xr-xr-x 3 bin bin 96 Jul 3 23:23 boot.sys
-rw-r--r-- 1 root sys 21 Jul 3 22:54 bootconf
lrwxr-xr-x 1 root sys 14 Jul 16 19:22 bootfs -> current/bootfs
drwxr-xr-x 5 root root 8192 Jul 9 01:16 current
-rw-rw-r-- 1 root sys 5312 Jul 14 22:36 ioconfig
-r--r--r-- 1 root sys 82 Jul 4 00:25 kernrel
drwxr-xr-x 2 root sys 96 Jul 16 19:22 krs
drwxr-xr-x 5 root sys 8192 Jul 4 00:26 last_install
drwxr-xr-x 2 root root 96 Jul 3 22:53 lost+found
lrwxr-xr-x 1 root sys 7 Jul 16 19:22 nextboot -> current
-rw------- 1 root root 12 Jul 9 01:16 rootconf
lrwxr-xr-x 1 root sys 15 Jul 16 19:22 system -> nextboot/system
-r--r--r-- 1 root sys 2791 Jul 3 23:45 system.import
-rwxr-xr-x 4 root sys 67867560 Jul 4 00:20 vmunix


I guess maybe the LIF area go bad??
Because the ls -l under ISL outputs like this.
HPUX> ls -l
total 1374
-rwxrwxrwx 1 -12289 root 256 Apr 19 2006 AUTO
-rwxrwxrwx 1 -12928 root 262144 Apr 19 2006 HPUX
-rwxrwxrwx 1 -12800 root 61952 Apr 19 2006 ISL
-rwxrwxrwx 1 -23951 root 2048 Jul 16 18:56 LABEL
-rwxrwxrwx 1 -12290 root 375808 Apr 19 2006 PAD

Matti_Kurkela
Honored Contributor

Re: NEED HELP! Server failed to startup, ISL prompt: "Could not open vmunix"

Your LIF listing looks OK to me.

The LABEL file within the LIF has a recent timestamp: what was changed on the system on 16 July, or last Friday?

MK
MK
Deeos
Regular Advisor
Solution

Re: NEED HELP! Server failed to startup, ISL prompt: "Could not open vmunix"

hi


If you are using mirror boot disk then please edit AUTO file as:

HPUX> ls -l
total 1374
-rwxrwxrwx 1 -12289 root 256 Apr 19 2006 AUTO
-rwxrwxrwx 1 -12928 root 262144 Apr 19 2006 HPUX
-rwxrwxrwx 1 -12800 root 61952 Apr 19 2006 ISL
-rwxrwxrwx 1 -23951 root 2048 Jul 16 18:56 LABEL
-rwxrwxrwx 1 -12290 root 375808 Apr 19 2006 PAD



HPUX>edit AUTO
boot vmunix -lq




Regards
Deeos

Deepak
swaintee
Occasional Advisor

Re: NEED HELP! Server failed to startup, ISL prompt: "Could not open vmunix"

hi, Matti Kurkela
I dont know what have done on this system
I just taken over the system when it was running, and I rebooted it, and then it couldn't start


swaintee
Occasional Advisor

Re: NEED HELP! Server failed to startup, ISL prompt: "Could not open vmunix"

hi, deeos
we can edit the AUTO files, and put it in the EFI partition, and how we can edit the AUTO files in the ISL?
I think the 5 files it list is in the ISL area
swaintee
Occasional Advisor

Re: NEED HELP! Server failed to startup, ISL prompt: "Could not open vmunix"

I think that the BDRA has the pointer to the /stand files system, it would like the BDRA goes bad? or how can we fix it?
Kapil Jha
Honored Contributor

Re: NEED HELP! Server failed to startup, ISL prompt: "Could not open vmunix"

have you tried to boot from second disk.

If that also does not work boot from CD and install EFI utilities again

http://pbraun.nethence.com/doc/sysutils_hpux/hpux_lvm_recovery.html

BR,
Kapil+

I am in this small bowl, I wane see the real world......
swaintee
Occasional Advisor

Re: NEED HELP! Server failed to startup, ISL prompt: "Could not open vmunix"

hi, Kapil Jha
I have tried to boot from the sec device, but it makes no sense

I dont think the EFI has problem, because the EFI partition and files can be accessed, but the /stand files cannot be read(while the files exist).