1830558 Members
3368 Online
110013 Solutions
New Discussion

Ignite issue

 
SOLVED
Go to solution
Vijeesh CTK
Trusted Contributor

Ignite issue

Hi Gurus,

I am facing a problem in one of my hpux server ( 11.23 ) while taking ignite.

here the errors in ignite log file.



===================================================
WARNING: Filesystem /opt/tivoli is not mounted. It will be ignored.
WARNING: Filesystem /upg is not mounted. It will be ignored.
WARNING: Filesystem /upg/prd is not mounted. It will be ignored.
WARNING: Filesystem /upg/prd/data/com/cau is not mounted. It will be ignored.
NOTE: File '/stand/vmunix' in list of essential files not found, or too big
for pax to handle. Skipping.
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/0mn -t n -s
local -n 2009-09-01,09:49 -m t -w
/var/opt/ignite/recovery/2009-09-01,09:49/recovery.log -u -R -g
/var/opt/ignite/recovery/2009-09-01,09:49/flist -a 13551410

* Preparing to create a system archive.
WARNING: /stand/bootconf has no boot disk entries.
No LIF files on the boot disk will be archived.
Make sure that /stand/bootconf has at least one valid entry.
See /stand/bootconf and man bootconf(4) for more details.

* Archiving contents of tlrhp96 via tar image to local device /dev/rmt/0mn.
* Creation of system archive complete.
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the backup:
/var/tmp/ign_configure/make_sys_image.log

* Archive created and rewind the tape to beginning of tape.

WARNING: Could not find the /stand/system file.


======= 09/01/09 10:02:21 CDT make_tape_recovery completed with warnings
=====================================================

Waiting for your valuable replies.

Thank you

Vijeesh CTK
16 REPLIES 16
Michal Kapalka (mikap)
Honored Contributor

Re: Ignite issue

hi,

check if the files from /stand are presented.

without the vmunix and entries in bootconf, you will be not able to boot the system.

which version of Ignite do you have.

mikap
Turgay Cavdar
Honored Contributor

Re: Ignite issue

Actually they are warnings not errors.
It looks like /stand file system is not mounted, or entires deleted from there.
Torsten.
Acclaimed Contributor

Re: Ignite issue

Without the files in /stand this image is quite useless - check them!

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Vijeesh CTK
Trusted Contributor

Re: Ignite issue

Turgay and Michal,

Reboot was completed Several times after this issue is found.Please find the lvlnboot -v information also below which has some error.

XXXX:/stand $ uname -a
HP-UX XXXX B.11.23 U 9000/800 379152250 unlimited-user license


XXXX:/stand $ bdf /stand
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol1 1776056 113248 1485200 7% /stand
XXXX:/stand $ ls -al /stand
total 164752
dr-xr-xr-x 7 bin bin 1024 Sep 2 12:24 .
drwxr-xr-x 16 root root 8192 Sep 2 12:24 ..
drwxr-xr-x 5 root sys 1024 Sep 2 12:03 backup
-rw-r--r-- 1 root sys 19 Aug 13 02:48 bootconf
lrwxr-xr-x 1 root root 14 Sep 2 12:24 bootfs -> current/bootfs
drwxr-xr-x 5 root sys 1024 Aug 14 03:51 current
-rw-r--r-- 1 root sys 4688 Sep 2 14:10 ioconfig
-r--r--r-- 1 root sys 82 Aug 13 09:53 kernrel
drwxr-xr-x 2 root sys 1024 Sep 2 12:25 krs
drwxr-xr-x 5 root sys 1024 Aug 13 09:53 last_install
drwxr-xr-x 2 root root 65536 Aug 13 02:47 lost+found
lrwxr-xr-x 1 root root 7 Sep 2 12:24 nextboot -> current
-rw------- 1 root root 12 Sep 2 12:24 rootconf
lrwxr-xr-x 1 root root 15 Sep 2 12:24 system -> nextboot/system
-rw-r--r-- 1 root sys 2895 Sep 1 11:32 system.090109
-rw-r--r-- 1 root sys 2853 Aug 20 03:20 system.aug20
-r--r--r-- 1 root sys 2207 Aug 13 09:25 system.import
-rw-r--r-- 1 root sys 2853 Aug 14 01:56 system.prev
-rwxr-xr-x 3 root sys 27931680 Aug 14 03:50 vmunix
-rwxr-xr-x 1 root sys 27931680 Sep 1 12:17 vmunix.090109
-rwxr-xr-x 1 root sys 27931680 Aug 20 03:21 vmunix.aug20
XXXX:/stand $

XXXX:/stand $ lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t1d0
Root: lvol4 on: /dev/dsk/c2t1d0
Swap: lvol2 on: /dev/dsk/c2t1d0
Dump: lvol2 on: /dev/dsk/c2t1d0, 0
Dump: lvol3 on: /dev/dsk/c2t1d0, 1

