Ignite issue

[Torsten.]

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

[Vijeesh CTK]

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.]

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.

[Vijeesh CTK]

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]

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. · Accepted solution]

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.

[Vijeesh CTK]

success!!!!!