HPUX BOOTING

[Alexander Yereshenko]

Hi
when i reboot my server, i've got next message:
Boot
: disk(1/0/0/3/0.6.0.0.0.0.0;0)/stand/vmunix
disk(1/0/0/3/0.6.0.0.0.0.0;0)/stand/vmunix: cannnot open, or not executable

how can i fix it?

[Steven E. Protter]

Shalom,


Boot off OS media. The method varies based on whether your system is Itanium or PA-RISC.

Once you boot you can go to recovery mode and gather information as far as whether its just a permissions problem or something that requires an OS reinstall.

I could provide a much more precise answer if you gave the model number and OS version of the system. Either detail would be extremely helpful.

SEP

[Alexander Yereshenko]

PA-RISC 8800, HPUX 11i version 1

[Nguyen Anh Tien]

/stand/vmunix may be corrupted.
Recommend you use recovery mode in OS DVD/CD by booting from it.
HTH

[Mridul Shrivastava]

Boot from recovery CD/DVD and then recover the LIF files and try to reboot???

[Patrick Wallek]

I would first check and see what your kernel looks like and then possibly try booting from your backup kernel.

Interrupt the boot process at the 10 second prompt. When you get to the next prompt type: bo pri

When it asks 'Interact with ISL' say: Y

Now you should be at the ISL prompt.

To see what you have try this:

hpux ls

or

hpux ll

If you don't see /stand/vmunix then you have a problem. If you have a /stand/vmunix.prev (backup kernel) then you can try booting from it by doing:

hpux /stand/vmunix.prev

For more information on booting from the alternate kernel, have a look at this document:

The "System Recovery" chapter of the "Software Recovery Handbook"
http://www1.itrc.hp.com/service/cki/search.do?prevQueryString=software+recovery+handbook&mode=id&searchString=emr_na-c01037105+&submit1=Search+%C2%BB&docTypeAll=yesX&docType=Advisories&docType=WhitePapers&docType=EngineerNotes&docType=SecurityBulletins&docType=Manuals&docType=Patch&dateSearchType=lastXdays&dateRange=all&startDateYear=1999&startDateMonth=0&startDateDay=1&endDateYear=2007&endDateMon...

This document also talks about other ways to try to get your system booted and recovered.

[Alexander Yereshenko]

Booted system as you've adviced.
Ls
: disk(1/0/0/3/0.6.0.0.0.0.0;0).
cannot open directory.

We don't have any kernel backup.

[Denver Osborn]

could be corrupt BDRA or boot lvol is not defined with lvlnboot. If so, then you should be able to boot to lvm maint mode.

From the ISL> prompt type 'hpux -lm' to boot to lvm maint mode.

once booted,

vgchange -a y vg00
lvlnboot -v vg00 # do you see boot, root, swap?

lvlnboot -b /dev/vg00/lvol1
lvlnboot -r /dev/vg00/lvol3
lvlnboot -s /dev/vg00/lvol2

lvlnboot -v vg00


-denver

[Alexander Yereshenko]

during recovery with d option, i've got a message:
/:write failed, file system is full
ERROR: tar: ./sbin/mkboot: HELP - extract write error: No space left on device (errno=28)
/:file system full

[Alexander Yereshenko]

Hello again!
So, I've temporary boot the system by repairing the LIF by choosing "b" option in recovery console menu.
"No free space" alert from previous message was about RAM-disk with repair vmunix image. That system had several unusable programs also. We've deleted its and recovery procedures have gone successfully.
First time system went online by "hpux -lm /stand/vmunix" command line.
Now system works with "hpux /stand/vmunix" start line, but I afraid, that in boot record start command line is "hpux -lm /stand/vmunix" still...
How should I check this situation and fix it?

[Mridul Shrivastava]

To change the contents of AUTO file you have to execute :

mkboot -a "hpux -lq" /dev/rdsk/

To check the contents of the AUTO file

lifcp /dev/rdsk/:AUTO -

[Alexander Yereshenko]

Thank you. I'll try to fix it on Monday.

Also I should notice, that command
# find / -name vmunix return nothing!

What should I do in this situation?

[Jov]

Try:
find / -name "vmunix*" or 'ls -l /stand' to see if there is an older kernel.

Someone might have started a kernel rebuild and not completed, but started to move the original vmunix.


Jov

[Jov]

Are you doing the find command on the original / filesystem after you mounted (eg /mnt/root) and not the the / from booting up from a CD/DVD?


Jov

[Alexander Yereshenko]