lvlnboot: LIF information corrupt or not present on "/dev/dsk/c2t0d0".
Use the "mkboot" command to initialize the LIF area.
lvlnboot: LIF information corrupt or not present on "/dev/dsk/c3t2d0".
Use the "mkboot" command to initialize the LIF area.
Boot Definitions for Volume Group /dev/vg01:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c3t2d0 (0/1/1/1.2.0) -- Boot Disk
/dev/dsk/c2t0d0 (0/1/1/0.0.0)
No Boot Logical Volume configured
Root: ??? on: /dev/dsk/c3t2d0
No Swap Logical Volume configured
No Dump Logical Volume configured

XXXXX:/stand $

Torsten.
Acclaimed Contributor

Re: Ignite issue

Looks a bit corrupted.

Try

# lvlnboot -R

first.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Vijeesh CTK
Trusted Contributor

Re: Ignite issue

XXXX:/stand $ lvlnboot -R
Warning: Logical Volume number "1073741828" found on physical volume not found in "/dev/vg01".
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf


After this run lvlnboot -v , there was no diffrence.
Torsten.
Acclaimed Contributor

Re: Ignite issue

The "lvlnboot -v" output looks bad.

Let's collect some information:

# vgdisplay -v vg00
# strings /etc/lvmtab
# lvdisplay -v /dev/vg00/lvol1 (~first 20 lines)

It doesn't look like mirrored - should it be?

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Vijeesh CTK
Trusted Contributor

Re: Ignite issue

root file system is not mirrored .It has only one disk with size 76 GB

Please find the out put of commands below .

XXXX/stand $ vgdisplay -v /dev/vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 10
Open LV 10
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4384
VGDA 2
PE Size (Mbytes) 16
Total PE 4374
Alloc PE 4058
Free PE 316
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 1792
Current LE 112
Allocated PE 112
Used PV 1

LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 12000
Current LE 750
Allocated PE 750
Used PV 1

LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 12000
Current LE 750
Allocated PE 750
Used PV 1

LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 64
Allocated PE 64
Used PV 1

LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 9008
Current LE 563
Allocated PE 563
Used PV 1

LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 3072
Current LE 192
Allocated PE 192
Used PV 1

LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 3072
Current LE 192
Allocated PE 192
Used PV 1

LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 6208
Current LE 388
Allocated PE 388
Used PV 1

LV Name /dev/vg00/lvol9
LV Status available/syncd
LV Size (Mbytes) 4240
Current LE 265
Allocated PE 265
Used PV 1

LV Name /dev/vg00/lvol10
LV Status available/syncd
LV Size (Mbytes) 12512
Current LE 782
Allocated PE 782
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c2t1d0
PV Status available
Total PE 4374
Free PE 316
Autoswitch On
Proactive Polling On


XXXX:/stand $ strings /etc/lvmtab
/dev/vg00
/dev/dsk/c2t1d0
/dev/vg01
/dev/dsk/c3t2d0
/dev/dsk/c2t0d0
XXXX:/stand $ lvdisplay -v /dev/vg00/lvol1 |head -20
--- Logical volumes ---
LV Name /dev/vg00/lvol1
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 1792
Current LE 112
Allocated PE 112
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c2t1d0 112 112
Torsten.
Acclaimed Contributor

Re: Ignite issue

OK, it is not mirrored.

Let's try

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

and check again with

lvlnboot -v

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Torsten.
Acclaimed Contributor

Re: Ignite issue

One moment, please post a "bdf", your configuration looks much different from a default.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Vijeesh CTK
Trusted Contributor

Re: Ignite issue

Please find bdf output.

XXX:/stand $ bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol4 1048576 315256 727632 30% /
/dev/vg00/lvol10 12812288 5844584 6913768 46% /var
/dev/vg00/lvol9 4341760 1696808 2624312 39% /usr
/dev/vg00/lvol6 3145728 854296 2273936 27% /tmp
/dev/vg00/lvol8 6356992 3576600 2758728 56% /opt
/dev/vg01/libm01 10485760 1097462 8801584 11% /opt/IBM
/dev/vg00/lvol7 3145728 2060464 1076800 66% /home
/dev/vg01/lupg01 10485760 7353479 2936527 71% /upg
/dev/vg01/lupg02 31457280 24528435 6495832 79% /upg/prd
/dev/vg01/lupg03 4194304 1553242 2476402 39% /upg/prd/data/com/cau
/dev/vg00/lvol5 9224192 18733 8630125 0% /opt/tivoli
/dev/vg00/lvol1 1776056 113248 1485200 7% /stand


XXX/stand $ more /etc/fstab
# System /etc/fstab file. Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol4 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol3 ... swap defaults 0 0
/dev/vg00/lvol6 /tmp vxfs delaylog 0 2
/dev/vg00/lvol7 /home vxfs delaylog 0 2
/dev/vg00/lvol8 /opt vxfs delaylog 0 2
/dev/vg00/lvol9 /usr vxfs delaylog 0 2
/dev/vg00/lvol10 /var vxfs delaylog 0 2
##/dev/vg00/lvol5 /opt/tivoli vxfs delaylog 0 2
/dev/vg01/libm01 /opt/IBM vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vg01/lupg01 /upg vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vg01/lupg02 /upg/prd vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vg01/lupg03 /upg/prd/data/com/cau vxfs rw,suid,largefiles,delaylog,datainlog 0 2
Torsten.
Acclaimed Contributor