2 Jov:
# find / -name "vmunix*"
/tmp/vmunix.CPQswsp
/var/adm/crash/crash.0/vmunix.gz
# ls -l `find / -name "vmunix*"`
-rwxr-xr-x 1 root sys 29024960 Apr 20 2005 /tmp/vmunix.CPQswsp
-rw-r--r-- 1 root root 11693980 Apr 20 2005 /var/adm/crash/crash.0/vmunix.gz
# ls -la /stand
total 48
drwxr-xr-x 5 root root 96 Jun 1 10:40 .
drwxr-xr-x 43 root root 8192 Jun 1 09:10 ..
-rw-rw-r-- 1 root sys 13164 Jun 1 11:01 ioconfig
drwxr-xr-x 2 root root 96 Jun 1 11:02 krs
drwxr-xr-x 2 root root 96 Jun 1 10:40 krs_lkg
drwxr-xr-x 2 root root 96 Jun 1 11:02 krs_tmp
Could you help me to understand, why kernel file is in /tmp?

[Alexander Yereshenko]

2 Jov:
As I know, our system have booted from its' hard drive. And its root directory is a real / now, not /ROOT, as in repair mode.

[Jov]

Are you able to boot the server or not?


Jov

[Alexander Yereshenko]

Yes, I'm able to boot server now, but I need to check its boot parameters first. How could I do it without any changes?

[Mridul Shrivastava]

Execute the following:

setboot
lvlnboot -v

In addition to it you can execute the previously mentioned command to check the content of AUTO file..

[Alexander Yereshenko]

It seems to me, that hardware boot settings are ok:
# setboot -v
Primary bootpath : 1/0/0/3/0.6.0
Alternate bootpath : 1/0/1/1/0/1/1.6.0

Autoboot is ON (enabled)
Autosearch is OFF (disabled)

# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t6d0 (1/0/0/3/0.6.0) -- Boot Disk
/dev/dsk/c4t6d0 (1/0/1/1/0/1/1.6.0) -- Boot Disk
No Boot Logical Volume configured

In your previous note you have written about mkboot program. Does this program have any "verbose" or "safe mode" with no-corrections option?

[Mridul Shrivastava]

lvlnboot -v output should be like following:
# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t0d0 (0/1/1/0.0.0) -- Boot Disk
/dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk
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

ur output doesn't seem to be correct.. you need to execute the following to correct the same:

# lvlnboot -r /dev/vg00/lvol3 /dev/vg00
# lvlnboot -b /dev/vg00/lvol1 /dev/vg00
# lvlnboot -s /dev/vg00/lvol2 /dev/vg00
# lvlnboot -d /dev/vg00/lvol2 /dev/vg00
# lvlnboot -R
# lvlnboot -v

As far as mkboot is concerned, the command I mentioned is used to update the AUTO file so If you want to check the contents of AUTO file execute the following:

# lifcp /dev/rdsk/:AUTO -

[Alexander Yereshenko]

Excuse me, Mr. Shrivastava, I didn't insert full output before. Here it is:
# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t6d0 (1/0/0/3/0.6.0) -- Boot Disk
/dev/dsk/c4t6d0 (1/0/1/1/0/1/1.6.0) -- Boot Disk
No Boot Logical Volume configured
Root: lvol3 on: /dev/dsk/c1t6d0
/dev/dsk/c4t6d0
Swap: lvol2 on: /dev/dsk/c1t6d0
/dev/dsk/c4t6d0
Dump: lvol2 on: /dev/dsk/c1t6d0, 0
Is this information ok?

Boot information are different:
# lifcp /dev/rdsk/c1t6d0:AUTO -
hpux -lm /stand/vmunix
# lifcp /dev/rdsk/c4t6d0:AUTO -
hpux (;0)/stand/vmunix

[Alexander Yereshenko]

I should notice, that I don't have any HW part to be mounted on /stand. I checked out our old L1000 system and 'bdf' showed me the next result:
/dev/vg00/lvol1 83733 57816 17543 77% /stand

In our new system I don't see /dev/vg00/lvol1 to be mounted on. I think that's why I cannot find vmunix on mounted partitions, despite that fact the system is online now.

[Mridul Shrivastava]

Still it says boot logical volume is not configured.. hence you need to execute

lvlnboot -b /dev/vg00/lvol1
lvlnboot -R

Have you checked the entries in /etc/fstab and is there /stand specified..

[Jov]

>> I think that's why I cannot find vmunix on mounted partitions, despite that fact the system is online now.

Maybe I've not worked on HP-UX for too long, but that makes no sense. On most modern installations /stand is part of / and without vmunix (default) then you can boot off another copy or version called anything, but by standard during a kernel change it'd be called vmunix.old (or similar).

For your system to be able to boot off its internal disk without vmunix makes no sense. There must be something that is the kernel booting the system.


Jov