Re: Ignite issue

According to your fstab it must be

lvlnboot -r /dev/vg00/lvol4
lvlnboot -b /dev/vg00/lvol1
lvlnboot -s /dev/vg00/lvol3
lvlnboot -d /dev/vg00/lvol3

Make sure your /stand/bootconf file has

l /dev/dsk/c2t1d0

This may already solve your problem.

The problems reported by lvlnboot are there because your data files are created by "pvcreate -B ...", but this isn't a real problem.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Vijeesh CTK
Trusted Contributor

Re: Ignite issue

XXX/stand $ more /stand/bootconf
l /dev/dsk/c2t1d0

I complted the lvlnboot -r -b -s and -d .

I will try a ignite backup and check the status.
Vijeesh CTK
Trusted Contributor

Re: Ignite issue

I took new ignite backup . Though there are erros for vg01 disks , ignite backup was succesful . Only a small worry about the line "No Boot Logical Volume configured" in log .

Thank you very much for help!!!!!



======= 09/04/09 13:32:59 CDT Started /opt/ignite/bin/make_tape_recovery.
(Fri Sep 04 13:32:59 CDT 2009)
@(#)Ignite-UX Revision C.7.2.94
@(#)ignite/net_recovery (opt) $Revision: 10.882 $ $Date: 2007/02/28
17:10:48 $


* Testing for necessary pax patch.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = /dev/rmt/0mn

* Number of Archives to Save = 2

* Pax type = tar


In? dsk/vg name minor# Associated disks/mountpoints
2 v /dev/vg00 0x00 /dev/dsk/c2t1d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3
/dev/vg00/lvol4 / 2
/dev/vg00/lvol5 /opt/tivoli 2
/dev/vg00/lvol6 /tmp 2
/dev/vg00/lvol7 /home 2
/dev/vg00/lvol8 /opt 2
/dev/vg00/lvol9 /usr 2
/dev/vg00/lvol10 /var 2
0 v /dev/vg01 0x01 /dev/dsk/c3t2d0 /dev/dsk/c2t0d0
/dev/vg01/libm01 /opt/IBM 0
/dev/vg01/lupg01 /upg 0
/dev/vg01/lupg02 /upg/prd 0
/dev/vg01/lupg03 /upg/prd/data/com/cau 0

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2009-09-04,13:32/system_cfg vg00
lvlnboot: LIF information corrupt or not present on "/dev/dsk/c2t0d0".
Use the "mkboot" command to initialize the LIF area.
lvlnboot: LIF information corrupt or not present on "/dev/dsk/c3t2d0".
Use the "mkboot" command to initialize the LIF area.
No Boot Logical Volume configured
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg00.mapfile /dev/vg00
vgexport: Volume group "/dev/vg00" is still active.

* Backing Up Volume Group /dev/vg01
* /usr/sbin/vgcfgbackup /dev/vg01
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf
* Creating Map Files for Volume Group /dev/vg01
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg01.mapfile /dev/vg01
vgexport: Volume group "/dev/vg01" is still active.

* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

* /opt/ignite/lbin/make_arch_config -c
/var/opt/ignite/recovery/2009-09-04,13:32/archive_cfg -g
/var/opt/ignite/recovery/2009-09-04,13:32/flist -n 2009-09-04,13:32 -r
pa -b 64 -d Recovery\ Archive -t 1 -i 2 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Tape Archive
* Checking configuration file for Syntax
* Writing boot LIF to tape
* Complete writing boot LIF onto tape.
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/0mn -t n -s
local -n 2009-09-04,13:32 -m t -w
/var/opt/ignite/recovery/2009-09-04,13:32/recovery.log -u -R -g
/var/opt/ignite/recovery/2009-09-04,13:32/flist -a 13735860

* Preparing to create a system archive.

* Archiving contents of tlrhp96 via tar image to local device /dev/rmt/0mn.
* Creation of system archive complete.

* Archive created and rewind the tape to beginning of tape.



======= 09/04/09 13:47:23 CDT make_tape_recovery completed successfully!

Torsten.
Acclaimed Contributor
Solution

Re: Ignite issue

lvlnboot: LIF information corrupt or not present on "/dev/dsk/c2t0d0".
Use the "mkboot" command to initialize the LIF area.
lvlnboot: LIF information corrupt or not present on "/dev/dsk/c3t2d0".
Use the "mkboot" command to initialize the LIF area.




Both disks are data disks (part of vg01), but created with a boot area. This area is empty, hence the message.

Even with a filled area these disks won't boot, because they are data disks. No need to worry.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Vijeesh CTK
Trusted Contributor

Re: Ignite issue

success!!!!!